Skip to content

Update file common.gitlab-ci.yml

John Skarbek requested to merge jts/extend-rails-build into master

What does this MR do?

The gitlab-rails-ee is occasionally running into the upper limit set forth by the configuration on our Security instance. This overrides the CI Project config to be configurable here. Most recent jobs whether successful or failed are hovering around 49-58 minutes in run time. This various across all three instances where this job is run.

Set it to 3 hours arbitrarily. Team Delivery will be alerted if builds still take obnoxiously long as we have limits in place on our own build pipelines.

Related issues

Discovered while watching auto-deploy

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Integration tests added to GitLab QA
  • The impact any change in container size has should be evaluated
  • New dependencies are managed with dependencies.io
Edited by John Skarbek

Merge request reports