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

Parameterized Trigger Plugin should print link to running job

    XMLWordPrintable

    Details

    • Similar Issues:
    • Released As:
      Parameterized Trigger 2.36

      Description

      We have some jobs that use this plugin to launch a child job execution. A major usability headache is that you can't directly find the child execution from the parent. A link is printed to the parent job at the start, and to the specific execution once it completes, but if you look at a life job, you have to go scrounging through lists of running jobs to find the child job. E.g. if you look at this log output, the job ID is only printed several hours after the job actual starts.

      18:58:00 Waiting for the completion of parallel-all-tests
      00:12:05 parallel-all-tests #5574 completed. Result was SUCCESS
       

       

      I started working on a potential patch for this - https://github.com/timarmstrong/parameterized-trigger-plugin

      I haven't worked on Jenkins code at all so would welcome feedback on whether this makes any sense and whether I'm heading in an appropriate direction.

        Attachments

          Activity

          tarmstrong_cloudera Tim Armstrong created issue -
          tarmstrong_cloudera Tim Armstrong made changes -
          Field Original Value New Value
          Description He have some jobs that use this plugin to launch a child job execution. A major usability headache is that you can't directly find the child execution from the parent. A link is printed to the parent job at the start, and to the specific execution once it completes, but if you look at a life job, you have to go scrounging through lists of running jobs to find the child job.
          {noformat}
          18:58:00 Waiting for the completion of parallel-all-tests
          00:12:05 parallel-all-tests #5574 completed. Result was SUCCESS
           {noformat}
           

          I started working on a potential patch for this - https://github.com/timarmstrong/parameterized-trigger-plugin

          I haven't worked on Jenkins code at all so would welcome feedback on whether this makes any sense and whether I'm heading in an appropriate direction.
          We have some jobs that use this plugin to launch a child job execution. A major usability headache is that you can't directly find the child execution from the parent. A link is printed to the parent job at the start, and to the specific execution once it completes, but if you look at a life job, you have to go scrounging through lists of running jobs to find the child job. E.g. if you look at this log output, the job ID is only printed several hours after the job actual starts.
          {noformat}
          18:58:00 Waiting for the completion of parallel-all-tests
          00:12:05 parallel-all-tests #5574 completed. Result was SUCCESS
           {noformat}
           

          I started working on a potential patch for this - https://github.com/timarmstrong/parameterized-trigger-plugin

          I haven't worked on Jenkins code at all so would welcome feedback on whether this makes any sense and whether I'm heading in an appropriate direction.
          tarmstrong_cloudera Tim Armstrong made changes -
          Attachment image.png [ 47213 ]
          tarmstrong_cloudera Tim Armstrong made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          tarmstrong_cloudera Tim Armstrong made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Fixed but Unreleased [ 10203 ]
          oleg_nenashev Oleg Nenashev made changes -
          Released As Parameterized Trigger 2.36
          Status Fixed but Unreleased [ 10203 ] Resolved [ 5 ]

            People

            Assignee:
            tarmstrong_cloudera Tim Armstrong
            Reporter:
            tarmstrong_cloudera Tim Armstrong
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: