Currently with stack dependencies that share outputs, if the output hasnt changed but the dependent stack is affected by the push - the run will still be skipped as the output has not changed.
Since I can’t edit the Post, here’s the description again:
Given two stacks: A and B, where B depends on output A.a, we get the following issue:
If both A and B are based on the same source repository and there is a PR commit that affects both of them, but does not change the output A.a, then the Run for B gets skipped in spite of the code changes that affect it.
SpaceliftUser
Team•
Jul 3
I believe you can define an always changing output (e.g. a timestamp), so it will always trigger B if A was triggered. What do you think? Does this address your case?
Harlequin Star
•
Feb 28, 2025
I don’t know why, but I can’t see the detailed description I provided in the “Problem” section of the form :/
Log in to comment and vote
Comments3
Harlequin Star
Feb 28, 2025
Since I can’t edit the Post, here’s the description again:
Given two stacks:
AandB, whereBdepends on outputA.a, we get the following issue:If both
AandBare based on the same source repository and there is a PR commit that affects both of them, but does not change the outputA.a, then the Run forBgets skipped in spite of the code changes that affect it.SpaceliftUser
Jul 3
I believe you can define an always changing output (e.g. a timestamp), so it will always trigger
BifAwas triggered. What do you think? Does this address your case?Harlequin Star
Feb 28, 2025
I don’t know why, but I can’t see the detailed description I provided in the “Problem” section of the form :/