Custom Plugins: APIs and Javadocs of Jenkins Enterprise plugins

Issue

  • You may wish to create custom plugins depending ( pom.xml) on CloudBees Jenkins Enterprise plugins
  • You may wish to call APIs in CloudBees Jenkins Enterprise plugins from custom Groovy scripts and want details on these APIs

Environment

  • CloudBees Jenkins Enterprise
  • Enterprise plugins

Resolution

Explicit dependency is not recommended unless you have a real use-case for it because:

  • Cloudbees does not guarantee binary compatibility
  • It makes migration path more complex

Having said that, for this scenario you can make use the Maven repository http://repo.cloudbees.com/content/repositories/dev-connect/.

If you end up including this type of dependency, the following disclaimer should be added to the custom plugin:

 - Backward compatibility of API and behaviour is not guaranteed for this plugin
 - Testing may be complicated, because CloudBees Templates plugin performs license checks

References

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.