[
https://issues.jboss.org/browse/JBIDE-22372?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22372:
------------------------------------
Other than the problem with bootstrapping the first time (eg., someone fires the Server
build before the Base one is done), which will create a whole bunch of false-failures
(easily solved by ignoring them and kicking a buildflow job to orchestrate the jobs in the
correct sequence)... +100.
This would get away from having a "stream" value of "4.4.neon" or
"10.0.neon", and instead we could combine version (4.4/10.0) w/ BUILD_ALIAS when
doing staging/publishing/promoting.
Would need some reworking of the various publish scripts but I like this idea because we
could publish to /staging/4.4.0.Alpha2 even if the parent pom was still at Alpha1.
Publish CI snapshots to a directory containing BUILD_ALIAS
----------------------------------------------------------
Key: JBIDE-22372
URL:
https://issues.jboss.org/browse/JBIDE-22372
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Reporter: Mickael Istria
To avoid even more "crossing streams", we could consider also adding the
BUILD_ALIAS to the URL of snapshots sites produced by CI. An advantage is that building a
new version wouldn't require to cleanup the /4.4.neon branch for example.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)