Page MenuHomePhabricator

Ensure efficient Gitlab CI operations for scap
Closed, ResolvedPublic


Efficient means that if the list of packages mentioned in .pipeline/blubber.yaml hasn't changed nor have any of requirements.txt, test-requirements.txt, or docs/requirements.txt changed, then CI should run quickly (not installing deb packages or python dependencies), even if the CI job is scheduled on a runner were it has not recently run. This means centralized cache storage will be required.

Stage execution time targets:

test2 minutes30 seconds
verify-deps1 minute15 seconds

Event Timeline

dancy claimed this task.

Scap Gitlab CI is working well, close enough to the desired time targets.