So you have a git repository with pipeline (as script) and want to run them all?
Its possible, but Its somewhat a messy syntax.
# global variable
def Myclosure
Node {
# has to be in a node
Checkout scripts
Myclosure = # load scripts and call them
}
# call the closure.
Myclosure()
See triggering
So you have a git repository with pipeline (as script) and want to run them all?
Its possible, but Its somewhat a messy syntax.
# global variable
def Myclosure
Node {
# has to be in a node
Checkout scripts
Myclosure = # load scripts and call them
}
# call the closure.
Myclosure()
See triggering
Sorry, its not really clear to me what you expect.
1 Build = one Pipeline (execution)
This Pipeline can be flexible and seperated horizontally with stages, and
vertically with parallel execution.
Further, what will be ultimately run can be scripted from multiple scripts
(some could be "pipelines
variable-in-a-method>
>>
>> for each.
>>
>>
>> On Wednesday, April 27, 2016 at 3:00:43 PM UTC-7, Norbert Lange wrote:
>>>
>>> Hi Brian,
>>>
>>> every single method in the "final foo" - including the String
>
ing keys and values using
> *myMap.key* and *myMap.value*. Not sure what the difference is with my
> more stubborn loop.
>
> On Wednesday, April 27, 2016 at 8:21:45 AM UTC-7, Norbert Lange wrote:
>>
>>
>>
>> Am Mittwoch, 27. April 2016 16:41:40 UTC+2 schrieb Jesse
Am Mittwoch, 27. April 2016 16:41:40 UTC+2 schrieb Jesse Glick:
>
> On Tuesday, April 26, 2016 at 7:18:55 PM UTC-4, Norbert Lange wrote:
>>
>> There seem to be some arcane rules on how to iterate over some
>> builtin Groovy/Java Types within a sandbox. I haven`t fo
Hello,
I trying to get comfortable with Pipelines, so far its a rather
unpleasant experience since I cant even get a simple script going.
1) There seem to be some arcane rules on how to iterate over some
builtin Groovy/Java Types within a sandbox. I haven`t found a way that
works without manually
