youngmon/atlassian-qna huggingface dataset:
Git clone failed to fetch repository from Bitbucket.
Asked by Pavankumar:

verbose log shows connection established:

GIT_SSH_COMMAND="ssh -vvv" git clone --depth=1 ssh://git@bitbucket.org/gop/tests.git  
Cloning into 'tests'...  
OpenSSH_9.2p1 Debian-2+deb12u1, OpenSSL 3.0.11 19 Sep 2023  
debug1: Reading configuration data /home/lava/.ssh/config  
debug1: Reading configuration data /etc/ssh/ssh_config  
debug1: /etc/ssh/ssh_config line 21: Applying options for \*  
debug3: expanded UserKnownHostsFile '\~/.ssh/known_hosts' -\> '/home/lava/.ssh/known_hosts'  
debug3: expanded UserKnownHostsFile '\~/.ssh/known_hosts2' -\> '/home/lava/.ssh/known_hosts2'  
debug2: resolving "bitbucket.org" port 22  
debug3: resolve_host: lookup bitbucket.org:22  
debug3: ssh_connect_direct: entering  
debug1: Connecting to bitbucket.org \[10.122.xx.xxx\] port 22.  
debug3: set_sock_tos: set socket 3 IP_TOS 0x10  
debug1: Connection established.  
debug1: identity file /home/lava/.ssh/id_rsa type 0  
debug1: identity file /home/lava/.ssh/id_rsa-cert type -1  
debug1: identity file /home/lava/.ssh/id_ecdsa type -1  
debug1: identity file /home/lava/.ssh/id_ecdsa-cert type -1  
debug1: identity file /home/lava/.ssh/id_ecdsa_sk type -1  
debug1: identity file /home/lava/.ssh/id_ecdsa_sk-cert type -1  
debug1: identity file /home/lava/.ssh/id_ed25519 type -1  
debug1: identity file /home/lava/.ssh/id_ed25519-cert type -1  
debug1: identity file /home/lava/.ssh/id_ed25519_sk type -1  
debug1: identity file /home/lava/.ssh/id_ed25519_sk-cert type -1  
debug1: identity file /home/lava/.ssh/id_xmss type -1  
debug1: identity file /home/lava/.ssh/id_xmss-cert type -1  
debug1: identity file /home/lava/.ssh/id_dsa type -1  
debug1: identity file /home/lava/.ssh/id_dsa-cert type -1  
debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u1

moves to

kex_exchange_identification: read: Connection timed out

banner exchange: Connection to 10.122.xx.xxx port 22: Connection timed out

fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

Each time it tries to fetch code from different IP address.

Any suggestion that i can en-route from the same IP address


Answers:
author: Pavankumar
body: Try adding an IP Address with domain name in /etc/hosts file


Tags: bitbucket-data-center

data-center

git

ssh
Git version corresponding to Bitbucket 8.9.10
Asked by Owen Chen:

<https://confluence.atlassian.com/bitbucketserver089/supported-platforms-1236436738.html>

I checked the support list of bitbucket 8.9,

But I still want to confirm whether Bitbucket 8.9.10 can support Git 2.31.x - 2.40.x or only 2.41.x - 2.42.x?


Answers:
author: Julius Davies _bit-booster_com_
body: Bitbucket 8.0 supports Git 2.31.0 and Atlassian is good about maintaining reverse-compatibility, and so you can expect all version of Bitbucket 8.x will support at least Git 2.31.0. And then as each new version of Bitbucket is released you can expect that it supports incrementally newer versions of Git.

Bitbucket 8.9.10 supports Git 2.31.x to 2.42.x.

Bitbucket 8.9.11 supports Git 2.31.x to 2.43.x.

comments: author: Owen Chen
body: Thank you for your reply.


Tags: bitbucket-data-center

server
Why are some checkboxes brownish-orange when I go to Browse Changelists?
Asked by Steve Mills:

![Orange checkbox](https://dl.dropboxusercontent.com/u/10058078/Crucible-orange-checkbox.png)


Answers:
author: Piotr Swiecicki
body: Hi Steve,

Every changeset in Crucible may contain a number of amended files. If you add all those changes to the review the checkbox is ticked, if you don't have any of those changes the checkbox is clear, but if you have only some of those changes on your reviews the checkbox will be highlighted as you noticed.

This typically happens when you add some file revisions manually to a review, or add full changeset but then decide to delete some of the file revisions from review.

Hope that helps,

comments: author: Steve Mills
body: Hmm, either I don't understand, or there's a bug, because all I did was create a new review and use Browse Changelists to select the 2 changelists I wanted to include. The 2nd one down was orange as soon as I clicked it.

This is kind of a weird way to show partial or mixed state. Normally it would show a dash through the center instead of a checkmark.
changing svn url in fisheye
Asked by BP:

I am moving my Subversion repo to a new server. Is it the case that I can just change the SVN URL in Fisheye "SCM Details" page? Will all the links, reviews, etc. continue to work?


Answers:
author: Piotr Swiecicki
body: Hi Bill,

Yes, just change the SVN URL, restart the repository when prompted so the change is effective and that's it. Your links and reviews would continue to work as expected.

Kind regards,
Fisheye exclude from filter
Asked by FrankV:

Hello, Is it possible to exclude specific text from filtered commits. For ex, I want to look at all my SVN changes in fisheye, but those WITHOUT the text "automated build". i.e. this would allow me NOT to see some commits that are not done by real people.

Thanks.


Answers:
author: Piotr Swiecicki
body: Hi FrankV,

You can use EyeQL to find this. Just to explain on example, go to [](https://fisheye2.atlassian.com/search/mb-unit/)<https://fisheye2.atlassian.com/search/mb-unit/>page and run the search with this query

```
select revisions   where comment matches 'tweaks'  group by csid return count(revisions), csid, author, date, comment
```

Notice you get 46 results, all the commits from mb-unit repository with 'tweaks' phrase. Now repeat the search with this query:

```
select revisions   where comment matches 'tweaks'   and not comment matches 'minor'  group by csid return count(revisions), csid, author, date, comment
```

to see only 20 changesets returned - all the changesets with phrase 'minor' in the commit message were excluded.

Hope that helps,

comments: author: FrankV
body: Basically this did work, but it would be nicer if it could be done directly from the page as the returned format is quite different.
Intergrate Crucible with Bugzilla
Asked by sathya narayanan:

Hi,

I would like to know whether we can intergrate crucible with bugzilla? If yes can you provide the details.

Thanks

Sathya


Answers:
author: Piotr Swiecicki
body: Hi Sathya,

Obviously for the best integration with the issue tracker, I can recommend Atlassian JIRA. You would be able to update issue workflow directly from Crucible, but also see status of your review directly on the issue page in Jira.

But it is certainly possible to integrate FishEye with Bugzilla so bug ids mentioned in comments and commit messages would be linked to your Bugzilla issues. You can find more information in [](https://confluence.atlassian.com/display/FISHEYE/Linkers#Linkers-Bugzillaexamples)<https://confluence.atlassian.com/display/FISHEYE/Linkers#Linkers-Bugzillaexamples>

Hope that helps,
Crucible Code Review on Shelved Code (perforce)
Asked by Rahul Aich [Nagra]:

Hi

We have Crucible (+Fisheye) 3.2, indexing our perforce repositories.

We would like to perform code reviews on Shelved Code on perforce.

I am not sure if this feature is provided out of box by crucible (+Fisheye) 3.2.

If not, is there any plugin? any alternatives?

Rahul


Answers:
author: Tom Davies
body: We don't currently support this. There is a feature request for this here: [CRUC-3378Consider use of p4 shelve / p4 unshelve for pre commit reviews](https://jira.atlassian.com/browse/CRUC-3378). Please vote for the request and watch it to be notified of progress. We do not currently have any time frame for implementing this feature.

As an alternative you can generate a diff of the changes and create a patch review: <https://confluence.atlassian.com/display/CRUCIBLE/Creating+patch+files+for+pre-commit+reviews>

comments: author: Rahul Aich [Nagra]
body: thanks Tom that helps.


Tags: fisheye-crucible-administration

perforce
I'm trying to use the CLI tool, but I'm getting an "Error encoding the request.."
Asked by CodeForCoffee:

I'm trying to use the CLI tool, but I'm getting an "Error encoding the request (tried UTF-8), please specify an --encoding parameter" I've tried this with utf_8, ascii, utf_32, utf8. All with the same result.

./crucible.py REVIEW-1 --encoding utf_8

Note I've tried leaving off the --encoding.


Answers:
author: Paul Collins
body: I just ran into this after a year using the tool successfully. Manually uploading the diff gave a clue: it would not anchor, and in the revision that Crucible said conflicted there was a funny character near the previous (and the new) changes:

There was an apostrophe encoded in Western MacOS Roman. I changed it to a plain ASCII apostrophe in my local source, made a new diff, and that uploaded and anchored ok

This did not fix the python error, but now I know what to look for and a workaround. Possibly fiddling around with encoding in the source file would have helped.


author: Tom Davies
body: Can you please try again without the --encoding parameter, but with a --debug parameter and tell us what the output of the command is?

Thanks,

Tom
How to make changelist associate with head instead of branch in Crucible (with FishEye)
Asked by Marnee DeRider:

We are using Crucible 3 and FishEye with Perforce.

We have a Crucible repository that references our project in Perforce (along with other projects as well). Example path: //software/source/project/java. We have many old branches in Perforce that include that path in the Perforce View. When a new change list is recognized in Crucible, it associates it to a branch.

I don't know what the Crucible search mechanism is, but it seems to be consistent. We have a branch called branch-2-0 (not its real name) and all the changelists I looked at were shown in Crucible under that branch instead of under "head". Realizing this, I removed the //software/source/project/java view from the branch-2-0. I could do this because branch-2-0 was obsolete. After that, Crucible then started associating the changelists with a branch-3-0 which also had //software/source/project/java in the view. (Just fyi, the activity for that branch shows only changelists created since I modified branch-2-0, as I would expect.)

Updating all branches that reference //software/source/project/java in the view is not a feasible way to fix this, however. Even if I knew how to search for them, I know at least one is not obsolete. In addition, new ones could be created at any time.

Is there a way to configure Crucible to simply use "head" and/or ignore all branches? I'm not sure if this is causing any functional problem. (I'm working through a variety of issues and trying to clean everything up to see if it helps, but have not identified an actual issue with this happening.) However, I do know that this behavior is spooking people, and that alone makes it worth trying to resolve this. Multiple people have contacted me while our group is ramping up on learning to use Crucible. They think they've done something wrong in creating their review (they haven't) and/or are fearful that the file "diff" won't be accurate when they see some strange branch they've never heard of. As for the latter issue (i.e. inaccurate "diff"), I am not so sure that this is a baseless fear. I'm a bit spooked myself.


Answers:
author: Felipe Kraemer
body: Hi Marnee,

You can configure FishEye to ignore specific paths while indexing by adding [Exclude](https://confluence.atlassian.com/display/FISHEYE/Include+Exclude+paths#IncludeExcludepaths-AddinganExclude) rules. Can you try this?

NOTE: the repository will need to be re-indexed from scratch after specifying Exclude rules. So as not to play around with a production repository, a suggestion is to create a new temp repository using the same configuration of the one you're talking about here and apply those Exclude rules to see if they help. Then, if yes, apply the same changes in the production repository and reindex it.

If this answer was helpful, please allow me to ask you to mark my answer as accepted in order to have it in the top of the thread, also helping other customers.

Thanks in advance!

Kind regards,  
Felipe Kraemer


Tags: branch

perforce

repository
Why does setting Start Revision have no effect in Crucible?
Asked by Marnee DeRider:

I am using Crucible 3 with Perforce. After I created a new repository in Crucible, and while it was still doing the initial indexing, I updated the repository to set a "Start Revision" on the "SCM Details". (The "InitialImport" checkbox has always been unchecked.) Then I clicked Stop on the Summary and Start. Yet, it is still indexing from apparently the first revision. (In any case, it started with revisions long before the Start Revision, from 1998 in fact. I can't say with 100% certainty that it's starting from the very first changelist.)

I would expect it to start indexing on the changelist specified in the Start Revision. Am I misunderstanding what the Start Revision is for?


Answers:
author: gustavo_refosco
body: Hi Marnee,

After setting a start revision (or performing any changes that affect the content of the indexes of the repository) a re-index is necessary, so only Stopping and Starting the repository again won't apply the change.

In order to re-index the repository you can go to **Administration \> Repositories \> click in repo's name \> Maintenance** and click in the **Start** button of the **Re-index** option under **Repository Source Index** .  

comments: author: Marnee DeRider
body: I think I remember that it prompted me for re-indexing and I confirmed, but I can't be sure. I will say that even though I saw in the status that it was still referencing changlists prior to the Start Revision, other tasks that I've done since then seem to indicate that it is now honoring the Start Revision. I made other changes and perhaps at one point, I did request it to reindex. I can't be sure at this point, but I am guessing you are correct in that the issue was I hadn't reindexed after setting the Start Revision. Even though I am not sure in my case, I will leave the question up since I think your response can be helpful to others. Thank you!


Tags: index

revision
REST API for commit hook fails with 401: not authorized
Asked by Brady Vidovic:

I followed [this guide](https://confluence.atlassian.com/display/FISHEYE/Configuring+commit+hooks "this guide") to create a curl command to trigger a scan of my respository:

I have verified multiple times that my API key is correct. I've also noticed that I get the same response when the repository name is changed from "sso" to something that doesn't exist.

I have a single repository named "sso" in my fisheye server.

```
curl -X POST -H "X-Api-Key: [my key was here]"  http://fisheye1/rest-service-fecru/admin/repositories-v1/sso/scan{"code":"401","message":"You must be an administrator to access this resource.","stacktrace":null}
```


Answers:
author: Brady Vidovic
body: I ended up adding another header

```
-H "Content-Type: application/json"
```

ANd it started working. I think the documentation needs to be updated because it doesn't specify this.

comments: author: lpater
body: Hi Brady,

I've updated the docs to mention needing to add the content type.

Thanks,

?ukasz


Tags: fisheye-crucible-administration
Any way to make Show All Whitespace a default option for files in Crucible?
Asked by Adam Kiczula:

The title says it all, I know you can select "Show All Whitespace" in the view menu for each file, but it would be nice to set this as a preference for my user account so I don't have to change it every time I view a new file. Our team uses Python, so all whitespace changes are significant, it would be nice to make this more convenient to use.


Answers:
author: gustavo_refosco
body: Hi Adam,

Unfortunately Crucible doesn't have such option at the moment, but I found a feature request for this option to be available for each user in its Profile settings. You can see it at [](https://jira.atlassian.com/browse/CRUC-6758)<https://jira.atlassian.com/browse/CRUC-6758>.  

I would suggest adding any comments to the issue above as well as [voting](https://confluence.atlassian.com/display/JIRA/Watching+and+Voting+on+an+Issue) on the issue to create it's popularity and likelihood of being implemented in a future release.  

For more information on how Atlassian implements new features and improvements please see the following document:  

[](http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy)<http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy>


Tags: whitespace
Connecting Fisheye to a remote Repository Location
Asked by FredericB:

Hi,

I am trying to connect fisheye to a Mercurial remote repository, and get the error :

Unable to pull from remote repository: \<DIRECTORY\> - \[abort: repository \<DIRECTORY\> not found!\]

From the same PC, I can clone the remote repository (using tortoise with the same options) and once on a local directory, I can connect it with fisheye.

I have the correct right on the remote directory, the same Mercurial revision.

Any idea ?

thanks,


Answers:
author: Nick
body: Some ideas to consider/check and in no particular order:

* does the fisheye runuser have correct access to clone/read from the repo?
* have you tried running the same command exactly that fisheye is trying to run when cloning the repo
* what have you put in place of the URL field in the FishEye configuration screen? Does this exist?
* for the remote repo - is it protected by password or ssh ? If so, are all your credentials in place ? ie. you've generated a key/pair in fisheye and uploaded the public key to your mercurial server ?
* what does the Test Connection reveal in FishEye

comments: author: FredericB
body: Updated to the latest version of Fisheye.

Issue came from the service Wrapper not using the configured user.

It now works.

thanks,


author: FredericB
body: Hi,

- The run user has the read right on the directory. Is tried with the service user set to my user also, without any success.  
- The same command "C:\\Mercurial\\hg.exe --config ui.verbose=false clone --noupdate -r 0 \\\\fav19win\\SRS\\srs D:\\FISHEYE_INST\\var\\tmp\\hg_test_clone_1402469900574" run from the Windows console create the cloned version  
- The URL field is set to \\\\fav19win\\SRS\\srs and this exists.  
- There is no SSH authentification, the remote directory is read only.  
- the test connection returns :

Error testing connection.  
Non-zero exit code: 255  
at com.atlassian.utils.process.PluggableProcessHandler.complete(PluggableProcessHandler.java:69)  
at com.atlassian.utils.process.ExternalProcessImpl.wrapUpProcess(ExternalProcessImpl.java:509)  
at com.atlassian.utils.process.ExternalProcessImpl.finish(ExternalProcessImpl.java:423)  
at com.atlassian.utils.process.ExternalProcessImpl.execute(ExternalProcessImpl.java:378)  
at com.atlassian.fisheye.dvcs.DvcsScmConfig.executeCommand(DvcsScmConfig.java:187)

Connection failed.

<br />


Tags: fisheye-crucible-administration
Upgrading from crucible 1.6.6 to version 3.4
Asked by nishant kakkarayil:

I am trying to upgrade from 1.6.6 to version 3.4. In 1.6.6 we did not use a database fo crucible. The data was stored in a local directory. The instructions i see to upgrade to 3.4 make a reference to backing up the data from the admin panel. I do not see this option in 1.6.6. i only see the option to back up configuration files.

What is the way to upgrade from 1.6.6? How do i get the data files into a db during the installation of 3.4?


Answers:
author: Felipe Kraemer
body: Hi Nishant,

If you use the FISHEYE_INST environment variable in FishEye/Crucible 1.6.6, your data is stored inside the directory referenced by this variable.

It usually would be just a matter of shutting down the old instance and starting up the new instance. Backing up FISHEYE_INST before starting the new instance is recommended.

If the upgrade fails, please consider trying to do intermediate upgrades, like this: 1.6.6 \> 2.0 \> 2.5 \> 2.7 \> 3.4. Just remember to create a new backup from FISHEYE_INST before upgrading to the next version.

Needless to say, but just in case, it's strongly recommended to try this in a test environment first.

Kind regards,  
Felipe Kraemer  
Atlassian Support
Crucible: My users are whining -- I need answers to "alternate diff tools"
Asked by Brent Webster:

I've been getting my users to play with Crucible/Fisheye so we can coming up with a common inspection process. They have questions -- I need answers:

1/ Can we use another diff tool? I understand, that review comments could only be made at the file level and not at the individual changes but my users come back with  
- too much wasted space with current browser based diff implementation  
- I want to stay within Eclipse  
- I like using meld, vimdiff, etc  
- This is a static view of the code but more code browser functionality available in Eclipse or even cscope, is needed. i.e. What type is this variable, where is it defined or where else is it being used, etc.


Answers:
author: Timothy
body: General answer is no ([](https://jira.atlassian.com/browse/CRUC-6053)<https://jira.atlassian.com/browse/CRUC-6053>).

comments: author: Brent Webster
body: Disappointed :-(


Tags: fisheye-crucible-administration
Crucible: My users are whining -- I need answers to "a failed review"
Asked by Brent Webster:

I've been getting my users to play with Crucible/Fisheye so we can coming up with a common inspection process. They have questions -- I need answers:

2/ A designer will setup the review but his manager and those involved in the review want to know if the comments made in the review have been addressed?  
- what constitutes a failed review and how would it show up in Crucible?  
- simply knowing that your comment has been read, does not constitute that it has been resolved.  
- I know I can "flag" a comment as a Defect and I can probably create another Jira issue from that flagged Defect but I don't want to. I already have a Jira defect issue opened for this review/code submission so I don't want to open more issues when the code hasn't been formally submitted yet.  
- how do others handle this situation?


Answers:
author: Felipe Kraemer
body: Hi Brent,

As can be seen [here](https://confluence.atlassian.com/display/CRUCIBLE/state), a review cannot be flagged as "*failed"* because there is no such review state in the [Crucible workflow](https://confluence.atlassian.com/display/CRUCIBLE/The+Crucible+workflow).

However, if a comment on a review is flagged as "Defect" and a JIRA issue has been created based on it, it can be understood that problems have been detected in the source code being reviewed, hence the review can be considered as "failed".

The outcome of the new JIRA issue will be a new commit with the necessary changes to fix the problem and close the JIRA issue, and a new review should be created for this new changeset committed, and this review will follow the same workflow as the previous one.

Kind regards,  
Felipe Kraemer


Tags: fisheye-crucible-administration