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

Weird IllegalArgumentException prevents SVN polling from working

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: core, maven-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.517
    • Similar Issues:

      Description

      My job stopped to poll changes from SVN some time ago - it all runs properly when started manually or by timer, but it won't poll when a change occurs in repository. I have tried tweaking with Maven installations, cloning the job etc. Other jobs using Git do not have this problem. SVN polling shows:

      ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@eafaabe[scmTest]
      java.lang.IllegalArgumentException: Null value not allowed as an environment variable: M2_HOME
      at hudson.EnvVars.put(EnvVars.java:172)
      at hudson.tasks.Maven$MavenInstallation.buildEnvVars(Maven.java:492)
      at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:173)
      at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1230)
      at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
      at hudson.scm.SCM.poll(SCM.java:373)
      at hudson.model.AbstractProject._poll(AbstractProject.java:1523)
      at hudson.model.AbstractProject.poll(AbstractProject.java:1448)
      at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439)
      at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468)
      at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
      at java.util.concurrent.FutureTask.run(FutureTask.java:166)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      at java.lang.Thread.run(Thread.java:722)

      When I get into job configuration in Maven build section I get "ERROR" below Root POM line. I am attaching the exact ERROR message as a separate file.

        Attachments

        1. build.txt
          5 kB
        2. ERROR.txt
          8 kB

          Issue Links

            Activity

            Hide
            kutzi kutzi added a comment -

            Can you show me the configuration of the job - especially which maven version is configured for the job ?

            Show
            kutzi kutzi added a comment - Can you show me the configuration of the job - especially which maven version is configured for the job ?
            Hide
            pawelg Pawel Gronkiewicz added a comment -

            This Maven version is used by other jobs without problem. I have tried changing it too. I will attach build settings.

            Show
            pawelg Pawel Gronkiewicz added a comment - This Maven version is used by other jobs without problem. I have tried changing it too. I will attach build settings.
            Hide
            kutzi kutzi added a comment -

            I don't really know how to continue. From the stacktrace it looks like the home directory of the used maven installation is null, but you say that the sam installation works fine for other jobs, so I don't know currently where to look.

            Show
            kutzi kutzi added a comment - I don't really know how to continue. From the stacktrace it looks like the home directory of the used maven installation is null, but you say that the sam installation works fine for other jobs, so I don't know currently where to look.
            Hide
            kutzi kutzi added a comment -

            Still having this problem?

            Show
            kutzi kutzi added a comment - Still having this problem?
            Hide
            pawelg Pawel Gronkiewicz added a comment -

            This bug is fixed after updating to Jenkins 1.525, which has a fix for related issue https://issues.jenkins-ci.org/browse/JENKINS-18898

            Show
            pawelg Pawel Gronkiewicz added a comment - This bug is fixed after updating to Jenkins 1.525, which has a fix for related issue https://issues.jenkins-ci.org/browse/JENKINS-18898

              People

              Assignee:
              vlatombe Vincent Latombe
              Reporter:
              pawelg Pawel Gronkiewicz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: