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

Claim plugin serializes concurrent builds

XMLWordPrintable

      When executing builds in parallel*, some post-build actions force the builds to end in the same order they were started. Even if build #2 is ready, it has to wait until build #1 is done. Claim plugin is one such plugin that serializes build order.

      Would it be possible to fix the plugin such that it would not block later builds from finishing even if earlier build was still ongoing?

      *) option "Execute concurrent builds if necessary" in project configuration

      "Executor #4 for master : executing project-x #2 : waiting for Check point hudson.plugins.claim.ClaimPublisher on project-x #1" Id=96 Group=main WAITING on hudson.model.Run$RunExecution$CheckpointSet@3fd2670d
	at java.lang.Object.wait(Native Method)
	-  waiting on hudson.model.Run$RunExecution$CheckpointSet@3fd2670d
	at java.lang.Object.wait(Object.java:485)
	at hudson.model.Run$RunExecution$CheckpointSet.waitForCheckPoint(Run.java:1453)
	at hudson.model.Run.waitForCheckpoint(Run.java:1411)
	at hudson.model.CheckPoint.block(CheckPoint.java:144)
	at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:25)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)
	at hudson.model.Run.execute(Run.java:1617)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)

            Unassigned Unassigned
            salsa Sami Salonen
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: