Untimely 'pages:deploy' execution causes the stage to be the last in the pipelines graph
Summary
Given the following stages:
stages:
- build-images
- build
- test
- deploy
- post-deploy
we have the pages
job running in the deploy
stage and some other jobs running in the post-deploy
stage. Yet, if the pages:deploy
job is executed after the jobs in post-deploy
finish, you can see it moved to the end of the pipeline: https://gitlab.com/gitlab-com/gitlab-docs/pipelines/19742330.
I guess this is correct based on the time each job/stage finished, but it doesn't agree with what you have set up in stages
. I would expect the order to be respected.
Example Project
- pipeline https://gitlab.com/gitlab-com/gitlab-docs/pipelines/19742330
-
.gitlab-ci.yml
https://gitlab.com/gitlab-com/gitlab-docs/blob/43b8108b036da5bb8f9c87630fc6987c9512cc2c/.gitlab-ci.yml
Possible fixes
We can mark the pages
job as running until pages:deploy
finishes (maybe we also need to put a timeout on pages:deploy
).