Details
Description
Summary
Bamboo is showing incorrect metadata when a build is re-run.
Steps to Reproduce
- Make sure you have at least 2 users inside Bamboo (e.g. admin and bob).
- Create a new Plan.
- It's not even necessary to set up a source repository.
- Create 2 stages inside the plan and make the second one is a manual stage:
- Default Stage.
- Second Stage.
- Inside the first stage create a job with a simple script task (e.g. echo "My first job!").
- Inside the second stage create another job with a simple script task (e.g. echo "My second job!").
- As the admin user, trigger the first build of that plan, including the manual stage.
- Log out of Bamboo and log back in as bob.
- Access that build and click Run > Rerun this build, including the manual stage.
- After that check the Metadata tab for both the build result and the second job result.
Expected Results
Both jobs should display the following metadata:
Job #1
Key | Value |
---|---|
ManualBuildTriggerReason.stageName | Default Stage |
ManualBuildTriggerReason.userName | bob |
Job #2
Key | Value |
---|---|
ManualBuildTriggerReason.stageName | Second Stage |
ManualBuildTriggerReason.userName | bob |
This is because bob re-run the build.
Actual Results
The build metadata information is correct but the jobs are not:
Job #1
Key | Value |
---|---|
ManualBuildTriggerReason.stageName | Second Stage |
ManualBuildTriggerReason.userName | admin |
Job #2
Key | Value |
---|---|
ManualBuildTriggerReason.stageName | Default Stage |
ManualBuildTriggerReason.userName | admin |
Each job is displaying the incorrect stage name – it should be the other way around – and both jobs have the user name set to admin when in fact bob is the one that re-run that build.
Attachments
Issue Links
- relates to
-
BAM-16353 ManualBuildTriggerReason metadata incorrect for different stages
- Gathering Impact