Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60159

Multibranch pipeline - existing branch seen as first time build

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      git-plugin:4.0.0 git-client-plugin:3.0.0. Jenkins:2.204. AWS Linux AMI 2.
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          thomasminke Thomas Minke created issue -
          thomasminke Thomas Minke made changes -
          Field Original Value New Value
          Description 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.
          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.
          thomasminke Thomas Minke made changes -
          Priority Major [ 3 ] Minor [ 4 ]
          thomasminke Thomas Minke made changes -
          Description 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. 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
          thomasminke Thomas Minke made changes -
          Description 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
          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.
          Hide
          markewaite Mark Waite added a comment - - edited

          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?

          Show
          markewaite Mark Waite added a comment - - edited 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?
          markewaite Mark Waite made changes -
          Assignee Mark Waite [ markewaite ]
          Hide
          thomasminke Thomas Minke added a comment -

          Hi Mark Waite, thanks for your quick response. I'm looking for more info to reproduce this issue, but I'm afraid I've got very little.

          • Today, 4 out of 5 builds show as 'first-time' in the console logs, and 1 shows a changelog.
          • These builds were both after branch merges and direct commits. Nothing irregular in the Git repository as far as I can see.
          • The Jenkinsfile was not changed in all of the builds.
          • We use a static agent with one SSH slave. All 5 builds that I started today ran on this SSH slave.  

          Do you have any hints which information would be relevant for reproducing or debugging? 

          Show
          thomasminke Thomas Minke added a comment - Hi Mark Waite , thanks for your quick response. I'm looking for more info to reproduce this issue, but I'm afraid I've got very little. Today, 4 out of 5 builds show as 'first-time' in the console logs, and 1 shows a changelog. These builds were both after branch merges and direct commits. Nothing irregular in the Git repository as far as I can see. The Jenkinsfile was not changed in all of the builds. We use a static agent with one SSH slave. All 5 builds that I started today ran on this SSH slave.   Do you have any hints which information would be relevant for reproducing or debugging? 
          Hide
          thomasminke Thomas Minke added a comment -

          Mark Waite, one other thing: we have another issue at the moment regarding Git checkout. Sometimes the checkout fails with an error message, without failing the build. This results in a deployment of the code without updating. I will create a separate issue for this, but it might be related.

          Show
          thomasminke Thomas Minke added a comment - Mark Waite , one other thing: we have another issue at the moment regarding Git checkout. Sometimes the checkout fails with an error message, without failing the build. This results in a deployment of the code without updating. I will create a separate issue for this, but it might be related.
          Hide
          markewaite Mark Waite added a comment -

          I'm not aware of cases where a checkout fails and does not fail the build. Definitely provide examples of the problem in a separate issue.

          Show
          markewaite Mark Waite added a comment - I'm not aware of cases where a checkout fails and does not fail the build. Definitely provide examples of the problem in a separate issue.
          Hide
          mkroell Michael Kroell added a comment -

          I wanted to report I am experiencing this issue as well, which results in some plugins for Jira not working.

          Show
          mkroell Michael Kroell added a comment - I wanted to report I am experiencing this issue as well, which results in some plugins for Jira not working.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            thomasminke Thomas Minke
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated: