-
Notifications
You must be signed in to change notification settings - Fork 144
Add Buildkite Config #305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Buildkite Config #305
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a comment. Thanks!
.buildkite/pipeline.yml
Outdated
@@ -0,0 +1,44 @@ | |||
env: | |||
SEGMENT_CONTEXTS: "snyk,npm,aws-credentials,ecr,saucelabs" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are going to need npm-publish
(I think that's the name). It's a context with write access on NPM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CarlosMecha I talked with tooling and updated the npm context to npm-publish
so it has read and write access, as well as pass the NPM_TOKEN
env var to the plugin as well in the publish step.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚒
This reverts commit ab2ec4d.
* Initial buildkite config * Test just build * Fix interpolation issue * Change docker image * Change dockerfile * Add user * Add buildkite tests * Fix user * Combine build and test * Add Synk test * Add saucelabs * Add publish step and remove comments * Remove circleci-enterprise * Change npm context for read/write access
* Initial buildkite config * Test just build * Fix interpolation issue * Change docker image * Change dockerfile * Add user * Add buildkite tests * Fix user * Combine build and test * Add Synk test * Add saucelabs * Add publish step and remove comments * Remove circleci-enterprise * Change npm context for read/write access
What does this PR do?
Are there breaking changes in this PR?
No.
Any background context you want to provide?
Segment is migrating from Circle CI Enterprise to using Buildkite. We will maintain 2 CI workflows for a.js integrations. Buildkite will be used as our internal CI workflow. Our external CI flow for contractors will run on CirclCI cloud.
Is there parity with the server-side/android/iOS integration components (if applicable)?
N/A
Does this require a new integration setting? If so, please explain how the new setting works
N/A
Links to helpful docs and other external resources
* Buildkite User Guide
* Buildkite migration guide