Conversation
|
This is ready for review. Until we have an artifacts viewer (that's more accessible than the s3 console) I don't think we should shut off the jenkins plugin, but I do think it makes sense to run in a limited fashion so we can make sure it's stable. When #14122 is merged I'm going to change the screenshots path. I'll change it after if this gets merged first. |
|
Can you create a follow-up issue to add a landing page to reference these assets, similar to the release manager? |
|
This needs updates to include a landing page, until then the uploads aren't especially useful. I'll come back to this in the future, my internal priority clock has pushed this down now that we aren't uploading assets on every build |
|
Nope nevermind I'm going to open a new PR for this, the build tasks have change. The issue to track is #13786. |
💔 Build Failed |
3 participants
At the end of a jenkins run this will publish screenshots and packages to an s3 bucket. We've been using the jenkins-s3 plugin but have been running into lower level upload errors that we have limited control over.
Closes #13786