I'm not understanding the process that Jenkins uses for interacting with the source control system. Oh, I understand that there are various plugins for various source control systems with various capabilities, but I'm not understanding what the flow is. Questions:
1. When is the source control system called to pull a workspace? 2. Can I control the parameters to the pull command? 3. Is it expected that every build is done to a fresh workspace? 4. Or is it that, after the workspace is setup, future builds will be incremental? 5. How and when does Jenkins do its polling of the source control system? 6. If the build does an update of some source (for instance, the build version#), how should the update be pushed back into the source control system? I hope that gives an idea of what I'm looking for. Is there any documentation or examples of setting up jobs in Jenkins to work with a source control system? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
