Quantcast

[JIRA] (JENKINS-13347) Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13347) Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'

JIRA noreply@jenkins-ci.org
Ronan Jouchet created JENKINS-13347:
---------------------------------------

             Summary: Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'
                 Key: JENKINS-13347
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13347
             Project: Jenkins
          Issue Type: Bug
          Components: build-name-setter
         Environment: Windows 2008 R2 SP1
Java 1.6.0_31 x64
Tomcat 6.0.35
Jenkins 1.458
SVN
            Reporter: Ronan Jouchet
            Assignee: Kohsuke Kawaguchi


My Jenkins instance/project are working just fine and builds work as expected.
Now I try to use the "build-name-setter" plugin. My goal is to have build names like "svn123build9879".

I installed the plugin via the plugin manager, and set the new "Build Name" field to "svn${SVN_REVISION}build${BUILD_NUMBER}" (without quotes). It looks like the expected syntax, and I can see ${SVN_REVISION} in my env-vars.html
However, this leads to the following error in the console log:
Unrecognized macro 'SVN_REVISION' in 'svn${SVN_REVISION}build${BUILD_NUMBER}'

I'm available for more info. I searched for similar bugs, sorry if that's not a but but just a misconfiguration, please point me to what you think might be wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13347) Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'

JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ronan Jouchet updated JENKINS-13347:
------------------------------------

    Environment:
Windows 2008 R2 SP1 x64
Java 1.6.0_31 x64 from Oracle
Tomcat 6.0.35
Jenkins 1.458, freshly installed and never upgraded
SVN

  was:
Windows 2008 R2 SP1
Java 1.6.0_31 x64
Tomcat 6.0.35
Jenkins 1.458
SVN

   

> Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13347
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13347
>             Project: Jenkins
>          Issue Type: Bug
>          Components: build-name-setter
>         Environment: Windows 2008 R2 SP1 x64
> Java 1.6.0_31 x64 from Oracle
> Tomcat 6.0.35
> Jenkins 1.458, freshly installed and never upgraded
> SVN
>            Reporter: Ronan Jouchet
>            Assignee: Kohsuke Kawaguchi
>              Labels: plugin
>
> My Jenkins instance/project are working just fine and builds work as expected.
> Now I try to use the "build-name-setter" plugin. My goal is to have build names like "svn123build9879".
> I installed the plugin via the plugin manager, and set the new "Build Name" field to "svn${SVN_REVISION}build${BUILD_NUMBER}" (without quotes). It looks like the expected syntax, and I can see ${SVN_REVISION} in my env-vars.html
> However, this leads to the following error in the console log:
> Unrecognized macro 'SVN_REVISION' in 'svn${SVN_REVISION}build${BUILD_NUMBER}'
> I'm available for more info. I searched for similar bugs, sorry if that's not a but but just a misconfiguration, please point me to what you think might be wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13347) Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161316#comment-161316 ]

Ronan Jouchet edited comment on JENKINS-13347 at 4/5/12 8:18 PM:
-----------------------------------------------------------------

Actually my problem is not related to SVN_REVISION. All macros seem to fail: setting build-name=${BUILD_NUMBER}-${JOB_NAME} returns this:
Unrecognized macro 'JOB_NAME' in '${BUILD_NUMBER}-${JOB_NAME}'
               
      was (Author: ronj):
    Actually my problem is not related to SVN_REVISION. All macros seem to fail: setting build-name=${BUILD_NUMBER}-${JOB_NAME} returns in:

Unrecognized macro 'JOB_NAME' in '${BUILD_NUMBER}-${JOB_NAME}'
                 

> Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13347
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13347
>             Project: Jenkins
>          Issue Type: Bug
>          Components: build-name-setter
>         Environment: Windows 2008 R2 SP1 x64
> Java 1.6.0_31 x64 from Oracle
> Tomcat 6.0.35
> Jenkins 1.458, freshly installed and never upgraded
> SVN
>            Reporter: Ronan Jouchet
>            Assignee: Kohsuke Kawaguchi
>              Labels: plugin
>
> My Jenkins instance/project are working just fine and builds work as expected.
> Now I try to use the "build-name-setter" plugin. My goal is to have build names like "svn123build9879".
> I installed the plugin via the plugin manager, and set the new "Build Name" field to "svn${SVN_REVISION}build${BUILD_NUMBER}" (without quotes). It looks like the expected syntax, and I can see ${SVN_REVISION} in my env-vars.html
> However, this leads to the following error in the console log:
> Unrecognized macro 'SVN_REVISION' in 'svn${SVN_REVISION}build${BUILD_NUMBER}'
> I'm available for more info. I searched for similar bugs, sorry if that's not a but but just a misconfiguration, please point me to what you think might be wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13347) Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161316#comment-161316 ]

Ronan Jouchet commented on JENKINS-13347:
-----------------------------------------

Actually my problem is not related to SVN_REVISION. All macros seem to fail: setting build-name=${BUILD_NUMBER}-${JOB_NAME} returns in:

Unrecognized macro 'JOB_NAME' in '${BUILD_NUMBER}-${JOB_NAME}'
               

> Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13347
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13347
>             Project: Jenkins
>          Issue Type: Bug
>          Components: build-name-setter
>         Environment: Windows 2008 R2 SP1 x64
> Java 1.6.0_31 x64 from Oracle
> Tomcat 6.0.35
> Jenkins 1.458, freshly installed and never upgraded
> SVN
>            Reporter: Ronan Jouchet
>            Assignee: Kohsuke Kawaguchi
>              Labels: plugin
>
> My Jenkins instance/project are working just fine and builds work as expected.
> Now I try to use the "build-name-setter" plugin. My goal is to have build names like "svn123build9879".
> I installed the plugin via the plugin manager, and set the new "Build Name" field to "svn${SVN_REVISION}build${BUILD_NUMBER}" (without quotes). It looks like the expected syntax, and I can see ${SVN_REVISION} in my env-vars.html
> However, this leads to the following error in the console log:
> Unrecognized macro 'SVN_REVISION' in 'svn${SVN_REVISION}build${BUILD_NUMBER}'
> I'm available for more info. I searched for similar bugs, sorry if that's not a but but just a misconfiguration, please point me to what you think might be wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13347) Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ronan Jouchet updated JENKINS-13347:
------------------------------------

    Summary: Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}  (was: Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION')
   

> Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}
> ------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13347
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13347
>             Project: Jenkins
>          Issue Type: Bug
>          Components: build-name-setter
>         Environment: Windows 2008 R2 SP1 x64
> Java 1.6.0_31 x64 from Oracle
> Tomcat 6.0.35
> Jenkins 1.458, freshly installed and never upgraded
> SVN
>            Reporter: Ronan Jouchet
>            Assignee: Kohsuke Kawaguchi
>              Labels: plugin
>
> My Jenkins instance/project are working just fine and builds work as expected.
> Now I try to use the "build-name-setter" plugin. My goal is to have build names like "svn123build9879".
> I installed the plugin via the plugin manager, and set the new "Build Name" field to "svn${SVN_REVISION}build${BUILD_NUMBER}" (without quotes). It looks like the expected syntax, and I can see ${SVN_REVISION} in my env-vars.html
> However, this leads to the following error in the console log:
> Unrecognized macro 'SVN_REVISION' in 'svn${SVN_REVISION}build${BUILD_NUMBER}'
> I'm available for more info. I searched for similar bugs, sorry if that's not a but but just a misconfiguration, please point me to what you think might be wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13347) Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Workaround:

${ENV,var="SVN_REVISION"}

Note: When using multiple Subversion locations, the environment variables are names such as:

SVN_REVISION_1, SVN_REVISION_2, ...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13347) Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Works! I think the more general bug remains valid, so I won't close yet.
Thanks for the help

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13347) Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Glad I could help. I looked up the environment variables for the project by calling:
http://localhost:8080/env-vars.html/?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] [build-name-setter] (JENKINS-13347) Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Juraj Misur commented on Bug JENKINS-13347

I have a release build where I can specify release version via "Release_version" string parameter and I want use that one for setting build name using this parameter as ${Release_version}. That would be super cool. Would the ENV hack work here?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Loading...