[JIRA] (JENKINS-57442) Parameterized Trigger Plugin should print link to running job

tarmstrong@cloudera.com (JIRA)

unread,

May 13, 2019, 8:36:03 PM5/13/19

to jenkinsc...@googlegroups.com

Tim Armstrong created an issue

Jenkins /

JENKINS-57442

Parameterized Trigger Plugin should print link to running job

Issue Type:	Improvement
Assignee:	Tim Armstrong
Components:	parameterized-trigger-plugin
Created:	2019-05-14 00:35
Labels:	user-experience
Priority:	Minor
Reporter:	Tim Armstrong

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.

 
                                                                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.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

tarmstrong@cloudera.com (JIRA)

unread,

May 13, 2019, 8:36:03 PM5/13/19

to jenkinsc...@googlegroups.com

Tim Armstrong updated an issue

Jenkins /

JENKINS-57442

Parameterized Trigger Plugin should print link to running job

Change By:	Tim Armstrong

He 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.