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

14 views
Skip to first unread message

trent.dailey@ehi.com (JIRA)

unread,
Jan 17, 2017, 4:04:01 PM1/17/17
to jenkinsc...@googlegroups.com
Trent Dailey created an issue
 
Jenkins / Bug JENKINS-41149
Jenkins Promotion Using Wrong Workspace, Workspace@2
Issue Type: Bug Bug
Assignee: Oleg Nenashev
Components: core, promoted-builds-plugin
Created: 2017/Jan/17 9:03 PM
Environment: Jenkins 2.19.4
Promoted builds plugin 2.28
Priority: Major Major
Reporter: Trent Dailey

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.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

trent.dailey@ehi.com (JIRA)

unread,
Jan 18, 2017, 10:37:01 AM1/18/17
to jenkinsc...@googlegroups.com
Trent Dailey updated an issue
Change By: Trent Dailey
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@ehi.com (JIRA)

unread,
Jan 18, 2017, 10:57:01 AM1/18/17
to jenkinsc...@googlegroups.com
Trent Dailey updated an issue
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@ehi.com (JIRA)

unread,
Jan 19, 2017, 5:16:04 PM1/19/17
to jenkinsc...@googlegroups.com
Trent Dailey updated an issue
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.

trent.dailey@ehi.com (JIRA)

unread,
Jan 19, 2017, 5:17:01 PM1/19/17
to jenkinsc...@googlegroups.com
Trent Dailey commented on Bug JENKINS-41149
 
Re: Jenkins Promotion Using Wrong Workspace, Workspace@2

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

o.v.nenashev@gmail.com (JIRA)

unread,
Jan 19, 2017, 6:27:02 PM1/19/17
to jenkinsc...@googlegroups.com

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@ehi.com (JIRA)

unread,
Jan 20, 2017, 3:33:01 PM1/20/17
to jenkinsc...@googlegroups.com

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.

dbeck@cloudbees.com (JIRA)

unread,
Jan 23, 2017, 12:11:01 PM1/23/17
to jenkinsc...@googlegroups.com

trent.dailey@ehi.com (JIRA)

unread,
Jan 25, 2017, 3:37:01 PM1/25/17
to jenkinsc...@googlegroups.com
Trent Dailey updated an issue
Change By: Trent Dailey
Environment:
Jenkins 2.19.4
Promoted builds plugin 2.28

Promoted builds plugin 2.27

trent.dailey@ehi.com (JIRA)

unread,
Jan 25, 2017, 3:37:01 PM1/25/17
to jenkinsc...@googlegroups.com
 
Re: Jenkins Promotion Using Wrong Workspace, Workspace@2

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@ehi.com (JIRA)

unread,
Feb 1, 2017, 9:43:01 AM2/1/17
to jenkinsc...@googlegroups.com

After downgrading to version 2.26 we no longer have this issue.

o.v.nenashev@gmail.com (JIRA)

unread,
Feb 1, 2017, 9:45:01 AM2/1/17
to jenkinsc...@googlegroups.com

Added it to my priority list. Still no ETA

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 13, 2018, 9:58:10 AM3/13/18
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Unassigned
 

Sorry, over last months I had no time to work on the plugin, because I had to focus on the Jenkins core and other projects. I also have not been using this plugin on my own since 2016. So I have decided to unassign the issues so that there is no expectation that I work on them anytime soon.

Currently the plugin is being transfered to another maintainer. Hopefully he will have some time to finish triaging of the issues and maybe to deliver some fixes. But, as in any community-driven project, everybody is welcome to propose pull requests and to contribute to the plugin's state.

Change By: Oleg Nenashev
Assignee: Oleg Nenashev
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

sergej.kleva@hermes-softlab.com (JIRA)

unread,
Dec 17, 2019, 3:52:02 PM12/17/19
to jenkinsc...@googlegroups.com
Sergej Kleva commented on Bug JENKINS-41149
 
Re: Jenkins Promotion Using Wrong Workspace, Workspace@2

Jenkins 2.190.3 and latest Promote BUild 3.5 and the same thing is happening with @2 workspace!

When want to promote build ... injecting file with variables cannot be found because it was created in workspace@1.

 

Any solution to this nasty cycle! ?

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

sergej.kleva@hermes-softlab.com (JIRA)

unread,
Dec 17, 2019, 3:55:03 PM12/17/19
to jenkinsc...@googlegroups.com
Sergej Kleva edited a comment on Bug JENKINS-41149
Jenkins 2.190.3 and latest Promote BUild 3.5 and the same thing is happening with @2 workspace!

When want to promote build ... injecting file with variables cannot be found because it was created in workspace@1.

 

To recap:

Job created env.props file in workspac@1, promote build want to include this file but cannot "look" into workspace@1 ..it only "see" workspace@2! So promote fail with an error "cannot find env.props" file!

 

Any solution to this nasty cycle! ?

sergej.kleva@hermes-softlab.com (JIRA)

unread,
Dec 18, 2019, 2:58:02 AM12/18/19
to jenkinsc...@googlegroups.com

To mention something real strange behaviour of this plugin:

When choosing: "Promote immediately once the build is complete" or "Promote immediately once the build is complete based on build parameters" it creates workspace@2 directory.

But if I choose: "Only when manually approved" it runs in the right workspace! Doesn't create workspace@2 !

What's the catch?

sergej.kleva@hermes-softlab.com (JIRA)

unread,
Dec 18, 2019, 4:09:03 AM12/18/19
to jenkinsc...@googlegroups.com

Plugin version: 2.27 it's the latest plugin which is not affected by this bug!

sergej.kleva@hermes-softlab.com (JIRA)

unread,
Dec 18, 2019, 4:09:04 AM12/18/19
to jenkinsc...@googlegroups.com
Sergej Kleva edited a comment on Bug JENKINS-41149
Plugin version: 2.27 it's is the latest plugin which is not affected by this bug!

sergej.kleva@hermes-softlab.com (JIRA)

unread,
Dec 18, 2019, 5:55:03 AM12/18/19
to jenkinsc...@googlegroups.com

Interesting ... 2.27 also works only if run for the first time after install/reinstall. Afterwards, all new promotions are affected with the same bug

Reply all
Reply to author
Forward
0 new messages