[jbosstools-issues] [JBoss JIRA] (JBIDE-12828) migrate JBT & JBDS jobs to use new github repos
[
https://issues.jboss.org/browse/JBIDE-12828?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-12828 at 11/10/12 1:39 PM:
--------------------------------------------------------------
*DONE*
* migrate soa jobs (trunk and stable_branch): bpel, esb, jbpm, runtime-soa
* rename/deprecate old jobs which are no longer needed (as, archives, jmx, common, ...)
(including stable_branch jobs and 4.0_trunk job for flow)
* verify job linkages are correct
* email to soa and jbt lists announcing the demise of build/ and download.jboss.org/
folders *DONE*
** svn delete build/ in trunk with a README.md pointing to the proper 5 root repos *DONE*
** svn delete download.jboss.org/ in trunk with a README.md pointing to the proper root
repo *DONE*
*TODO DOC*
*
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
-- see JBIDE-12945
* contributor guide (can wait until max get back) - see wiki
* document use of checkout.sh and fetch_all_projects.sh
* clean up JIRA components -- merge old components into new ones or archive old ones?
*TODO LATER*
* JBDS SOA 6.0_trunk job
* after Beta2 branch, apply all changes to trunk in stable_branch jobs too
was (Author: nickboldt):
*IN PROGRESS*
*TODO*
* rename/deprecate old jobs which are no longer needed (as, archives, jmx, common, ...)
* verify job linkages are correct
* email to soa and jbt lists announcing the demise of build/ and download.jboss.org/
folders *DONE*
** svn delete build/ in trunk with a README.md pointing to the proper 5 root repos
** svn delete download.jboss.org/ in trunk with a README.md pointing to the proper root
repo
*TODO DOC*
*
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
-- see JBIDE-12945
* contributor guide (can wait until max get back) - see wiki
* document use of checkout.sh and fetch_all_projects.sh
* clean up JIRA components -- merge old components into new ones or archive old ones?
*TODO LATER*
* JBDS SOA 6.0_trunk job
* after Beta2 branch, apply all changes to trunk in stable_branch jobs too
migrate JBT & JBDS jobs to use new github repos
-----------------------------------------------
Key: JBIDE-12828
URL: https://issues.jboss.org/browse/JBIDE-12828
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng, updatesite
Affects Versions: 4.0.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.0.0.CR1
For first the trunk jobs, then AFTER Beta1 is released the stable_branch jobs, the
following must be done.
Work to start Oct 22
{quote}
* [Max] For every repo moved - svn delete in trunk, put Readme with pointer.
* [Nick] Open branch 4.0.0.Beta1 for writes, keep trunk locked down. *[DONE]*
* [Nick] create root poms for chunk repos; for N:1 "chunk" repos (base,
server, javaee, central): merge jbosstools-base/[as,archives,jmx]/site/* into
jbosstools-base/site/* - one site w/ all features on it *[DONE]*
- - https://github.com/nickboldt/temp-jbosstools-javaee,
https://github.com/nickboldt/temp-jbosstools-base,
https://github.com/nickboldt/temp-jbosstools-server,
https://github.com/nickboldt/temp-jbosstools-central *DONE*
* [Nick] merge stuff from the above temp-* repos into the new actual repos *[DONE]*
* [Nick/Mickael] switch trunk jobs to source from github instead of svn *[DONE]*
* [Nick/Mickael] Change jbosstools composite
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/ sites to point at
"server" update site folder instead of as, archives, and jmx when building JBT
aggregate site
* [Nick] make sure all jobs (including rsync for download.jboss.org) are updated to
fetch from git instead of svn *[DONE]*
* [Nick/Mickael] make sure all refs to promote.sh, jbosstools-cleanup.sh, promote.sh
are pointed at github instead of svn
* for 1:1 individual repos: no change needed for ./site/ folder *[DONE]*
{quote}
(see also http://ether-man.rhcloud.com/p/build.next )
--
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