-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Flask] bitrise pipelines #6645
Merged
Merged
Changes from 1 commit
Commits
Show all changes
39 commits
Select commit
Hold shift + click to select a range
99710ef
basic pipeline scaffold
owencraston f621274
flask release ios
owencraston 95fda8a
android release scripts
owencraston 018ff06
check for sentry props on flask build
owencraston 3e0e16e
bitrise certificate
owencraston cd861a8
debug/release provisioning profiles
owencraston 9b02f37
basic build steps
owencraston 47b75d2
flask pipelines
owencraston 50a3475
fix yaml
owencraston 5247447
remap flask variables
owencraston 5924596
remove pubnub keys
owencraston 7b275c4
add deploy pipelines
owencraston 56f03d4
fix file paths and undo edits to qa build
owencraston 69ccfe9
new flask release pipelines
owencraston 061b507
update set-versions script and try to fix sourcemaps for flask
owencraston df55ec1
try a different sourcemp filepath
owencraston e82ff36
upgrade ruby version
owencraston 5727bc3
update signing
owencraston 2acb01b
set env to flask
owencraston 5ca20dd
square icons
owencraston 5b6d2d8
manually remove icon alpha
owencraston 48b71e8
add archive path var
owencraston 575e326
introduce build types in build pipeline
owencraston 2191e4c
remove echo
owencraston 17b6758
pass params to derive sentry environment and tests
owencraston 2a71962
new build numbers
owencraston 37aeb8a
fix: update cookie-tough dependency (#6772)
tommasini 80aa292
move versions into product flavours
owencraston 78c4a01
test prod build with flask variables
owencraston da12ce0
cleanup deriveSentryEnvironment function
owencraston fe3069e
cleanup comment
owencraston f79aab3
reset build numbers
owencraston 9490d89
enable deploy to android and pass in env variable
owencraston 38d2dc6
new syntax
owencraston 1da8ac1
is expand true
owencraston 6dfcce6
no android pipeline
owencraston cbd72aa
new syntax
owencraston 889d066
new new syntax
owencraston 285b28c
new new new syntax
owencraston File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -708,7 +708,7 @@ workflows: | |
- content: |- | ||
#!/usr/bin/env bash | ||
node -v | ||
METAMASK_ENVIRONMENT='flask' yarn build:ios:pre-flask | ||
METAMASK_BUILD_TYPE=flask METAMASK_ENVIRONMENT='production' yarn build:ios:pre-flask | ||
title: iOS Sourcemaps & Build | ||
is_always_run: false | ||
- [email protected]: | ||
|
@@ -756,7 +756,7 @@ workflows: | |
- content: |- | ||
#!/usr/bin/env bash | ||
node -v | ||
METAMASK_ENVIRONMENT='flask' yarn build:android:pre-release:bundle:flask | ||
METAMASK_BUILD_TYPE=flask METAMASK_ENVIRONMENT='production' yarn build:android:pre-release:bundle:flask | ||
title: Build Android Pre-Release Bundle | ||
is_always_run: false | ||
- save-gradle-cache@1: {} | ||
|
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.
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.
Can you add tests with explicit output and comments? This thing is getting out of hand.
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.
On extension we found it easier to disable Sentry entirely in development builds (see https://github.com/MetaMask/metamask-extension/blob/230c0c6fa1626bc1afd68c22321f5c166425dd12/app/scripts/lib/setupSentry.js#L88). Most of our Sentry testing was done with QA or production-like builds as part of regression testing. On the rare occasion that we wanted to test Sentry with a development build, it's easy to comment out that line.
That would reduce this condition to a single ternary:
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.
If we wanted to go that route here, and disable Sentry for development builds, that would be simpler to do in a separate PR. Better to keep this one focused if we can.
A more direct solution to cleaning this up for now would be to split this into two steps: determine the environment, then the sentry environment. e.g.
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 have went ahead and modified this logic to live inside a function I am calling
deriveSentryEnvironment
.This function is well tested in the new
sentryUtils.test.ts
file. I opted to not split up the meta mask environment and sentry environment to keep continuity with what we have already published in sentry. what would be the use case for having a separatemetamaskEnvironment
if we don't log it in sentry?