-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins 2.204.1
BuildMaster plugin 3.0.0
After upgrading to 3.0 of the plugin I can no longer specify the Release Number with a variable as I could before in the Create Build and Deploy Build tasks.
This in the classic Jenkins job mode.
We run multiple release builds simultaneously at times so I need to be able to specify it via a variable otherwise we have to have have extra jobs and hard code the release number as we cannot use Latest Active Release.
Having the ability to override it in the both tasks or even better would be to have the override in the Inject BuildMaster release details step that would then set the buildmaster_release_number variable for the other BM tasks.
I have not tried yet in declarative script mode yet but this would be needed there as well.
I am going to have to downgrade to the older 2.4.0 version of the plugin for now but I don't know if that version will work with BuildMaster 6.2 when it comes out.
I sort of thought doing that might prove difficult. It's solvable in other ways so it really is not a big deal.
I had used that plugin before on an older server but I had to drop it as it ended up causing the server to become corrupted, or rather the scriptler portion. I never used the scriptler portion but it eventually made it so the Jenkins server could not be upgraded. I never had a chance to dig real deep into it.
Then with Scriptler is of course a security issue plugin which here I cannot risk using.
Anyway, thanks for spending the time to look into it.
Have a great year!