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

Should not be able to re-run a successful pipeline from a favourite card

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • blueocean-plugin
    • None

      Scope

      • Hide the rerun action on successful state favourite cards

      Original request
      The main dashboard at $JENKINS_URL/jenkins/blue/pipelines allows you to both re-run (sic) and run a pipeline.

      However you should not allow a user to re-run the pipeline as there is no link to what is re-run.
      You can not re-run a job, only a build and given there is no build context displayed it may not be the expecte outcome for a user if they cliecked re-run when a new build had just been kicked off.

      Re-run (replay) should be reserved for displaying soley on a build.

          [JENKINS-42353] Should not be able to re-run a successful pipeline from a favourite card

          James Nord created issue -
          James Nord made changes -
          Attachment New: incorrect use of re-run.png [ 36169 ]
          James Nord made changes -
          Description Original: The main dashboard at $JENKINS_URL/jenkins/blue/pipelines allows you to both re-run (sic) and run a pipeline.

          However you should not allow a user to re-run the pipeline as there is no link to what is re-run.
          You can not re-run a job, only a build and given there is no build context displayed it may not be the expecte outcome for a user if they cliecked re-run when a new build had just been kicked off.

          Re-run (replay) should be reserved for displaying soley on a build.
          New: The main dashboard at $JENKINS_URL/jenkins/blue/pipelines allows you to both re-run (sic) and run a pipeline.

          However you should not allow a user to re-run the pipeline as there is no link to what is re-run.
          You can not re-run a job, only a build and given there is no build context displayed it may not be the expecte outcome for a user if they cliecked re-run when a new build had just been kicked off.

          Re-run (replay) should be reserved for displaying soley on a build.

           !incorrect use of re-run.png|thumbnail!
          James Dumay made changes -
          Summary Original: should not be able to re-run a pipleine from the main dashboard New: Should not be able to re-run a successful pipeline from the Blue Ocean dashboard
          James Dumay made changes -
          Summary Original: Should not be able to re-run a successful pipeline from the Blue Ocean dashboard New: Should not be able to re-run a successful pipeline from a favourite card
          James Dumay made changes -
          Description Original: The main dashboard at $JENKINS_URL/jenkins/blue/pipelines allows you to both re-run (sic) and run a pipeline.

          However you should not allow a user to re-run the pipeline as there is no link to what is re-run.
          You can not re-run a job, only a build and given there is no build context displayed it may not be the expecte outcome for a user if they cliecked re-run when a new build had just been kicked off.

          Re-run (replay) should be reserved for displaying soley on a build.

           !incorrect use of re-run.png|thumbnail!
          New: *Scope*
          * Hide the rerun action on successful state favourite cards

          *Original request*
          The main dashboard at $JENKINS_URL/jenkins/blue/pipelines allows you to both re-run (sic) and run a pipeline.

          However you should not allow a user to re-run the pipeline as there is no link to what is re-run.
          You can not re-run a job, only a build and given there is no build context displayed it may not be the expecte outcome for a user if they cliecked re-run when a new build had just been kicked off.

          Re-run (replay) should be reserved for displaying soley on a build.

           !incorrect use of re-run.png|thumbnail!
          James Dumay made changes -
          Epic Link New: JENKINS-35761 [ 171656 ]

          James Nord added a comment -

          jamesdumay why is this special for a successful pipeline. a failed pipeline will exhibit exactly the same issues.

          James Nord added a comment - jamesdumay why is this special for a successful pipeline. a failed pipeline will exhibit exactly the same issues.

          James Dumay added a comment -

          teilo we frequently use it to restart our deployment job when it fails. I am not sure about removing it (yours is the first data point).

          James Dumay added a comment - teilo we frequently use it to restart our deployment job when it fails. I am not sure about removing it (yours is the first data point).

          James Dumay added a comment -

          James Dumay added a comment - michaelneale WDYT?

            Unassigned Unassigned
            teilo James Nord
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: