Buildkite pipeline for acceptance tests #741
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Porting the acceptance job to Buildkite. I moved all the logic of the Makefile into a more Buildkite way of handling secrets (via pre-command) to benefit from secrets redaction.
This reverts commit 4211c0e.
nkammah
commented
Nov 21, 2023
catalog-info.yaml
Outdated
| spec: | ||
| repository: elastic/terraform-provider-ec | ||
| pipeline_file: ".buildkite/pipeline.yml" | ||
| teams: |
There was a problem hiding this comment.
The below team perms mirror the current GitHub permissions on the repository - this is also reflected in the GH repository RE : https://github.com/elastic/catalog-info/pull/635
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Migrate the Jenkins Acceptance tests pipeline to Buildkite.
Notes:
EC_API_KEYinto the pre-command hook under theTERRAFORM_PROVIDER_API_KEY_SECRETvariable - this allows us to benefit from Buildkite's built-in secrets redaction (see doc).ci/Makefileor any of its target, but we should keep it around for developers to run this locally (tho we may need to update the secrets path to point to the new ci-vault-path)Related Issues
Motivation and Context
How Has This Been Tested?
Types of Changes
Readiness Checklist