[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 I only have one build set up. All I did was include several repositories on the same build. Then I added one build step: windows batch file. That step runs a few metrics apps and then calls the company's older bat file that actually builds the application. That older bat can access the environment variables listed here: http://yourjenkinsURL/env-vars.html/ and while SVN_REVISION_1 isn't listed, it works. Email-ext is a post-build step. Is it possible the variable becomes unavailable after building? my build log is kind of big, but the email bit is this: 16:47:14 Email was triggered for: Success 16:47:14 Sending email for trigger: Success 16:47:14 Sending email to: myemailhere 16:47:21 Finished: SUCCESS 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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito
commented on JENKINS-16373
email-ext cant access SVN_REVISION_1
Actually, ${ENV, var="SVN_REVISION_1"} DOES work. I was aborting the project in order to force the email SVN_REVISION_1 was never created. Sorry for wasting your time.
But if you do have some time, I still haven't been able to use these correctly (email has all these lines, none seem to be working):
${CHANGES, showPaths="true", format="%a: %r %p \n--\ %m\", pathFormat="\n\t- %p"}
${CHANGES, showPaths="true", format="%a: %r %p %m\", pathFormat="\t%p\n"}
${CHANGES, showPaths="true", showDependencies="false", format="%a: %r %p \n--\"%m\", pathFormat="\n\t- %p"}
${CHANGES, "true", "false", "%a: %r %p \n--\ %m\", "\n\t- %p"}
${CHANGES, "true", "true", "%a: %r %p %m\", "\n\t- %p"}
${BUILD_LOG_MULTILINE_REGEX, "error", "10", "true", null, "false", null}
${BUILD_LOG_MULTILINE_REGEX, "error", "10", "true"}
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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Slide-O-Mix resolved JENKINS-16373 as Not A Defect email-ext cant access SVN_REVISION_1 Change By: Slide-O-Mix (17/Jan/13 12:30 PM) Status: Open Resolved Resolution: NotADefect 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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito
created JENKINS-16373
email-ext cant access SVN_REVISION_1
Issue Type:
Bug
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
16/Jan/13 11:55 AM
Description:
I'm building a project with multiple SVN repositories. Using the Email-ext plugin to email when a job is successfull or failed.
When I use the token ${SVN_REVISION} all I get is the number 400, which isn't the build number nor any of the repositories' revision number.
What I want to use is the same variable the svn plugin provides: %SVN_REVISION_1%, but neither ${ENV, var="SVN_REVISION_1"} nor ${ENV, var="%SVN_REVISION_1%"} work. Both show up as blanks
Also, when I list the variables (${ENV, var=""}) I can't find SVN_REVISION or SVN_REVISION_1.
The email needs to have SVN_REVISION_1 on the subject, or else it'll be quite a hassle to find what version was built.
Are there any workarounds?
Environment:
Windows XP, Jenkins ver. 1.498, Jenkins Subversion Plug-in 1.44, email-ext 2.25
Project:
Jenkins
Priority:
Major
Reporter:
Eric Brito
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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Slide-O-Mix commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 If the svn plugin doesn't make it available, there is nothing email-ext can do. 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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 I understand. I can access it through a batch file (build step), does that mean it's been made available? And where does the 400 come from when I use $(SVN_REVISION) ? (doesn't svn_revision come from jenkin's built-in svn plugin, just like svn_revision_1) 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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito edited a comment on JENKINS-16373 email-ext cant access SVN_REVISION_1 I understand. I can access it through a batch file (build step), does that mean it's been made available? And where does the 400 come from when I use $(SVN_REVISION) ? (doesn't svn_revision come from jenkin's built-in svn plugin, just like svn_revision_1?) 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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 This is from the Subversion Plugin. Doesn't this mean it should be available? Subversion Revision and URL information as Environment Variables The Subversion SCM plugin exports the svn revisions and URLs of the build's subversion modules as environment variables. These are $SVN_REVISION_n and $SVN_URL_n, where n is the 1-based index of the module in the configuration. For backwards compatibility if there's only a single module, its values are also exported as $SVN_REVISION and $SVN_URL. 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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Slide-O-Mix
commented on JENKINS-16373
email-ext cant access SVN_REVISION_1
Then it should be available to the ENV token, it just uses the build environment variables. Do you have a space between the comma and the words? ${ENV, var="SVN_REVISION_1"}
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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Slide-O-Mix commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 do they expose then through token macro? 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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito
commented on JENKINS-16373
email-ext cant access SVN_REVISION_1
No space, even though the examples I posted above had them. just tried with and without spaces, the results are the same as below:
when I try these 3 lines:
${ENV,var="SVN_REVISION_1"} - blank
${ENV,var="SVN_REVISION"} - blank
${ENV,var=""} - doesn't have SVN_REVISION, SVN_URL
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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito
commented on JENKINS-16373
email-ext cant access SVN_REVISION_1
sorry for posting something off-topic, but while I have your attention: what is wrong with these lines? none of them are working, the email just the entire line as I typed it, no change report:
${CHANGES, showPaths=true, format="%a: %r %p \n--\"%m\", pathFormat="\n\t- %p"}
${CHANGES, showPaths=true, format="%a: %r %p "%m\", pathFormat="\t%p\n"}
${CHANGES, showPaths=true, showDependencies=false, format="%a: %r %p \n--\"%m\", pathFormat="\n\t- %p"}
${CHANGES, true, false, "%a: %r %p \n--\"%m\", "\n\t- %p"}
(would love if there were examples on the tokens reference.
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
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Slide-O-Mix commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 Is the SVN plugin stuff you are doing part of the same build? If not, then the environment variables won't be available. You would have to pass them as parameters to the second build, and then they would be available. 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
