Hello Björn,
I'm not sure if you've already subscribed to the Jenkins Documentation
Google Group, but in case you haven't yet seen it, we recently published a
tutorial to demonstrate the CI/CD process of delivering a Python
application using Jenkins
(https://jenkins.io/doc/tutorials/build-a-py
On Thu, Dec 14, 2017 at 6:53 PM Nathaniel Irons wrote:
> When a stash is being performed on a non-master agent, is the stash
> operation really CPU-intensive on the master? I wasn't sure from that
> description whether it assumed the master was also executing the stash
> phase. We did try triplin
When a stash is being performed on a non-master agent, is the stash
operation really CPU-intensive on the master? I wasn't sure from that
description whether it assumed the master was also executing the stash
phase. We did try tripling the CPU allocated to the master's VM, and saw
no change in stas
I have configured a job that will be triggered when messages are written to
a given AWS SQS queue. I've defined the job with the required sqs
parameters (sqs_body, sqs_messageId, sqs_bodyMD5, and sqs_receiptHandle).
I have other hidden parameters that I would also like to pass along. Is
this
On Thu, Dec 14, 2017 at 4:13 PM Nathaniel Irons wrote:
> Jenkins is building an iOS project with five similarly-sized targets.
> The git repository is 251 MB, of which the .git dir is 130 MB. A
> pipeline stage handles the checkout, injects build numbers, and stashes
> the modified sources, minus
Hello,
You had enabled logging on your test master and we display in the build
logs the logs of the plugin, this is why you had these messages on your
test masters.
You can disable globally publishers through the Global Tools Configuration
screen.
The message may not be intuitive but here is
Jenkins is building an iOS project with five similarly-sized targets.
The git repository is 251 MB, of which the .git dir is 130 MB. A
pipeline stage handles the checkout, injects build numbers, and stashes
the modified sources, minus the unnecessary .git dir, for the other
build nodes to consume.
I guess, that's more specific about your use case, but if that's something
about how to do it within Jenkins, please go ahead, likely others can
provide you some feedback too :)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe f
Thanks Victor
May I ask you for further help regarding the script needed to copy artifact
files into the desired location ?
Le mercredi 13 décembre 2017 15:55:09 UTC+1, Victor Martinez a écrit :
>
> If you meant about using the promote build plugin, you can add some input
> parameters in the j
Am Montag, 14. April 2014 22:30:37 UTC+2 schrieb solid:
>
> Hi Guys
>
>
> JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Xmx2048m
> -XX:MaxPermSize=1024m"
>
Well that's 2GB allocated to jenkins. Which is not too bad, depending on
the number of jobs and the discard-build settings.
(always und
> On 14. Dec 2017, at 11:37, 'Christoph Rieß' via Jenkins Users
> wrote:
>
> Then i configured (under /configureSecurity/) my ACL rules (see attached
> screen).
At least Overall/Read and Item/Read are also needed to access the job in
question at all. This option enables another restriction,
Just noticed that PROD has a different logger. It is using:
org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution
and test was using:
org.jenkinsci.plugins.pipeline.maven
Both were set to log level ALL.
After set test instance to use the same logger, the output are similar in
both instance
On Tuesday, April 15, 2014 at 2:00:37 AM UTC+5:30, solid wrote:
>
> Hi Guys
>
> Over the last few weeks I have been getting memory errors with jenkins. It
> first starts of as "pending—Waiting for next available executor" when
> attempting to execute a new job. I restart the jenkins daemon only
13 matches
Mail list logo
