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

Job cannot be built with parameters

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Won't Fix
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      Git plugin 2.0.1
      git-client 1.6
      Jenkins 1.5.45 v.1.5.46
    • Similar Issues:

      Description

      FATAL: Null value not allowed as an environment variable: GIT_COMMIT
      java.lang.IllegalArgumentException: Null value not allowed as an environment variable: GIT_COMMIT
      at hudson.EnvVars.put(EnvVars.java:356)
      at hudson.EnvVars.put(EnvVars.java:74)
      at hudson.plugins.git.GitSCM.buildEnvVars(GitSCM.java:983)
      at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:919)
      at hudson.plugins.git.GitSCM.checkout(GitSCM.java:865)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1414)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
      at hudson.model.Run.execute(Run.java:1678)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:231)

      The jobs works if it's modified to normal and build with "Build now".
      We encountered the same behaviour with Git plugin 2.0 and not parameterized builds.

        Attachments

          Issue Links

            Activity

            Hide
            markewaite Mark Waite added a comment -

            I saw a similar message about the time that I mistakenly updated by Jenkins 1.580.3 matrix project plugin from 1.4 to 1.4.1. The matrix project wiki page now warns that users of Jenkins versions older than 1.600 should not install matrix project plugin 1.4.1. I was seeing the message in a multi-branch job (a free-style multi-branch project), but not seeing it from any other job. I was unable to find any work around for the problem, though downgrading the matrix plugin version on my Jenkins may have helped.

            As far as I understand it, 1.600 correctly bundles matrix project plugin 1.4.1, so there isn't any way for you to attempt to downgrade, nor is there any firm evidence (at least from me) that a downgrade will help.

            Can you identify a series of steps which cause the problem to become visible? I was unable to identify those steps in my investigation yesterday.

            Show
            markewaite Mark Waite added a comment - I saw a similar message about the time that I mistakenly updated by Jenkins 1.580.3 matrix project plugin from 1.4 to 1.4.1. The matrix project wiki page now warns that users of Jenkins versions older than 1.600 should not install matrix project plugin 1.4.1. I was seeing the message in a multi-branch job (a free-style multi-branch project), but not seeing it from any other job. I was unable to find any work around for the problem, though downgrading the matrix plugin version on my Jenkins may have helped. As far as I understand it, 1.600 correctly bundles matrix project plugin 1.4.1, so there isn't any way for you to attempt to downgrade, nor is there any firm evidence (at least from me) that a downgrade will help. Can you identify a series of steps which cause the problem to become visible? I was unable to identify those steps in my investigation yesterday.
            Hide
            dineenr Bobby Dineen added a comment -

            That's really confusing. Why would they publish a new version of the matrix plugin and then tell everyone not to install it? Wouldn't it be less of a headache for everyone to remove the offending version...?

            I upgraded to version 1.600, got a message about the matrix plugin not working with that version and all my jenkins jobs were throwing an exception in the configuration pages when rendering source control sources. I then tried upgrading and then ultimately disabling the plugin.

            On this test server I only have a few jobs on it so I have completely removed Jenkins and reinstalled it. I'll see a bit later if my jobs work when I re set them up.

            Show
            dineenr Bobby Dineen added a comment - That's really confusing. Why would they publish a new version of the matrix plugin and then tell everyone not to install it? Wouldn't it be less of a headache for everyone to remove the offending version...? I upgraded to version 1.600, got a message about the matrix plugin not working with that version and all my jenkins jobs were throwing an exception in the configuration pages when rendering source control sources. I then tried upgrading and then ultimately disabling the plugin. On this test server I only have a few jobs on it so I have completely removed Jenkins and reinstalled it. I'll see a bit later if my jobs work when I re set them up.
            Hide
            danielbeck Daniel Beck added a comment -

            That's really confusing. Why would they publish a new version of the matrix plugin and then tell everyone not to install it? Wouldn't it be less of a headache for everyone to remove the offending version...?

            1.4.1 is required to fix a security issue (https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27). Jenkins 1.600 was released at the same time and bundles 1.4.1. So it needs to exist, and the wiki should mention it to prevent confusion. Unfortunately, it was available to older Jenkins releases from the update center for a short time, but it's incompatible to them. It has been removed from there by now.

            Show
            danielbeck Daniel Beck added a comment - That's really confusing. Why would they publish a new version of the matrix plugin and then tell everyone not to install it? Wouldn't it be less of a headache for everyone to remove the offending version...? 1.4.1 is required to fix a security issue ( https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27 ). Jenkins 1.600 was released at the same time and bundles 1.4.1. So it needs to exist, and the wiki should mention it to prevent confusion. Unfortunately, it was available to older Jenkins releases from the update center for a short time, but it's incompatible to them. It has been removed from there by now.
            Hide
            dineenr Bobby Dineen added a comment -

            The problem showed up after I upgraded to 1.600 which should have included the matrix plugin, so I don't think it is related to having the new plugin with the old Jenkins.

            After upgrading, when I went into the "Manage Jenkins" section it was warning about the plugin that was now built in and telling me to upgrade it. I assume seen as it was mentioning anything at all about the plugin after the upgrade there could have been references to the old still that was not resolved by the auto upgrade.

            Like I mentioned before this is not my main build server so there were only a couple jobs in it so a complete wipe and re install of Jenkins was much faster for me than digging through logs to find what things were not playing nice.

            I can go through the steps of installing 1.599, upgrading and trying to recreate it if it helps, but if I'm the only one to see this in an upgrade it may not be beneficial.

            Show
            dineenr Bobby Dineen added a comment - The problem showed up after I upgraded to 1.600 which should have included the matrix plugin, so I don't think it is related to having the new plugin with the old Jenkins. After upgrading, when I went into the "Manage Jenkins" section it was warning about the plugin that was now built in and telling me to upgrade it. I assume seen as it was mentioning anything at all about the plugin after the upgrade there could have been references to the old still that was not resolved by the auto upgrade. Like I mentioned before this is not my main build server so there were only a couple jobs in it so a complete wipe and re install of Jenkins was much faster for me than digging through logs to find what things were not playing nice. I can go through the steps of installing 1.599, upgrading and trying to recreate it if it helps, but if I'm the only one to see this in an upgrade it may not be beneficial.
            Hide
            markewaite Mark Waite added a comment -

            You're not the only one who has seen it, since I had the same stack trace on Saturday. I was so busy removing the multi-project plugin 1.4.1 that I didn't spend significant time investigating the failure.

            When I installed 1.600, it showed that the multi-project plugin version I had pinned was 1.4, rather than 1.4.1. Once I unpinned the matrix plugin and restarted Jenkins, the warning was removed and things seemed well behaved.

            I don't think it is yet worth a large investigation from you. I think others will see the problem, but will find this bug report through a google search or a Jira search.

            Show
            markewaite Mark Waite added a comment - You're not the only one who has seen it, since I had the same stack trace on Saturday. I was so busy removing the multi-project plugin 1.4.1 that I didn't spend significant time investigating the failure. When I installed 1.600, it showed that the multi-project plugin version I had pinned was 1.4, rather than 1.4.1. Once I unpinned the matrix plugin and restarted Jenkins, the warning was removed and things seemed well behaved. I don't think it is yet worth a large investigation from you. I think others will see the problem, but will find this bug report through a google search or a Jira search.

              People

              • Assignee:
                ndeloof Nicolas De Loof
                Reporter:
                tompos Tamas Papp
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: