According to @tom, we have some seriously beefy aws instances on both
linux and windows (4 times beefier than linux!). Let's see what this does.
Signed-off-by: Ryan Davis <zenspider@chef.io>
Allow expeditor to automatically assign PR's opened by the team.
Prevent expeditor from posting pull_request template on PR's opened by the team.
Signed-off-by: Miah Johnson <miah@chia-pet.org>
This change updates InSpec begin using the streamlined release notes
process we are already using on Automate and Chef Workstation. More
details on this new process can be found on the following epic:
https://github.com/chef/release-engineering/issues/692
Signed-off-by: Seth Chisamore <schisamo@chef.io>
This change ensures we are promoting our Hab packages to `current` and
`stable` at the same time we execute said promotions for the Omnibus
packages.
Signed-off-by: Seth Chisamore <schisamo@chef.io>
The Habitat plan has been modified to support building from the repo
rather than relying on a gem being pushed to RubyGems. This allows
us to build current packages at every merge rather than only pushing to
Habitat Builder when we promote to stable.
This change also enables Expeditor to perform builds for us and removes
the dependency on the rake task as it is no longer needed.
Signed-off-by: Adam Leff <adam@leff.co>
* Build and tag docker image via Expeditor
In order to provide Docker images of all unstable, current, and stable
builds of InSpec, and to avoid having to manually publish Docker images
each time we release InSpec, Expeditor will now take care of this for us.
Signed-off-by: Adam Leff <adam@leff.co>
merge_actions must now be an array rather than a hash. Also adding
the ability for Expeditor to create a GitHub Release entry when
an artifact is promoted to stable.
Signed-off-by: Adam Leff <adam@leff.co>
* Publish rubygem via expeditor
When InSpec is promoted to the `stable` channel, Expeditor will take care of the gem publishing!
Signed-off-by: Adam Leff <adam@leff.co>
This will allow for four different changelog categories (in addition to the default)
that will be used based on PR label.
Signed-off-by: Adam Leff <adam@leff.co>
In the event we have a docs-only change or similar which does not necessitate a
version bump, changelog update, or omnibus build, a single label named
`Expeditor: Skip All` can be used rather than adding individual labels.
Signed-off-by: Adam Leff <adam@leff.co>
With this configuration change, expeditor will add a "latest stable"
section to the changelog automatically whenever we promote InSpec
to the stable channel. All existing changelog entries will remain,
and any additional changelog entries that have been made in newer
versions that are newer than the artifact being promoted will
remain intact.
Signed-off-by: Adam Leff <adam@leff.co>
This change updates this repo to begin using the following standard
behavior from Expeditor following a merge to the master branch:
* Automatically bump the `PATCH` version in the `VERSION` file (see https://git.io/vQQYR)
* Create a git tag for the new version (see https://git.io/vQQYR)
* Trigger a release build on manhattan.ci.chef.co using the new tag (see https://git.io/vQQY1)
* Automatically update CHANGELOG (coming soon...the `built_in:update_changelog` merge action is in development)
More details on Expeditor can be found at:
https://github.com/chef/es-lita/tree/master/lita-expeditor
Signed-off-by: Seth Chisamore <schisamo@chef.io>
