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
Is it possible to ignore a failure in a ContainerSet dependency chain?
My case is that I clone a repo into a ContainerSet pod and then run linter, unit tests and build containers in a dependancies chain.
However I don’t want the linter failing to cause the workflow to fail (but I do want the step marked red)
Previously I did this with continueOn in a steps workflow. But that had issues with sharing the source code clone between pods without multiple clones or copying elsewhere.
Any advice on the most efficient way to achieve this use case (using ContainerSets or not) would be fantastic.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is it possible to ignore a failure in a ContainerSet dependency chain?
My case is that I clone a repo into a ContainerSet pod and then run linter, unit tests and build containers in a dependancies chain.
However I don’t want the linter failing to cause the workflow to fail (but I do want the step marked red)
Previously I did this with continueOn in a steps workflow. But that had issues with sharing the source code clone between pods without multiple clones or copying elsewhere.
Any advice on the most efficient way to achieve this use case (using ContainerSets or not) would be fantastic.
Thanks
Adam
Beta Was this translation helpful? Give feedback.
All reactions