You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dagger now offers built-in interactive debugging with Terminal(), which is much nicer than what we have right now.
While converting to use Terminal(), we should also switch to the new dagger pipeline structure - this is not exactly necessary since the old way is still supported (and there are no plans to discontinue it), it would however make use of Terminal() a much nicer and more convenient.
With Terminal() we get more control over what happens - right now we have to roll-back into state before the compilation started because of technical reason. With this new Terminal(), this should no longer be necessary. This would be great thing for projects which take long time to compile, such as OpenBMC (whenever we add support to it). Use would not longer have to wait for build to fail, have the container reset, ssh into it and re-run the compilation step to try to reproduce the error.
The text was updated successfully, but these errors were encountered:
Dagger blog post and discussion #239
The plan:
Terminal()
, which is much nicer than what we have right now.Terminal()
, we should also switch to the new dagger pipeline structure - this is not exactly necessary since the old way is still supported (and there are no plans to discontinue it), it would however make use ofTerminal()
a much nicer and more convenient.Terminal()
we get more control over what happens - right now we have to roll-back into state before the compilation started because of technical reason. With this newTerminal()
, this should no longer be necessary. This would be great thing for projects which take long time to compile, such as OpenBMC (whenever we add support to it). Use would not longer have to wait for build to fail, have the container reset, ssh into it and re-run the compilation step to try to reproduce the error.The text was updated successfully, but these errors were encountered: