-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 7.0.6, 8.2.4
-
Component/s: Deployments, Tasks
-
None
-
1
-
Severity 2 - Major
Issue Summary
When changing the repository in the Repository Commit configuration by userA. UserB is not getting the same configuration
This is reproducible on Data Center: yes
Steps to Reproduce
- Create a deployment that contains Repository Commit task with userA
- Add a user (userB) to have edit privilege to the deployment.
- Change the repository inside the Repository Commit task with userA
- View the task configuration with userB
Expected Results
userA and userB will see the new changed repo in the Repository Commit task
Actual Results
userA see the new changed repo
userB see the old changed repo
When exporting the deployment configuration as Java specs it gets the correct repo
I tried to run the deployment with userB got the below error:
26-Sep-2022 10:59:02 Starting task 'Repository Commit' of type 'com.atlassian.bamboo.plugins.vcs:task.vcs.commit' 26-Sep-2022 10:59:02 Error occurred while running Task '(3)' of type com.atlassian.bamboo.plugins.vcs:task.vcs.commit. 26-Sep-2022 10:59:02 com.atlassian.bamboo.task.TaskException: Repository id 950273 is invalid. Please reselect from the configuration screen. 26-Sep-2022 10:59:02 at com.atlassian.bamboo.utils.BambooPreconditions.checkThat(BambooPreconditions.java:29) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.plugins.vcs.task.VcsCommitTask.execute(VcsCommitTask.java:52) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.task.TaskExecutorImpl.lambda$executeTasks$3(TaskExecutorImpl.java:323) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.task.TaskExecutorImpl.executeTaskWithPrePostActions(TaskExecutorImpl.java:258) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:323) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.task.TaskExecutorImpl.execute(TaskExecutorImpl.java:118) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.call(ExecuteBuildTask.java:73) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.executeBuildPhase(DefaultBuildAgent.java:205) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:177) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.lambda$waitAndPerformBuild$0(BuildAgentControllerImpl.java:169) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.variable.CustomVariableContextImpl.withVariableSubstitutor(CustomVariableContextImpl.java:118) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:162) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.lambda$start$0(DefaultBuildAgent.java:122) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:48) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:26) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:17) 26-Sep-2022 10:59:02 at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:41) 26-Sep-2022 10:59:02 at java.base/java.lang.Thread.run(Thread.java:829)
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
