-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
git-plugin:4.0.0 git-client-plugin:3.0.0. Jenkins:2.204. AWS Linux AMI 2.
Sometimes when building an existing multi-branch pipeline, the build is incorrectly regarded as first-time. The console log shows "First time build. Skipping changelog." ,and the build-overview says "no changes", both incorrectly.
This results in confusion whether commits/merges have been done correctly as they are not visible.
[JENKINS-60159] Multibranch pipeline - existing branch seen as first time build
Description |
Original:
Sometimes when building an existing multi-branch pipeline, the build is incorrectly regarded as first-time. The console log shows: First time build. Skipping changelog. |
New: Sometimes when building an existing multi-branch pipeline, the build is incorrectly regarded as first-time. The console log shows "First time build. Skipping changelog." ,and the build-overview says "no changes", both incorrectly. |
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Description | Original: Sometimes when building an existing multi-branch pipeline, the build is incorrectly regarded as first-time. The console log shows "First time build. Skipping changelog." ,and the build-overview says "no changes", both incorrectly. |
New:
Sometimes when building an existing multi-branch pipeline, the build is incorrectly regarded as first-time. The console log shows "First time build. Skipping changelog." ,and the build-overview says "no changes", both incorrectly. This results in confusion whether merges have |
Description |
Original:
Sometimes when building an existing multi-branch pipeline, the build is incorrectly regarded as first-time. The console log shows "First time build. Skipping changelog." ,and the build-overview says "no changes", both incorrectly. This results in confusion whether merges have |
New:
Sometimes when building an existing multi-branch pipeline, the build is incorrectly regarded as first-time. The console log shows "First time build. Skipping changelog." ,and the build-overview says "no changes", both incorrectly. This results in confusion whether commits/merges have been done correctly as they are not visible. |
Assignee | Original: Mark Waite [ markewaite ] |
Can you provide more details about conditions that might cause a build to be identified as a first-time build?
Were there specific changes that happened at the time in the git repository, in the job definition, or in the agent definitions?
Are you using ephemeral or static agents?
I inserted detection checks into several of my test jobs in hopes of seeing it, but did not see it. Will need more details in order to duplicate the problem.
Any other hints that might make the problem repeatable?