Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44263

Values of injected variables are not shown anymore

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      After upgrading EnvInject Plugin from 2.0 to 2.1, injected variables aren't shown under "job->build-number->Environment Variables" anymore for newly build jobs.

      Instead "No environment variables were been injected." is shown. But this is not true. Jobs are still working well using injected variables.

        Attachments

          Issue Links

            Activity

            Hide
            gmc_devel GMC Software Development B&R Corporate added a comment - - edited

            Hi!

            With this following temporary fix, I.e., changing
                <org.jenkinsci.plugins.envinject.EnvInjectPluginAction plugin="envinject@2.1"/>
            in the affected build.xml - file(s) to
                <org.jenkinsci.plugins.envinject.EnvInjectPluginAction plugin="envinject@2.1">
                    <build class="build" reference="../../.."/>
                </org.jenkinsci.plugins.envinject.EnvInjectPluginAction>
            the injected environment variables (page) will be shown again!

            Note: Needs restart (I know no other work-around) of the master to force re-load of these build-config change.
            I have checked/tested this work-around twice, to ensure that it is working.

            Best regards from Salzburg,
            Markus

             

            Show
            gmc_devel GMC Software Development B&R Corporate added a comment - - edited Hi! With this following  temporary fix , I.e., changing     <org.jenkinsci.plugins.envinject.EnvInjectPluginAction plugin="envinject@2.1"/> in the affected build.xml - file(s) to     <org.jenkinsci.plugins.envinject.EnvInjectPluginAction plugin="envinject@2.1">         <build class="build" reference="../../.."/>     </org.jenkinsci.plugins.envinject.EnvInjectPluginAction> the injected environment variables (page) will be shown again! Note: Needs restart (I know no other work-around) of the master to force re-load of these build-config change. I have checked/tested this work-around twice, to ensure that it is working. Best regards from Salzburg, Markus  
            Show
            oleg_nenashev Oleg Nenashev added a comment - Pull request: https://github.com/jenkinsci/envinject-plugin/pull/121
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I have also created JENKINS-44965 to prevent further API misusage

            Show
            oleg_nenashev Oleg Nenashev added a comment - I have also created JENKINS-44965 to prevent further API misusage
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Oleg Nenashev
            Path:
            src/main/java/org/jenkinsci/plugins/envinject/EnvInjectPluginAction.java
            src/test/java/org/jenkinsci/plugins/envinject/EnvInjectVarListTest.java
            http://jenkins-ci.org/commit/envinject-plugin/994a02bc0a51d60adc6b00a3e363271b9c7bc2a7
            Log:
            [FIXED JENKINS-44263] - Get rid of explict cached value access.

            In EnvInject 3.1 I was doing refactoring for better Pipeline Support, and I have somehow removed cache calculation in the Build lazy loading chain.
            It caused regression (missing data) in EnvInjectPluginAction#getEnvInjectVarList(), which was always reading the cache value instead of invoking the Getter method.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectPluginAction.java src/test/java/org/jenkinsci/plugins/envinject/EnvInjectVarListTest.java http://jenkins-ci.org/commit/envinject-plugin/994a02bc0a51d60adc6b00a3e363271b9c7bc2a7 Log: [FIXED JENKINS-44263] - Get rid of explict cached value access. In EnvInject 3.1 I was doing refactoring for better Pipeline Support, and I have somehow removed cache calculation in the Build lazy loading chain. It caused regression (missing data) in EnvInjectPluginAction#getEnvInjectVarList(), which was always reading the cache value instead of invoking the Getter method.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            The fix has been released in 2.1.1

            Show
            oleg_nenashev Oleg Nenashev added a comment - The fix has been released in 2.1.1

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                s_hildwein Samuel Hildwein
              • Votes:
                2 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: