[
https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi...
]
Nick Boldt reassigned JBIDE-12973:
----------------------------------
Assignee: Martin Malina (was: Nick Boldt)
Job simply copies from staging/{JOB_NAME} to a new location. It doesn't rebuild,
refactor, or relabel.
It will however *replace* an existing build folder w/ new content, so you can overwrite
your 0.2.0.Final folder when you respin.
I'm not 100% sure whether it merges in or wipes clean before republishing, but it
doesn't really matter because when you're satisfied w/ your builds enough to call
it Final, that CI-built nightly can simply be pushed to /stable/ instead of /development/
or /integration/ and we can manually delete the old cruft.
If you prefer to have uniquely names folders, consider using BUILD_NUMBER in the target
folder... eg., 0.2.0.CI-${BUILD_NUMBER}
publish reddeer update site to
download.jboss.org
-------------------------------------------------
Key: JBIDE-12973
URL:
https://issues.jboss.org/browse/JBIDE-12973
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, testing, updatesite
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Martin Malina
Fix For: 4.1.x
Red deer should publish nightly/development/stable update sites like other components of
JBT onto
download.jboss.org.
Simplest way to get a nightly build into
download.jboss.org/jbosstools/builds/staging/ is
to use my publish.sh [1] script as a step during your build job.
Then, if you want to copy that to a more stable URL (for a dev milestone or stable
release) use this job [2]:
[1]
https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh
[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