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

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

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.

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.

Added it to my priority list. Still no ETA

Also an issue with version 2.29 of the plugin

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

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.

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! ?

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?

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

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