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
Lock down everything in branch to this release #767
Conversation
|
Thinking more about that...that's dumb, we can just use the canary image on release-1.0/release-1.1 branch for the broker images. |
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.
👍
| @@ -418,7 +418,7 @@ parameters: | |||
| - description: Container Image to use for Ansible Service Broker in format of imagename:tag | |||
| displayname: Ansible Service Broker Image | |||
| name: BROKER_IMAGE | |||
| value: ansibleplaybookbundle/origin-ansible-service-broker:latest | |||
| value: ansibleplaybookbundle/origin-ansible-service-broker:release-1.0 | |||
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.
Do we just do this as part of our branching exercise?
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.
I believe we should. I think in the future, when we talk about branching, we should make sure the container images (and tags) exist for the branch and are up to date then create the new branch with these changes.
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.
seems reasonable.
Make it so things in the
release-1.0branch userelease-1.0images + packages + etc.