[JIRA] (JENKINS-39218) Rebuild uses the wrong commit

Rebuild uses the wrong commit

Issue Type:	Bug
Assignee:	ragesh_nair
Attachments:	Screen Shot 2016-10-24 at 17.30.30.png, Screen Shot 2016-10-24 at 17.32.36.png
Components:	rebuild-plugin
Created:	2016/Oct/24 4:33 PM
Priority:	Major
Reporter:	Sam Deane

When clicking Rebuild on a job, I would expect it to rebuild using the exact same commit that the original used - that's surely the point?

However, the behaviour I'm observing is that it's using the commit of the last job that was run.

See attached screenshots. Job 6687 used commit 0c5ae798ca03ad75e54793660c8c9aeda028efcb, and yet the rebuild is using commit 28f803414b92115ab878f60d69a91d0262084ec4.

Am I misunderstanding what this plugin is supposed to do?

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

raquel.moreno.carmena@gmail.com (JIRA)

unread,

Oct 24, 2016, 5:03:01 PM10/24/16

to jenkinsc...@googlegroups.com

Rachel Moreno updated an issue

Jenkins /

Rebuild uses the wrong commit

Change By:	Rachel Moreno
Issue Type:	Bug Improvement

raquel.moreno.carmena@gmail.com (JIRA)

unread,

Oct 24, 2016, 5:05:01 PM10/24/16

to jenkinsc...@googlegroups.com

Rachel Moreno commented on

From Bug to Improvement, because this plugin only considers parameters: it allows the user to rebuild a parametrized build without entering the parameters again.

sam@elegantchaos.com (JIRA)

unread,

Oct 25, 2016, 4:36:01 AM10/25/16

to jenkinsc...@googlegroups.com

Sam Deane commented on

Ah, so I did misunderstand the purpose of the plugin?

Weird - I could have sworn that it used to work the way I described, but I'm obviously imagining things.

sam@elegantchaos.com (JIRA)

unread,

Oct 25, 2016, 4:37:02 AM10/25/16

to jenkinsc...@googlegroups.com

Sam Deane commented on

Is there any way to achieve what I want right now (re-run the same job, using the same commit), without having to resort to dummy commits to kick it off again?

I occasionally have to do this - if I encounter an error in our build scripts, for example.

raquel.moreno.carmena@gmail.com (JIRA)

unread,

Oct 25, 2016, 9:50:02 AM10/25/16

to jenkinsc...@googlegroups.com

Rachel Moreno commented on

I think there is no plugin with that feature, but I'd suggest you a workaround in your case.

In order not to change your job configuration disabling SCM configuration, you could create another job using its workspace:

Create another job
General > Advanced... > Use custom workspace:
Directory: $JENKINS_HOME/jobs/<under inspection job name>/workspace

It could be a parametrized job in which you provide the job name you want to debug (e.g. parameter with name JOB_NAME_UNDER_TEST):
Directory: $JENKINS_HOME/jobs/$JOB_NAME_UNDER_TEST/workspace

brian.murrell@intel.com (JIRA)

unread,

May 6, 2020, 9:52:03 AM5/6/20

to jenkinsc...@googlegroups.com

Brian J Murrell commented on

To be frank, rebuilding on the commit of the job that the Rebuild link was clicked from feels like a basic requirement of calling the functionality that this plugin provides rebuild.

Maybe the link that this plugin provides in a job's menu should be Re-use parameters or something. But unless using the same commit is included in the functionality, Rebuild probably deceives more people than it doesn't.