ci: artifacts-upload to s3 - Tag before we upload artifacts to S3#2532
Merged
Ricardo Salveti (ricardosalveti) merged 1 commit intoJul 1, 2026
Merged
Conversation
Satish Mhaske (sampra2025)
force-pushed
the
s3tags
branch
2 times, most recently
from
eb06b60 to
229b73f
Compare
Satish Mhaske (sampra2025)
force-pushed
the
s3tags
branch
3 times, most recently
from
1a4707b to
21b7169
Compare
Satish Mhaske (sampra2025)
force-pushed
the
s3tags
branch
2 times, most recently
from
a7b5e7c to
0df11e8
Compare
Test Results 104 files 628 suites 5h 47m 34s ⏱️ For more details on these failures, see this check. Results for commit 38e878f. ♻️ This comment has been updated with latest results. |
Satish Mhaske (sampra2025)
force-pushed
the
s3tags
branch
2 times, most recently
from
49157ac to
4486a46
Compare
Satish Mhaske (sampra2025)
force-pushed
the
s3tags
branch
from
4486a46 to
b974772
Compare
IT has recently introduced a Tagging policy for S3, requiring each object to be tagged according to the retention policy, for example, "retention=7d" for artifacts kept for 7 days in the S3 bucket. Additional tags like Build type and branch can help to isolate artifacts in the S3 Browser. This will also help to address below issue: - qualcomm-linux#2498 Signed-off-by: Satish Mhaske <smhaske@qti.qualcomm.com>
Satish Mhaske (sampra2025)
force-pushed
the
s3tags
branch
from
b974772 to
38e878f
Compare
Ricardo Salveti (ricardosalveti)
approved these changes
Jun 24, 2026
Contributor
Author
|
Thanks for approving this change Ricardo Salveti (@ricardosalveti) , I think we need one more approval before we merge it to mainline. Can someone else approve this change. |
Ricardo Salveti (ricardosalveti)
requested a review
from Jose Quaresma (quaresmajose)
Jose Quaresma (quaresmajose)
approved these changes
Jul 1, 2026
Contributor
Author
|
Thanks Ricardo Salveti (@ricardosalveti) and Jose Quaresma (@quaresmajose) for approving my change, I have resolved all the conversation and now we should be able to merge this PR, do let me know if I need to take any further action from my end. |
Ricardo Salveti (ricardosalveti)
merged commit b768975
into
qualcomm-linux:master
252 of 254 checks passed
Contributor
|
Successfully created backport PR for |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
IT has recently introduced a Tagging policy for S3, requiring each object to be tagged according to the retention policy, for example, "retention=7d" for artifacts kept for 7 days in the S3 bucket.
Additional tags like Build type and branch can help to isolate artifacts in the S3 Browser.
This will also help to address below issue: