[
https://issues.jboss.org/browse/JBIDE-9775?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-9775 at 2/3/12 10:11 AM:
------------------------------------------------------------
I don't think we can automate the parts that require and SVN commit (2-4), so the
process for you would be:
1. run your existing job
(
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/m2eclipse-wtp/job/...)
2. run the (new) publishing job (eg.,
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/m2eclipse-wtp/job/...
or
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/m2eclipse-wtp/job/...).
3. commit updated metadata to SVN
-->
http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosst...
4. run the
svn-to-download.jboss.org rsync update job
(
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j...).
5. verify everything works!
6. update the m2e/m2e-wtp mirror used in the JBoss Tools requirements mirror, respin the
TPs, verify content
a) edit, then run
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/build...
b) sftp/rsync new release folder to server, eg.,
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/20111...
c) open a JIRA to get approval from Max to change the requirements mirror / update the
target platform
d) update composite metadata, eg.,
http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosst...
d) respin target platform -
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platfo...,
https://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.target-platfor...
e) verify updated TPs contain your updated m2e-wtp bits
was (Author: nickboldt):
I don't think we can automate the parts that require and SVN commit (2-4), so the
process for you would be:
1. run your existing job
(
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/m2eclipse-wtp/job/...)
2. run the (new) publishing job (eg.,
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/m2eclipse-wtp/job/...
or
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/m2eclipse-wtp/job/...).
3. commit some stuff to SVN
(
http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosst...).
4. run the
svn-to-download.jboss.org rsync update job
(
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j...).
5. verify everything works!
Create publishing job for m2e-wtp-e37 job
------------------------------------------
Key: JBIDE-9775
URL:
https://issues.jboss.org/browse/JBIDE-9775
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, maven, updatesite, UpStream, Webservices
Affects Versions: 3.3.0.M4
Reporter: Nick Boldt
Assignee: Fred Bricon
Fix For: 3.3.0.M4
fbricon would like a job to facilitate the process of publishing staged/vetted bits to
production URL on
download.jboss.org.
Last time we did this by hand (0.13.1).
1. Copy bits from
http://download.jboss.org/jbosstools/jbosstools/updates/requirements/m2ec... to
http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2ecl...
2. Update
http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/ to point at new
release? Add or replace? What about m2e-extras?
3. Update
http://download.jboss.org/jbosstools/updates/indigo/SR1/ to point at new
release?
4. Update
http://download.jboss.org/jbosstools/updates/helios/ to point at new release?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira