If you run such a job the 1st time, all is well.
If you run it again, it may or may not decide to grab the latest version
vs. use the one it already has.
I'm not sure if it's finding it on the Jenkins master, or on a local worker.
In my case it's an image built and pushed to a local repo by anot
Did you try in "configure system" after installing the Docker plugin
setting the Docker URL to something like tcp://172.16.42.43:4243
On Friday, May 19, 2017 at 2:20:52 AM UTC-5, Kirill Peskov wrote:
>
> Hi All,
>
> I'm googling already about an hour if not longer, but I really cannot
> find an
It also means if you use a JobDSL statement to generate a Pipeline job with
authorization {
permission('...
then if your Pipeline Jenkinsfile uses
options {
buildDiscarder(
It wipes out the permissions, since they both use the properties mechanism,
which only works once.
I'm not
You can use a JobDSL statement in the Jenkinsfile in the root of your repo
to generate other jobs. Those jobs wouldn't be triggered by subsequent
repo changes, unless you add a call to them in your main Jenkinsfile - they
also could be triggered on-demand, through replay, a cron ...
--- Matt
I think script {} is the answer...
On Friday, May 5, 2017 at 3:36:41 PM UTC-5, Guy Knights wrote:
>
> I've been playing around with the declarative pipeline syntax and I'm
> having trouble running a docker container to do some processing. To
> clarify, I *don't* want to run my entire pipeline in
It seems you can use
Library
in a declarative pipeline file to do stuff like
mySpecialPipeline {
someString = 'foo'
}
and have
pipeline { ...
...echo config.someString
}
in vars/mySpecialPipeline.groovy
and you can reference vars/myCustomStep.groovy
but is it possible to share job
p
You can add build parameters while the build's in flight, with
[jenkinsURL]/cli/command/set-build-parameter
You should be able to refer to those in subsequent builds
See also https://wiki.jenkins-ci.org/display/JENKINS/Plot+Plugin (though
I've never used it)
--- Matt
On Sunday, May 22, 2016 a
We updated to 1.6.24 last Saturday, since then, we're running into problems
where the Web interface gets suddenly slow, then eventually stops
responding, though jobs are still processing.
I installed the javamelody plugin after the 2nd time, it show a sudden
spike in memory from ~ 2GB to near t
You need to curl -X POST
On Thursday, March 19, 2015 at 11:06:34 AM UTC-7, Vinoth raj wrote:
>
> I need to use curl to remotely trigger build for a project.
>
> Jenkins ver. 1.580.3
> Following setting is done:
> In Configure Global Security section:
> - Jenkins' own user database set is enabled
It looks like it's failing before it gets to your job steps. Are you sure
the slave node user has access to all the relevant directories?
On Thursday, April 23, 2015 at 3:30:53 AM UTC-7, Krishna Kumar Tiwari wrote:
>
> Hi
>
> How can i find the jenkins version ? I haev attached the jenkins serv
We have multiple Jenkins jobs using maven with the same userID with /home
on a file system shared between slave nodes, so the default
~/.m2/repository led to ... nice speedups, but had the downside of doing
The Wrong Thing, and causing errors. So for jobs that call mvn in the
middle of a bash
I found that using that standard method is quite slow compared to scp. So
I use that method to copy just a few small files, and one with GUIDs for
fingerprinting, and for the big ones I do something like
scp -v ${WORKSPACE}/bigfile.tar.gz
user@jenkins_host_name:path_to_jenkins_root/jobs/${JOB
12 matches
Mail list logo