-
Notifications
You must be signed in to change notification settings - Fork 841
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
Consolidate and Automate Enterprise Release Process #6606
Comments
All work is being done on a branch on gitlab, on our All the enterprise stuff should happen in gitlab + runway. That way we can open up the governance teams to non-vmware employees. |
pipeline is set in https://runway-ci.eng.vmware.com/teams/concourse-team/pipelines/enterprise-release. The publish job will create a release that contains both bosh and helm release together with related license files. Tasks remaining:
|
Added https://gitlab.eng.vmware.com/concourse/osm for manually OSM source package uploading. |
There are now three releases that we need to ship every time that we release the commercial version of Concourse:
Unfortunately, these releases all have separate pipelines/steps to deploy. Some are more automated than others:
It would be nice to consolidate all of these pipelines/process as much as we can into one large enterprise release pipeline. This would make it easier for anyone on the team to ship the enterprise release as well as remove a lot of the manual toil of which @scottietremendous holds most of the context.
As an added bonus, it'd be nice to use these pipelines to automate the OSL and OSM process. This would make releasing especially stress-free.
The text was updated successfully, but these errors were encountered: