Hi Greg,
It turns out that, while I have permission to edit and start a job, I don't have permission to actually fully run a job on openshift so I can't actually test.
I have written the script, based on CDT, that promotes a build from Jenkins saved artifacts for a specific build to the download server. You can run the promote-build* job which will prompt for parameters. Those parameters, defined in the Jenkinsfile, allow you essentially to select a source and destination for a build to promote.
AFAICT there is little point in continuing to maintain compositeArtifacts/Contents files in your use case as you are only using them for milestones, but in the simrel you are pointing directly at the individual milestone build. So going forward I recommend you simply stop providing them and as such I have not written scripts to do anything with that.
I am now handing back to you with these next steps for you to do:
2) Delete the promote-download job as it isn't needed (see not about composites above)
2) Add archive the artifacts post build step for ptp-build job of releng/org.eclipse.ptp.repo/target/repository/** - the remote-build and photran-build already do - you won't be able to promote a ptp-build until you do.
3) Try promoting a build for M1 to see if it works.
* the -a- got lost along the way, it makes it look like "promote-build" is equivalent to "remote-build", "ptp-build" and "photran-build" instead of being a different kind of job.
HTH,
Jonah