Tag Info

New answers tagged


I'm not sure the polling resources argument is compelling. It's a relatively efficient operation on most version control systems, especially if you're just checking and not actually downloading the changes yet. Although, a push notification is certainly preferable. Usually it's the building resources that are the limiting factor, depending how frequently ...


There are two things here - the client (in this case Jenkins) and the server (svn or git or something else). As the client, asking every minute can consume a bit of resources - network and disk on the server, not to mention its own internal builds that compete with local resources for checking if anything has been updated. At the server side, having a half ...

Top 50 recent answers are included