Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 0 additions & 24 deletions .expeditor/announce-release.sh

This file was deleted.

4 changes: 0 additions & 4 deletions .expeditor/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -32,27 +32,27 @@
description: "Run a nightly build in the omnibus/adhoc pipeline"
cronline: "0 6 * * *"

pipelines:
- verify
- verify:
public: true
- habitat/build
- habitat/test:
public: true
definition: .expeditor/habitat-test.pipeline.yml
trigger: default
- omnibus/release:
env:
- IGNORE_CACHE: true # caching causes constant build failures
- OMNIBUS_BUILDKITE_PLUGIN_VERSION: 065a32e7298e4998340d119fd5c72e3f7ed0411b
- omnibus/adhoc:
definition: .expeditor/release.omnibus.yml
env:
- ADHOC: true
- OMNIBUS_BUILDKITE_PLUGIN_VERSION: 065a32e7298e4998340d119fd5c72e3f7ed0411b
- post-promote:
description: "Generate and upload release manifest"
definition: .expeditor/post-promote.pipeline.yml

Check failure on line 55 in .expeditor/config.yml

View check run for this annotation

Chef Expeditor / Expeditor Config Validation

.expeditor/config.yml#L35-L55

Could not find .expeditor/verify.pipeline.yml in your repo

# These actions are taken, in the order specified, when an Omnibus artifact is promoted
# within Chef's internal artifact storage system.
Expand All @@ -78,11 +78,7 @@
- built_in:rollover_changelog
- bash:.expeditor/promote_harts_and_containers.sh:
post_commit: true
- bash:.expeditor/publish-release-notes.sh:
post_commit: true
- purge_packages_chef_io_fastly:{{target_channel}}/chef-server/latest
- bash:.expeditor/announce-release.sh:
post_commit: true
- built_in:notify_chefio_slack_channels
- workload: artifact_published:LTS-2024:chef-server:{{version_constraint}}
actions:
Expand Down
30 changes: 0 additions & 30 deletions .expeditor/publish-release-notes.sh

This file was deleted.

2 changes: 1 addition & 1 deletion RELEASE_NOTES.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
# Chef Infra Server Release Notes

See [Chef Infra Server Release Notes](https://docs.chef.io/release_notes_server) for the complete list of product release notes.
See [Chef Infra Server Release Notes](https://docs.chef.io/release_notes/server/) for the complete list of product release notes.
8 changes: 1 addition & 7 deletions RELEASE_PROCESS.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,7 @@ Ensure documentation in [docs-site](https://docs.chef.io/) is updated for change

### Update Release Notes

#### Pending Release Notes In Wiki

https://github.com/chef/chef-server/wiki/Pending-Release-Notes
Release notes are published from the [chef/chef-web-docs repository](https://github.com/chef/chef-web-docs/blob/main/content/release_notes/server.md).

### Getting the build to be released into current with a minor/major version bump

Expand Down Expand Up @@ -237,10 +235,6 @@ https://discourse.chef.io/c/chef-release/9

1. Confirm the existence of the notification in the #chef-server-notify channel.
1. Confirm that the release appears at https://downloads.chef.io/tools/infra-server. This usually takes a while.
1. Confirm that the release notes from Pending Release Notes are automatically posted on discourse. Sample post:
https://discourse.chef.io/t/chef-infra-server-14-10-23-released/20438
1. Confirm that the data for the Pending Release Notes at https://github.com/chef/chef-server/wiki/Pending-Release-Notes is automatically deleted by expeditor, and only the titles remain. Notify releng at https://github.com/chef/release-engineering/issues if this does not automatically happen on promote.
1. Confirm that the release notes appear at https://docs.chef.io/release_notes_server/ . This should happen automatically via expeditor, but if it does not you need to perform the steps manually and create an issue with releng at https://github.com/chef/release-engineering/issues. For instructions on how to proceed with a manual edit, contact docs-support.

In case of release failure, consult appropriate documentation to assist with troubleshooting and correcting the issue.
https://expeditor.chef.io/dashboard/?token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJleHAiOjE2NDYxODMwMTgsImlhdCI6MTY0NjE2ODYxOCwiaXNzIjoiaHR0cHM6Ly9leHBlZGl0b3IuY2hlZi5pbyIsInVzZXJfbG9naW4iOiJQcmFqYWt0YVB1cm9oaXQiLCJ1c2VyX25hbWUiOm51bGwsImFjY2Vzc190b2tlbiI6ImdodV95R3o4MkE5dWg5TzdnVXhOMHhEbXQ5bHU1YXM0YUE0TVZuVjYiLCJhZG1pbiI6dHJ1ZX0.5EZ1GvD_ufWmXPzfosGbs11RXYnHNm7gABgc-TpLgkQ#/
Expand Down
7 changes: 5 additions & 2 deletions omnibus/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,12 @@ In order to facilitate the tedious communication tasks involved in releasing Che

## Release Notes

The RELEASE_NOTES.md file can be viewed as a higher-level, customer-friendly version of CHANGELOG.md. Significant changes to `opscode-omnibus` and its dependencies should be represented in one of the following three categories:
Release notes are a higher-level, customer-friendly version of `CHANGELOG.md`. Significant changes to `opscode-omnibus` and its dependencies should be represented in one of the following three categories:

* What's New
* Bug Fixes
* Security Fixes

These notes will be included as part the blog post for each release.
These notes will be included as part the blog post for each release.

Release notes are published from the [chef-web-docs repository](https://github.com/chef/chef-web-docs/blob/main/content/release_notes/server.md).
Loading