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

Runs that use the Git plugin do not always have changes

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • git-plugin
    • None

      It appears under common triggering scenarios the Git plugin does not produce changesets for runs.

      This is ticket should serve as an umbrella ticket for known problems such as JENKINS-42689 and there needs to be some further investigation to test that the Git plugin creates changesets under other conditions (basically we need to recheck everything).

      Steps to reproduce

      1. Fork the app-store-demo project on Github
      2. Create a new multibranch pipeline that uses the forked repository as a branch source.
      3. Ensure there is 1 run of the master branch
      4. Commit a change to the master branch with the message "Test"
      5. Manually run the branch

      Expected results
      You should see run 2 with one changeset that contains the commit ID and message of the "Test" commit.

      Problem
      There are no changesets associated with run 2.

          [JENKINS-44262] Runs that use the Git plugin do not always have changes

            Unassigned Unassigned
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: