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
As far as I know, the configurations contain "options" for executors, not the dependency list. So I don't think this is achievable with a custom plugin/executor.
My use case: I want the "deploy" target to rely on "^build" in DEV environment/configuration. And I want it to rely on nothing in QA or PREPROD environment/configuration.
Workaround: create a separate target with the same executor/command with a different list of dependencies:
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
-
Is it possible to define different lists of task dependencies for different configurations/context?
Something like:
As far as I know, the configurations contain "options" for executors, not the dependency list. So I don't think this is achievable with a custom plugin/executor.
My use case: I want the "deploy" target to rely on "^build" in DEV environment/configuration. And I want it to rely on nothing in QA or PREPROD environment/configuration.
Workaround: create a separate target with the same executor/command with a different list of dependencies:
Beta Was this translation helpful? Give feedback.
All reactions