I agree external artifact mgmt is the way to go, and I'll be doing that in some work later this year. (Thanks for the link to JEP-202, I've already learned a lot from skimming it.)
I have now gleaned that the branch segment of a multibranch job path is the same for all jobs using a given branch. This indicates there's a common algorithm computing it from the branch name. *Can anyone point in the right direction in the source code where the multibranch job path is created?* If I can compute that from the downstream job, I can then fully form the src path to pass to scp and I'm done. On Monday, March 1, 2021 at 2:49:13 PM UTC-8 Jesse Glick wrote: > On Mon, Mar 1, 2021 at 4:50 PM Tim Black <[email protected]> wrote: > >> In lieu of installing a proper artifact management system and replacing >> all archive/copyArtifact with calls to its REST API >> > > Suggest https://plugins.jenkins.io/artifact-manager-s3/ (or some other > JEP-202 implementation) instead. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e7dd72d2-7225-4ec2-ab4b-a10bda37760dn%40googlegroups.com.
