Re: Running build does not provision docker salve

Hello Richard, On Sunday, July 19, 2015 at 12:40:52 AM UTC+2, Richard Bywater wrote: > > You'll need to restrict the job to the label you gave in the Image > configuration section (mylabel in your case) > > I haven't used the "Docker Container" option but I think that is for when > you want to s

Re: Running build does not provision docker salve

Great - glad I could help. Would be interested in your experiences of using the Docker plugin as I've had issues with it not sparking off more than one instance of a particular label at a time (e.g. if there's a build already running with a mylabel build a second build would just sit there and wai

/crumbIssuer/api/json return 404

Hi, I'm trying to add a new job using https://github.com/RisingOak/jenkins-client (Java client), and it fails In the log I see the following error 17:08:00.184 [main] DEBUG org.apache.http.wire - << "HTTP ERROR 404[\n]" 17:08:00.184 [main] DEBUG org.apache.http.wire - << "Problem accessing

Re: SCM Sync Configuration Plugin

Hi, I just checked on my jeknins installation and scm-sync-configuration works for me. Versions: Jenkins: 1.618 GIT client plugin: 1.18.0 GIT plugin: 2.4.0 SCM Sync Configuration Plugin: 0.0.8 Br, Christoph Am 2015-07-17 um 23:40 schrieb Brandon Koepke: Hey, Has anyone been able to get the s

Re: grayed-out font style in build history list

It would be easier to use the Simple Theme Plugin to override the CSS in question than rebuilding the WAR yourself: https://wiki.jenkins-ci.org/display/JENKINS/Simple+Theme+Plugin I haven't noticed the text change you mention, possibly due to the version I'm running, but if it's really difficul

unable to read config.xml - GlobalMatrixAuthorizationStrategy

I have checked the permissions on the config.xml and I am still receiving this error message. We are using Jenkins version 1.598. I recently rebooted it after a number of plugins were installed, so I am not certain if any are cause of the the issue. I get this error right after restart. I have at

Re: "WARNING: Failed to construct Command" when dynamic slave is terminated

A little more information: here is how the AbstractCloudSlave._terminate() method is implemented in my custom slave: @Override protected void _terminate(TaskListener listener) throws IOException, InterruptedException { LOGGER.log(Level.INFO, "Terminating Kubernetes instance for