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

After Jenkins updated to ver. 2.60.1 Caused: com.google.common.util.concurrent.UncheckedExecutionException

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Critical
    • Resolution: Unresolved
    • core
    • Jenkins ver. 2.60.1
      master - jdk1.8.0_112, Windows2008R2
      slave - jdk1.8.0_112, RHEL 6.5

    Description

      git-plugin does not cause this error

      Git plugin:
      Global Config user.name Value - null
      Global Config user.email Value - null
      Create new accounts based on author/committer's email - False

      1. Prerequisite:

      master Jenkins ver. 2.43 , jdk1.8.0_112, Windows2008R2
      slave1 - jdk1.7.0_51, RHEL 6.5
      slave2 - jdk1.7.0_51, RHEL 6.5

      2. Create:
      job1 Freestyle project(For Example: Empty job or add Shell Execute Block: sleep 300, gradle build)

      3. Update Jenkins:
      master to ver. 2.60.1, jdk1.8.0_112
      slave1 - slave.jar, jdk1.8.0_112
      slave2 - slave.jar, jdk1.8.0_112

      4. Configure slaves:
      Jenkins->Nodes->slave1->Configure->Labels: LabelRunJob
      Jenkins->Nodes->slave2->Configure->Labels: LabelRunJob

      5. Configure job1:
      Jenkins->View1->job1->Configure->Enable "This project is parameterized":
      Add Label:
      Name: LabelRunJob
      Default Value: LabelRunJob
      Disable "Run on all nodes matching the label"

      6. Run job1 on slaves(parallel run job)
      After 10-50 success build, get:
      Caused: com.google.common.util.concurrent.UncheckedExecutionException

      Workarщund:
      Create new job2 copy from job1
      or
      Create new Node slave3 copy from slave1
      and
      Create new Node slave4 copy from slave2

      Log and build.xml in attach

      Attachments

        1. build_without_git-plugin.xml
          4 kB
        2. build.xml
          8 kB
        3. Log_without_git-plugin.txt
          2 kB
        4. Log.txt
          2 kB

        Activity

          danielbeck Daniel Beck added a comment -

          git-plugin does not cause this error

          Interesting. The stack trace still says

           at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:452)

          and the build.xml contains

            <scm class="hudson.plugins.git.GitChangeLogParser" plugin="git@3.5.0">
              <authorOrCommitter>false</authorOrCommitter>
            </scm>

          So something is going on here.

          danielbeck Daniel Beck added a comment - git-plugin does not cause this error Interesting. The stack trace still says  at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:452) and the build.xml contains   <scm class="hudson.plugins.git.GitChangeLogParser" plugin="git@3.5.0">     <authorOrCommitter>false</authorOrCommitter>   </scm> So something is going on here.
          zolotorevsky Vitaly Zolotorevsky added a comment - - edited

          if run job without git-plugin whatever get error

          zolotorevsky Vitaly Zolotorevsky added a comment - - edited if run job without git-plugin whatever get error

          add Log and build.xml without using git-plugin

          zolotorevsky Vitaly Zolotorevsky added a comment - add Log and build.xml without using git-plugin
          danielbeck Daniel Beck added a comment -
          at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:379)
          at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:452)

          It's still being called.

          Nobody's claiming you're manually configuring it, but undoubtedly it's still being used.

          danielbeck Daniel Beck added a comment - at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:379) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:452) It's still being called. Nobody's claiming you're manually configuring it, but undoubtedly it's still being used.
          danielbeck Daniel Beck added a comment -

          However, it looks like the job in question had Git SCM configured in the past. Specifically, in older build.xml after the previous successful build. So if the same job ever had Git configured, that could be enough for this to be triggered.

          danielbeck Daniel Beck added a comment - However, it looks like the job in question had Git SCM configured in the past. Specifically, in older build.xml after the previous successful build. So if the same job ever had Git configured, that could be enough for this to be triggered.

          People

            Unassigned Unassigned
            zolotorevsky Vitaly Zolotorevsky
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: