No files in connect stash/fisheye Crucible

No commiters, no files in browser repo:

-Atlassian Stash v2.8.2

-Atlassian FishEye analysis with Crucible code review. (Version:3.1.5 Build:20131030082910 2013-10-30)


5 answers

0 vote
Jeff Thomas Atlassian Team Nov 17, 2013

Hi Rodrigo,

In your screenshot, the Updates column has Queued listed for the Pre repository. It looks like the Fisheye has not pulled the lastest changes on the repository. Have you setup polling or a commit hook to trigger Fisheye to update the repository?

Hi Jeff,

To bring the repository from stash, you should bring the commits that already exist?, It should bring the files that already exist? ... Well, something is wrong because I do not bring anything ...

first to bring what has been done ..... Do you have any idea? ... should be simple ...

Thanks for responding!

Jeff Thomas Atlassian Team Nov 17, 2013

With the updates column saying Queued for the Pre repository, it seems to indicate that Fisheye has not processed the repository yet. If you click on Pre and look at the log, what is listed? What are the update/polling settings for Pre?

Jeff:

and log:

In the log i see fetch and in the repository i see branches, but not see activity, committers, etc.

Jeff Thomas Atlassian Team Nov 17, 2013

In the repository administration, if you open the pre repository and select Maintenance on the left, what is the Last Index Update?

You might also try starting the Re-clone and Re-index, which would delete the cache and repository and try to index from scratch.

hummmmm, yep ... i starting re-clone, re-index, etc ..... and nothing ...

T

the two applications are on the same machine and have access to internet via proxy .... in this setting in stash via setenv.sh:

JVM_SUPPORT_RECOMMENDED_ARGS="-Datlassian.plugins.enable.wait=300 -Dhttp.proxyHost=10.186.101.10 -Dhttp.proxyPort=80 -Dhttps.proxyHost=10.186.101.10 -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts=localhost\|10.232.128.97 -Dhttp.auth.ntlm.domain=TCHILE -Dhttp.proxyUser=eve_rraley -Dhttp.proxyPassword=Cojones2013 -Dhttps.proxyUser=eve_rraley -Dhttps.proxyPassword=Cojones2013"

in fisheeye/crucuble via .profile file:
export FISHEYE_OPTS="-Datlassian.plugins.enable.wait=300 -Dhttp.proxyHost=10.186.101.10 -Dhttp.proxyPort=80 -Dhttps.proxyHost=10.186.101.10 -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts=localhost\|10.232.128.97 -Dhttp.auth.ntlm.domain=TCHILE -Dhttp.proxyUser=eve_rraley -Dhttp.proxyPassword=Cojones2013 -Dhttps.proxyUser=eve_rraley -Dhttps.proxyPassword=Cojones2013"

this is so?

Jeff Thomas Atlassian Team Nov 17, 2013

I'm not sure what's going on. Hopefully someone else will see this question and provide an answer. I'd also suggest contacting Atlassian Support - https://support.atlassian.com/

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,758 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you