Jochen,
don't use ${WORKSPACE} from outside the pipeline, it will be available as
soon as you are inside the pipeline with an agent.
That means: no need to have it as argument of your isccrPipeline
BR
jochen@gmail.com schrieb am Mittwoch, 18. Januar 2023 um 15:22:52 UTC+1:
>
> Okay, is
Okay, is there anything that I could use as a reference to the code
directory instead?
On Wed, Jan 18, 2023 at 3:17 PM 'Xavier Raynaud' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
> Hi,
>
> AFAIK, WORKSPACE is defined per agent, not for a global pipeline.
> For instance, if you
Hi,
AFAIK, WORKSPACE is defined per agent, not for a global pipeline.
For instance, if you run a pipeline on two distincts agents, each of them will
have its own WORKSPACE
Xavier Raynaud
Integration & Release Manager • Kalray
Phone: +33 6 32 19 22 56
xrayn...@kalrayinc.com • [ https://ww
Hi,
I have a build job with the following pipeline, which works just fine:
@Library('isccr-addons')_
pipeline {
agent any
stages {
stage ('init') {
steps {
isccrExec "${ISCCR_ADDONS_CONFIG}", "${WORKSPACE}
}
Hello,
It deletes the files even if the polling did not find any change and the
job did not start. So the step Clean should not be executed (in current
Jenkins it is like that).
Thank you.
Vladimir
st 18. 1. 2023 v 8:35 odesílatel 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googl
