We have been using the heavy job plugin and configured the nodes so that
they have as many executors as cpus.
There we could set in the job the job weight to as many cpus the job
really used.
But we shifted over to using pipeline and groovy script and now that
parameter is not possible to set
On 2017-04-28 13:38, Kenneth Johansson wrote:
I want to test if a property on a job exist att all. and then do
something depening on if it true or false.
if the property exist there is no issue testing if its true or false
but I do not want to force the job to have to create the property so I
I want to test if a property on a job exist att all. and then do
something depening on if it true or false.
if the property exist there is no issue testing if its true or false but
I do not want to force the job to have to create the property so I want
to test if the variable exist and that
On 2017-04-27 17:52, Mark Waite wrote:
On Thu, Apr 27, 2017 at 9:36 AM Kenneth Johansson
<kenneth.johans...@inteno.se <mailto:kenneth.johans...@inteno.se>> wrote:
On 2017-04-27 17:22, Mark Waite wrote:
Refer to
https://jenkins.io/doc/pipeline/steps/workflow-durab
r 27, 2017 at 9:16 AM Kenneth Johansson
<kenneth.johans...@inteno.se <mailto:kenneth.johans...@inteno.se>> wrote:
How do I find out what functions exist that can be used from a groovy
script and how to use them ??
like how to get the shell script output from a shell comma
How do I find out what functions exist that can be used from a groovy
script and how to use them ??
like how to get the shell script output from a shell command into a
variable.
so the sh command is in basically all examples written as "sh
'command'" but there is another way also so that
On 2017-04-26 16:14, Björn Pedersen wrote:
Am Mittwoch, 26. April 2017 14:43:39 UTC+2 schrieb Kenneth Johansson:
hmm I'm starting to question the usefulness of the pipeline
system. Its
very hard to understand how to do even very basic stuff.
Even something as easy as finding
hmm I'm starting to question the usefulness of the pipeline system. Its
very hard to understand how to do even very basic stuff.
Even something as easy as finding out what type of parameters I can use
is hard.
The documentation on https://jenkins.io/doc/book/pipeline/syntax/ only
mention
the basic
configuration step.
On Wed, Apr 26, 2017 at 5:01 AM Kenneth Johansson
<kenneth.johans...@inteno.se <mailto:kenneth.johans...@inteno.se>> wrote:
So I have a pipeline job that is using the "pipeline script from
SCM" as
suggested in the documentation
So I have a pipeline job that is using the "pipeline script from SCM" as
suggested in the documentation.
But for developing code this is really really annoying as I now need to
checking every single change even if its just to test something out and
for a new user its going to be quite a lot
10 matches
Mail list logo
