As a paas-templates author
In order to cut and official new release
I need an automated process to
build a final bosh release
publish it into a draft github release along with artefacts
Given a tag is manually pushed
git tag -a -m "manually cutting 0.7.0" 0.7.0
git push origin 0.7.0
[x] Then the release-after-build workflow triggers
[x] creates a new branch 0.7.0-release
[ ] push the new branch 0.7.0-release
[x] build a final bosh release 0.7.0
[x] commits the bosh files to branch 0.7.0-release
[x] merge the branch 0.7.0-release into master and push master
[ ] create a new tag 0.7.0-bosh
publish it into a final github release 0.7.0 along with artefacts
Contribute new feature
As a paas-templates author
In order to contribute to the release (e.g. add new properties such as #6)
I need an automated process to
build a final bosh release
publish it into a draft github release along with artefacts (named after the feature branch name + commit-hash summary)
Given a feature branch issue-6-tracing is pushed and referenced in a PR #7
[ ] Then a worflow triggers and creates a bosh final release published into a draft github release
Pb: coa and paas-templates only support immutable bosh releases and forward-only naming schemes.
Test a new feature onto a bosh director
Given a feature branch issue-6-tracing is pushed and referenced in a PR #7
And a draft github release published the release tgz and git tag
When I need test it in paas-templates onto a bosh director
And I update the coa root-deployment.yml to bump to the new version
Then coa precompiles the release and trigger new deployment
Use cases
Cut a new final release
As a paas-templates author In order to cut and official new release I need an automated process to
Given a tag is manually pushed
release-after-buildworkflow triggers0.7.0-release0.7.0-release0.7.00.7.0-release0.7.0-releaseintomasterand push master0.7.0-bosh0.7.0along with artefactsContribute new feature
As a paas-templates author In order to contribute to the release (e.g. add new properties such as #6) I need an automated process to
Given a feature branch
issue-6-tracingis pushed and referenced in a PR #7Pb: coa and paas-templates only support immutable bosh releases and forward-only naming schemes.
Test a new feature onto a bosh director
Given a feature branch
issue-6-tracingis pushed and referenced in a PR #7 And a draft github release published the release tgz and git tag When I need test it in paas-templates onto a bosh director And I update the coaroot-deployment.ymlto bump to the new version Then coa precompiles the release and trigger new deploymentCurrent state
Branches
Workflows:
git tag -a v1.25.4+k3s1+bosh-1 -m "additional release for wrapper changes".github/workflows/on-tags.yml(say tag124.14)releases/k3s/k3s-124.14.yml)v124.14) with updated final bosh release source (egreleases/k3s/k3s-124.14.yml)124.14)v124.14).github/workflows/on-commits.ymlfrommasterandrelease-*branchesRenovate:
release-1.24to only k3s patch versions