[jbosstools-issues] [JBoss JIRA] (LOCUS-7) When publishing Locus builds, support case where TARGET_PLATFORM=NONE, PARENT_FOLDER=PROJECT_NAME=locus

[Max Rydahl Andersen (JIRA)]

     [ https://issues.jboss.org/browse/LOCUS-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen reassigned LOCUS-7:
---------------------------------------

              Project: JBoss Tools Locus  (was: Tools (JBoss Tools))
                  Key: LOCUS-7  (was: JBIDE-15260)
    Affects Version/s: 1.0.0
                           (was: 1.0.0-LOCUS)
             Assignee:     (was: Nick Boldt)
          Component/s:     (was: build)
                           (was: locus)
        Fix Version/s: 1.0.0
                           (was: 1.0.0-LOCUS)


> When publishing Locus builds, support case where TARGET_PLATFORM=NONE, PARENT_FOLDER=PROJECT_NAME=locus
> -------------------------------------------------------------------------------------------------------
>
>                 Key: LOCUS-7
>                 URL: https://issues.jboss.org/browse/LOCUS-7
>             Project: JBoss Tools Locus
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Nick Boldt
>             Fix For: 1.0.0
>
>
> When publishing Locus builds, support case where TARGET_PLATFORM=NONE, PARENT_FOLDER=PROJECT_NAME=locus
> Currently, the Locus job [1] kicks off the jbosstools-promote job [2] when it's done, which pushes the bits to a versioned folder under 
> http://download.jboss.org/jbosstools/updates/integration/kepler/core/locus/
> Ideally, we would simply skip those two path segments and publish to 
> http://download.jboss.org/jbosstools/updates/integration/locus/
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.site_10/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)