I care about history, so I'll wait.

On Thursday, February 18, 2021 at 5:52:09 PM UTC+1 Harry G. wrote:

> If you cannot delete on disk, I see only 2 options left:
> - wait until the bug is fixed 
> https://issues.jenkins.io/browse/JENKINS-64894 - might take some time I 
> guess 
> - if you don't care about build history, delete and recreate the entire 
> multibranch project and re-scan
>
> [email protected] schrieb am Mittwoch, 17. Februar 2021 um 19:25:24 
> UTC+1:
>
>> Here at my end the display name of the old repo is not changed.
>> Other than that, same symptoms.
>>
>> I do not have access to the disk that contains the Jenkins folders, as 
>> this is a server managed by our hosting company, and currently I do not 
>> feel comfortable with them digging deep down into the Jenkins internals.
>>
>> On Wed, Feb 17, 2021 at 6:18 PM 'Harry G.' via Jenkins Users <
>> [email protected]> wrote:
>>
>>> We have the same issue. 
>>> Dropdown delete only works for disabled branches, not for repos.
>>> And it's even worse: Jenkins recognizes the new repo name and also 
>>> renames the display name, which looks like duplicated folders if you don't 
>>> check the URL!
>>>
>>> The only workaround I see currently is to delete the folder on disk and 
>>> reload config from disk.
>>>
>>> As this seems to be a clear bug, I filed it now: 
>>> https://issues.jenkins.io/browse/JENKINS-64894
>>> This is more serious as it sounds, as it is very confusing for the users 
>>> because of the duplicate folder with same display name. 
>>> Mark Waite schrieb am Mittwoch, 17. Februar 2021 um 15:55:26 UTC+1:
>>>
>>>> I've used the "Delete" selection from the dropdown menu to remove 
>>>> individual builds (like the disabled PR jobs that are visible on 
>>>> ci.jenkins.io) and pull request jobs.  Maybe that would work for 
>>>> disabled organization folder jobs as well?
>>>>
>>>> On Wed, Feb 17, 2021 at 6:32 AM Amedee Van Gasse <[email protected]> 
>>>> wrote:
>>>>
>>>>> I have a Bitbucket project organization folder.
>>>>> Each repository inside the project is a multibranch pipeline.
>>>>>
>>>>> A few weeks ago one of the repositories inside the project was renamed.
>>>>> The old repository name is still shown in Jenkins, as disabled.
>>>>>
>>>>> How do I remove the old repository name?
>>>>> I have already done multiple scans of the organization folder.
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "Jenkins Users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to [email protected].
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/fe34c100-5d4e-4fc8-87a0-4646f94905c9n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/fe34c100-5d4e-4fc8-87a0-4646f94905c9n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> -- 
>>>
>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-users/TcGPnRFZZvA/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/adcf1da2-254c-4f22-877c-6b5ee0ba8704n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/adcf1da2-254c-4f22-877c-6b5ee0ba8704n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>
>>
>> -- 
>> Amedee Van Gasse
>> Email: [email protected]
>> Calendar: [email protected]
>> Phone: +32 485 805 674
>> Twitter: @amedee
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/65f23d04-3845-4f7c-936f-da1c444c6cf0n%40googlegroups.com.

Reply via email to