-
Notifications
You must be signed in to change notification settings - Fork 160
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
Test pr to test expeditor validation #432
Closed
Closed
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
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
…ckage Package chef-vault as an hab package
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
…line-for-hab [CHEF-17477] Buildkite pipelines for building and verifying hab pkgs
…ique/test-hab-pipelines
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Signed-off-by: Ashique Saidalavi <[email protected]>
Fixing the buildkite pipelines for hab
Signed-off-by: Ashique Saidalavi <[email protected]>
Test commit for pipeline testing
Obvious fix; these changes are the result of automation not creative thinking.
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Removed the manually created pipelines and added the channels
Obvious fix; these changes are the result of automation not creative thinking.
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Adding pipelines to trigger pipeline automatically
Obvious fix; these changes are the result of automation not creative thinking.
Signed-off-by: nikhil2611 <[email protected]>
Empty commit to test pipelines
Obvious fix; these changes are the result of automation not creative thinking.
* updating version to major version and few plan file fixes Signed-off-by: nikhil2611 <[email protected]> * reverting back the release branch changes and version update Signed-off-by: nikhil2611 <[email protected]> * swapping order of action Signed-off-by: nikhil2611 <[email protected]> * swapping order of action to fix expeditor error Signed-off-by: nikhil2611 <[email protected]> * commenting the trigger pipeline to test expeditor config Signed-off-by: nikhil2611 <[email protected]> * commenting the build gem to test expeditor config Signed-off-by: nikhil2611 <[email protected]> * commenting the build gem to test expeditor config Signed-off-by: nikhil2611 <[email protected]> * fixing expeditor error Signed-off-by: nikhil2611 <[email protected]> * fixing expeditor error Signed-off-by: nikhil2611 <[email protected]> * fixing the expeditor errro Signed-off-by: nikhil2611 <[email protected]> * adding back the trigger pipeline Signed-off-by: nikhil2611 <[email protected]> * adding old config to test the expeditor failure Signed-off-by: nikhil2611 <[email protected]> * now trying to add updated config Signed-off-by: nikhil2611 <[email protected]> * adding release branch to test the expeditor validation Signed-off-by: nikhil2611 <[email protected]> * reverted back the release branch Signed-off-by: nikhil2611 <[email protected]> * update to unstable channel in the workload Signed-off-by: nikhil2611 <[email protected]> * removed the build gem Signed-off-by: nikhil2611 <[email protected]> * added back the release branch Signed-off-by: nikhil2611 <[email protected]> * added back the release branch Signed-off-by: nikhil2611 <[email protected]> * added the env variable in the builkite config Signed-off-by: nikhil2611 <[email protected]> --------- Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
|
|
Just for testing. Not needed closing this. |
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
Related Issue
Types of changes
Checklist:
Gemfile.lock
has changed, I have used--conservative
to do it and included the full output in the Description above.