On Thu, Apr 12, 2018 at 7:57 AM, Ronald Petty wrote:
> The
> global.jelly is not generated, so there was no Configure screen for the
> plugin.
Yes, that was removed from the `Builder` archetype, as it was using an
old idiom that does not generalize well and is no longer
Thanks for the information. I did find part of the issue for me. The
global.jelly is not generated, so there was no Configure screen for the
plugin. There was an option (which I didn't check first time) for the job,
but not the plugin. Adding global.jelly, repackage, it then worked like it
Cool you're trying this! Welcome!
You should follow https://jenkins.io/doc/developer/tutorial/create/ then
IIUC you will want to choose the (as of now) choice number 2:
"2: remote -> io.jenkins.archetypes:hello-world-plugin (Skeleton of a
Jenkins plugin with a POM and an example build step.)"
Hello,
I could be living in the past, but I am trying to get the old `mvn hpi:...`
to work and it seems it has changed. I found a page saying we should use
this method here:
mvn archetype:generate -B -DarchetypeGroupId=io.jenkins.archetypes
-DarchetypeArtifactId=hello-world-plugin