-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Change Azure PR deploy storage #16304
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 7e1fd8b:
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: 7f3b1fa3fac2b558c9c8b63a4b55ac6da5a4687d (build) |
@ecraig12345 we need apply the "404 page" trick for new storage with a redirect otherwise N* docs will be broken on deep URLs:
|
I suggest to update the database anyway to avoid this warning. |
That is also in the existing 404 in the the fabricweb storage account |
Thanks for the note on the 404 page, I knew there was something else we needed to do but for some reason when I downloaded the existing 404 page from fabricweb storage it didn't include the script block? That's fixed now. |
From the error message it wasn't clear to me whether this was a real issue and if so, whether the suggested fix was actually applicable to our situation. I was also hesitant to mess with this dependency since it's specific to northstar, which I'm less familiar with. So I'd prefer if one of you could fix it @layershifter or @ling1726. |
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Potential regressions comparing to master
Perf comparison
Perf tests with no regressions
|
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.
LGTM, thanks for addressing comments 👍
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
CI still fails with unclear timeout. @ecraig12345 any ideas? |
cac9623
to
35669c0
Compare
On second thought, closing this and making a new PR. |
Switch PR deploys and perf results to use the
fluentuipr
Azure storage account (and an Azure connection which only has access to that storage account), and simplify the URLs. This means PR deploy URLs will now be likehttps://fluentuipr.z22.web.core.windows.net/pull/#####/
instead ofhttp://fabricweb.z5.web.core.windows.net/pr-deploy-site/refs/pull/#####/merge/
. (Or for CI builds it'shttps://fluentuipr.z22.web.core.windows.net/heads/branchname/
.)Also switch the release build to only upload artifacts, and use a separate internal release pipeline to upload those artifacts to
fabricweb
blob storage.After this PR merges, I'll be changing permission settings so that pipelines (particularly in the public ADO project) don't have permission to upload to
fabricweb
.Additional related changes:
Build.SourceBranch
(notBuild.SourceVersion
) in deploy URLs. This makes the structure easier to navigate in the storage explorer and easier for humans to parse.pull/####/react-northstar-screener
(orheads/branchname/react-northstar-screener
)fabricweb
storage