I started and got the basic function and configuration working. How are moves and renames handled? E.g. if a admin moves a job to a folder? How does the ArtifactManager handle this? I was thinking of saving the redirected artifact build dir in the build.xml in order to be able to keep the artifacts working in case of a move. The alternative is to move the artifacts so they match the new build dir structure in the alternative location, but I don't know where I would do this... I found StashAwareArtifactManager.copyAllArtifactsAndStashes() from the s3-plugn implementation, but this implies handling stashes also which is not in the scope for my ArtifactManager. Is there a correct way of handling artifacts when jobs are moved?
/S On Friday, 30 November 2018 20:06:28 UTC+1, Jesse Glick wrote: > > On Fri, Nov 30, 2018 at 8:59 AM Staffan Forsell <sta...@gmail.com > <javascript:>> wrote: > > artifact-manager-s3 seems to contain examples of most of the things > needed. > > Too complicated for your purpose. Creating a plugin with a lightly > edited clone of `StandardArtifactManager` would suffice. (Use the > Maven archetype for a plugin with global configuration, so the user > can pick the location in the GUI or using configuration-as-code.) > -- 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/a4d2e037-43a1-4f2c-abe3-286717cce3bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
