-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
Jenkins 1.651.2 or 2.6
Parameterized Trigger Plugin 2.30
Works in Jenkins 1.651.1
Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate:
- Create two Jenkins projects: proj1 and proj2
- In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file
- Build proj1 which should trigger proj2
- Check environment variables for proj2, the variables=values from the properties file is not present.
Again, works fine in Jenkins 1.651.1
- duplicates
-
JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (SECURITY-170 / CVE-2016-3721)
-
- Open
-
[JENKINS-35113] Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin
Summary | Original: Upgrade to 1.651.2 or 2.6.x broke 'Parameters from properties' in 'Parameterized Trigger' plugin | New: Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin |
Summary | Original: Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin | New: Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin |
Description |
Original:
*Works in Jenkins 1.651.1* Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, *Works fin in Jenkins 1.651.1* |
New:
*Works in Jenkins 1.651.1* Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, *Works fine in Jenkins 1.651.1* |
Description |
Original:
*Works in Jenkins 1.651.1* Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, *Works fine in Jenkins 1.651.1* |
New:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, *{color:#d04437}Works fine in Jenkins 1.651.1{color}* |
Description |
Original:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, *{color:#d04437}Works fine in Jenkins 1.651.1{color}* |
New:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, *{color:#14892c}Works fine in Jenkins 1.651.1{color}* |
Description |
Original:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, *{color:#14892c}Works fine in Jenkins 1.651.1{color}* |
New:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, {color:#14892c}*Works fine in Jenkins 1.651.1*{color} |
Description |
Original:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, {color:#14892c}*Works fine in Jenkins 1.651.1*{color} |
New:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, {color:red}*Works fine in Jenkins 1.651.1*{color} |
Description |
Original:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, {color:red}*Works fine in Jenkins 1.651.1*{color} |
New:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, {color:red}{color:#d04437}*Works fine in Jenkins 1.651.1*{color}{color} |
Description |
Original:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, {color:red}{color:#d04437}*Works fine in Jenkins 1.651.1*{color}{color} |
New:
{color:red}{color:#d04437}*Works in Jenkins 1.651.1*{color}{color} Upgrade to 1.651.2 or 2.6.x breaks 'Parameters from properties file' in 'Parameterized Trigger' plugin. Steps to recreate: - Create two Jenkins projects: proj1 and proj2 - In proj1: add a build step to 'Trigger/call builds on other projects', specify proj2, click 'Add Parameters' and select 'Parameters from properties', specify a valid properties file - Build proj1 which should trigger proj2 - Check environment variables for proj2, the variables=values from the properties file is not present. Again, {color:#14892c}*Works fine in Jenkins 1.651.1*{color} |