Hi,

Solution to problem you describe should probably be a per repository 
limitation, not for SCM type alone.
Symptoms mentioned in this case are per server, but the proposed solution 
focuses on SCM type. 

I would see following use cases:
1) multiple servers of the same SCM type where different servers have different 
load capabilities.
         (i.e. some internal that are powerful some external that should not be 
taxed heavily)

2) a server running multiple SCMs with different resource needs.
         ( i.e. server running a slow legacy SCM from a tape library and a new 
SCM on SSD)  

Jan

On Sep 26, 2013, at 02:44, Sascha Vogt wrote:

> Hi all,
> 
> We are currently in the unfortunate situation that we have multiple SCM
> types (CVS, SVN, Git) and use polling for them. Now, our CVS server is
> quite slow and to restrict the load, we have to put a limit on the
> concurrent pollings. While the other SCMs are much faster (and with Git
> we even push, but pushing means a custom poll task is added to the
> polling queue), CVS tasks block the queue.
> 
> Would it make sense to have a queue per SCM type? Would this be a
> welcomed contribution? Or should this be a new configuration option
> (flag: restrict per type or overall)?
> 
> For Git we're using the URL
> /git/notifyCommit?url=$url/git/$repository.name - would it be possible
> to bypass the polling queue only for Git? That would already help a bit.
> 
> Greetings
> -Sascha-
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" 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.

Jan Ruzicka
Senior Software Engineer
Comtech Mobile Datacom Corporation
20430 Century Blvd, Germantown, MD 20874
Office: 240-686-3300
Fax: 240-686-3301
 
The information contained in this message may be privileged and/or 
confidential. If you are not the intended recipient, or responsible for 
delivering this message to the intended recipient, any review, forwarding, 
dissemination, distribution or copying of this communication or any 
attachment(s) is strictly prohibited. If you have received this message in 
error, please so notify the sender immediately, and delete it and all 
attachments from your computer and network.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" 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.

Reply via email to