Skip to main content

number_of_concurrent_updates

Configuration​

name: number_of_concurrent_updates
type: int
default: 0
{
"name": "company/project",
"extra": {
"violinist": {
"number_of_concurrent_updates": 0
}
}
}

Indicate how many open pull requests you want at a time.

Explanation​

If you have a whole range of build steps and environments for a project per branch, having a bunch of branches come in from Violinist might clog up your build pipeline or spin up many servers. If this is the case, and you want to throttle the pull requests Violinist keeps open, then this option is for you.

Example​

If you have a large project, some times the number of dependencies that are out of date could be many, especially when starting Violinist monitoring for the first time. And maybe you are creating QA enviroments for all your branches, or maybe your branches trigger build steps that take a long time to complete. So you want to throttle Violinist somehow. Then this option is for you. So if you wanted to limit the number of open pull requests to 5, for example, then you would change your composer.json to look something like this:

{
"name": "company/project",
"description": "My awesome project",
"require": {
"vendor/package": "~1.0.0",
},
"extra": {
"violinist": {
"number_of_concurrent_updates": 5
}
}
}

This way, Violinist will normally stop creating additional update pull requests when 5 are already open. Explicit concurrency exceptions can allow additional pull requests beyond this limit, such as security updates or packages configured in concurrent_updates_bypass_packages.