On Tue, Dec 4, 2018 at 3:48 AM Staffan Forsell <sta...@gmail.com> wrote: > How are moves and renames handled? E.g. if a admin moves a job to a folder? > How does the ArtifactManager handle this?
For `StandardArtifactManager`, that would be implicit in the job directory itself moving. For others, including `artifact-manager-s3`, this is not handled automatically. `JCloudsArtifactManager.key` could perhaps be made non-`transient` to track the originally stored location, or there could be an `ItemListener.onLocationChanged` to physically relocate the blob(s), or the `unique-id` plugin could be relied on for another key which persists across moves. For now we decided to keep things simple and transparent—there is a predictable blob location based on what you see in Jenkins—and just punt on the use case of historical builds preceding a move/rename. (On a related note, by default `artifact-manager-s3` declines to remove artifacts after build deletion in Jenkins, on the grounds that AWS retention policies and Glacier migration are likely better, and we want the Jenkins master to require minimal IAM permissions: a compromised master should not be able to destroy or alter cloud data.) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2Wii6KnaMpkz_oAsLyH74JbkP%3Da4MEk8-twJHgWRu7tA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
