Jenkins core archive step

Using Jenkins
1

Hi All

Is acceptable to send a patch to Jenkins core to allow to select the backend storage to use during archive steps? There are few reason where this is needed:

  • Use cloud only for temp rotate storage
  • Use on premise for build that are need to be kept
  • Just two different teams with different requirements or two different kind of applications

Let me know if this is acceptable

Michadl

2

The archive step is basically to use the first artifact manager that returns non null or so. I once wrote an artifact manager for inhouse and made it possible to configure via a job property if the manager should be used or not.
So technically you can do what you want without a change in core I think.

3

Hi

Yes was my idea but I think that this require then adapt each plugin. we have the list in the core and I think that run should even handle it when the store is saved in build.xml and we have everything almost in place. The new step could be something like ArchiveWithManager

Michael

4

You could write a kind of meta artifact manager, another archiveartict step could also line in an own repo