Re: ERROR: Processing failed due to a bug in the code.

2017-10-06 Thread Mark Waite
Possibly there are other administrators on that Jenkins instance, and one of them assigned a value to the artifactory server in the general configuration? On Fri, Oct 6, 2017 at 9:43 AM Charles Karney wrote: > Thanks for the information. My problem seems to have cleared up

Re: ERROR: Processing failed due to a bug in the code.

2017-10-06 Thread Charles Karney
Thanks for the information. My problem seems to have cleared up by itself! --Charles On Thursday, October 5, 2017 at 11:05:51 AM UTC-4, Mark Waite wrote: > > That failure message is unrelated to git. > > The message "java.lang.RuntimeException: java.lang.IllegalArgumentException: > No >

Re: ERROR: Processing failed due to a bug in the code.

2017-10-05 Thread Mark Waite
That failure message is unrelated to git. The message "java.lang.RuntimeException: java.lang.IllegalArgumentException: No matching Artifactory server was found in General Configuration. Please update your job configuration." seems to indicate that some method which expects an artifactory server

Re: ERROR: Processing failed due to a bug in the code.

2017-10-05 Thread Charles Karney
I'm running Jenkins 1.589. On Thursday, October 5, 2017 at 10:32:20 AM UTC-4, Charles Karney wrote: > > Triggering a Jenkins build on a job that has "usually" worked gives: > > ERROR: Processing failed due to a bug in the code. Please report this > to jenkinsci-users@googlegroups.com > >

Re: ERROR: Processing failed due to a bug in the code

2015-04-16 Thread Eero Aaltonen
After unticking Publish documents, this error disappeared. On Thursday, April 16, 2015 at 3:25:19 PM UTC+3, Eero Aaltonen wrote: From a maven job with target 'clean compile' Followed by execute shell 'mvn pre-site' This occurred after I disabled automatic reporting and tried to do it

RE: ERROR: Processing failed due to a bug in the code.

2012-10-30 Thread Ahmet Maruf Aytekin
If someone else experiencing the same problem, following script worked for me on Jenkins ver. 1.486: import hudson.model.*; import hudson.util.*; def thr = Thread.currentThread(); def currentBuild = thr?.executable; def mavenVer = currentBuild.getParent().getModules().toArray()[0].getVersion();