packer

Commit Graph

Author	SHA1	Message	Date
Lucas Bajolet	27538f377b	release/ci: remove trailing whitespace	2 years ago
Lucas Bajolet	55a11fe7f4	release/ci: disable automatic version bump	2 years ago
hashicorp-copywrite[bot]	19055df3ec	[COMPLIANCE] License changes (#12568 ) * Updating the license from MPL to Business Source License Going forward, this project will be licensed under the Business Source License v1.1. Please see our blog post for more details at https://hashi.co/bsl-blog, FAQ at https://hashi.co/license-faq, and details of the license at www.hashicorp.com/bsl. * Update copyright file headers to BUSL-1.1 --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
hashicorp-copywrite[bot]	b7df3ca36f	[COMPLIANCE] Add Copyright and License Headers (#12254 ) Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	3 years ago
Wilken Rivera	150767792c	Add release branches to CRT build pipeline This change will allow for release branches `release/<MAJOR>.<MINOR>.x` to be built add uploaded to the CRT build tool chain, which can then be promoted and released publicly if needed.	3 years ago
claire labry	0d94e7d753	Introduce action-set-product-version for Packer (#12135 ) This change introduces the new actions-set-product-version, a tiny, but mighty, GitHub action that acts as a bridge between the product repo and our new CRT feature: automated version bumping. tl;dr automated version bumping has a new command (bob update version) in the bob CLI that automatically bumps the version to a new patch. This automation has been introduced to crt-workflows-common as a new workflow (with the new bob command) and handles version bumping at the end of the release pipeline (after being released to production); for example, 1.0.0→1.0.1 and 1.0.0-dev→1.0.0. Bumping the minor version (ie 1.0.x→1.1.0) is only supported manually via bob update version -bump minor, but not supported in CRT (this work is upcoming). This is made possible by adding the new event “bump-version” in the ci.hcl file in this PR. What this small action does: Allows for the static version string from the version/VERSION file to be read by the new CRT workflow and automagically be bumped to the next version (whether it be a minor, or patch, or major version bump). Outputs an error if there’s no VERSION file in the version dir Outputs an error if there’s no version string in the VERSION file Is able to parse product_version if it is 1.3.0-alpha1 as 1.3.0 (example: when product_version = 1.3.0-alpha1, base_version = 1.3.0) Is able to parse prerelease product versions such as alpha1 (example prerelease_product_version = alpha1) in the statement above.	3 years ago
Mariano Asselborn	08255b8ca4	Enable Iron Bank integration	4 years ago
Claire Labry	3c76f5a95e	introduces the post publish website event	4 years ago
Michele Degges	a8bbf7ae92	[CI-only] Build and publish dev dockerhub images (#11790 )	4 years ago
Jeanne Angeles Franco	ea70359e52	Add release metadata config (#11747 ) * Add release metadat config * Move the release metadata config to the correct event workflow	4 years ago
Adrien Delorme	7661e41412	reference main branch instead of master branch (#11652 ) using search-n-replace	4 years ago
Michele Degges	b63a9c9803	Onboard to CRT (#11564 ) Onboard Packer to CRT Co-authored-by: Wilken Rivera <wilken@hashicorp.com> Co-authored-by: Claire Labry <claire@hashicorp.com>	4 years ago

12 Commits (plugin_load_spec_docs)