-
Notifications
You must be signed in to change notification settings - Fork 227
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
ci: Add Cilium to CNI | LSG Integration Pipeline #2574
Conversation
3ef6a0b
to
8cc3995
Compare
This pull request is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days |
This pull request is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days |
8cc3995
to
e05a503
Compare
e05a503
to
fcf5c62
Compare
e06bbd6
to
6ddbf15
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How/When will we run this pipeline ?
This pipeline is to be triggered by LSG through their CI/CD. The only time we run it ourselves is if we see something breaking ex. nightly pipelines.
There will be documentation that supports this pipeline that explains the How and key areas of importance. |
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
a8dfe5b
to
1712761
Compare
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
Reason for Change:
Adding cilium scenario for additional coverage.
Changing from parameter injection when triggering pipeline to variable injection.
Issue Fixed:
Requirements:
Notes: