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

Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)

      If a Github repo is renamed, due to the fact that Github supports repository redirects (which doesn't seem possible to disable) Jenkins will create a repository and trigger a build for a repo under the old name and under the new name as well.

      Re-scanning the old repo name does not cause it to be removed.

      https://developer.github.com/changes/2015-07-21-automatic-redirects-for-renamed-repositories/

      This is problematic as it can confuse users and also trigger duplicate builds under the new and old repo names.

      Github branch source plugin 2.2.3

      Github API plugin 1.86

          [JENKINS-46068] Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)

          John Hovell created issue -
          Stephen Connolly made changes -
          Summary Original: Renaming Github repo causes duplicate projects / builds New: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)

          James Dumay added a comment -

          jhovell to clarify is this using a Github Organization Folder?

          James Dumay added a comment - jhovell to clarify is this using a Github Organization Folder?

          John Hovell added a comment -

          jamesdumay yes, I have only tested using a Github Organization folder.

          John Hovell added a comment - jamesdumay yes, I have only tested using a Github Organization folder.

          James Dumay added a comment -

          Thanks jhovell

          James Dumay added a comment - Thanks jhovell
          James Dumay made changes -
          Labels New: org-folder

          Joshua Noble added a comment -

          I'm also seeing this. Any ideas about a potential fix?

          Joshua Noble added a comment - I'm also seeing this. Any ideas about a potential fix?

          Under the covers, the Github Organization Folder should be tracking the repository ID (a number) instead of the name of the repository.

          Christian Höltje added a comment - Under the covers, the Github Organization Folder should be tracking the repository ID (a number) instead of the name of the repository.

          Simon Wydooghe added a comment - - edited

          I can confirm this behaviour after renaming a bunch of our repositories. What's the easiest workaround to remove the old repo in Jenkins for now?

          Simon Wydooghe added a comment - - edited I can confirm this behaviour after renaming a bunch of our repositories. What's the easiest workaround to remove the old repo in Jenkins for now?

          Phil Whelan added a comment -

          I'm hitting this too. It's a real pain not being able to remove a repo. Keen to hear a workaround for this, too, if anyone has one.

          Phil Whelan added a comment - I'm hitting this too. It's a real pain not being able to remove a repo. Keen to hear a workaround for this, too, if anyone has one.

            Unassigned Unassigned
            jhovell John Hovell
            Votes:
            7 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated: