youngmon/atlassian-qna huggingface dataset:
Your account now has more than 30 repositories created today. Don't worry! You can still create more
Asked by icon-technology:

I was importing our modules to repositories for our all odoo module version wise. when the number of my repositories reached 30 I got a message: "Your account now has more than 30 repositories created today. Don't worry! You can still create more"

My bitbucket workspace url: \<removed\>


Answers:
author: Nikola Perisic
body: Hello [@icon-technology](/t5/user/viewprofilepage/user-id/2003628)

You can find the reference to this issue on this page: <https://community.atlassian.com/t5/Bitbucket-questions/Your-account-now-has-more-than-30-repositories-created-today-Don/qaq-p/2138388>

I will tag Atlassian team for a higher visibility of this issue.


author: Theodora Boudale
body: Hi [@icon-technology](/t5/user/viewprofilepage/user-id/2003628),

For workspaces on the Free plan we have a limit of 30 repositories per day to prevent abuse (Bitbucket Cloud has been often targeted by spammers).

I'm afraid that we can no longer override this limit and I have reached out to my team to adjust this error message we show.

You should be able to create more repos the next day (up to a maximum of 30 per day).

Just a heads up, I removed the workspace URL from your post to protect your privacy.

Kind regards,  
Theodora

comments: author: icon-technology
body: Ok, Got it, Thank you


Tags: bitbucket-cloud

cloud
Adding an option in the clone URL displayed in the clone pop-up window
Asked by jang shin:

Can I change the command to "git clone --recurse-submodules git@bitbucket.org:username/fpga.git" in the pop-up window?

![clone-popup.png](https://community.atlassian.com/t5/image/serverpage/image-id/305333iF3892064366CF308/image-size/large?v=v2&px=999 "clone-popup.png")


Answers:
author: Ben
body: Hi Jang,

Unfortunately - this is not yet possible. I have raised a [feature request](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html) with our developers on your behalf, however. Please feel free to **Watch** this for future updates and **Vote**for it to imrpvoe its visibility with regard to customer demand:

* <https://jira.atlassian.com/browse/BCLOUD-23090>

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-cloud

cloud
Pipelines - Pull Request triggers - merges
Asked by Andy Rouse:

The Documentation states that the destination branch is merged into the working branch before it begins:

<https://support.atlassian.com/bitbucket-cloud/docs/pipeline-start-conditions/>

This is very helpful, but I'd like to check the behaviour in a multi-step pipeline.

When the documentation says "before it runs" - Does it mean "before it runs, for the first step" or "before it runs each step"?

The reason I ask is that I have a pipeline where the second step is manual and may not happen for a while. In that time, there may be additional commits to the destination branch and I've seen some odd discrepancies in diffs that happen in the different steps. I'd like to understand whether this merge might have any impact or not.

I'm attempting to run some automated validations and deployments into Salesforce using sfdx and a very useful plugin called [sfdx-git-delta](https://www.npmjs.com/package/sfdx-git-delta). It's been very useful, but due to some differences in behaviour between the steps, I'm cautious.


Answers:
author: Theodora Boudale
body: Hi Andy,

I see that you created a support ticket for this issue, but I wanted to leave a reply here for any other users who may come across your question:

For every step of your build, a Docker container starts (the build container) using the image you have specified in your bitbucket-pipelines.yml file. The repo is cloned in this container, the merge occurs (for pull-requests pipelines) and then the commands of the step's script get executed. When the step is finished, the container gets destroyed.

This process occurs for every step, so it will also occur for a manual step that you trigger later. If there are any additional commits in the destination branch by the time you trigger the manual step, they will not be taken into account. The pipeline will merge the same commit of the destination branch that it used in the first step of the same pipeline. You can see that if you expand the **Build Setup** part of the build log for each step.

Kind regards,  
Theodora


Tags: bitbucket-cloud

bitbucket-pipelines

cloud

pull-request
Is there any plugin or tool which does the code review by AI like code rabbit does for github
Asked by vaibhav.gupta@gameskraft.com:

Is there any plugin or tool which does the code review by AI like code rabbit does for github. And if it is not then by when it is coming. Don't suggest Code review assistant by Mibex Software.


Answers:
author: Mikael Sandberg
body: Hi [vaibhav.gupta@gameskraft.com](/t5/user/viewprofilepage/user-id/5425654),

Welcome to Atlassian Community!

Atlassian Intelligence should be coming to Bitbucket any day now with AI-assisted code review, the [public roadmap](https://www.atlassian.com/roadmap/cloud?selectedProduct=bitbucket&search=code%20review) has is listed to be available Q4 2023.

comments: author: Reese
body: I think, he is referring to datacenter/server, not "Cloud"........


author: vaibhav.gupta@gameskraft.com
body: Don't suggest Code review assistant by Mibex Software.


Tags: bitbucket-server

server
Mark a defect as handled/fixed
Asked by Richard Skoog:

Hi,

I'm missing functionality in Crucible to set a defect as handled (done by the author) and fixed (done by the reviewer).

The author should be able to set that the defect is handled before uploading updated files. This is partially described in this ticket:

[](https://jira.atlassian.com/browse/CRUC-6160)<https://jira.atlassian.com/browse/CRUC-6160>

What I'm missing is that the reviewer after looking at the updated files should mark that the defect is fixed. Otherwise the author/moderator doesn't know that the reviewer has checked all updates.

It should also be nice to have all the defects presented in a list in the "Details" view. The defect list should also include the "Defect-fixed" status and the name of the person who wrote the defect.

Regards Richard


Answers:
author: Thomas Waldecker
body: This is now possible in Crucible 4.2:

<https://confluence.atlassian.com/crucible/crucible-4-2-release-notes-847744868.html>


author: Richard Skoog
body: Hi,

I wrote this feature request: [](https://jira.atlassian.com/i#browse/CRUC-6812)<https://jira.atlassian.com/i#browse/CRUC-6812> to highlight that this feature is wanted. It was duplicated by: [](https://jira.atlassian.com/i#browse/CRUC-6160)<https://jira.atlassian.com/i#browse/CRUC-6160>, so my suggestion is that you either write another feature request and link it towards CRUC-6160, or write a comment in CRUC-6160.

Regards Richard


author: abby shen
body: Hi Richard,

I'm looking for similar feature as well.

1. Author/Reviewer can mark the defect to be fixed.

2. Reviewer can filter the defect based on it's status so that only review the fixed defect.

3. One can look at the list of defects with link (click link to jump to the defect) and status, change time.
Getting ssl_error_no_cypher_overlap after enabling SSL on fisheye
Asked by Isaac Montes:

Anyone knows how to fix this, I'm getting this error on my web browser ssl_error_no_cypher_overlap  
when I try to access fisheye over ssl followed the instructions <https://confluence.atlassian.com/display/FISHEYE/FishEye+SSL+configuration#FishEyeSSLconfiguration-configuringssl>Any ideas


Answers:
author: gustavo_refosco
body: Hi Isaac,

<br />

I've found a similar case where one of our customers were facing the same error.

Can you please check, as per [](https://confluence.atlassian.com/display/FISHKB/Errors+getting+SSL+up+and+running)<https://confluence.atlassian.com/display/FISHKB/Errors+getting+SSL+up+and+running>if you can find a similar error in your logs, and also give a try to its resolution regarding the certificate alias and key/keystore password?
Issues creating repository with SSH
Asked by nishant kakkarayil:

Hello, i am trying to connect Crucible 3.4.0 version to my SVN repository using svn+ssh. I can add a new repository and test the connection and it works fine. Also i can browse the repo in fisheye. When I first add the repository Crucible scans the repo fine and is able to scan all the changesets which i am also able to view. However i get an Authorization exception when Crucible attempts to index the changesets. Which is kind of strange. Any ideas on why this is happening. i had the same issues with 3.3 versions as well.

com.cenqua.fisheye.rep.RepositoryClientException: org.apache.subversion.javahl.ClientException: svn: E170001: Authorization failed org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Authorization failed

When i look up the scan status, it shows that the scanning of the changesets is 100% complete but indexing changesets is at 0% and stopped because of this.

Also jsvn worked connecting to my repo.


Answers:
author: nishant kakkarayil
body: thanks got this to work. When i ran the jsvn command i opted to not store the password and that seems to have resolved the issue


author: Nick
body: Can you run with DEBUG logging enabled and then try and run the same svn commands that are failing as the same user that fisheye is connecting with, from the svn command line.

Indeed if the Scan completes with no Auth errors, then so should the Index.

comments: author: nishant kakkarayil
body: I am trying to migrate from 1.6.3 to 3.4.0. I know this is big leap. what is the best way to go about this. is there an intermediate version i need to upgrade to before i can move to 3.4.0 ?


author: Nick
body: Theoretically the upgrade should just work from 1.6.x to 3.4.3 . (NB: 3.4.3 is the latest version released).

Be sure to take a **full** backup before commencing, so you can roll back at anytime.

You could even do a test upgrade from the backup.zip on a non-production server to see that everything works fine for you.

Depending on the number of repositories you have and the repository types and the size of the repsitories you have, some upgrade tasks may take a little while to run. The instance should still be usable while they do however.

Please report back how you go.

Cheers,

Nick Pellow
Preventing review comments from modifying completion percentage?
Asked by Kattie Grady:

I'm almost possitive I know the answer to this, but it's worth asking in case we're wrong.

<br />

Right now new review comments modify the % completion for there review audience if they're already finished. Is there away to exclude comments from doing this?


Answers:
author: Foong
body: Hi Kattie,

That's weird. Adding new comment should not affect the progress tracking.

As you can see in this documentation [Using Progress Tracking](https://confluence.atlassian.com/display/CRUCIBLE/Using+Progress+Tracking), the percentage only track the files that the user have viewed not the comment.

Are you able to reproduce the problem again?

comments: author: Kattie Grady
body: Yes, we are. Reviewer progress tracking is being decrimented when a new defect, comment, or response to a defect is added to the review. Which we'd expect on new defects, but not on the other two options.


Tags: fisheye-crucible-administration
Restrict repository visibilty (fisheye)
Asked by Rahul Aich [Nagra]:

Hi

I am on fisheye 3.2.2

When someone creates a crucible review, they choose the repositories. Now since in our instance we have hundreds of repositories indexed, it becomes quite difficult identifying the right repository

So, my question is - is there a way we can restrict the visibility of repositories to users, as a user i am only interested in the 3-5 repositories i am working on , and i should be presented with only 3-5 repostories to choose from not the entire list of 100.

How can i achieve this?

rAHUL


Answers:
author: Felipe Kraemer
body: Hello Rahul,

Yes, it is possible to restrict the visibilities of repositories to groups of users. So, these are the steps:

1. Create [groups](https://confluence.atlassian.com/display/FISHEYE/Creating+a+group) of users
2. [Add](https://confluence.atlassian.com/display/FISHEYE/Adding+a+user+to+a+group) users to these groups
3. Edit the repository [permissions](https://confluence.atlassian.com/display/FISHEYE/Permissions) and make sure that the correct groups are chosen.

Then, while creating reviews, only the repositories that the user creating the review is allowed to see will be listed.

Kind regards,  
Felipe Kraemer  
Atlassian Support

comments: author: Rahul Aich [Nagra]
body: Thanks Felipe..that helps


Tags: fisheye-crucible-administration
When the too many open files error occurred in fisheye?
Asked by Atlassian Support in ARGP:

Hi,

The 'too many open files error' are occurred today in my server.

I wonder about when the fisheye are open these many files at a same time? e.g. indexing

Could you answer for my question?

Thank you.


Answers:
author: Svante Gustafsson Bj?rkegren
body: Hey,

Have you checked out the following pages:

[](https://confluence.atlassian.com/display/FISHEYE/Tuning+FishEye+performance#TuningFishEyeperformance-Defaultnumberofopenfiles)<https://confluence.atlassian.com/display/FISHEYE/Tuning+FishEye+performance#TuningFishEyeperformance-Defaultnumberofopenfiles>

[](https://confluence.atlassian.com/pages/viewpage.action?pageId=137265407)<https://confluence.atlassian.com/pages/viewpage.action?pageId=137265407>

They pretty much describe the whole issue and how to tweak fisheye to not run into the problem again.

Cheers,

// Svante


Tags: fisheye-crucible-administration
Possible problem with your *.gwt.xml module after upgradeing to FishEye 3.4.2
Asked by Neal Culiner:

Hello,

I just updated Fisheye to the latest (3.4.2) and now when I click on a change set number I get a popup in Chrome (not Firefox or IE 11) of:

ERROR: Possible problem with your \*.gwt.xml module file. The compile time user.agent (gecko1_8) does not match the runtime user.agent value (safari). Expect more errors.

I'm using Google Chrome Version 34.0.1847.131 m


Answers:
author: Maciej Swinarski
body: Hi Neal,

This is caused by a bug in 3.4.2 [](https://jira.atlassian.com/browse/FE-5195)<https://jira.atlassian.com/browse/FE-5195>

I am afraid the only way to fix is to upgrade to FeCru 3.4.3.

Sorry for all the trouble.

mac
Show more buttons on review
Asked by Micha? Wieczorek:

When I complete the review I see three buttons ("Edit Details", "Uncomplete", and Tools menu).

![](../../upfiles/screen_1.jpg)

Is it possible to show more buttons? I'd like to have 'Close' button on the screen, not in 'Tools' menu.


Answers:
author: Piotr Swiecicki
body: Micha?,

I am guessing you are the reviewer and because of that you see default options - Edit Details and Uncomplete. Default actions differ per role, review author would be presented Edit Details and Close options. I believe that makes more sense as usually it is review author not reviewer closing the review.

Hope that helps,  
Piotr

comments: author: Micha? Wieczorek
body: Piotr,

Thank you for the answer.

I understand your point of view, but in my review workflow sometimes reviewer is closing the review (let's drop the discussion if it makes sense or not :-) )

So is it possible to show this button somehow? (In Jira you can extend number of shown workflow action buttons in config properties)


author: Piotr Swiecicki
body: I'm afraid you can't configure that. Crucible always shows edit action if you have permission to edit the review, then it always shows one prime action followed by a share and tools menu with the rest of possible transitions.

The prime action is the first action allowed by the user, in this order: complete, uncomplete, join and close review.

You could possibly work it around by revoking uncomplete permission from your user in permission scheme, but this is not really workable solution. You won't be able to ever uncomplete a review if you marked it complete by mistake.

Feel free to raise a feature enhacement in [](https://jira.atlassian.com/browse/CRUC)<https://jira.atlassian.com/browse/CRUC>project if you feel this is something more users would find useful.

Kind regards,


author: Micha? Wieczorek
body: Thanks Piotr,

Following your advise I created issue: <https://jira.atlassian.com/browse/CRUC-6807>


author: Nick
body: Those button placements are not configurable, however you may find the latest dot shortcut interesting.

When viewing a review, hit ".", then you get an autocomplete for all the actionas available on the review. This is the same behaviour for a JIRA issue.

This feature is available from Crucible 3.4 and onwards.

![](http://monosnap.com/image/raasag36tnb1queZrzjFf6mdPN5gxZ.png)

comments: author: Micha? Wieczorek
body: That's also a great hint. Thanks
fisheye parsing repository is extremely slow
Asked by Brent Webster:

Crucible/Fisheye(CF) is going to be used for code reviews ONLY even though Fisheye is a SVN Repo browser with limited capabilities compared with ToroiseSVN or RapidSVN. CF needs to parse the repository and then store the results in a SQL based database(MySQL in our case). This is an incredibly slow process. I don't need CF to parse the "actual" source code repository branches (i.e. /main, /trunk, /branches/release\[s\]/**) because the code needs to be inspected before it is allowed on these branches. As a result, the only branch that needs to be parsed is the /branches/private/** subdirectories but this is massive with every designer taking a copy of /main, /trunk or /branches/release\[s\]/?? to work on. CF with its native/default svn plugin does not understand or emulate the lightweight directory structure of SVN and its incredibly efficient means of copying directories and only storing the deltas.

The actual/entire repository is 5.7G in size and after a day of parsing (and indicating 0% complete) of just the /branches/private/\* subtree, the "FISHEYE_INST" directory is 1.2G so this could result in a CF database being considerably larger than the actual SVN repo.

Suggestions?  


Answers:
author: Brent Webster
body: I stopped it after 24 hours. I decided to rethink my process and instead created a new /branches/reviews branch and I'll only parse that branch. The process will be that any code submission destine for formal code release (i.e. /main or /branches/releases) will be developed in this new branch. Starting fresh.

I would have be nicer if fisheye could better interface with SVN rather than "indexing" and creating a blotted view in another database.


author: Nick
body: Has the Scan phase already finished ? If so, you can begin using Crucible immediately. The Indexing phase which takes the longest provides functionality needed by FishEye only.

Also - have you added **/branches/private/** as an includes to ensure nothing else is indexed by FishEye that doesn't need to be.


Tags: fisheye-crucible-administration
Recommend steps for moving a crucible environment to a new server
Asked by jcurleyWR:

We are upgrading our production crucible server. Before we do it for real, we want to copy the existing environment to the new machine, for verification purposes.

We plan to install the same version of Crucible (3.0.1) and MySQL 5.1 on the new server.

The crucible user ids come from the Jira system.

What steps would you recommend?

Thank you.


Answers:
author: gustavo_refosco
body: Hi John,

You will find all the instructions you need for this at [](https://confluence.atlassian.com/display/FISHEYE/Migrating+FishEye+Between+Servers)<https://confluence.atlassian.com/display/FISHEYE/Migrating+FishEye+Between+Servers>

The document above will instruct you on how to moving your instance to the new server. Also please notice that in order to carry the data from your database to the new one, you will also need to follow the instructions at [](https://confluence.atlassian.com/display/FISHEYE/Backing+up+and+restoring+FishEye+data)<https://confluence.atlassian.com/display/FISHEYE/Backing+up+and+restoring+FishEye+data> as pointed by the migration document (notice that FishEye/Crucible are the same application, so the migration document applies for Crucible the same way).

In order to upgrade you can then follow the instructions contained at [](https://confluence.atlassian.com/display/FISHEYE/FishEye+upgrade+guide)<https://confluence.atlassian.com/display/FISHEYE/FishEye+upgrade+guide>

comments: author: jcurleyWR
body: Thank you. We'll working on this, this week and will re-confirm.


Tags: fisheye-crucible-administration
Crucible\FishEye changing Perforce repo
Asked by Simon Hayes:

While evaluating Crucible and FishEye we indexed a subset of our depot. Now we would like to expand it to include the entire depot. I was planning to change the depot path from //depot/something/something/ to //depot/

Just wondering if this will cause a complete re-index or will FishEye\\Crucible only index the new data? It took around 2 weeks to index the subset so it would be nice to know what to expect.

Thanks in advance.


Answers:
author: Felipe Kraemer
body: Hi Simon,

This action will require a complete re-index, because you'll be reconfiguring the repository location in order to include more folders and files.

In order to have a better idea of how long it would require to have that repository fully indexed again, a suggestion is to configure that repository in a test environment first.

Kind regards,  
Felipe Kraemer  
Atlassian Support

comments: author: Simon Hayes
body: We're concerned that it will take a month or more to index the data, which is not great. The indexer appeared to be single threaded (ie it only used a single core of the machine it was on), and was CPU bound. Is there any way to speed the process? Are there any plans to improve the performance?
Fisheye Exclude path
Asked by Tushar Kamble(HONEYWELL):

If an item is 'excluded' by Fisheye, does that prevent Jira updates from showing the code change (when the Jira issue ID is included in the svn commit message)?

If we 'exclude' a sub-tree in Fisheye, is there another way we can get email notifications of commits for 'excluded' items?

<br />


Answers:
author: gustavo_refosco
body: Hi Tushar,

As the item is excluded, any commit on it won't show up in FishEye, and consequently won't show up in JIRA as well, even if you include the JIRA issue ID in the commit (performing the smart commit).

If you, for example, perform a commit containing an excluded item and another item which is not excluded, only the not excluded item will show up (also valid for the smart commit referring to the JIRA issue).

As it is not indexed by FishEye, it is also not possible to send a notification for something FishEye didn't index.
Fisheye Review Coverage Reports filter as date
Asked by Ramesh Muthu:

fisheye review coverage reports by having an option to choose a date range on the reporting options

using the 'Advanced Search' option you can set the date range to generate a list of reviews performed between two dates. Unfortunately it's not a graphical report

So my question is, do we hava an option to use filter as date and generate reports ? any plugin ?

Please suggest me

Thanks,

Ramesh Muthuraj.


Answers:
author: Foong
body: Hi Ramesh,

It seems that you are looking for this feature request: [](https://jira.atlassian.com/browse/CRUC-5870)<https://jira.atlassian.com/browse/CRUC-5870>


Tags: fisheye-crucible-administration