Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41149

Jenkins Promotion Using Wrong Workspace, Workspace@2

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • promoted-builds-plugin
    • 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.

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

          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.

          Trent Dailey added a comment -

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

          Trent Dailey added a comment - After downgrading to version 2.26 we no longer have this issue.

          Oleg Nenashev added a comment -

          Added it to my priority list. Still no ETA

          Oleg Nenashev added a comment - Added it to my priority list. Still no ETA

          Trent Dailey added a comment -

          Also an issue with version 2.29 of the plugin

          Trent Dailey added a comment - Also an issue with version 2.29 of the plugin

          Trent Dailey added a comment -

          Did PR #90 cause the issue that we are seeing with all the versions since 2.26?

          Trent Dailey added a comment - Did PR #90 cause the issue that we are seeing with all the versions since 2.26?

          Oleg Nenashev added a comment -

          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.

          Oleg Nenashev added a comment - 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.

          Sergej Kleva added a comment - - edited

          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 added a comment - - edited 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 added a comment -

          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 added a comment - 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 added a comment - - edited

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

          Sergej Kleva added a comment - - edited Plugin version: 2.27 is the latest plugin which is not affected by this bug!

          Sergej Kleva added a comment -

          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

          Sergej Kleva added a comment - 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

            Unassigned Unassigned
            trent_dailey Trent Dailey
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: