Add BitbucketBuildEnvironment for better progress indicators #3685
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
knutwannheden
approved these changes
Nov 14, 2023
|
Looks like this needs another coordinate merge and deploy, because we're adding a marker. |
|
sure, will do! |
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.
What's changed?
Add Bitbucket BuildEnvironment
What's your motivation?
Recognize bitbucket CI, such that the CLI progress bar adjusts output.
Anything in particular you'd like reviewers to focus on?
Any reason we didn't have this before?
Anything we should be mindful of in terms of detection order?
Have you considered any alternatives or workarounds?
We could detect
CIonly as a catch all CI env; but then we lack input forGitProvenance.Any additional context
As per https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/