Jenkins Plugin Open Source Group ID

[Dennis Gu]

Based on Jenkins Plugin documentation, in order to create a new Jenkins plugin, we have to host our plugin repository under GitHub Jenkins organization, and using this group ID:

<groupId>io.jenkins.plugins</groupId>

<artifactId>veracode-scan</artifactId>

Unfortunately, we already developed a plugin which is not open source and used by many customers, and only host in our internal server, and we used group ID as:

<groupId>com.veracode.jenkins</groupId>

<artifactId>veracode-jenkins-plugin</artifactId>

This caused some migration issue for our existing customer, because above plugins are being treated as totally two different Jenkins plugin, and existed customer need to migrate new one from old one manually.

Is there any way Jenkins will allow me to still using the old group ID for my new plugin, so customer won't need to do migration.

Or it is impossible because any Jenkins open source plugin need to be using io.jenkins.plugins group.

Thank you for any suggestion!

Dennis

[Jesse Glick]

The group ID is mostly irrelevant. The artifact ID becomes the plugin identifier, which may never be changed once released.

[Slide]

We request using io.jenkins.plugins, but if you already have something for your company, you are welcome to use that as well. As Jesse mentioned, its the artifactId that is the most important to get right.

On Mon, May 4, 2020 at 9:47 AM Jesse Glick <jgl...@cloudbees.com> wrote:

The group ID is mostly irrelevant. The artifact ID becomes the plugin identifier, which may never be changed once released.

--
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/CANfRfr17t2QRor582eFzepPPQSk76tU5Jd%3DO-WG2NWQS8zB0fQ%40mail.gmail.com.

--

Website: http://earl-of-code.com