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 alr
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
wrote:
>
Can anyone please help me?
Regards,
Venkatesh
On Tue, Feb 16, 2021 at 5:22 PM Ven H wrote:
> Thank you very much for your reply, Mark. Unfortunately, that is also not
> working for me. Can you please provide some samples? I can see from the
> Plugin documentation that it is excluding some file
Thanks for the suggestions guys.
I copied the new agent.jar to the machine when using the new version. I am
executing it on demand from the command line.
How would I update the remoting.jar on the slave? As far as I can tell
there is only one .jar used on the slave and that is the one you down
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
Doesn't work. There is no Delete.
On Wed, Feb 17, 2021 at 3:55 PM Mark Waite
wrote:
> 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
>
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 Jenki
Yes, there is only one file to update the remoting.jar. If you install the
remoting process as a service the update is done by the service see
https://github.com/jenkinsci/windows-slave-installer-module and
https://github.com/winsw/winsw/blob/master/doc/installation.md#winsw-installation-guide
If
