-
Bug
-
Resolution: Unresolved
-
Major
-
SUSE Linux Enterprise Server 11 SP2
Oracle JDK 1.8.0_91 x64
Tomcat 8.0.33
Jenkins LTS version 1.651.2
Parameterized Trigger plugin 2.30
After upgrading from 1.651.1 to 1.651.2, when accessing administration page, I found a warning about configuration versions.
I found messages related to parameterized trigger and also promoted builds plugins, stating config version was 1.653.
The option to change configuration compatibility only showed the same version 1.653.
After applying it, however, the messages disappeared (though they appeared again later, perhaps because of executions of other tasks or new executions of the same ones).
I have a commons task which is triggered via parameterized trigger plugin and receives from this plugin a file.
The plugin si configured with some properties and a parameter factory to send one file to a concrete location and name of the common task.
Before upgrading, everything worked fine.
After upgrading, the task was triggered (therefore, the plugin found the file to send), but the file was never copied into the common-task workspace.
Reverting to previous version, fixed the problem.
- duplicates
-
JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (SECURITY-170 / CVE-2016-3721)
- Open