Re: [cbi-dev] Interrogations on the new Jenkins/Kubernetes instances

[Ed Willink <ed@xxxxxxxxxxxxx>]

Hi

My approach did not survive the migration to JIRO.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=548942#c6 revises the invocation to e.g.

rm -f downloads.sh updates.sh
curl -s ${PUBLISH__DOWNLOADS_SH} > downloads.sh
curl -s ${PUBLISH__UPDATES_SH} > updates.sh
ssh genie.qvt-oml@xxxxxxxxxxxxxxxxxxxxxxxxxxxx rm -f downloads.sh updates.sh
scp downloads.sh genie.qvt-oml@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:downloads.sh
scp updates.sh genie.qvt-oml@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:updates.sh
ssh genie.qvt-oml@xxxxxxxxxxxxxxxxxxxxxxxxxxxx chmod +x downloads.sh updates.sh
ssh genie.qvt-oml@xxxxxxxxxxxxxxxxxxxxxxxxxxxx bash -ex downloads.sh -u "'${PUBLISH__URL}'" -v "'${PUBLISH__VERSION}'" -t "'${PUBLISH__BUILD_T}'" -q "'${PUBLISH__QUALIFIER}'" -a "'${PUBLISH__ALIAS}'" -j "'${PUBLISH__JAVADOC}'"
ssh genie.qvt-oml@xxxxxxxxxxxxxxxxxxxxxxxxxxxx bash -ex updates.sh -u "'${PUBLISH__URL}'" -v "'${PUBLISH__VERSION}'" -t "'${PUBLISH__BUILD_T}'" -q "'${PUBLISH__QUALIFIER}'"

https://git.eclipse.org/c/mmt/org.eclipse.qvtd.git/commit/?id=35f1cd8d73b8aed8c24b088eacad83b14b6d6bb4 shows the necessary script changes to use getopts rather than inherited environment passing.

    Regards

        Ed Willink

On 11/06/2019 16:52, Jonah Graham wrote:

Hi Ed,

Thanks for that (I have been following conversation for my own education). Can you make your jobs' configuration readable (extended read on) so that we can see all the details?

A picture if it help:

Thanks,

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

On Tue, 11 Jun 2019 at 11:48, Ed Willink <ed@xxxxxxxxxxxxx> wrote:

Hi

On 11/06/2019 16:00, Denis Roy wrote:

2-      I tried to add a promote step to the job but I cannot figure out how one would access the archive files from the job as the promote step is launched in another agent. I gather you can get them through a (curl ?) request but that can be a big overhead for larger project archives (e.g. RCPs, zipped p2s containing hundreds of plugins, …). There must be a way to do it cleanly but I didn’t find how.

If you're using a pipeline build, you can use stash for this:

https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/

Rather than add a step to the build you can add a downstream job. This has the benefits of a very simple and so reliable if-the-build-fails don't promote guard.

You can look at the https://ci.eclipse.org/ocl/job/promoter/ which executes the very simple (not-in-GIT) script:

rm -f downloads.sh updates.sh
curl -s -k ${PUBLISH__DOWNLOADS_SH} > downloads.sh
curl -s -k ${PUBLISH__UPDATES_SH} > updates.sh
chmod +x downloads.sh updates.sh
bash -ex downloads.sh
bash -ex updates.sh

to use the downloads.sh and updates.sh scripts from GIT and parameters from the original job.

Regards

Ed Willink

Virus-free. www.avast.com

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cbi-dev

_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cbi-dev