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
This is Issue is motivated by some hiccups trying to run the minimal system quick test on this morning's candidate fddaq-v5.2.1-rc1-a9 release. It seems like it would be a good idea if we extended the integration test workflow to allow users to manually pass it the name of an arbitrary frozen or candidate release to run on (this is already available for nightlies). It would of course require adding some if-then logic to account for the fact that dbt-setup-workarea uses different arguments based on the kind of release, but shouldn't be too difficult.
The text was updated successfully, but these errors were encountered:
This is Issue is motivated by some hiccups trying to run the minimal system quick test on this morning's candidate
fddaq-v5.2.1-rc1-a9
release. It seems like it would be a good idea if we extended the integration test workflow to allow users to manually pass it the name of an arbitrary frozen or candidate release to run on (this is already available for nightlies). It would of course require adding some if-then logic to account for the fact thatdbt-setup-workarea
uses different arguments based on the kind of release, but shouldn't be too difficult.The text was updated successfully, but these errors were encountered: