|
||||||||
|
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-13831) Need a way to co... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)
- [JIRA] (JENKINS-13831) Need a way ... [email protected] (JIRA)

Yes, of course. We used to use rsync and it works fine. But we wanted to switch over to a more integrated configuration experience: Configure the target hosts in the jenkins configuration and refer to this configuration from a job., use include patterns as in every other place within the build jobs and so on. So this is not a real blocker, but would make life a lot easier. Not to mention that rsync is not available on Windows hosts, in contrast to jenkins and its plugins.