[JIRA] (JENKINS-60067) The custom build name not seen until the job is executing

[mi+jenkins-2019@aldan.algebra.com (JIRA)]

Mikhail T created an issue

Jenkins / JENKINS-60067 The custom build name not seen until the job is executing Issue Type: Bug Assignee: Damian Szczepanik Attachments: image-2019-11-05-17-32-52-344.png Components: build-name-setter-plugin Created: 2019-11-05 22:34 Priority: Minor Reporter: Mikhail T Although the buildname is nicely set, when the job begins executing, it is not seen, while the job is pending: It would've been a lot nicer otherwise... Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[mi+jenkins-2019@aldan.algebra.com (JIRA)]

Mikhail T updated an issue

Jenkins / JENKINS-60067 The custom build name not seen until the job is executing

Change By: Mikhail T Labels: regression

Add Comment

[mi+jenkins-2019@aldan.algebra.com (JIRA)]

[damian.publicemail@gmail.com (JIRA)]

Damian Szczepanik resolved as Not A Defect

Jenkins / JENKINS-60067 The custom build name not seen until the job is executing

Change By: Damian Szczepanik Status: Open Resolved Resolution: Not A Defect

Add Comment

[damian.publicemail@gmail.com (JIRA)]

Damian Szczepanik commented on JENKINS-60067

Re: The custom build name not seen until the job is executing If you configure as a post action it won't be but if you set at the beginning or via properties then it should

Add Comment

[mi+jenkins-2019@aldan.algebra.com (JIRA)]

Mikhail T reopened an issue

I do have both pre- and post- enabled. You can see on my screenshot, that the name of the build #33 is indeed set before the build is over. But the #34, #35, and #36 remain nameless – until the building actually starts.

Jenkins / JENKINS-60067

The custom build name not seen until the job is executing

Change By: Mikhail T Resolution: Not A Defect Status: Resolved Reopened

Add Comment

[mi+jenkins-2019@aldan.algebra.com (JIRA)]

Mikhail T edited a comment on JENKINS-60067

Re: The custom build name not seen until the job is executing I do have both pre- and post- enabled. You can see on my screenshot, that the name of the build #33 is indeed set _before_ the build is over. But the #34, #35, and #36 remain nameless -- – until the building actually starts. Here is the snapshot of the configuration – note both check-boxes: !image-2019-11-07-09-28-27-829.png!

Add Comment

[damian.publicemail@gmail.com (JIRA)]

Damian Szczepanik commented on JENKINS-60067

Re: The custom build name not seen until the job is executing

Pending means not started AFAIR and then that's why name is not updated. This is quite expected.

Add Comment

[mi+jenkins-2019@aldan.algebra.com (JIRA)]

Mikhail T commented on JENKINS-60067

Re: The custom build name not seen until the job is executing

Yes, "pending" means not started, but why not set the name already? Is it a Jenkins' limitation (no job-specific code is invoked until actual start), or something else?

Add Comment