We are finally starting to use Crucible and have run into a question/issue. When adding content to a review (Add Content > Browse Changesets), it appears that we are unable to navigate to or choose a nested branch. For example, we have the following branch structure:
So, I was wondering if I was doing something wrong, or if it is not supported. If it is the latter, I am curious as to why (best practice, technical constraint, etc.).
We've tossed around the idea of making our branch structure flat (one level), but wanted to investigate further before changing our entire process.
While the list of branches in Browse Changesets is indeed flat, you can probably configure Crucible svn handling to use your current repository structure and get branches that are mapped to your directories with names like 'team1-project1' and 'team2-project3'.
To do that you'll have to set up symbolic rules for the svn repository, to tell Crucible what you consider a branch. You can see the details on this feature here: https://confluence.atlassian.com/display/FISHEYE/SVN+tag+and+branch+structure. I believe your repo structure is similar to the 'Example from FishEye customer' one and you could use similar rules.
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 ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot