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
I'm looking for a way to declare build dependencies. These have a reversed logic to normal dependencies.
The current logic with dependencies is correct for most cases: tasks can optionally be skipped based on status or sources, dependencies need to be run before making the decision to skip because they may change the decision 👌
But with build dependencies that sequence is reversed. The build dependencies only need to be run if the task is not skipped. So the decision to skip need to be made before executing the dependancies, and skip the building the dependencies if the dependant is skipped.
That is, build dependencies should be skipped if all of their dependants are skipped.
Example use cases include:
building a build tool that is executed in a later step
downloading large static reference data. The reference data may not be included in the final artefact, but is needed for the build
As a trivial example I want a way to make something like this, where build-a will be skipped on the second run.
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.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm looking for a way to declare build dependencies. These have a reversed logic to normal dependencies.
The current logic with dependencies is correct for most cases: tasks can optionally be skipped based on
status
orsources
, dependencies need to be run before making the decision to skip because they may change the decision 👌But with build dependencies that sequence is reversed. The build dependencies only need to be run if the task is not skipped. So the decision to skip need to be made before executing the dependancies, and skip the building the dependencies if the dependant is skipped.
That is, build dependencies should be skipped if all of their dependants are skipped.
Example use cases include:
As a trivial example I want a way to make something like this, where
build-a
will be skipped on the second run.Beta Was this translation helpful? Give feedback.
All reactions