Comments (2)
Okay I made a few edits to the steps, feel free to make any changes to it!
Steps for a new major/minor release:
-
Once all the commits are into master for your release, create the release notes. Move the contents ofrelease-notes/latest.md
into a new release note file ofrelease-notes/v<M.m.p>
. Then create your release branch on theconcourse/concourse
github repo with the following formatrelease/M.m.x
(M being the major version and m being the minor version)- This is now automated using https://github.com/clarafu/release-me,
Lines 930 to 934 in f8e639f
ci/tasks/scripts/build-release-notes
Lines 6 to 12 in f8e639f
- This is now automated using https://github.com/clarafu/release-me,
-
Create the release branch on the
concourse/concourse-bosh-release
repository. Make any missing changes to the spec ofweb
orworker
depending on if the release contains any changes that adds or modifies any flags.- Any changes you make on the branch will not get automatically merged back to master so try to make the changes on master and then create the branch from there.
- We should really have something that will merge the branch back to master. (like we do for the
concourse/concourse
branches)
-
Create the release branch on
concourse/concourse-bosh-deployment
repository. -
Create the release branch on
concourse/concourse-chart
repository. Same with theconcourse-bosh-release
repo, make any missing changes tovalues.yaml
ortemplates/web-deployment.yaml
for changes to flags on web ortemplates/worker-deployment.yaml
for changes to flags on the worker. New features to the chart are added to thedev
branch vsmaster
gets bug-fixes. This distinction should guide whether the release branch should be created fromdev
(major/minor release) ormaster
(patch release). -
Bump the appropriate versions for resource types. Go to the releases page
https://project.concourse-ci.org/releases
and take a look at which resource type repositories have had new commits or PRs. Take a look at what those changes entail and bump the version in their respective pipeline inci.concourse-ci.org
.- If the changes were only README or repo restructuring changes with no user impact, you don't need to bump the version
- If the changes were small bug fixes or changes, you can do a patch version bump
- If the changes were adding of features, you can do a minor version bump
- If the changes involve a breaking changes, that should be a major version bump
-
Add your release pipeline to the
reconfigure-pipeline
-
Go through all the
needs-documentation
PRs in the release page for your milestonehttps://project.concourse-ci.org/releases/concourse?milestone=v<M.m.p>
and make sure that everything has proper documentation withinconcourse/docs
(if needed). You can organize which PRs by clicking on the button to add whichever label best fits that PR.- If it is already documented within
concourse/docs
, add arelease/documented
label - If there is no documentation and the changes have user impact that should be documented, add the documentation to
concourse/docs
(or delegate) then add arelease/documented
label after finished. E.g. the addition of a new step type ( set_pipeline step). - If there is no documentation and the changes have user impact that do not need to be documented, add a
release/undocumented
label. E.g. an experimental feature. - If there is no documentation and the changes do not have user impact, add a
release/no-impact
label. E.g. refactors.
- If it is already documented within
-
Once the all source code changes are finalize, Concourse RC version should be deployed to CI
- including all the external workers (pr-worker, ci-topgun-worker, darwin-worker & BOSH deployed windows worker)
-
Once the final commit has made it through the pipeline, the
create-draft-release
job can be triggered. This job will create a draft release within the concourse GitHub release page where you can make any final adjustments or arrangements to the generated release notes. PLEASE NOTE that any manual changes made on the draft release WILL BE OVERWRITTEN if you retrigger thecreate-draft-release
job. Please be sure to only make manual edits AFTER you are sure this is the final run of the job.- If you would like to edit the content, you can directly edit the PRs that it was generated from. The title is used for each PR and also the body within the
Release Note
header in the PR. After you have made your edits within the PR, you can rerun thecreate-draft-release
job in order to regenerate a new release note. - If you would like to change the arrangement of the PRs within the release note, you can make the edits directly on the release note of the draft release.
- If you would like to edit the content, you can directly edit the PRs that it was generated from. The title is used for each PR and also the body within the
-
Once everything is ready, the
shipit
job can be triggered. Thepublish-binaries
job will convert your draft release into a final release including the body of your draft release (which will persist any changes you made to the draft release body). Subsequently, the promote concourse job will run automatically. Thepublish-docs
job needs to be triggered manually. -
The helm-chart pipeline is used to bump & then publish the chart.
-
Once the Concourse release is shipped, Concourse should be deployed to Hush-House
from ci.
I've made some changes that incorporate Clara's changes directly to the issue description
from ci.
Related Issues (20)
- shipping the latest `cbd` with `release.yml` does not result in a tag on master HOT 1
- regressions on older Linux kernels HOT 1
- Release 6.4.0 HOT 24
- Revert Downgrade `fly watch` test being skipped
- Visibility into failures while working remotely HOT 4
- containerd binaries are not bundled in release tarballs HOT 2
- enable `across` step on CI, use it for testflight/bin-smoke permutations HOT 4
- Release 6.6.0 HOT 5
- fly can't reach the concourse server HOT 3
- Release 6.7.0 HOT 2
- PR pipeline will fail for older patch releases HOT 1
- Release 6.7.3 HOT 1
- Release 6.7.4 HOT 1
- Golang darwin 1.18.1 break fly build
- Infrastructure generate report job report bosh jumpbox vm as not needed HOT 1
- Wavefront Concourse cluster is terminated for production, hush-house and dispatcher usage HOT 1
- Cant see pipelines in concourse ui with my github credentials HOT 2
- Bump terraform version for ubuntu Jammy support HOT 1
- dev-image dockerfile is broken since gdn binary supports arm
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ci.