I have multiple materials for a pipeline which are for separate repositories. Often, a check-in spans multiple repositories.Is there any way to delay the trigger of a pipeline when a repository change is detected, to allow the developer to make multiple check-ins prior to having a continuous build kickoff? And is it possible for this muti-repository triggering to be consolidated, such that only one pipeline trigger is done, rather than one for every check-in during this time delay window?
By default, Go polls the repository once every minute. Therefore the trigger of the pipeline is not dependent on the every check in. Go server wait for one minute (in this time there might be multiple check ins from multiple users. After a minute has passed the server will check for changes and pick up all the changes that occurred in that minute.
You can increase the polling frequency of the server in order to delay the polling time.
Steps to increase the polling frequency:
#stop the server
sudo /etc/init.d/go-server stop
#please update this line in /etc/default/go-server
#and make sure that the next line that exports the property is uncommented
Here is an example of increase the polling frequency to 5 minutes (300000 milliseconds = 5 minutes)