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

The rebuild action doesn't reset the pipeline

      I have the following pipeline:

      1. Job A (Build - Build Branch) automatically triggers Job B
      2. Job B (Build - Ready) manually triggers Job C
      3. Job C (Dev - Deploy) manually triggers job D (Dev - Integrate).
        The pipeline is configured to allow manual triggers and rebuilds.

      I build Job A, B and C and all pass. The pipeline shows ok (build.png).

      If I rebuild the job B (Build - Ready), the jobs (C and D) that follow job B are not reset and are shown having the previous results. (rebuild.png). The same behaviour is even if the job B fails after rebuild.

      If I run again the pipeline by building manually the Job A, all the jobs are reset.

      I checked the same scenarios in the build pipeline plugin and there the issue doesn't reproduce.

        1. build.png
          build.png
          66 kB
        2. rebuild.png
          rebuild.png
          64 kB

          [JENKINS-30100] The rebuild action doesn't reset the pipeline

          This issue reproduces also on the latest plugin version.

          Marius Balteanu added a comment - This issue reproduces also on the latest plugin version.

          Jiri Tyr added a comment -

          If patbos would elaborate what's necessary to do in the plugin, I would try to fix it.

          Jiri Tyr added a comment - If patbos would elaborate what's necessary to do in the plugin, I would try to fix it.

          Tommy Tynjä added a comment -

          marius_balteanu jtyr Sorry for the slow response. In which version did you encounter the specific issue? Can you reproduce it with the latest release (0.10.1)?

          Tommy Tynjä added a comment - marius_balteanu jtyr Sorry for the slow response. In which version did you encounter the specific issue? Can you reproduce it with the latest release (0.10.1)?

          Hi Tommy, I'm not using anymore this plugin, I've moved to Jenkins Pipelines.

          Marius Balteanu added a comment - Hi Tommy, I'm not using anymore this plugin, I've moved to Jenkins Pipelines.

          Jiri Tyr added a comment -

          I can confirm that the reported issue is still present in the latest release (v0.10.1).

          Jiri Tyr added a comment - I can confirm that the reported issue is still present in the latest release (v0.10.1).

          Tommy Tynjä added a comment -

          jtyr Thank you for confirming this. Do you think you could help us in solving this? You could try to reproduce this with a simple pipeline and debug, or do this through our unit test framework. If you check out the source code, you could e.g. start the project (mvn hpi:run) in debug mode in an IDE.

          Tommy Tynjä added a comment - jtyr Thank you for confirming this. Do you think you could help us in solving this? You could try to reproduce this with a simple pipeline and debug, or do this through our unit test framework. If you check out the source code, you could e.g. start the project (mvn hpi:run) in debug mode in an IDE.

          Jiri Tyr added a comment - - edited

          I think it would be better if you would do the debugging, tommysdk. You can use JJB and the following definition to create the jobs:

          http://pastebin.com/irdxqnR1

          Just create the Delivery Pipeline View with the following configuration:

          • Enable start of new pipeline build
          • Enable manual triggers
          • Enable rebuild
          • Set the Test1 job as the Initial Job

          Then trigger a new pipeline, trigger the job Test2, then trigger the job Test3a. Then rebuild the Test2. You will see that the job Test3a and Test3b will stay active and ready to be built/rebuilt even though the job Test2 was rebuilt. Expected behavior is that the job Test3a and Test3b will become disabled as soon as the Test2 is rebuilt.

          Jiri Tyr added a comment - - edited I think it would be better if you would do the debugging, tommysdk . You can use JJB and the following definition to create the jobs: http://pastebin.com/irdxqnR1 Just create the Delivery Pipeline View with the following configuration: Enable start of new pipeline build Enable manual triggers Enable rebuild Set the Test1 job as the Initial Job Then trigger a new pipeline, trigger the job Test2, then trigger the job Test3a. Then rebuild the Test2. You will see that the job Test3a and Test3b will stay active and ready to be built/rebuilt even though the job Test2 was rebuilt. Expected behavior is that the job Test3a and Test3b will become disabled as soon as the Test2 is rebuilt.

          Tommy Tynjä added a comment -

          jtyr Thank you for providing details about how to reproduce the behaviour. We'll take a look as soon we have the chance.

          Tommy Tynjä added a comment - jtyr Thank you for providing details about how to reproduce the behaviour. We'll take a look as soon we have the chance.

          Tommy Tynjä added a comment -

          This is still an issue when using rebuild together with manual triggers (on version 1.0.0).

          Tommy Tynjä added a comment - This is still an issue when using rebuild together with manual triggers (on version 1.0.0).

            tommysdk Tommy Tynjä
            marius_balteanu Marius Balteanu
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: