[jbosstools-issues] [JBoss JIRA] (JBIDE-22372) Publish CI snapshots to a directory containing BUILD_ALIAS

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242789#comment-13242789 ] 

Nick Boldt commented on JBIDE-22372:
------------------------------------

So this is a variation / automation of the process of creating staged builds for QE.

Instead of 
* /snapshots/builds/ (many folders with unique BUILD#s & a symlinked latest one) 
* pushed at some point to /staging/4.4.0.Alpha2/, /staging/4.4.0.Alpha3/, /staging/4.4.0.Alpha4/

We would have
* /snapshots/builds/4.4.0.Alpha2/ (many folders with unique BUILD#s & a symlinked latest one)
* /snapshots/builds/4.4.0.Alpha3/ (many folders with unique BUILD#s & a symlinked latest one)
* /snapshots/builds/4.4.0.Alpha4/ (many folders with unique BUILD#s & a symlinked latest one)
* pushed at some point to /staging/4.4.0.Alpha2/, /staging/4.4.0.Alpha3/, /staging/4.4.0.Alpha4/


> 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
>             Fix For: 4.4.0.Alpha3
>
>
> 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)