added numberOfPipelinesPerProject option to GitLab service config #75
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds a new configuration option called
numberOfPipelinesPerProject
to the GitLab service config, allowing the user to specify the maximum number of pipelines (builds) to fetch for a single project.This will allow users to select a group of repositories (e.g., all repositories that are owned by the user corresponding to the key that the GitLab API is called with) and specify that the build monitor should show only X builds per project. When the builds are sorted by IDs (which is the case right now), this ensures that only the most recent X builds appear on the CI display. In our case, we use it with X=1 to show only the most recent build for a group of repositories being monitored.