• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: promoted-builds-plugin
• Labels:

  None
• Environment:

  Jenkins 2.19.4
  Jenkins 2.46.2
  Promoted builds plugin 2.29
  Promoted builds plugin 2.28
  Promoted builds plugin 2.27

[JENKINS-41149] Jenkins Promotion Using Wrong Workspace, Workspace@2

Trent Dailey created issue - 2017-01-17 21:03

Trent Dailey made changes - 2017-01-18 15:36

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 - 2017-01-18 15:56

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 - 2017-01-19 22:15

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.

Daniel Beck made changes - 2017-01-23 17:10

Component/s

Original: core [ 15593 ]

Trent Dailey made changes - 2017-01-25 20:36

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 made changes - 2017-08-22 15:24

Environment

Original: Jenkins 2.19.4 Promoted builds plugin 2.28 Promoted builds plugin 2.27

New: Jenkins 2.19.4 Jenkins 2.46.2 Promoted builds plugin 2.29 Promoted builds plugin 2.28 Promoted builds plugin 2.27

CloudBees Inc. made changes - 2017-12-05 05:32

Remote Link

New: This issue links to "CloudBees Internal OSS-1921 (Web Link)" [ 18510 ]

Oleg Nenashev made changes - 2018-03-13 13:57

Assignee

Original: Oleg Nenashev [ oleg_nenashev ]