[JIRA] (JENKINS-59008) Merge before build, reference is not a tree on second build

[petekol@mail.ru (JIRA)]

P K created an issue

Jenkins / JENKINS-59008 Merge before build, reference is not a tree on second build Issue Type: Bug Assignee: Mark Waite Attachments: first-good.txt, second-bad.txt Components: git-plugin Created: 2019-08-20 11:05 Environment: 2.176.2 git-plugin 2.8.0 Priority: Major Reporter: P K Pipeline Jenkins build with SCM: GIT Branches to build: refs/tags/*_${RELEASE}_feature Additional Behaviours: Merge before build   first polled build is ok (change is detected and merged), see log second build triggered by hand gets error (no change), see log   Add Comment

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

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build Is SHA-1 a487d775943bc781fc0425601a15cb7445c67c6a a valid SHA-1 in any of the repositories involved in the (failing) second job? For example, are you using a pipeline shared library and is that SHA-1 one of the commits in the pipeline shared library?

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite edited a comment on JENKINS-59008

Re: Merge before build, reference is not a tree on second build

Is SHA-1 a487d775943bc781fc0425601a15cb7445c67c6a a valid SHA-1 in any of the repositories involved in the (failing) second job?  For example, are you using a pipeline shared library and is that SHA-1 one of the commits in the pipeline shared library?

Was able to answer my own question. That must be a valid SHA-1 in the repository since the first build succeeds using the same SHA-1

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build

I don't know how to duplicate the conditions you're seeing. Refer to the JENKINS-51638 verification job and its contributor branch in the JENKINS-51638-project-1 branch for an example of what I've attempted. Does the "branches to build" need to be a tag? Does it behave differently if you use a branch instead of a tag? My test case did not attempt to use a tag, just two branches.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-59008

Merge before build, reference is not a tree on second build

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[petekol@mail.ru (JIRA)]

P K commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build it should be a tag for my project and i can reproduce the error. i'll try branch later on.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build

Can you provide the config.xml of the job? The failure mode is surprising, though it may be similar to a recent report related to tags and merges.

Add Comment

[petekol@mail.ru (JIRA)]

P K updated an issue

Jenkins / JENKINS-59008

Merge before build, reference is not a tree on second build

Change By: P K Attachment: config.xml

Add Comment

[petekol@mail.ru (JIRA)]

P K commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build see the config attached...

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Mark Waite

Jenkins / JENKINS-59008

Merge before build, reference is not a tree on second build

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[petekol@mail.ru (JIRA)]

P K updated an issue

Jenkins / JENKINS-59008 Merge before build, reference is not a tree on second build

Change By: P K Summary: Merge before build, reference is not a tree on second build if merge target is a tag

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build Sorry, I don't know what's different between your failing cases and my working cases. I've completed my investigation and placed my results into publicly accessible locations. I'll rely on you to compare my working cases and your failing cases. Jenkinsfile on first branch that confirms pre-build merge works with branch targets and confirms it does not work with tag targets Jenkinsfile on second branch that confirms pre-build merge works with branch targets and confirms it does not work with tag targets Docker image definition that uses the Jenkinsfile to run the job (and many others)

Add Comment

[petekol@mail.ru (JIRA)]

P K commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build

please add push at the end of your Jenkinsfile without push it works and has always somthing to merge!!!

Add Comment

[petekol@mail.ru (JIRA)]

P K commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build

any progress on this?????

Add Comment

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

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build

No progress and none planned.

Add Comment

[petekol@mail.ru (JIRA)]

P K commented on JENKINS-59008

Re: Merge before build, reference is not a tree on second build

great! see my last comment and retest with push

Add Comment