Gerhard Lazu
Gerhard Lazu
Started looking into this.
This is almost there: - [x] address my comments above - [x] uncomment all the workflows that should be running - [x] rebase on top of `main` - [x] trigger...
https://github.com/dagger/dagger/actions/runs/3583093358/jobs/6028108171 triggered https://github.com/dagger/dagger/actions/workflows/provision.yml, but 3x instead of just once 🤔 I think this is happening because we are publishing separate images at once: I know that we are building &...
> For the 1 vs 3x runs, I believe it is due to ... > It gets triggered for each update, however, I wouldn't surprised if the last deployment impacted...
> Is the provision workflow being triggered when a new engine is published? Shouldn't the tests be run against a `DAGGER_HOST` pointing to that new engine? Otherwise you can easily...
FWIW, there is a follow-up diagram here https://github.com/dagger/dagger/pull/4065#issuecomment-1335584172 We still need to add provisioning tests part of publishing, before we actually publish anything (potentially) broken. @grouville has the context.
What should we do about this one @slumbering @dolanor?
Great, looking forward to having this one merged! 💪
Now that https://github.com/dagger/dagger/pull/3459 is in, we are ✅ ❌ ❌ there as far as these blockers are concerned: https://github.com/dagger/dagger/issues/3719#issuecomment-1310171238. Now is a good time to rebase and try to get...
Leaving this with @marcosnils since he has the most context.