-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.19.4
Jenkins 2.46.2
Promoted builds plugin 2.29
Promoted builds plugin 2.28
Promoted builds plugin 2.27
The workspace used in the build job is /opt/jenkins/workspace, but the promotion that is kicked off creates and uses the workspace /opt/jenkins/workspace@2. This is causing our promotions to fail.
We are also not using concurrent builds. The promotion is triggered immediately after a successful build, so it appears the build job and the promotion job are conflicting with eachother for the workspace.
- links to
[JENKINS-41149] Jenkins Promotion Using Wrong Workspace, Workspace@2
Trent Dailey
created issue -
Trent Dailey
made changes -
| Description | Original: The workspace used in the build job is /opt/jenkins/workspace, but the promotion that is kicked off uses the workspace /opt/jenkins/workspace@2. This is causing our promotions to fail. |
New:
The workspace used in the build job is /opt/jenkins/workspace, but the promotion that is kicked off uses the workspace /opt/jenkins/workspace@2. This is causing our promotions to fail. We are also not using concurrent builds. The promotion is triggered immediately after a successful build, so it appears the build job and the promotion job are conflicting with eachother. |
Trent Dailey
made changes -
| Description |
Original:
The workspace used in the build job is /opt/jenkins/workspace, but the promotion that is kicked off uses the workspace /opt/jenkins/workspace@2. This is causing our promotions to fail. We are also not using concurrent builds. The promotion is triggered immediately after a successful build, so it appears the build job and the promotion job are conflicting with eachother. |
New:
The workspace used in the build job is /opt/jenkins/workspace, but the promotion that is kicked off uses the workspace /opt/jenkins/workspace@2. This is causing our promotions to fail. We are also not using concurrent builds. The promotion is triggered immediately after a successful build, so it appears the build job and the promotion job are conflicting with eachother for the workspace. |
Trent Dailey
made changes -
| Description |
Original:
The workspace used in the build job is /opt/jenkins/workspace, but the promotion that is kicked off uses the workspace /opt/jenkins/workspace@2. This is causing our promotions to fail. We are also not using concurrent builds. The promotion is triggered immediately after a successful build, so it appears the build job and the promotion job are conflicting with eachother for the workspace. |
New:
The workspace used in the build job is /opt/jenkins/workspace, but the promotion that is kicked off creates and uses the workspace /opt/jenkins/workspace@2. This is causing our promotions to fail. We are also not using concurrent builds. The promotion is triggered immediately after a successful build, so it appears the build job and the promotion job are conflicting with eachother for the workspace. |
I have no access to the laptop right now, so cannot check what causes it. Maybe it is being caused by launching promotion in parallel with another build
Trent Dailey
added a comment - The downgrading of the plugin from 2.28 to 2.27 resolved the issue on all of our build agents except for one. When we point our promotion jobs to it they fail, when we point them to another build agent they succeed. They always fail because the promotion is creating and using a new workspace with @2 on the end of it. Also the build agents are the same OS and setup.
It is not competing against another build as we have disabled all other builds that use that workspace, and it is also not intermittent.
It seems like something from the promoted builds plugin 2.28 version was cached on the build agent since the downgrade resolved the issue for the other build agents. I disconnected the build agent, deleted the .jenkins directory located in the root directory, and connected the agent but we are still getting the same issue.
Trent Dailey
added a comment - The downgrading of the plugin from 2.28 to 2.27 resolved the issue on all of our build agents except for one. When we point our promotion jobs to it they fail, when we point them to another build agent they succeed. They always fail because the promotion is creating and using a new workspace with @2 on the end of it. Also the build agents are the same OS and setup.
It is not competing against another build as we have disabled all other builds that use that workspace, and it is also not intermittent.
It seems like something from the promoted builds plugin 2.28 version was cached on the build agent since the downgrade resolved the issue for the other build agents. I disconnected the build agent, deleted the .jenkins directory located in the root directory, and connected the agent but we are still getting the same issue. | Component/s | Original: core [ 15593 ] |
Trent Dailey
made changes -
| Environment |
Original:
Jenkins 2.19.4 Promoted builds plugin 2.28 |
New:
Jenkins 2.19.4 Promoted builds plugin 2.28 Promoted builds plugin 2.27 |
Trent Dailey
added a comment - It was just reported that this issue is also occurring on another build agent. So it appears to always occur on version 2.28, and be restrained to certain build agents on version 2.27.
Trent Dailey
added a comment - It was just reported that this issue is also occurring on another build agent. So it appears to always occur on version 2.28, and be restrained to certain build agents on version 2.27.
After downgrading the promoted build plugin from 2.28 to 2.27 the issue no longer exists. This issue is isolated to version 2.28