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

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.