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
Stop publishing runtime-extension-internal.zip #3984
Conversation
StressTestWebsite.zip is still used (we upload it to IIS Stress Test Infra). Can we still build StressTestWebsite.zip, but keep it in a bin folder next to the stress test site as we don't need to sign it? |
Oh, I was misinformed then. Who uploads this and when? I couldn't find anything in our build drops or CI config for this. |
We have to manually upload it unfortunately because we can't access corpnet through VSTS. Hence, we can probably just create a zip file in a bin folder instead of artifacts. |
…tension-internal.zip
Okay, I'm going to change the output path for this zip so it goes to |
…time-extension-internal.zip
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 don't see any changes for runtime-extension-internal.zip, did you revert them accidentally?
Oops, re-reverted |
🆙 📅 Chatted in person. We'll leave the /t:PackageStressTestApp target, but remove it from running by default on CI since we normally only upload local builds anyways into our internal stress test infrastructure. |
Neither of these zips are used anymore, and they currently fail sign checks because they were not configure to run through SignTool.