[jbosstools-issues] [JBoss JIRA] (JBIDE-10013) Break OpenShift into its own component

[Nick Boldt (Issue Comment Edited) (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637059#comment-12637059 ] 

Nick Boldt edited comment on JBIDE-10013 at 10/25/11 6:46 PM:
--------------------------------------------------------------

(1) DONE
(2) DONE
(3) commented out; not yet deleted. Will wait a bit
(4) 2 jobs added:
* https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--openshift/ (build is blue! disabled for now)
* https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--openshift/ (disabled, no Beta1 branch avail yet)
ref to openshift git and express features refactored in ~/trunk/build/aggregate/site/site.xml; features moved into Cloud category from web category as per Max's request in #jbosstools:
{quote}
(2011-10-24 12:03:51) maxandersen: adietisheim: nickboldt: btw. OpenShift express is not listed under Cloud for some reason.
(2011-10-24 12:04:49) maxandersen: adietisheim: nickboldt: its also listed under web/java eE development which is probably a stretch ;)
{quote}

(5) DONE. successfully built w/ `mvn clean install -f ~/trunk/build/pom.xml -Popenshift-bootstrap`
(6) DONE
(7) DONE

                
      was (Author: nickboldt):
    (1) DONE
(2) DONE
(3) commented out; not yet deleted. Will wait a bit
(4) 2 jobs added:
* https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--openshift/ (build is blue! disabled for now)
* https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.component--openshift/ (disabled, no Beta1 branch avail yet)
ref to openshift git and express features refactored in ~/trunk/build/aggregate/site/site.xml; features moved into Cloud category from web category as per Max's request in #jbosstools:
{quote}
(2011-10-24 12:03:51) maxandersen: adietisheim: nickboldt: btw. OpenShift express is not listed under Cloud for some reason.
(2011-10-24 12:04:49) maxandersen: adietisheim: nickboldt: its also listed under web/java eE development which is probably a stretch ;)
{quote}

(5) DONE. successfully built w/ `mvn clean install -f ~/trunk/build/pom.xml -Popenshift-bootstrap`
(6) DONE
(7) DONE

----

*{color:red}TODO:{color}*

3) Remove openshift from astools build, including test features

8) verify continuous and tests jobs work after this change, and that both AS and OpenShift components are built
 -- http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/2982/ is blue, with as and openshift bits == BUILD SUCCESS
 -- https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/1035/ in progress ...

9) verify new stuff in updates/nightly/trunk site (once aggregate builds are running again)

                  
> Break OpenShift into its own component
> --------------------------------------
>
>                 Key: JBIDE-10013
>                 URL: https://issues.jboss.org/browse/JBIDE-10013
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: JBossAS/Servers, openshift
>    Affects Versions: 3.3.0.M4
>            Reporter: Rob Stryker
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 3.3.0.Beta1
>
>
> Openshift and egit plugins and features and tests need to be moved from the AsTools component into it's own. Steps are as follows:
> 1) Copy code over, including test features 
> 2) Modify descriptors / plugin.xml / feature.xml / site.xml etc
> 3) Remove openshift from astools build, including test features
> 4) Add openshift component to beta1 build
>   - 2 new jobs in Hudson
>   - link into ~/trunk/build/aggregate/*/site.xml as appropriate
> 5) update ~/trunk/build/pom*.xml to provide hooks to build w/ bootstrap
> 6) add to swimlanes.txt to record job interlinkages
> 7) verify both AS and OpenShift can build locally from bootstrap profiles
> 8) verify comtinuous and tests jobs work after this change, and that both AS and OpenShift components are built
> 9) verify new stuff in updates/nightly/trunk site (once aggregate builds are running again)

--
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