[jbosstools-issues] [JBoss JIRA] (JBIDE-15260) Locus needs its own publish/promote script since it does not need to specify /TARGET_PLATFORM=kepler/PARENT_FOLDER=core/ in its published URL

[Nick Boldt (JIRA)]

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

Nick Boldt updated JBIDE-15260:
-------------------------------

    Description: 
Locus needs its own publish/promote script since it does not need to specify /TARGET_PLATFORM=kepler/PARENT_FOLDER=core/ in its published URL

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/


  was:
Locus needs its own publish/promote script since it does not need to specify /TARGET_PLATFORM=kepler/PARENT_FOLDER=core/ in its published URL

Currently, the https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.site_10/ job kicks off the jbosstools-promote job 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/




    
> Locus needs its own publish/promote script since it does not need to specify /TARGET_PLATFORM=kepler/PARENT_FOLDER=core/ in its published URL
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15260
>                 URL: https://issues.jboss.org/browse/JBIDE-15260
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, locus
>    Affects Versions: 1.0.0-LOCUS
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>
> Locus needs its own publish/promote script since it does not need to specify /TARGET_PLATFORM=kepler/PARENT_FOLDER=core/ in its published URL
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira