[
https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-20904:
-------------------------------
Sprint: devex #115 May 2016, devex #116 June 2016, devex #118 July 2016, devex #119
August 2016, devex #121 October 2016, devex #125 December 2017 (was: devex #115 May 2016,
devex #116 June 2016, devex #118 July 2016, devex #119 August 2016, devex #121 October
2016, devex #124 December 2017)
automate publishing latest CI build to staging, then from staging to
development (or stable)
--------------------------------------------------------------------------------------------
Key: JBIDE-20904
URL:
https://issues.jboss.org/browse/JBIDE-20904
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.4.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.x
Suggestion:
rather than opening 10 bash terminals to perform the
copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to
clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today
that we could use `wait` or `parallel` to orchestrate these steps via a bash script so
they run in parallel (as quickly as possible), but still return feedback when all parallel
steps are completed.
So, where today we run these steps sorta-by-hand (copy script into a console and wait
until it's done) [1], in future we could simply kick a job and wait for the job to
notify its completion.
[1]
https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui...
Examples of using a series of commands in parallel w/ a wait at the end:
http://stackoverflow.com/questions/19543139/bash-script-processing-comman...
{code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and
returns the PID of the last one + its return code}
echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $#
{code}
More discussion:
{quote}
[12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into
functions
[12:54:41 PM] Mickael Istria: so, to hack the script, it could be just:
* add && after the 1st rsync in each loop
* add & after the last one
* put a wait after the last loop
* give the big piece of code to procede directly to bash
{quote}
After this job is done, releng would still have to "wire up" the new bits by
updating composite*.xml and index.html pages, but that's considerably easier to do
locally in a terminal, or even to script too. Rather than updating these files w/ sed, we
could generate them from a template.
And if we don't care about committing those changes back to github, we could even
push them to the dl.jb.o and ds.jb.c servers directly as part of the above job.
Scary, but much faster!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)