-
Notifications
You must be signed in to change notification settings - Fork 456
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
chore: Download latest bundle analysis artifact from base branch #2994
Conversation
Branch preview✅ Deploy successful! https://fix_bundle_analysis--walletweb.review-wallet-web.5afe.dev |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
2e7e134
to
514d651
Compare
Coverage report
Show files with reduced coverage 🔻
Test suite run success1288 tests passing in 178 suites. Report generated by 🧪jest coverage report action from 16b9bde |
af7d339
to
9f75fe7
Compare
📦 Next.js Bundle Analysis for safe-wallet-webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
9f75fe7
to
bf119b6
Compare
bf119b6
to
16b9bde
Compare
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 it works, it works, but not ideal that we have to do it "manually"...
set +x | ||
curl -H "Accept: application/vnd.github+json" -H "Authorization: token $GH_TOKEN" -L -o "${DESTINATION}.zip" "$DOWNLOAD_URL" | ||
set -x | ||
unzip "${DESTINATION}.zip" -d "${DESTINATION}" && mkdir -p "${DESTINATION}/bundle" && mv "${DESTINATION}/__bundle_analysis.json" "${DESTINATION}/bundle/" |
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.
We need to unzip the contents of ${DESTINATION}.zip
into the directory ${DESTINATION}/bundle
. I tried using wildcards but without success so I hard-code the filename here.
Agreed, I've left a message in a related issue on hashicorp/nextjs-bundle-analysis#66 |
What it solves
Follow up for #2803
The download-artifact action we use downloads artifacts in chronological order so it always compares with the oldest dev bundle instead of the newest. There is an open issue on the board but no fix so far (see discussion). We switch to a custom bash script that is also linked in the discussion to download and unzip the bundle from dev.
Screenshots
Checklist