Grzegorz Lewandowski Atlassian Team

@Chris Nollstadt, I suppose you use local agents only. In that particular case, the only benefit of using multiple jobs is running them in parallel (in case it's actually benefit and your hardware can handle whole load) and build composition/organization. Jobs are meant to be run on different remote agents, which in fact…

You should have only single Bamboo Specs project in bamboo-specs directory. Within this project you can have (and publish) as many plans as you want. Please refer to the tutorial in order to get information how to create Specs project within your repository (there's a command you should use to get you started) and to the…

Bamboo API is dedicated strictly to plugins. Regarding REST apis, it's limited in general to reading data from the system. However, you could use REST Based Bamboo Specs to do what you want.

I believe a Java Bamboo Specs is a solution for your problem. Here's a tutorial

With Java Bamboo Specs it's totally fine to have a single repository which defines multiple plans and deployments for Bamboo. Furthermore, that's the concept Bamboo team uses internally to manage our plans. YAML Bamboo Specs support only single plan - per repository at the moment. 

Where do you try to log in ? This is a password reset for Admin principal so you need to go to the http://FISHEYE_URL/admin and provide the password. Then you can reset/manage users in order to restore your access. Obviously, it's also recommended to change this admin principal password afterwards for security reasons.

It's not possible to take a Fisheye&Crucible backup without taking the application into maintenance mode. Such situation could lead to data inconsistency therefore there's no such feature.

Unfortunately, it's not that simple, mostly because of plugins. Technically, you can list Fisheye&Crucible tables by looking at sql create scripts to get list of Fisheye tables (they are mostly prefixed with cru) But there's a library called ActiveObjects which is used in plugins to provide database access and…

Hello, Thank you for contacting us. Java and YAML Specs are a little bit different in terms of it's base assumptions: * Java is more powerful but the learning curve is a little bit higher (although it doesn't use any sophisticated language features so a person proficient in other programming language should handle that) *…

It seems like you used a single database for 2 products JIRA and Fishey&Crucible, which is against Atlassian recommendations. Fisheye&Crucible in version 4.0 completely redesigned user management system and introduced Atlassian library called Embedded Crowd, which is already used by JIRA (and other Atlassian products).…

Why don't you use Gradle wrapper for that purpose ? Create a ScriptTask and execute ```./gradlew build```.

Hello, The idea behind Bamboo Specs YAML is to make it as simple as possible, therefore some tradeoffs have been made to make it possible and some of the settings like notifications are hard coded and you can't change them. E.g: notifications are sent to commiters and watchers of the plan when plan fails You can read more…

Hello, I think you reached https://jira.atlassian.com/browse/BAM-19584. This issue was fixed in Bamboo 6.3.1. 

There's no such feature, but I bet you can easily write a plugin which does that for you. Just listen to Bitbucket repository added remote event and add it to Fisheye.

So a changeset contains of single or many revisions/files (let's not consider empty CS). When you add a changeset to a review you basically add a revision from that CS (SHA-2) and a parent (SHA-1). So the orange box means that there are some revisions from this CS (SHA-1) but it's not checked because this changeset touched…

I don't think it's going to work with 100% features. There's a cross-repository index which is used IIRC for searches and you can't simply replicate it via copying files. 

Hello, The project you're for to is called 'Divergent plan branches'. Currently Bamboo can't take different plan definition for 'master' plan and different for its branches, therefore Bamboo processes YAML files only on master branch. Here's the feature request to add this divergent branches support to Bamboo. 

What's wrong with managing all plans via Bamboo Specs? Then you don't have to use clon. You can leverage all benefits of Bamboo Specs like, syntax highlighting, IDE support, offline validation. You can extract common parts (aka. clone) to some method or part of config which will be used by all plans. Then you can override…

Crucible empowers iterative reviews and tries to show you the changes you haven't seen yet. If you're reviewing a new file, usually there's no point in showing the diff between intermediate changes, since user should be interested in the end version of that file. When you're reviewing file modifications Crucible will show…

Bamboo YAML Specs allow only for using plain scripts. You can't use any task builders. I think the only way who to achieve what you want is to run "grep" and get the values you need. 

@ssytnikov, here's open feature request. You can vote for it and watch to track updates: https://jira.atlassian.com/browse/BAM-18785 

IIRC, there were changes in RSS security handling and now RSS code is executed in different context. I suppose that happened in your case, you can refer to Security Administration to get more details. Java was chosen as high level language to aid in configuration of complex plans. You don't have to use Maven or Java in…

Your Bamboo Specs pom.xml is missing. Are you sure Bamboo Specs Maven project is in a right directory (bamboo-specs) ? Here's a tutorial how to get started with Bamboo Specs stored in Bitbucket Server repository 

Still not really sure what do you want to achieve. Do you want to run test environment ? If so, I think you can create a backup and restore it to test environment, but make sure then you use different database, otherwise data in a production DB might be overwritten. It's not recommended to copy any files by hand,…

I don't really understand what you're trying to achieve but it's not recommend to mess with Fisheye&Crucible files. The application store its data on a filesystem and database. That's why the only recommended way of creating backups is using built-in backup feature. 

Fisheye&Crucible can only modify its own Internal Directory. You can't modify external ones, like CROWD/JIRA or LDAP. In order to resolve your licensing problem I recommend to: * check how many different user directories have you configured for Fisheye&Crucible server and remove the ones you don't use/need -> Note this…

It's not true. Stride and HipChat are different systems and Bamboo needs dedicated support to send notifications to Stride. It's not implemented yet. Here's a JIRA feature request to add such support. 

AFAIR, there's no endpoint to create a project. The permissions payload should be in the request body, e.g. ["BUILD","READ"] If you need more examples, you can navigate to any permissions widget (e.g project or plan permissions) in Bamboo and use browser console to lookup requests that are being sent. Those use the same…

You can use those REST endpoints to achieve what you want: * https://docs.atlassian.com/atlassian-bamboo/REST/6.2.5/#d2e4367 * https://docs.atlassian.com/atlassian-bamboo/REST/6.2.5/#d2e44 In 6.2. permissions rest endpoints were unified and support all CRUD operations.

Here are the guides how Fisheye/Crucible application should be upgraded: * https://confluence.atlassian.com/fishkb/migrating-and-upgrading-fisheye-crucible-423298099.html * https://confluence.atlassian.com/fisheye/upgrading-fisheye-on-windows-600115292.html…