Hi, We are switching from SVN to GIT, and I am now looking into how to get/keep our projects running on Jenkins. I have some questions about the GIT-plugin, which I hope someone here might be able to answer.
With the SVN-plugin and multi config job, the master checked out the latest version and 'told' the slaves which version to use for the build. Does the GIT-plugin do the same? Since my testing repository is small, the checkout is very fast and I am unable to simulate a check-in during the update on master. Also, if I use the option to make a 'shallow clone', will I still be able to see the changes made since my last build or only those that were in the last push to the server? For now, it's not a problem to do a full clone, the repo will be very small, but if it will grow as large as our SVN did, the shallow-option will be a real performance-gain. Thanks! Roland -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
