Yes - that's what I ended with - I was a bit dim in the start not really
reasoning over what WORKSPACE really is.
Thanks a lot for your time and answer!
onsdag 27. januar 2016 20.20.25 UTC+1 skrev Craig Rodrigues følgende:
>
> Hi,
>
> You could also work around this by doing:
>
> node() {
> workspace = pwd()
> // rest of code here
> }
>
> See:
> https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test.groovy
>
> for an example.
> --
> Craig
>
> On Wed, Jan 27, 2016 at 10:49 AM, Eric Pyle <[email protected]
> <javascript:>> wrote:
>
>> Workaround:
>>
>> sh 'pwd > pwd.txt'
>> workspace = readFile('pwd.txt')
>>
>>
>> On 1/27/2016 1:15 PM, Eric Pyle wrote:
>>
>> WORKSPACE is documented as not being available in workflow/pipeline
>> scripts. I found this when you select "env" under Global Variables in the
>> snippet generator:
>>
>> The following variables are currently unavailable inside a workflow
>> script:
>>
>> - EXECUTOR_NUMBER
>> - NODE_LABELS
>> - WORKSPACE
>> - SCM-specific variables such as SVN_REVISION
>>
>>
>>
>> On 1/27/2016 4:14 AM, David Karlsen wrote:
>>
>> I have this build definition:
>>
>> node ('docker') {
>> wrap([$class: 'TimestamperBuildWrapper']) {
>> stage 'checkout'
>> checkout scm: [$class: 'GitSCM', branches: [[name: '*/develop']],
>> userRemoteConfigs: [[url: ' <javascript:>ssh:...@myserver:port/myrepo.git
>> <javascript:>']]]
>>
>> stage 'unit-test'
>> env.JAVA_HOME="${tool 'Oracle-JDK8-64bit'}"
>> def mvnHome = tool 'apache-maven-3.x'
>> def workSpace = env.WORKSPACE
>> def mvnCmd = "${mvnHome}/bin/mvn -B
>> -Dmaven.repo.local=${workSpace}/.m2"
>> echo "workspace: ${workSpace} mvnCmd: ${mvnCmd}"
>> sh "${mvnCmd}/bin/mvn -B clean install"
>> ....
>>
>>
>>
>>
>> But workspace is null:
>>
>> Running: Print Message*08:55:38* *workspace: null* mvnCmd:
>> /var/lib/jenkins/tools/maven/apache-maven-3.x/bin/mvn -B
>> -Dmaven.repo.local=null/.m2
>>
>>
>> Should it not be assigned to the env.WORKSPACE var by default?
>> --
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit
>> <https://groups.google.com/d/msgid/jenkinsci-users/5d2f08e0-f692-4b6e-a657-dbb5bc66a251%40googlegroups.com>
>> https://groups.google.com/d/msgid/jenkinsci-users/5d2f08e0-f692-4b6e-a657-dbb5bc66a251%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/56A9114F.8080909%40cd-adapco.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/56A9114F.8080909%40cd-adapco.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/1ee35c16-f449-4136-a30a-4e5dc0e370f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
