Hi, I redirected both jobs to use our main git repository directly. The trick was to read via HTTPS, plain HTTP didn't work. The on-commit job now polls in a 10 minute interval.
Both changes together should give us much faster feedback. Regards, Matthias On Thursday, 2012-08-09, Matthias Friedrich wrote: > On Thursday, 2012-08-09, Josh Wills wrote: > [...] > > What are the consequences of Jenkins being able to push to the main > > repo? All else being equal, I prefer the quick feedback. > > Since we didn't activate any publishing option in the config, it most > probably won't push anything. I don't have production experience with > the Git plugin though, so I'm a bit cautious. > > Feel free to switch to the main repo and set polling to something like > "*/10 * * * *" if you want quicker feedback. > > Really quick feedback would require triggering Jenkins from a Git > post-commit hook. But let's stay with polling for now, it's less error > prone and easier to set up. > > Regards, > Matthias
