> On 13. Jul 2017, at 09:48, Gergely Brautigam <skarlso...@gmail.com> wrote: > >> That said, the plugin archetype is reasonably well written in a pipeline >> compatible way (mvn hpi:create). > > You mean when I'm creating a plugin skeleton with mvn?
Yes. >> Depending on what your plugin does, reading the guides how to integrate it >> with Credentials, Pipeline, and Script Security should take care of the >> major "recent" technology available. > > Uh, which are... where? Wiki? :) Credentials: https://wiki.jenkins.io/display/JENKINS/Credentials+Plugin#CredentialsPlugin-InformationforPluginDevelopers (Also, I think the plugin maintainer is writing new guides right now) Pipeline: https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md Script security: https://wiki.jenkins.io/display/JENKINS/Script+Security+Plugin#ScriptSecurityPlugin-Developer%E2%80%99sguide -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/206BB131-4419-48B4-910A-EB91F1043143%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
