[JIRA] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto resolved as Not A Defect Jenkins / JENKINS-30044 Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Change By: Manuel Jesús Recena Soto Status: In Progress Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Patrick Ryan, It seems it is not related to EnvInject Plugin. Thanks for your feedback. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Patrick Ryan commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Although, not related to envInject, POM_VERSION seems to be stuck. If I update the version in the repo, POM_VERSION is still set to the value it was at the first time the job was run, even after I run a Maven target. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Patrick Ryan commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 I'm sorry. It seems the reboot from upgrading the plugin caused the issue. Although not well documented, The Maven variables are not exposed/available for use until maven has been run. It was working before becuase the job ran once before i tried accessing these variables, but that cached info must have been lost on reboot and i was access them before maven ran. Therefore, to solve my issue (since these are all pre build steps) I just run Invoke Top Level Maven Targets->validate first. This issue can be closed. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Patrick Ryan Fantastic. I'm working on it. The first step will be to try to reproduce the bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title
Patrick Ryan edited a comment on JENKINS-30044
Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
My second step:"Copy artifacts from another project" ->pipeline.properties"Inject environment variables" -> pipeline.propertiespipeline.properties:variableA="foo"variableB="bar"Script: {code:java} echo "${POM_ARTIFACTID} - ${variableA}" {code} Output:"- foo"This was working before the update. I'm know wondering if the maven build needs to occur before these variables exist? It doesn't say anything in documentation for Maven except: "Maven project type exposes the following environment variables, allowing you to use them as variable expansions in build configuration."This makes it sound like they are there from the beginning which was the case for the past couple of weeks that this has been working. This morning I update EnvInject and restart and now I cannot get any of the Maven Variables. Thanks for looking into this. I'm trying things on my end too and cannot get those variables back. I will let you know if I find anything.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title
Patrick Ryan commented on JENKINS-30044
Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
My second step: "Copy artifacts from another project" ->pipeline.properties "Inject environment variables" -> pipeline.properties
pipeline.properties: variableA="foo" variableB="bar"
Script: echo "$ {POM_ARTIFACTID}
-$ {variableA}
"
Output: "-foo"
This was working before the update. I'm know wondering if the maven build needs to occur before these variables exist? It doesn't say anything in documentation for Maven except: "Maven project type exposes the following environment variables, allowing you to use them as variable expansions in build configuration." This makes it sound like they are there from the beginning which was the case for the past couple of weeks that this has been working. This morning I update EnvInject and restart and now I cannot get any of the Maven Variables. Thanks for looking into this. I'm trying things on my end too and cannot get those variables back. I will let you know if I find anything.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title
Patrick Ryan edited a comment on JENKINS-30044
Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
My second step:"Copy artifacts from another project" ->pipeline.properties"Inject environment variables" -> pipeline.propertiespipeline.properties:variableA="foo"variableB="bar"Script:echo "${POM_ARTIFACTID}-${variableA}"Output:"-foo"This was working before the update. I'm know wondering if the maven build needs to occur before these variables exist? It doesn't say anything in documentation for Maven except: "Maven project type exposes the following environment variables, allowing you to use them as variable expansions in build configuration."This makes it sound like they are there from the beginning which was the case for the past couple of weeks that this has been working. This morning I update EnvInject and restart and now I cannot get any of the Maven Variables. Thanks for looking into this. I'm trying things on my end too and cannot get those variables back. I will let you know if I find anything.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Patrick Ryan, Thanks for your feedback. What do you mean in your second step? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Patrick Ryan commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 I have since changed my job to workaround this issue, but here are the steps: 1) clone git 2) Pull in artifact archived by upstream job. This is a properties file, 'x'='y'. 3) Inject properties file into environment with "Inject environment variables." 4) Execute shell. The script would grab maven properties and echo them into the properties file that would be passed on to other freestyle jobs in my pipeline. Variables POM_ARTIFACTID and POM_GROUPID were working, but are no longer. The Maven Version never changed, so it seems that the current version of EnvInject is losing these build/maven parameters when a file is injected. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Patrick Ryan, Could you provide a detailed description about your Job? A step by step process would be great, or a screenshot with the configuration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-30044 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Patrick Ryan created an issue Jenkins / JENKINS-30044 Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Issue Type: Bug Assignee: Manuel Jesús Recena Soto Components: envinject-plugin Created: 19/Aug/15 5:21 PM Environment: Jenkins 1.610 EnvInject 1.92 Maven 2.10 Priority: Minor Reporter: Patrick Ryan In my Maven Job, I pull a properties file into the environment. In a build script, I access POM_ARTIFACTID and POM_GROUPID. Before the upgrade this worked fine. Now those variables resolve to nothing. Add Comment
