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 can think of two different approaches to set-up tests for this repository and none is ideal.
convert to luigi pipeline and run the translated recipe - this approach will catch the issues in the recipe but will not catch any pollination-specific issues.
push to pollination and run a test - In this case the recipe is already pushed to pollination so it might be too late to learn about the issue.
@AntoineDao, what are your thoughts about the best approach here?
The text was updated successfully, but these errors were encountered:
We could use queenbee-argo with a special "CI" config to schedule the runs on our staging cluster and somehow track the outputs.
The recipe could be scheduled like the one in this example.
Tracking the recipe would be trickier... I would propose adding some special start/end handling system inside of queenbee-argo so it scheduled modified argo workflows that communicate with the github API to create check suites.
I can think of two different approaches to set-up tests for this repository and none is ideal.
@AntoineDao, what are your thoughts about the best approach here?
The text was updated successfully, but these errors were encountered: