[JIRA] (JENKINS-13325) PYTHONPATH gets undefined with latest 1.44 version of EnvInject

Marc Sanfacon created JENKINS-13325:
---------------------------------------

             Summary: PYTHONPATH gets undefined with latest 1.44 version of EnvInject
                 Key: JENKINS-13325
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
             Project: Jenkins
          Issue Type: Bug
          Components: envinject
         Environment: Jenkins 1.457, Windows master, Linux slave
            Reporter: Marc Sanfacon
            Assignee: gbois


We are using envinject on our Linux slave. With version 1.36, we get the following behavior:

08:51:39  [EnvInject] - Injecting environment variables from a build step.
08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
08:51:39  [EnvInject] - Variables injected successfully.
08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.

But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.

With version 1.44, we get this:
08:49:16  [EnvInject] - Injecting environment variables from a build step.
08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
08:49:16  [EnvInject] - Variables injected successfully.
08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.

Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.

I don't know what changed between the builds, but reverting the plugin fixed it.

Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JENKINS-13325 started by gbois.

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161186#comment-161186 ]

gbois commented on JENKINS-13325:
---------------------------------

Please attach your job configuration file ($JENKINS_HOME/jobs<job_name>/config.xml0 and your 'BuildFingerprint.txt' file.
I'll look at it.
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marc Sanfacon updated JENKINS-13325:
------------------------------------

    Attachment: BuildFingerprint.txt
   

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marc Sanfacon updated JENKINS-13325:
------------------------------------

    Attachment: config.xml
   

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161199#comment-161199 ]

Marc Sanfacon commented on JENKINS-13325:
-----------------------------------------

Done - Thanks for the quick feedback.
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161260#comment-161260 ]

gbois commented on JENKINS-13325:
---------------------------------

Could you try to reproduce it in on an isolated environment?
I tested in my context and it is OK.
Thanks
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161352#comment-161352 ]

gbois commented on JENKINS-13325:
---------------------------------

Any update?
Are you sure it is the right file, your given file is filled with plain values.
Therefore it should never be unseted variables.
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161417#comment-161417 ]

Marc Sanfacon commented on JENKINS-13325:
-----------------------------------------

These are the right file. I can't test it right now since it is our production environment.

What exactly would you like me to test? Is there a log I can activate?

               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161433#comment-161433 ]

gbois commented on JENKINS-13325:
---------------------------------

I tested to inject your input 'BuildFingerprint.txt' file and it is OK in my environment (no variables are unset).
I also tested with your job configuration file and it is OK.
Therefore, I didn't reproduce your issue.
Additionally, according to the uploaded file I don't understand your log because all properties values are not variables. They have to be injected as plain values.

Therefore, have you injected the right file?
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161434#comment-161434 ]

Marc Sanfacon commented on JENKINS-13325:
-----------------------------------------

Here is the ouput of the job running today with EnvInject 1.36
12:38:15  + cp /mnt/buildsjenkins/7.0_RC_Continuous-20/BuildFingerprint.txt .
12:38:15  [EnvInject] - Injecting environment variables from a build step.
12:38:15  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
12:38:15  [EnvInject] - Variables injected successfully.
12:38:15  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
12:38:15  [EnvInject] - Unset unresolved 'PATH' variable.
12:38:15  [EnvInject] - Unset unresolved 'NEWSCP' variable.
12:38:15  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
12:38:15  [EnvInject] - Unset unresolved 'TEMP' variable.

And the content of /mnt/buildsjenkins/7.0_RC_Continuous-20/BuildFingerprint.txt
[BuildInfo]
BuildId=2012-04-10_12-37-30
BuildNumber=20
DBBuildNumber=4775
BuildName=7.0_RC_Continuous-20
SymbolStoreUUID=92113861832b11e1b3bf00219b99e084
HGRev=c65e9f8e929175f8706a8a51bfecdb10da78503c
Branch=prerelease-7.0-RC

The config is the same that I already have attached.

As I said, the Master Jenkins is running on Windows and the slave on Linux, I don't know if that changes anything.

I can do more testing by creating a job that only injects the variables, if you want.

Thanks
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161444#comment-161444 ]

gbois commented on JENKINS-13325:
---------------------------------

Ok, I think I found it.
The injected file doesn't cause the error.
The problem is due to the internal EnvInject solving.
EnvInject gets Jenkins and build environment variables and then tries to merge them.
If a variable contains variable anymore, the variable is removed (or unset), it is not used by the Jenkins build).
Therefore, I suppose PATH, SRC_SHARED, NEWSCP, PYTHONPATH and TEMP are predefined environment variables and these variables can't resolve each other.
Could you check with the 'env' command?
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161479#comment-161479 ]

Marc Sanfacon commented on JENKINS-13325:
-----------------------------------------

They are indeed environment variables on the linux server. They are set in the .bash_profile file.

They are defined like this:
export DEVHOME=/usr/local/jenkins
export SRC_SHARED=${DEVHOME}/Projects/Shared
export NEWSCP=${DEVHOME}/Projects/DevTools/newscp

# Python scripts
export PYTHONPATH=${PYTHONPATH}:${DEVHOME}/Projects/DevTools/newscp
export PATH=${PATH}:${DEVHOME}/Projects/DevTools/newscp:${DEVHOME}/Projects/DevTools/redhat

Does that help?
I'm not sure I understand what you mean by:  these variables can't resolve each other.

               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161490#comment-161490 ]

gbois commented on JENKINS-13325:
---------------------------------

I think these variables are not loaded by the Jenkins process.
Could you check if Jenkins process reads the .bash_profile file?

Jenkins expects to have all these variables resolved.
For example:
DEVHOME=/usr/local/jenkins
SRC_SHARED=${DEVHOME}/Projects/Shared
is OK because the SRC_SHARED variable can be resolved with DEVHOME value but only if DEVHOME is take into account (loaded by the Jenkins process).

Please check 'Manage Jenkins > System Information' and check if each variable can be resolved.
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161504#comment-161504 ]

Marc Sanfacon commented on JENKINS-13325:
-----------------------------------------

The variables were not defined in the Jenkins process, only in the .bash_profile.

Looks like the ssh command does not run the .bash_profile. I modified the launch script and they are now defined. I upgraded to the latest build of EnvInject (1.44) and it fixes the problem.

Thanks
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

gbois resolved JENKINS-13325.
-----------------------------

    Resolution: Fixed
   

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161506#comment-161506 ]

gbois commented on JENKINS-13325:
---------------------------------

I'm happy to read that
               

> PYTHONPATH gets undefined with latest 1.44 version of EnvInject
> ---------------------------------------------------------------
>
>                 Key: JENKINS-13325
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
>             Project: Jenkins
>          Issue Type: Bug
>          Components: envinject
>         Environment: Jenkins 1.457, Windows master, Linux slave
>            Reporter: Marc Sanfacon
>            Assignee: gbois
>         Attachments: BuildFingerprint.txt, config.xml
>
>
> We are using envinject on our Linux slave. With version 1.36, we get the following behavior:
> 08:51:39  [EnvInject] - Injecting environment variables from a build step.
> 08:51:39  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:51:39  [EnvInject] - Variables injected successfully.
> 08:51:39  [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'NEWSCP' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> 08:51:39  [EnvInject] - Unset unresolved 'TEMP' variable.
> But somehow, the variable PYTHONPATH is still set afterwards since we call a script found in the path and it works.
> With version 1.44, we get this:
> 08:49:16  [EnvInject] - Injecting environment variables from a build step.
> 08:49:16  [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt'
> 08:49:16  [EnvInject] - Variables injected successfully.
> 08:49:16  [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
> Only PYTHONPATH gets undefined, but it really is. The next build step fails when calling the script because it is not found in the path.
> I don't know what changed between the builds, but reverting the plugin fixed it.
> Also, why does EnvInject undefines other variables? All I want is for it to inject the variables I asked. The ini files does not contain PYTHONPATH.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Marc Sanfacon reopened JENKINS-13325

PYTHONPATH gets undefined with latest 1.44 version of EnvInject

Just upgraded to version 1.60 and I got this error, which looks the same... 13:03:32 [EnvInject] - Injecting environment variables from a build step. 13:03:32 [EnvInject] - Injecting as environment variables the properties file path 'BuildFingerprint.txt' 13:03:32 [EnvInject] - Variables injected successfully. 13:03:32 [EnvInject] - Unset unresolved 'PATH' variable. 13:03:32 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
Change By:	Marc Sanfacon (06/Jul/12 5:10 PM)
Resolution:	Fixed
Status:	Resolved Reopened

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Gregory Boissinot commented on JENKINS-13325

PYTHONPATH gets undefined with latest 1.44 version of EnvInject

Should be fixed from EnvInject 1.61

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Gregory Boissinot commented on JENKINS-13325

PYTHONPATH gets undefined with latest 1.44 version of EnvInject

Is it fixed for your with the last version? Can I set the issue to Resolved?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira