[JIRA] (JENKINS-40112) Having '=' in injected variable value, erases build history after running JobDSL
Title: Message Title Daniel Spilker closed an issue as Cannot Reproduce Jenkins / JENKINS-40112 Having '=' in injected variable value, erases build history after running JobDSL Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40112) Having '=' in injected variable value, erases build history after running JobDSL
Title: Message Title Daniel Spilker resolved as Cannot Reproduce Jenkins / JENKINS-40112 Having '=' in injected variable value, erases build history after running JobDSL Change By: Daniel Spilker Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40112) Having '=' in injected variable value, erases build history after running JobDSL
Title: Message Title Daniel Spilker commented on JENKINS-40112 Re: Having '=' in injected variable value, erases build history after running JobDSL I can not reproduce this with Jenkins 1.642.1, Environment Injector Plugin 1.93.1 and JobDSL 1.53. Job DSL does not modify builds. Having a '=' symbol in the property value is possible, only the first '=' in the line is relevant as delimiter. See java.util.Properties. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40112) Having '=' in injected variable value, erases build history after running JobDSL
Title: Message Title Oleg Nenashev commented on JENKINS-40112 Re: Having '=' in injected variable value, erases build history after running JobDSL So it happens, because "=" is a special symbol in the *.properties format. And the value is being passed without escaping. It's either "not a defect" or UX issue in Job DSL since it contains logic for envinject. Reassigned to Daniel Spilker in order to get his opinion. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40112) Having '=' in injected variable value, erases build history after running JobDSL
Title: Message Title Oleg Nenashev assigned an issue to Daniel Spilker Jenkins / JENKINS-40112 Having '=' in injected variable value, erases build history after running JobDSL Change By: Oleg Nenashev Assignee: Oleg Nenashev Daniel Spilker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40112) Having '=' in injected variable value, erases build history after running JobDSL
Title: Message Title
Jacek Sniecikowski created an issue
Jenkins / JENKINS-40112
Having '=' in injected variable value, erases build history after running JobDSL
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
envinject-plugin, job-dsl-plugin
Created:
2016/Nov/30 1:26 AM
Environment:
Jenkins ver. 1.609.3;Environment Injector Plugin 1.93.1;JobDSL 1.45
Priority:
Minor
Reporter:
Jacek Sniecikowski
Looks like EnvInject and/or JobDSL have a bug. Steps to reproduce: 1. Set up a job that runs this JobDSL: `job('run_deploy_mock') { steps { environmentVariables { env('deployedArtifacts', 'component1=1.0.0.2') } } }` 2. Run it and it will create a job called 'deploy_mock' 3. Run the 'deploy_mock' job. After build #1 is done, go to build details and check 'Environmental Variables' section for an entry called 'component1' 4. Run the JobDSL job again 5. Check 'Environmental Variables' section for 'deploy_mock' build #1. The 'component1' variable is now missing. If I substitute the '=' for something else, it works as expected.
