Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
Jenkins 1.626
Java 1.8
CentOS 6.6 (x86_64)
Description
After upgrades (I'm not sure whether it happened after jenkins or jenkins plugin upgrade), jenkins doesn't set configured environment variables with default values in the "This build is parameterized" section on commit notification from SCM (Stash) using /git/notifyCommit request. However it works properly when build is manually triggered with "Build with parameters" button. The only difference I can see is the lack of these configured variables set – everything else works as expected.
It is a regression – this setup is used for a very long time in our environment.
Attachments
Issue Links
- is blocking
-
JENKINS-27902 Allow to pass additional request parameter for notifyCommit
-
- Closed
-
- is related to
-
JENKINS-13768 default parameter values are ignored when triggering parameterized build from groovy post-build script
-
- Open
-
In my tests with git plugin 2.4.0 and git client plugin 1.19.0, I can only duplicate the problem if I include "sha1=" in the notify commit argument list (just as Daniel Beck observed in an earlier comment). When I include no argument, and when I include only the argument "branch=", then the default parameter values are visible to the XShell and Shell build steps in my test job.
The notify commit I used to show the problem was:
The notify commit I used that does not show the problem is: