lab ci wait

[temp]

I don't know wether or not this is possible, but it would be nice to have a ci command that simpy waits for the current pipeline to finish and then exits with status code 0 for success, and 1 for failure.
This would allow scripting of several pipelines that need to be run in a specific order. I know you can trigger builds inside a pipeline, but we need it the other way - like a listener.

This would allow something like this:

cd /whatever/docker-base
lab ci create
lab ci wait
cd /whatever/docker-project-that-uses-docker-base
# or maybe
lab ci create --wait
cd /whatever/another-docker-project-that-uses-docker-base
# or maybe
lab ci create
lab ci trace --exit-on-finish
...

[zaquestion]

I'm pretty sure we can pull this off! Thanks for including your usecase as well, that goes a long way in integrating your idea into lab as a whole and provide a tangible workflow to justify implementation.

That said, have you looked at multi-project pipelines in GitLab? This may fit your usecase more elegantly that the feature would?? https://docs.gitlab.com/ee/ci/multi_project_pipelines.html -- Let me know!

[temp]

Yes, I looked at multi project pipelines, but they don't support our use case.
We don't need a trigger from upstream, but a listen from downstream.
Like in my example a base docker image.
Now for example 10 projects use this base docker image, and every time the base docker image is built, I want the 10 project docker images to be rebuild. But I don't want to add trigger code for each project in the base docker repository...

[zaquestion]

@temp lab ci status --wait was added in 0.15.0 please let me know if this works for your purpose and reopen if needed.

[temp]

Looking good!
Maybe the spam-factor can be reduced by waiting a second between status-check while --wait'ing? Or add something like --quiet?

[temp]

Ah, some weirdness remains ;-)
I have a status --wait running, and it's still printing running messages, but a status on a second console reveals:

± lab ci status
Stage:   Name              - Status
...
Pipeline Status: failed

Maybe the wait is already done, but he's still busy printing?