Re: How to use the environment variables set by a parameterized build?

[Martin Lichtin]

I'm talking about a build job that is parameterized. The parameter is of 
type "run parameter".
Jenkins creates variables with names that cannot be used in a pre-step 
shell script. Quite annoying.

On Saturday, November 17, 2012 11:56:40 PM UTC+1, r2_ wrote:
>
> Hey,
>
> Checkout the environmental variable here: 
> https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project
> Short answer: 
> echo ${JOB_NAME}
> echo ${BUILD_NUMBER}
>
>
> On Friday, November 16, 2012 3:39:26 PM UTC-5, Martin Lichtin wrote:
>>
>> Hi
>> For a parameterized build with one "run parameter" (let's name it X), 
>> Jenkins set three environment variables.
>>
>> X
>> X.jobName
>> X.number
>>
>> How can the latter two be used in a pre-step shell script?
>> Bash cannot handle environment variables containing a dot, it seems.
>>
>> $ echo ${X.jobName}
>> bash: ${X.jobName}: bad substitution
>>
>>

How to use the environment variables set by a parameterized build?

[Martin Lichtin]

Hi
For a parameterized build with one "run parameter" (let's name it X), 
Jenkins set three environment variables.

X
X.jobName
X.number

How can the latter two be used in a pre-step shell script?
Bash cannot handle environment variables containing a dot, it seems.

$ echo ${X.jobName}
bash: ${X.jobName}: bad substitution

Scm of type: org.jenkinsci.plugins.multiplescms.MultiSCM is not supported

[Martin Lichtin]

Hi

I'm running into the following problem and report it as requested:

[RELEASE] Release build triggered
ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-us...@googlegroups.comjava.lang.UnsupportedOperationException 
:
 Scm of type: org.jenkinsci.plugins.multiplescms.MultiSCM is not supported
at 
org.jfrog.hudson.release.scm.AbstractScmCoordinator.createScmCoordinator(AbstractScmCoordinator.java:63)
 

at 
org.jfrog.hudson.release.maven.MavenReleaseWrapper.setUp(MavenReleaseWrapper.java:130)
 

at 
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:605) 

at 
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473) 

at hudson.model.Run.run(Run.java:1410) 

at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) 

at hudson.model.ResourceController.execute(ResourceController.java:88) 

at hudson.model.Executor.run(Executor.java:238) 



Running Jenkins ver. 1.456 

Problem with Artifactory Plugin Release Management

[Martin Lichtin]

Trying to "Build and Release to Artifactory", using all default settings.
It fails with a strange Git error.

*> [RELEASE] Committing release version on branch 'REL-BRANCH-inuc-0.0.2'*

*> [RELEASE] Creating tag 'inuc-0.0.2'*

*> [RELEASE] Pushing branch 'REL-BRANCH-inuc-0.0.2' to 
'/git/inuc/core/main.git'*

*> [RELEASE] Pushing tag 'inuc-0.0.2' to '/git/inuc/core/main.git'*

*> Failure in post build SCM action: Failed checkout branch: Command 
"/usr/bin/git checkout dev" returned status code 1:*

*> stdout:*

*> stderr: error: pathspec 'dev' did not match any file(s) known to git.*
Any ideas what could be wrong here. The "dev" branch obviously exists, its 
the only branch and the one we do development on.

*> [RELEASE] Committing release version on branch 'REL-BRANCH-inuc-0.0.2'*

*> [RELEASE] Creating tag 'inuc-0.0.2'*

*> [RELEASE] Pushing branch 'REL-BRANCH-inuc-0.0.2' to 
'/git/inuc/core/main.git'*

*> [RELEASE] Pushing tag 'inuc-0.0.2' to '/git/inuc/core/main.git'*

*> Failure in post build SCM action: Failed checkout branch: Command 
"/usr/bin/git checkout dev" returned status code 1:*

*> stdout:*

*> stderr: error: pathspec 'dev' did not match any file(s) known to git.*