Crucible build status
What is Crucible build status app
The Crucible build status app helps reviewers to see build statuses for changes which as still under review. The app provides integration with Atlassian Bamboo and Bitbucket Pipelines. Aggregated build results are displayed on a review page and all the details of the builds are available in a dialog window.
Installation of Crucible app
Crucible build status app is available in the Atlassian Marketplace and can be installed as any other app.
Crucible version 4.8.6 or higher is required to run Crucible build status.
Integration with Bamboo
If you want to see build results from Bamboo, you have to install the Bamboo build status notifier app on your Bamboo instance. This app is available in the Atlassian Marketplace.
For the connection between Crucible and Bamboo to work, both apps have to be connected with an applink. To learn how to create applinks, click here.
If you want to connect multiple Bamboo servers to Crucible, each of them must have the Bamboo build status notifier app installed.
Integration with Bitbucket Pipelines
Install the Crucible build status app on your Crucible instance.
Define a webhook in Crucible:
Go to Administration > Global Settings > Bitbucket Pipelines webhooks.
Click Add a new webhook.
Define a distinct name for a new webhook.
Copy the unique URL generated for your webhook to clipboard.
Set up a webhook in Bitbucket:
Go to Repository settings > Webhooks.
Click Add webhook.
Fill the form in the following way:
Title - enter whatever you like, for example Crucible.
Url - paste the URL generated by Crucible from your clipboard.
Triggers - select ‘Choose from a full list of triggers’. On the list of triggers select:
Aggregated build status is displayed on the top bar of the review.
Click on aggregated status opens a dialog displaying build details.
Aggregated summary - the summary displayed in the review screen shows the aggregation of build results for this review. The app takes the latest execution of each Bamboo plan or Bitbucket pipeline, that includes any changeset under review and shows the aggregated status of the review:
All tests have passed
Not all builds have finished execution, but there are no failures
There is at least 1 failed build
The app supports reviews containing changsets from multiple repositories.
Dialog window displays the whole build history for a review. If a build has been rerun only the latest result is presented.
Supported version control systems are Git, Mercurial, and Subversion.
In order to save database space, old build statuses are cleaned. Clean-up job runs every 12 hours and removes statuses older than 30 days.
As Crucible build status relies on events and webhooks to gather data, information on builds executed before installation and the app setup is not accessible in Crucible.
While Git and Mercurial commit hashes are globally unique, SVN assigns commits consecutive numbers. For Crucible to recognise that build was executed against a changeset that is under review, the SVN repository URL must be exactly the same on Bamboo and Fisheye / Crucible. For example, if one is defined over http and the other over https, they won’t be recognised and build status won’t be displayed.
Build results from Bitbucket Pipelines contain only overall status (success or failure), but not the exact number of passed and failed tests.