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

[docwhat@gerf.org (JIRA)]

Christian Höltje commented on JENKINS-46068

Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) Under the covers, the Github Organization Folder should be tracking the repository ID (a number) instead of the name of the repository. Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[simon@wydooghe.com (JIRA)]

Simon Wydooghe commented on JENKINS-46068

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

I can confirm this behaviour after renaming a bunch of our repositories.

Add Comment

[simon@wydooghe.com (JIRA)]

Simon Wydooghe edited a comment on JENKINS-46068

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

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?

Add Comment

[phil.whelan@bench.co (JIRA)]

Phil Whelan commented on JENKINS-46068

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

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.

Add Comment

[simon@wydooghe.com (JIRA)]

Simon Wydooghe edited a comment on JENKINS-46068

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

[~philw_bench] You can delete the job directory and reload the Jenkins configuration for now I think. Still a pain in the ass ;)

Add Comment

[simon@wydooghe.com (JIRA)]

Simon Wydooghe commented on JENKINS-46068

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

Phil Whelan You can delete the job directory and reload the Jenkins configuration for now I think.

Add Comment

[phil.whelan@bench.co (JIRA)]

Phil Whelan commented on JENKINS-46068

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

Thanks Simon Wydooghe! My solution was to exclude the names via the regex setting for this plugin.

Add Comment

[docwhat@gerf.org (JIRA)]

Christian Höltje commented on JENKINS-46068

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

If you don't care about the history, you can do this: 1. Rename the repository 'original' to 'classic' in github. 2. Create a new repository 'original' 3. Delete the (empty) repository 'original' This deletes the redirect. It's a crappy workaround and loses the history.

Add Comment

[docwhat@gerf.org (JIRA)]

Christian Höltje commented on JENKINS-46068

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

Under the covers, the plugin should be using the repository ID for tracking, not the name. The name is changeable, but the ID isn't.

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[vivek.pandey@gmail.com (JIRA)]

Vivek Pandey updated an issue

Jenkins / JENKINS-46068

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

Change By: Vivek Pandey Labels: org-folder triaged-2018-11

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[avadhmr@gmail.com (JIRA)]

Avadh Sharma commented on JENKINS-46068

Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) I'm also seeing this. Any fix planned?

Add Comment

[pibeitz@gmail.com (JIRA)]

Pierre Beitz commented on JENKINS-46068

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

Seeing the issue, although no new build is triggered on the old job anymore. I believe this is still the same issue though, part of it was fixed somehow since this bug was reported.

Add Comment

[jtaboada@cloudbees.com (JIRA)]

Jose Blas Camacho Taboada assigned an issue to Jose Blas Camacho Taboada

Jenkins / JENKINS-46068

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

Change By: Jose Blas Camacho Taboada Assignee: Jose Blas Camacho Taboada

Add Comment

[jtaboada@cloudbees.com (JIRA)]

Jose Blas Camacho Taboada started work on JENKINS-46068

Change By: Jose Blas Camacho Taboada

Status: Open In Progress

Add Comment

[jtaboada@cloudbees.com (JIRA)]

Jose Blas Camacho Taboada commented on JENKINS-46068

Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) This issue is already fixed in version 2.5.4 snapshot;

Add Comment

[jtaboada@cloudbees.com (JIRA)]

Jose Blas Camacho Taboada updated JENKINS-46068

Jenkins / JENKINS-46068

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

Change By: Jose Blas Camacho Taboada

Status: In Progress Fixed but Unreleased Resolution: Fixed

Add Comment

[jtaboada@cloudbees.com (JIRA)]

Jose Blas Camacho Taboada edited a comment on JENKINS-46068

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

This issue is already fixed in version 2.5. 4 snapshot; 3

Add Comment

[jtaboada@cloudbees.com (JIRA)]

Jose Blas Camacho Taboada updated JENKINS-46068

Jenkins / JENKINS-46068

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

Change By: Jose Blas Camacho Taboada

Status: Fixed but Unreleased Closed

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord commented on JENKINS-46068

Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) and yet nothing in the release notes for 2.5.3?

Add Comment