Hi,
On Wed, Jan 15, 2020 at 02:38:26PM +, David Aldrich wrote:
> We build large C++ projects using Jenkins for Linux platforms. These build
> jobs currently run on a single executor. I want 'make -j' or ninja to
> compile concurrently on several cores to speed up the build time. How can
>
Am Mittwoch, den 15.01.2020, 14:38 + schrieb David Aldrich:
We build large C++ projects using Jenkins for Linux platforms. These build
jobs currently run on a single executor. I want 'make -j' or ninja to compile
concurrently on several cores to speed up the build time. How can I cause a
is way?
I saw a similar question discussed in a StackOverflow question:
https://stackoverflow.com/questions/20003919/jenkins-with-parallel-builds.
The answer given there was to use the Heavy Job Plugin. But that plugin
seems quite old. Is it still the best solution?
Best regards
David
--
You rec
It was released as part of git plugin versions git-3.1.0, git-3.0.5,
git-3.0.4, git-3.0.3, git-3.0.2, git-3.0.1, git-2.6.5, git-2.6.4,
git-2.6.2, and git-2.6.1.
Mark Waite
On Sun, Mar 19, 2017 at 2:07 AM wrote:
> Was this merged already?
> Is it safe to use checkout scm within for parallel jo
Was this merged already?
Is it safe to use checkout scm within for parallel jobs?
On Thursday, September 22, 2016 at 6:53:06 AM UTC+3, Mark Waite wrote:
>
> The intent of the checkout scm step is that it takes a single revision,
> and uses that revision for the duration of the job.
>
> Unfortunat
So I was not running in a node block I will do more testing thank you.
Here is a sample of my code:
*#!groovy*
*import hudson.model.**
*stage('many_jobs') {*
*parallel (get_many_jobs(6000))*
*}*
*def get_many_jobs(num_builds) {*
*// The map we'll store the parallel steps in before exec
So I have not run in an ode block I will do more testing thank you.
Here is a sample of my code:
*#!groovy*
*import hudson.model.**
*stage('many_jobs') {*
*parallel (get_many_jobs(6000))*
*}*
*def get_many_jobs(num_builds) {*
*// The map we'll store the parallel steps in before executi
Hey there -
I think it might be worth posting the pipeline of your orchestration job
that runs the 12000 builds for anyone to comment in more detail.
>From what I understand, if your pipeline is not orchestrating each build in
a node section it will use something called a 'flyweight executor' o
So not sure if this is a Jenkins limitation or pipeline.
The jobs never exceeded available resources.
The garbage collection was stable.
So why did it lock-up?
It did say I used
- 2950 million active threads
- 350 threads
--
You received this message because you are subscribed to the Go
I need to retry it may be that the jobs never all started
Branch: job_0 - (1ms in block)
Branch: job_9830 - (3min 16sec in block)
Branch: job_9831 - (No timing in block)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this
So 3 hr 30 min later the pipeline is locked up
--
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-users+unsubscr...@googlegroups.com.
To view this discus
I am doing testing of our Jenkins setup.
I have a build job that sleeps for 30 sec.
I ran a pipeline that runs 12,000 of these in parallel on 100 agents.
Best possible time is 1 hr.
The builds seem to finish in a reasonable amount of time.
So after build queue is emptied and the pipeline continues
Thanks for the quick reply.
Any info about the recommended way to get the sha that was actually used ?
--
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 jenkinsc
The intent of the checkout scm step is that it takes a single revision, and
uses that revision for the duration of the job.
Unfortunately, a bug was found during discussions after Jenkins World which
seem to indicate that there area cases where git plugin 2.5.3 and beyond
risks not checking out th
Hi
I was playing with JenkinsFiles and Organization folders (multi-branch
pipeline) and I was wondering:
Is there is any guarantee the 'checkout scm' command would checkout the
exact same revision on all node, even if new commits are pushed before the
build is finished ?
Also, I saw an environm
On Tuesday, January 13, 2015 at 11:14:49 AM UTC-5, Timur Batyrshin wrote:
>
> Is there a way to separate logs for the branches to make them easily readable?
>
>
https://issues.jenkins-ci.org/browse/JENKINS-26122 would help.
--
You received this message because you are subscribed to the Google Gr
lly!
> Compiled ack_wrk.c successfully!
> Compiled main.c successfully!
>
>
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> [INFO] --- jacoco-maven-plugin:0.7.2.201409121644:report (default-report) @
> core-net ---
>
>
>
re than the 2 branches building in parallel there will be
even more difficulty in that.
Is there a way to separate logs for the branches to make them easily
readable?
Alternatively I could spawn subjobs as parallel builds but I've read here
that it is not recommended
and I don't like v
I don't know where and how to use this fix
https://issues.jenkins-ci.org/browse/JENKINS-2181
-Original Message-
From: jhoomsharabi
To: jenkinsci-users
Sent: Sat, Apr 12, 2014 10:08 am
Subject: Re: Parallel builds with Build Flow
Hi,
Any progress on this parallel build proce
-Original Message-
From: hi
To: jenkinsci-users
Sent: Thu, Mar 27, 2014 9:41 pm
Subject: Re: Parallel builds with Build Flow
Just correcting a typo with job names.
parallel (
{ build("job1", id:"1", type:"foo") },
{ build("job1"
Dick"
>> wrote:
>>
>> I think you can only do that in each job definition, that is in the
>> specification for Job1, 2, and 3. I don’t think you can pass anything to
>> the build method to do that.
>>
>>
>>
>> *From:* jenki
ion, that is in the
> specification for Job1, 2, and 3. I don’t think you can pass anything to
> the build method to do that.
>
>
>
> *From:* jenkins...@googlegroups.com [
> mailto:jenk...@googlegroups.com ] *On Behalf Of *
> h...@renatorodrigues.me
> *Sent:* Thursday, March 27,
Ah, good to know, thanks.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Marc MacIntyre
Sent: Thursday, March 27, 2014 12:02 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Parallel builds with Build Flow
Use the node label parameter plugin
, 2014 11:36 AM
> To: jenkinsci-users@googlegroups.com
> Subject: Parallel builds with Build Flow
>
> Build Flow plugin allows one to have parallel builds in a simple way:
>
> parallel (
> // job 1, 2 and 3 will be scheduled in parallel.
> { build("job1") },
: Thursday, March 27, 2014 11:36 AM
To: jenkinsci-users@googlegroups.com
Subject: Parallel builds with Build Flow
Build Flow plugin allows one to have parallel builds in a simple way:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build("job1") },
{ b
Build Flow plugin allows one to have parallel builds in a simple way:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.{ build("job1") },
{ build("job2") },
{ build("job3") }
)// job4 will be triggered after jobs 1, 2 and 3 completebu
Hello,
Could you point out a sample for the approach you are
recommending ? Is the 'Build Flow plugin' another way of doing what you
mean ?
Thanks.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this g
e concerned with how long it takes to actually
> >> build the software, see the discussion at
> >>
> http://stackoverflow.com/questions/3727493/using-multiple-cores-processors-when-compiling-java.
>
>
> >> It looks like there are ways to parallelize withi
on at
>> http://stackoverflow.com/questions/3727493/using-multiple-cores-processors-when-compiling-java.
>> It looks like there are ways to parallelize within ANT, completely
>> orthogonal to how (or if) you use Jenkins.
>>
>>
>>
>> --Rob
>>
>>
>>
ooglegroups.com ] *On Behalf Of *JonathanRRogers
> *Sent:* Thursday, May 02, 2013 3:55 PM
> *To:* jenkins...@googlegroups.com
> *Subject:* Re: Parallel builds
>
>
>
> On Thursday, May 2, 2013 5:02:58 AM UTC-4, Mohan Radhakrishnan wrote:
>
> Hi,
>
> What is
oglegroups.com] On Behalf Of JonathanRRogers
Sent: Thursday, May 02, 2013 3:55 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Parallel builds
On Thursday, May 2, 2013 5:02:58 AM UTC-4, Mohan Radhakrishnan wrote:
Hi,
What is the recommended way to run parallel builds on multi-core systems
On Thursday, May 2, 2013 5:02:58 AM UTC-4, Mohan Radhakrishnan wrote:
>
> Hi,
> What is the recommended way to run parallel builds on multi-core
> systems ? Mine has 4 cores with capability of 2 hardware threads on each
> core. Is master/slave mode recommended ?
>
>
Hi,
What is the recommended way to run parallel builds on multi-core
systems ? Mine has 4 cores with capability of 2 hardware threads on each
core. Is master/slave mode recommended ?
How does a single ANT script help in this case ?
Thanks.
--
You received this message because you
Great plugin along with the multijob... however I have one slight problem...
I have a sequence of parallel builds, one after the other, and all complete
ok but the overall build is marked as failure.
I have noticed that having a build job start another job can cause a
failure particularly if
That was it.
Nicolas you found my problam -- thanks --
I had neglected to tick the "Execute concurrent builds if necessary" box on
the jobs I wanted to have run in parallel.
On Wednesday, November 28, 2012 1:48:16 PM UTC-8, Mike Finneran wrote:
>
> When I execute the following build flow script
Do you have this job configured to allow concurrent execution ?
this is not a restriction for the build-flow plugin : this one only
schedule jobs, but execution depends on jenkins build queue management and
related job configuration
2012/12/7 Glenn McElhoe
> I noticed this problem as well. If
I noticed this problem as well. If you run parallel build of the same job,
it doesn't work.
My workaround was to make 12 jobs (Job-Build-1 through Job-Build-12), and
it will call them in parallel.
When I execute the following build flow script on a cluster of four
identical nodes, only one node is used to execute all twelve instances of
"job-Build".
If I pull that node, All instances are still build on only one node, just
the next node that is still on line.
I would have thought that all
Jenkins.
Mark Waite
>
> From: Z W
>To: jenkinsci-users@googlegroups.com
>Sent: Thursday, November 15, 2012 5:15 PM
>Subject: Re: parallel builds on single Hudson possible - quick question
>
>Hi Mark
>
>Thanks for responding.
>What's are alternat
: Thursday, November 15, 2012 4:15 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: parallel builds on single Hudson possible - quick question
Hi Mark
Thanks for responding.
What's are alternatives out there for Hudson to deal with parallel builds
requests besides upgrading to Jenkins.
On Tue,
Hi Mark
Thanks for responding.
What's are alternatives out there for Hudson to deal with parallel
builds requests besides upgrading to Jenkins.
On Tue, Nov 13, 2012 at 8:14 PM, Mark Waite wrote:
> In the Jenkins job configuration screen, there is a check box "Execute
> conc
ns.
Mark Waite
>
> From: Z W
>To: jenkinsci-users@googlegroups.com
>Sent: Tuesday, November 13, 2012 8:03 PM
>Subject: parallel builds on single Hudson possible - quick question
>
>Hi All
>
>We have a single Hudson server and we like to perform parallel builds
&
Hi All
We have a single Hudson server and we like to perform parallel builds
for multiple different builds.
Can Hudson support that, meaning one job starts at 815am and another
at 820am so in the build queue there would be 2 paralllel builds ?
If not, what's the usual practice to support mul
43 matches
Mail list logo
