Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

ci: build and push layotto/proxyv2 image after new version is released #708

Open
seeflood opened this issue Jul 9, 2022 · 0 comments
Open

ci: build and push layotto/proxyv2 image after new version is released #708

seeflood opened this issue Jul 9, 2022 · 0 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed kind/ci kind/easy

Comments

@seeflood
Copy link
Member

seeflood commented Jul 9, 2022 •
edited
Loading

What would you like to be added:
Our CI can build and push layotto/proxyv2:latest image after new PR merged. See #655

The next step is to build and push layotto/proxyv2:version image in layotto-release pipeline, e.g. automatically build layotto/proxyv2:v0.5.0 after v0.5.0 is released

It's a subtask of #471

Why is this needed:
For istio deployment
@seeflood seeflood added good first issue Good for newcomers help wanted Extra attention is needed kind/easy kind/ci labels Jul 9, 2022
@seeflood seeflood mentioned this issue Jul 9, 2022
Closed
26 tasks
@seeflood seeflood changed the title ci: build and push layotto/proxyv2:version image in layotto-release pipeline ci: build and push layotto/proxyv2:version image after new version is released Jul 9, 2022
@seeflood seeflood changed the title ci: build and push layotto/proxyv2:version image after new version is released ci: build and push layotto/proxyv2 image after new version is released Jul 9, 2022
@Kelei0215 Kelei0215 mentioned this issue Jul 11, 2022
Open
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers help wanted Extra attention is needed kind/ci kind/easy
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@seeflood