Has anyone used the 'Throttle Concurrent Builds Plugin' in a declarative
pipeline?
>From what i understand, throttle() will throttle nodes, which are optional
in a dp:
pipeline {
agent any
}
When introducing an explicit node
pipeline {
throttle(['THROTTLE1']) {
Stupid me - just configured two factories, each using a distinct filename
w/o wildcards, runs like a charm.
--
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 jen
Dear group,
i have a bunch of jobs that all prepare a zip and a readme in the
workspace, and those two files need to be passed to a dedicated file job
that expects two files ('zipfile' and 'readme') as job parameters. Usually
the parameterized trigger plugin is of great help, but it seems that
>
> Jobs as code - beautiful. Not to say that yaml doesn't cut it, but being a
> happy Gradle user the job DSL hits the sweet spot.
>
Awesome tip, thanks!
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and st
Jerome,
did you come up with a pleasing solution?
Thanks in advance
Jochen
On Monday, 23 July 2012 16:57:15 UTC+2, romje wrote:
>
> Hi all,
> I wondered if someone went to same conclusions I could have made...
> I 'm working for one very client in France , this company owns seevral
> brands ,
Dear group,
we want to follow the same rules for Jenkins jobs that our software itself
must confirm to: development in test, testing in staging, and the official
version in a production environment. Copy and paste will always work, but
i'm too lazy to do that for the 200+ jobs. Maybe something
Dear group,
since upgrading LTS from 1.532.1. to 1.532.2, the
commit
https://github.com/jenkinsci/jenkins/commit/5548b5220cfd496831b5721124189ff18fbb12a3
is active and breaks our existing authentication setup for remote scripts.
Jenkins is configured to use LDAP for human login users, and tec
