Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve automation of ova release process #1287

Closed
ghost opened this issue Jan 5, 2018 · 4 comments
Closed

Improve automation of ova release process #1287

ghost opened this issue Jan 5, 2018 · 4 comments
Labels
component/infrastructure Infrastructure related to building and testing product/ova Related to the OVA packaging of vSphere Integrated Containers status/needs-estimation The issue needs to be estimated by the team status/needs-triage The issue needs to be evaluated and metadata updated

Comments

@ghost
Copy link

ghost commented Jan 5, 2018

User Statement:

As a release manager for the Vic appliance ova, I want minimal user interaction to spin up and release an appliance ova using drone.

Details:

Our release process is far too manual, mostly because we need to provide component dependency versions by hand.

One possible way to improve the automation is by running a “smarter” build script on pushes to tags, which should use versioned components instead of latest.

Acceptance Criteria:

The release process is less manual, requiring no drone cli interaction. It should be documented in the installer directory.
@AngieCris AngieCris added product/ova Related to the OVA packaging of vSphere Integrated Containers team/lifecycle status/needs-triage The issue needs to be evaluated and metadata updated status/needs-estimation The issue needs to be estimated by the team labels Jan 5, 2018
@andrewtchin andrewtchin removed status/needs-estimation The issue needs to be estimated by the team status/needs-triage The issue needs to be evaluated and metadata updated labels Jan 11, 2018
@andrewtchin
Copy link
Contributor

this story also includes improvement on inclusion of UI plugin in the build to specifically define which version to pull in instead of current dependency on engine build

@andrewtchin andrewtchin added the component/infrastructure Infrastructure related to building and testing label Jan 11, 2018
@andrewtchin
Copy link
Contributor

this story needs to have a discussion with stakeholders about requirements

@andrewtchin andrewtchin added status/needs-triage The issue needs to be evaluated and metadata updated status/needs-estimation The issue needs to be estimated by the team labels Jan 11, 2018
@andrewtchin
Copy link
Contributor

leaving needs estimate to reevaluate after design discussion

@ghost ghost mentioned this issue Feb 1, 2018
Merged
ghost pushed a commit that referenced this issue Feb 15, 2018
Use component release versions in release builds (#1391)
3413da3 
Fetches most recent release component versions 
when building a release ova. Progress #1287.
@zjs
Copy link
Member

zjs commented Jan 28, 2019

The process has been significantly improved. Additional improvements can be tracked separately.

@zjs zjs closed this as completed Jan 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/infrastructure Infrastructure related to building and testing product/ova Related to the OVA packaging of vSphere Integrated Containers status/needs-estimation The issue needs to be estimated by the team status/needs-triage The issue needs to be evaluated and metadata updated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@zjs @andrewtchin @AngieCris