|
||||||||
|
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... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)
- [JIRA] (JENKINS-16373) email-ext can't access... [email protected] (JIRA)

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