Change the root fork of an existing plugin

[Aurélien Bourdon]

Hello,

We recently did some changes in our Github organisation (CerberusTesting) and would like to spread changes to existing forks that now use deprecated root repositories, as our Jenkins plugin.

The concerned plugin is the following: https://github.com/jenkinsci/cerberus-testing-plugin

This plugin is a fork of the now deprecated https://github.com/abourdon/cerberus-jenkins-plugin repository.

Would it be possible to re-recreate the repository by now forking the repository in the CerberusTesting organisation: https://github.com/cerberustesting/cerberus-cicd-jenkins-plugin? 

As this is not strictly a new plugin creation, and the identification/configuration is the same as the "previous" one, I guess it's possible to re-create the repo easily on your side?

Thank you

Aurélien

[Gavin Mogan]

You can ask github to break that link (so github doesn't say its forked), and then your development can be on a fork.

You can probably ask them to change the source as well.

Advantage of jenkins being the source is that github search will work org wide for it.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ec2871eb-3f7a-4d6b-9a29-ec4894acf3c0n%40googlegroups.com.

[Basil Crow]

On Fri, Aug 26, 2022 at 9:36 AM 'Gavin Mogan' via Jenkins Developers
<jenkin...@googlegroups.com> wrote:
>
> Advantage of jenkins being the source is that github search will work org wide for it.

Also, CD is only supported when the GitHub repository is in the
jenkinsci GitHub organization. In general I think we prefer for all
plugins hosted on our Update Center to have their repository of record
in the jenkinsci GitHub organization, although there are a few
exceptions for historical reasons. That enables us to manage
repository write access and Artifactory upload permissions using our
unified and well-documented system.

[Aurélien Bourdon]

Ah, I thought the "forking process" was the default behaviour when adding a plugin to the JenkinsCI organisation. 

Thank you all for your answers, indeed breaking the fork link is the simpler solution. I'll ask github directly.

Kind regards

Aurélien

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrn0AVSLR6HGAchUi8R8ixa%2BkygmV3uctbeA_UY0Dd7QQ%40mail.gmail.com.