Some feedback: 2.5-beta-4 passed 'smoke-testing', both with a local, and a remote executor. My current setup is Jenkins 1.593 on Ubuntu 14.04 x64 Java 1.8.0, and Debian Wheezy x64 OpenJDK-6 on the slave.

When I use the 'svn' step everything worked as expected (polling, etc) as long as the repository doesn't require credentials.

Using the 'general SCM', credentials were passed correctly to the executor (also remote). However, I observed the following problems:

  • when the authentication fails (i.e. wrong, or no credentials) I get a stack trace together with the error message from the SCM step
  • polling doesn't work with the 'general SCM' step (I think this is a known bug, and there is a work-around which I should look up)
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to