Target intrinsic order

Some targets should be run before others, to minimize harm in case one of them fails. The order should be determined by ascending impact/cost of reverting ratio. For example, registry should always be run last. We may also want to have an option to disable this order. How to approach this is open for discussion.

For context, see https://github.com/getsentry/sentry-javascript/pull/4171.

[BYK]

@iker-barriocanal not every target. The current way, the ordered-list definition does what you say and we will keep that way of defining targets for backwards compatibility. What I’m proposing is a new type of target config with a dict where you can optionally set dependencies.

For instance, for the Craft releases themselves, I see on reason why npm, docker, and registry targets to wait for each other. Heck, even the github target can just happen anytime as it has its own artifact, the compiled binary. So, for Craft itself for instance, running all targets in parallel would be the more sensible solution. For any other project that wants to be more conservative, they can keep using the old list-style config or manually depend on things (such as registry depending on others, and github depending on registry etc.)

[iker-barriocanal]

I understand, but that way will make every target depend on another target, which means executing targets linearly in a specific order and not parallelizing them. Is there something I’m missing?