-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.176.2
git-plugin 2.8.0
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
- is related to
-
JENKINS-57089 Tag fails with merge before build triggered by GitLab
-
- Open
-
[JENKINS-59008] Merge before build, reference is not a tree on second build
Assignee | Original: Mark Waite [ markewaite ] |
Attachment | New: config.xml [ 48383 ] |
Assignee | New: Mark Waite [ markewaite ] |
Summary | Original: Merge before build, reference is not a tree on second build | New: Merge before build, reference is not a tree on second build if merge target is a tag |
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