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

Retrigger jobs

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Sometimes, for different reasons, you need to run a job that has been triggered again.
      It could be because of a communication error with the git repo or the connection to Gerrit went down when the approve command was supposed to be sent.
      Instead of creating a new patch and upload it to Gerrit it should be possible to click a button that runs the job again and reports the result back to Gerrit.

      Sub-features:
      Retrigger one job: Rebuild just one job, if multiple jobs where triggered before the build results from the old jobs should count in the final approve report.
      Retrigger all jobs: Rebuild all jobs that was triggered before on the patchset event.

        Attachments

          Activity

          Hide
          rsandell rsandell added a comment -

          Retrigger one job pushed to master @ http://github.com/hudson/gerrit-trigger-plugin commit: 89ae85cc447d8d1d53eb

          Show
          rsandell rsandell added a comment - Retrigger one job pushed to master @ http://github.com/hudson/gerrit-trigger-plugin commit: 89ae85cc447d8d1d53eb
          Hide
          antonystubbs antonystubbs added a comment -

          Excellent! this will really really help with my disconnecting problem (JENKINS-6965) What's the easiest way for me to get this into my Hudson?

          Show
          antonystubbs antonystubbs added a comment - Excellent! this will really really help with my disconnecting problem ( JENKINS-6965 ) What's the easiest way for me to get this into my Hudson?
          Hide
          rsandell rsandell added a comment -

          The quickest way would be to download the code from GitHub, build it and install it.

          The easiest way would be to wait a couple of days when I will release version 2.1 and you'll be able to install it as usual

          Show
          rsandell rsandell added a comment - The quickest way would be to download the code from GitHub, build it and install it. The easiest way would be to wait a couple of days when I will release version 2.1 and you'll be able to install it as usual
          Hide
          rsandell rsandell added a comment -

          Pushed to master @ http://github.com/hudson/gerrit-trigger-plugin commit: 7ed09ee0df9690ba5d80

          Show
          rsandell rsandell added a comment - Pushed to master @ http://github.com/hudson/gerrit-trigger-plugin commit: 7ed09ee0df9690ba5d80
          Hide
          antonystubbs antonystubbs added a comment -

          Ok, I've installed the plugin update. Am I missing something here? How do you actually trigger a re-build of a given gerrit patch set?

          Show
          antonystubbs antonystubbs added a comment - Ok, I've installed the plugin update. Am I missing something here? How do you actually trigger a re-build of a given gerrit patch set?
          Hide
          antonystubbs antonystubbs added a comment -

          Ah - ok. Note to everyone else: the re-trigger button only appears on builds performed by the new version of gerrit-trigger. I.e. you can't re-trigger your old builds. :/ that's a shame.

          Show
          antonystubbs antonystubbs added a comment - Ah - ok. Note to everyone else: the re-trigger button only appears on builds performed by the new version of gerrit-trigger. I.e. you can't re-trigger your old builds. :/ that's a shame.

            People

            • Assignee:
              rsandell rsandell
              Reporter:
              rsandell rsandell
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: