Deear Jérôme,
I really wanted to thank you for having taken the time to share both
abstract ideas, an overall view of your architecture, and also very
valuable code. To tell you the truth, it didn't help me to become friend
with all this Groovy soup, but this is by no means your fault and I am
on
@googlegroups.com On
Behalf Of jeremy mordkoff
Sent: August 14, 2020 2:52 PM
To: Jenkins Users
Subject: Re: Pipeline design question
How do you maintain and verify backwards compatibility with older releases if
you keep your devops code in a separate repo? I keep my devops code in the same
repo as the
s: [[credentialsId: 'BitBucketAmotus', url:
> repos['url']]]
> ]);
> }
> }
> }
>
> // Perform the build/test stages from here
> }
>
> That give a good idea on how things are executed on the slave node. I also
> use node env var to override default pa
e build/test stages from here
}
That give a good idea on how things are executed on the slave node. I also use
node env var to override default path for tools if they not install into the
default path or the OS have a special path (I'm looking at you MacOS).
There is still quiet some room for imp
Many thanks for your contribution Jeremy. Definitely more than $0.02!
;-)
I am not sure how high-level my Jenkinsfiles are at the moment, but at
least we are departing frm defining the jobs in Jenkins' UI, which feels
good and a step in the right direction on which we can always improve
later.
Be
Hello Jérôme, thanks a lot for your response.
Jérôme Godbout (2020/08/11 16:00 +):
> Hi,
> this is my point of view only,but using a single script (that you put
> into your repos make it easier to perform the build, I put my pipeline
> script into a separated folder). But you need to make sure
Dear Gianluca,
Many thanks for your helpful comments! I do not have a strong opinion at
the moment about what is best, but at least I understand the pros and
cons in a better way.
Best wishes,
Sébastien.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Use
decide or plan you build architecture.
>
> Jerome
>
> -Original Message-
> From: jenkins...@googlegroups.com <
> jenkins...@googlegroups.com > On Behalf Of Sébastien
> Hinderer
> Sent: August 11, 2020 10:33 AM
> To: jenkins...@googlegroups.com
> Subject:
-users@googlegroups.com On
Behalf Of Sébastien Hinderer
Sent: August 11, 2020 10:33 AM
To: jenkinsci-users@googlegroups.com
Subject: Pipeline design question
Dear all,
When a pipeline needs to run a sequence of several shell commands, I see
several ways of doing that.
1. Several "sh" invo
Hi,
from functional point of view there is no different ... but there are from
reporting point of view ... and that's a matter of taste :-)
1. In BlueOcean view, each "sh" invocation will be displayed separately
from the other steps and "sh" takes as parameter a name that BlueOcean will
use to
Dear all,
When a pipeline needs to run a sequence of several shell commands, I see
several ways of doing that.
1. Several "sh" invocations.
2. One "sh" invocation that contains all the commands.
3. Having each "sh" invocation in its own step.
4. Putting all the commands in a script and invokin
11 matches
Mail list logo
