I am looking into using Jenkins as a tool for continuous deployment. A commit to a git repository triggers building of rpms, updating a yum repo, possibly triggering production machines to do a yum update, etc. I've set up a test project, and Jenkins seems like it provides a lot of useful functionality.
Unfortunately the way our company is set up, we have hundreds of git repositories and more added every week (they are all separate ad campaigns for various clients). Some questions I have: Does Jenkins performance suffer with potentially hundreds of repositories? (As of today, 352. Most are not changed on a daily basis. Maybe 5-10. Eventually we may have 500 or more simultaneous active campaigns.) Is there an API to create projects? Manually adding 352 is not going to be a good time. I can use Fake or something to script a web browser but that is distasteful. Plus we're going to have to automatically add the new campaigns as they are created. Let me know what you think. Thanks. -jsd- -- 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.
