[
https://issues.jboss.org/browse/JBIDE-15260?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-15260.
------------------------------
Fix Version/s: 1.0.0-LOCUS
Resolution: Done
Fixed. We can now publish via the shared promote.sh to a folder such as
http://download.jboss.org/jbosstools/updates/integration/locus/
using this syntax:
{code}
SOURCE_PATH = jbosstools-locus.site_10/all/repo
BUILD_TYPE = integration
TARGET_PLATFORM = NONE
PARENT_FOLDER = locus
PROJECT_NAME = locus
TARGET_FOLDER = 1.0.0.x (or 1.0.0.CR2, or 1.0.0.Final, etc.)
{code}
When publishing Locus builds, support case where
TARGET_PLATFORM=NONE, PARENT_FOLDER=PROJECT_NAME=locus
-------------------------------------------------------------------------------------------------------
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
Fix For: 1.0.0-LOCUS
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.sit...
[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