[SERVER-55125] Explicitly control uid, gid, and perms when archiving build artifacts with tar Created: 10/Mar/21  Updated: 09/Aug/23  Resolved: 09/Aug/23

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Server Development Platform
Backwards Compatibility: Minor Change
Participants:

 Description   

We currently use the python tarfile module to produce the tarfiles for the server build. Currently, we just reflect whatever the real filesystem permissions were on disk at the time the tarfile was created. This has lead to some surprises at various times. The tarfile module provides a facility by which we can explicitly set the uid, guid, and permissions bits on the files to be whatever we would like them to be, without regard for what they might happen to have on disk. We should apply this technique to ensure that our tarfiles have consistent contents.



 Comments   
Comment by Alex Neben [ 09/Aug/23 ]

Closing this issues as part of some SDP backlog cleanup. Please reopen if you feel this should be prioitized.

Generated at Thu Feb 08 05:35:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.