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
Recently work was done to expand the Job Dependencies feature to give the ability for builders to have more control over when a job is run due to changes in a dependent file. There is a PR posted here: o3de/o3de#6862 with the changes. There's been some discussion over whether or not this change warrants an RFC, so I'd like to see what the SIG's opinion is on it.
Overview of the change:
This change is meant to address the problem of too many jobs being unnecessarily run as a result of 1 file changing. It adds an additional field to Job Dependencies allowing a list of SubIds to be specified. When the AP sees a dependency with a list of source dependencies, it no longer triggers the job immediately, it instead waits until the triggering job has finished process, compares the current vs previous hash of the product and only processes the dependency if one of the products from the SubId list has changed.
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
-
Recently work was done to expand the Job Dependencies feature to give the ability for builders to have more control over when a job is run due to changes in a dependent file. There is a PR posted here: o3de/o3de#6862 with the changes. There's been some discussion over whether or not this change warrants an RFC, so I'd like to see what the SIG's opinion is on it.
Overview of the change:
This change is meant to address the problem of too many jobs being unnecessarily run as a result of 1 file changing. It adds an additional field to Job Dependencies allowing a list of SubIds to be specified. When the AP sees a dependency with a list of source dependencies, it no longer triggers the job immediately, it instead waits until the triggering job has finished process, compares the current vs previous hash of the product and only processes the dependency if one of the products from the SubId list has changed.
Beta Was this translation helpful? Give feedback.
All reactions