Wizard should reload jenkins at the end was Re: [workflow-plugin] Java.lang.NoSuchMethodError: No such DSL method

[Arnaud Héritier]

I just had this issue today with Jenkins 2.x.

It occurs at the very first time you start a new jenkins install and install plugins.

Probably the pipeline is installed/loaded before the git plugin in the installation process and thus you don't have access to it

java.lang.NoSuchMethodError: No such DSL method 'git' found among [archive, bat, build, catchError, checkout, deleteDir, dir, echo, emailext, error, fileExists, input, isUnix, load, mail, node, parallel, properties, pwd, readFile, retry, sh, sleep, stage, stash, step, svn, timeout, timestamps, tool, unarchive, unstash, waitUntil, withCredentials, withEnv, wrap, writeFile, ws]

Restarting the server solves the issue

Maybe after the installation wizard we should automatically trigger a restart to avoid this problem

WDYT ?

On Thu, Jan 15, 2015 at 9:25 PM, Jesse Glick <jgl...@cloudbees.com> wrote:

On Thursday, January 15, 2015 at 1:55:57 PM UTC-5, Daniel Tschan wrote:

You also need the Git Plugin

2.3+: https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md#scms 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1e8b3202-c166-4561-a146-d40d351a6962%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

-----

Arnaud Héritier

http://aheritier.net

Mail/GTalk: aheritier AT gmail DOT com

Twitter/Skype : aheritier

[Jesse Glick]

On Mon, May 30, 2016 at 4:07 AM, Arnaud Héritier <aher...@gmail.com> wrote:
> Maybe after the installation wizard we should automatically trigger a
> restart to avoid this problem
> WDYT ?

No, the proper fix is to stop using optional extensions
(JENKINS-19508). I think this would best be done by finally moving the
`git` and `svn` steps to the respective SCM plugins. Let me see if I
can get buy-in from the plugin owners.

[Arnaud Héritier]

If you succeed to do JENKINS-35247 it should be more efficient/robust for pipeline usecase. 

But I'm afraid (maybe I'm wrong) that we could have such dependency issue across various others plugins ... thus my brutal/heavy solution, let's restart all :-)

For JENKINS-19508 yes it is sure

--
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/CANfRfr1%2B6t_9Uz_DgDapkUoNuNo6nu%2B05NBs1vFy-k_ee01Q5g%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.