-
Notifications
You must be signed in to change notification settings - Fork 735
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 argo-ci and pr check #34
Comments
@edlee2121 @shrinandj Can you guys tackle this issue? Right now, we just need it to run the project tests. |
Sure. I'll do this. |
I have access to the Kubernetes cluster where Argo's current builds happen. Currently creating the workflow for building |
I created a workflow for running the CI for argo-events. However, I'm running into a problem where the workflow does not complete even though the pod execution has completed. Filed an issue on the main argo repo for it. |
This commit creates the workflow that will be run on every PR for argo-events. Testing Done: 1. Ran workflow independently on a cluster. It succeeded modulo appropriate RBAC role (See argoproj/argo-workflows#898 for details). Refs argoproj#34.
This commit creates the workflow that will be run on every PR for argo-events. Testing Done: 1. Ran workflow independently on a cluster. It succeeded modulo appropriate RBAC role (See argoproj/argo-workflows#898 for details). Refs #34.
CI for pull-requests has been setup. |
This commit creates the workflow that will be run on every PR for argo-events. Testing Done: 1. Ran workflow independently on a cluster. It succeeded modulo appropriate RBAC role (See argoproj/argo-workflows#898 for details). Refs argoproj#34.
Is your feature request related to a problem? Please describe.
Since this project is now under the Argo Project, we should follow suite with the other projects and add an
.argo-ci/ci.yaml
file and setup the appropriate build/test checks.Describe the solution you'd like
Create the CI process for Argo-Events.
Describe alternatives you've considered
I have a working
.travis.yml
file in the repo and was previously using Travis-CI test/builds to verify PR checks. I would need access to the Travis CI for Argo.The text was updated successfully, but these errors were encountered: