-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add tests #6
Labels
Comments
mostaphaRoudsari
added
P2-Important: ⚠️
RFC/Discussion 💬
Request for Comments / Discussion
labels
Feb 7, 2021
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: