Re: Jenkins Plugin Wiki Question

[Kohsuke Kawaguchi]

Yeah, we lost this service. I need to find a new home for it, but I got a bit of push back from other admins about running a random service like this.

Maybe if we wrap this into a container and make sure it gets auto-restarted when it dies, perhaps that would help reduce the operational overhead...?

2015-09-14 12:18 GMT-07:00 Ryerson CCS <ryerson...@gmail.com>:

I noticed that you made the wiki page:

https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial

Would you happen to have a live link for "the online skeleton generator", the current one is broken?

Thanks! Cheers.

--

Kohsuke Kawaguchi

[Daniel Beck]

I never understood this. You need Maven to do anything anyway, and `mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create` is trivial to run. Yet we have some random service that does basically the same thing needs to be kept running -- something we're clearly not good at.

What am I missing?

> --
> 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/CAN4CQ4yBNY_Ej5d7D8YKL%3Dj32s_49mkbLUxTwX1aGmncfnh%3DGg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[Richard Bywater]

+1 - I think the resources to create & keep stuff running is already stretched so having something that doesn't really add any value just seems to be throwing people's time away?

Richard.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/941124BE-F528-48D6-B127-8AB3A5388402%40beckweb.net.

[Jesse Glick]

On Wed, Sep 16, 2015 at 12:48 AM, Daniel Beck <m...@beckweb.net> wrote:
> You need Maven to do anything anyway, and `mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create` is trivial to run. Yet we have some random service that does basically the same thing

Agreed, I think the effort would be better placed into cleaning up the
introductory plugin author documentation and clearly listing the
command to run.

BTW it is not quite that simple, since the archetype is not in Central:

$ docker run --rm maven mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/org/jenkins-ci/tools/maven-hpi-plugin/maven-metadata.xml
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.250 s
[INFO] Finished at: 2015-09-16T13:18:43+00:00
[INFO] Final Memory: 8M/178M
[INFO] ------------------------------------------------------------------------
[ERROR] Error resolving version for plugin
'org.jenkins-ci.tools:maven-hpi-plugin' from the repositories [local
(/root/.m2/repository), central
(https://repo.maven.apache.org/maven2)]: Plugin not found in any
plugin repository -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException