5:45 a.m.
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
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
2) Modify descriptors / plugin.xml / feature.xml etc
3) Remove openshift from astools build
4) Add openshift component to beta1 build
--
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
11:15 a.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10013:
-------------------------------
Description:
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)
was:
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
2) Modify descriptors / plugin.xml / feature.xml etc
3) Remove openshift from astools build
4) Add openshift component to beta1 build
Priority: Blocker (was: Major)
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
11:17 a.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10013:
-------------------------------
Description:
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)
was:
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)
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
11:19 a.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10013:
------------------------------------
In progress building locally:
{code}
[INFO] Reactor Summary:
[INFO]
[INFO] tests.all ......................................... SUCCESS [0.970s]
[INFO] tests.plugins ..................................... SUCCESS [0.033s]
[INFO] org.jboss.tools.tests ............................. SUCCESS [4.350s]
[INFO] org.jboss.tools.ui.bot.ext ........................ SUCCESS [4.451s]
[INFO] org.jboss.tools.ui.bot.ext.test ................... SUCCESS [1.611s]
[INFO] tests.features .................................... SUCCESS [0.086s]
[INFO] org.jboss.tools.test.feature ...................... SUCCESS [0.576s]
[INFO] org.jboss.tools.test.source.feature ............... SUCCESS [0.339s]
[INFO] tests.site ........................................ SUCCESS [4.846s]
[INFO] common.all ........................................ SUCCESS [0.130s]
[INFO] common.plugins .................................... SUCCESS [0.079s]
[INFO] org.jboss.tools.common ............................ SUCCESS [2.170s]
[INFO] org.jboss.tools.common.model ...................... SUCCESS [4.115s]
[INFO] org.jboss.tools.common.resref.core ................ SUCCESS [0.399s]
[INFO] org.jboss.tools.common.el.core .................... SUCCESS [1.112s]
[INFO] org.jboss.tools.common.text.xml ................... SUCCESS [2.069s]
[INFO] org.jboss.tools.common.ui ......................... SUCCESS [2.545s]
[INFO] org.jboss.tools.common.text.ext ................... SUCCESS [2.139s]
[INFO] org.jboss.tools.common.validation ................. SUCCESS [0.672s]
[INFO] org.jboss.tools.common.base.test .................. SUCCESS [0.678s]
[INFO] org.jboss.tools.common.model.ui ................... SUCCESS [5.901s]
[INFO] org.jboss.tools.common.el.ui ...................... SUCCESS [0.545s]
[INFO] org.jboss.tools.common.gef ........................ SUCCESS [0.638s]
[INFO] org.jboss.tools.common.meta.ui .................... SUCCESS [0.886s]
[INFO] org.jboss.tools.common.model.ui.capabilities ...... SUCCESS [0.222s]
[INFO] org.jboss.tools.common.projecttemplates ........... SUCCESS [2.784s]
[INFO] org.jboss.tools.common.resref.ui .................. SUCCESS [0.464s]
[INFO] org.jboss.tools.common.verification ............... SUCCESS [0.551s]
[INFO] org.jboss.tools.common.verification.ui ............ SUCCESS [0.954s]
[INFO] org.jboss.tools.common.jdt.debug .................. SUCCESS [0.344s]
[INFO] org.jboss.tools.common.jdt.debug.ui ............... SUCCESS [0.822s]
[INFO] org.jboss.tools.common.jdt ........................ SUCCESS [0.706s]
[INFO] org.jboss.tools.common.jdt.ui ..................... SUCCESS [0.752s]
[INFO] common.features ................................... SUCCESS [0.043s]
[INFO] org.jboss.tools.common.core.feature ............... SUCCESS [0.151s]
[INFO] org.jboss.tools.common.verification.feature ....... SUCCESS [0.163s]
[INFO] org.jboss.tools.common.text.ext.feature ........... SUCCESS [0.200s]
[INFO] org.jboss.tools.common.ui.feature ................. SUCCESS [0.109s]
[INFO] org.jboss.tools.common.feature .................... SUCCESS [0.155s]
[INFO] org.jboss.tools.common.all.feature ................ SUCCESS [0.236s]
[INFO] org.jboss.tools.common.all.source.feature ......... SUCCESS [0.234s]
[INFO] common.tests ...................................... SUCCESS [0.075s]
[INFO] org.jboss.tools.common.test ....................... SUCCESS [0.653s]
[INFO] org.jboss.tools.common.model.test ................. SUCCESS [0.802s]
[INFO] org.jboss.tools.common.model.ui.test .............. SUCCESS [0.502s]
[INFO] org.jboss.tools.common.el.core.test ............... SUCCESS [0.550s]
[INFO] org.jboss.tools.common.verification.ui.test ....... SUCCESS [0.713s]
[INFO] org.jboss.tools.common.verification.test .......... SUCCESS [0.531s]
[INFO] org.jboss.tools.common.validation.test ............ SUCCESS [0.770s]
[INFO] org.jboss.tools.common.all.test.feature ........... SUCCESS [0.256s]
[INFO] org.jboss.tools.common.all.test.source.feature .... SUCCESS [0.229s]
[INFO] org.jboss.tools.common.jdt.feature ................ SUCCESS [0.167s]
[INFO] org.jboss.tools.common.jdt.source.feature ......... SUCCESS [0.258s]
[INFO] common.site ....................................... SUCCESS [4.525s]
[INFO] org.jboss.tools.common.ui.test .................... SUCCESS [0.589s]
[INFO] archives.all ...................................... SUCCESS [0.098s]
[INFO] archives.plugins .................................. SUCCESS [0.022s]
[INFO] org.jboss.ide.eclipse.archives.core ............... SUCCESS [3.341s]
[INFO] org.jboss.ide.eclipse.archives.ui ................. SUCCESS [1.176s]
[INFO] org.jboss.ide.eclipse.archives.jdt.integration .... SUCCESS [0.590s]
[INFO] archives.features ................................. SUCCESS [0.081s]
[INFO] org.jboss.ide.eclipse.archives.feature ............ SUCCESS [0.264s]
[INFO] org.jboss.ide.eclipse.archives.source.feature ..... SUCCESS [0.286s]
[INFO] archives.tests .................................... SUCCESS [0.058s]
[INFO] org.jboss.ide.eclipse.archives.ui.test ............ SUCCESS [0.694s]
[INFO] org.jboss.ide.eclipse.archives.test ............... SUCCESS [0.867s]
[INFO] org.jboss.ide.eclipse.archives.test.feature ....... SUCCESS [0.215s]
[INFO] org.jboss.ide.eclipse.archives.test.source.feature SUCCESS [0.266s]
[INFO] archives.site ..................................... SUCCESS [2.739s]
[INFO] jmx.all ........................................... SUCCESS [0.115s]
[INFO] jmx.plugins ....................................... SUCCESS [0.082s]
[INFO] org.jboss.tools.jmx.core .......................... SUCCESS [0.586s]
[INFO] org.jboss.tools.jmx.ui ............................ SUCCESS [1.308s]
[INFO] jmx.features ...................................... SUCCESS [0.043s]
[INFO] org.jboss.tools.jmx.feature ....................... SUCCESS [0.160s]
[INFO] org.jboss.tools.jmx.source.feature ................ SUCCESS [0.248s]
[INFO] jmx.tests ......................................... SUCCESS [0.081s]
[INFO] org.jboss.tools.jmx.ui.test ....................... SUCCESS [0.279s]
[INFO] org.jboss.tools.jmx.core.test ..................... SUCCESS [0.771s]
[INFO] org.jboss.tools.jmx.test.feature .................. SUCCESS [0.281s]
[INFO] org.jboss.tools.jmx.test.source.feature ........... SUCCESS [0.210s]
[INFO] jmx.site .......................................... SUCCESS [2.765s]
[INFO] as.all ............................................ SUCCESS [0.133s]
[INFO] as.plugins ........................................ SUCCESS [0.071s]
[INFO] org.jboss.ide.eclipse.as.wtp.core ................. SUCCESS [1.372s]
[INFO] org.jboss.ide.eclipse.as.wtp.ui ................... SUCCESS [1.249s]
[INFO] org.jboss.ide.eclipse.as.core ..................... SUCCESS [1.881s]
[INFO] org.jboss.ide.eclipse.as.ui ....................... SUCCESS [1.919s]
[INFO] org.jboss.ide.eclipse.archives.webtools ........... SUCCESS [0.814s]
[INFO] org.jboss.ide.eclipse.as.classpath.core ........... SUCCESS [0.963s]
[INFO] org.jboss.ide.eclipse.as.classpath.ui ............. SUCCESS [0.504s]
[INFO] org.jboss.ide.eclipse.as.doc.user ................. SUCCESS [0.225s]
[INFO] org.jboss.ide.eclipse.as.ui.mbeans ................ SUCCESS [1.794s]
[INFO] org.jboss.ide.eclipse.as.rse.core ................. SUCCESS [0.834s]
[INFO] org.jboss.ide.eclipse.as.rse.ui ................... SUCCESS [0.798s]
[INFO] org.jboss.ide.eclipse.as.jmx.integration .......... SUCCESS [0.651s]
[INFO] org.jboss.ide.eclipse.as.management.as7 ........... SUCCESS [0.487s]
[INFO] as.tests .......................................... SUCCESS [0.092s]
[INFO] org.jboss.ide.eclipse.as.test ..................... SUCCESS [2.352s]
[INFO] org.jboss.ide.eclipse.as.archives.integration.test SUCCESS [0.563s]
[INFO] org.jboss.ide.eclipse.as.management.as7.tests ..... SUCCESS [1.618s]
[INFO] org.jboss.ide.eclipse.as.ui.test .................. SUCCESS [0.559s]
[INFO] as.features ....................................... SUCCESS [0.088s]
[INFO] org.jboss.ide.eclipse.as.serverAdapter.wtp.feature SUCCESS [0.205s]
[INFO] org.jboss.ide.eclipse.as.archives.integration.feature SUCCESS [0.213s]
[INFO] org.jboss.ide.eclipse.as.jmx.integration.feature .. SUCCESS [0.137s]
[INFO] org.jboss.ide.eclipse.as.server.rse.integration.feature SUCCESS [0.128s]
[INFO] org.jboss.ide.eclipse.as.feature .................. SUCCESS [0.150s]
[INFO] org.jboss.ide.eclipse.as.source.feature ........... SUCCESS [0.278s]
[INFO] org.jboss.ide.eclipse.as.test.feature ............. SUCCESS [0.367s]
[INFO] org.jboss.ide.eclipse.as.test.source.feature ...... SUCCESS [0.153s]
[INFO] as.site ........................................... SUCCESS [4.455s]
[INFO] openshift.all ..................................... SUCCESS [0.168s]
[INFO] openshift.plugins ................................. SUCCESS [0.004s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [0.704s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.304s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [0.472s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [1.641s]
[INFO] openshift.tests ................................... SUCCESS [0.031s]
[INFO] org.jboss.tools.openshift.egit.test ............... FAILURE [0.052s]
[INFO] org.jboss.tools.openshift.express.client.test ..... SKIPPED
[INFO] openshift.features ................................ SKIPPED
[INFO] org.jboss.tools.openshift.egit.integration.feature SKIPPED
[INFO] org.jboss.tools.openshift.egit.integration.source.feature SKIPPED
[INFO] org.jboss.tools.openshift.express.feature ......... SKIPPED
[INFO] org.jboss.tools.openshift.express.source.feature .. SKIPPED
[INFO] openshift.site .................................... SKIPPED
[INFO] org.jboss.tools.build ............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
{code}
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
12:40 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/24/11 1:39 PM:
--------------------------------------------------------------
both AS and Openshift components build fine in trunk now. Haven't run tests, just
compilation.
was (Author: nickboldt):
In progress building locally:
{code}
[INFO] Reactor Summary:
[INFO]
[INFO] tests.all ......................................... SUCCESS [0.970s]
[INFO] tests.plugins ..................................... SUCCESS [0.033s]
[INFO] org.jboss.tools.tests ............................. SUCCESS [4.350s]
[INFO] org.jboss.tools.ui.bot.ext ........................ SUCCESS [4.451s]
[INFO] org.jboss.tools.ui.bot.ext.test ................... SUCCESS [1.611s]
[INFO] tests.features .................................... SUCCESS [0.086s]
[INFO] org.jboss.tools.test.feature ...................... SUCCESS [0.576s]
[INFO] org.jboss.tools.test.source.feature ............... SUCCESS [0.339s]
[INFO] tests.site ........................................ SUCCESS [4.846s]
[INFO] common.all ........................................ SUCCESS [0.130s]
[INFO] common.plugins .................................... SUCCESS [0.079s]
[INFO] org.jboss.tools.common ............................ SUCCESS [2.170s]
[INFO] org.jboss.tools.common.model ...................... SUCCESS [4.115s]
[INFO] org.jboss.tools.common.resref.core ................ SUCCESS [0.399s]
[INFO] org.jboss.tools.common.el.core .................... SUCCESS [1.112s]
[INFO] org.jboss.tools.common.text.xml ................... SUCCESS [2.069s]
[INFO] org.jboss.tools.common.ui ......................... SUCCESS [2.545s]
[INFO] org.jboss.tools.common.text.ext ................... SUCCESS [2.139s]
[INFO] org.jboss.tools.common.validation ................. SUCCESS [0.672s]
[INFO] org.jboss.tools.common.base.test .................. SUCCESS [0.678s]
[INFO] org.jboss.tools.common.model.ui ................... SUCCESS [5.901s]
[INFO] org.jboss.tools.common.el.ui ...................... SUCCESS [0.545s]
[INFO] org.jboss.tools.common.gef ........................ SUCCESS [0.638s]
[INFO] org.jboss.tools.common.meta.ui .................... SUCCESS [0.886s]
[INFO] org.jboss.tools.common.model.ui.capabilities ...... SUCCESS [0.222s]
[INFO] org.jboss.tools.common.projecttemplates ........... SUCCESS [2.784s]
[INFO] org.jboss.tools.common.resref.ui .................. SUCCESS [0.464s]
[INFO] org.jboss.tools.common.verification ............... SUCCESS [0.551s]
[INFO] org.jboss.tools.common.verification.ui ............ SUCCESS [0.954s]
[INFO] org.jboss.tools.common.jdt.debug .................. SUCCESS [0.344s]
[INFO] org.jboss.tools.common.jdt.debug.ui ............... SUCCESS [0.822s]
[INFO] org.jboss.tools.common.jdt ........................ SUCCESS [0.706s]
[INFO] org.jboss.tools.common.jdt.ui ..................... SUCCESS [0.752s]
[INFO] common.features ................................... SUCCESS [0.043s]
[INFO] org.jboss.tools.common.core.feature ............... SUCCESS [0.151s]
[INFO] org.jboss.tools.common.verification.feature ....... SUCCESS [0.163s]
[INFO] org.jboss.tools.common.text.ext.feature ........... SUCCESS [0.200s]
[INFO] org.jboss.tools.common.ui.feature ................. SUCCESS [0.109s]
[INFO] org.jboss.tools.common.feature .................... SUCCESS [0.155s]
[INFO] org.jboss.tools.common.all.feature ................ SUCCESS [0.236s]
[INFO] org.jboss.tools.common.all.source.feature ......... SUCCESS [0.234s]
[INFO] common.tests ...................................... SUCCESS [0.075s]
[INFO] org.jboss.tools.common.test ....................... SUCCESS [0.653s]
[INFO] org.jboss.tools.common.model.test ................. SUCCESS [0.802s]
[INFO] org.jboss.tools.common.model.ui.test .............. SUCCESS [0.502s]
[INFO] org.jboss.tools.common.el.core.test ............... SUCCESS [0.550s]
[INFO] org.jboss.tools.common.verification.ui.test ....... SUCCESS [0.713s]
[INFO] org.jboss.tools.common.verification.test .......... SUCCESS [0.531s]
[INFO] org.jboss.tools.common.validation.test ............ SUCCESS [0.770s]
[INFO] org.jboss.tools.common.all.test.feature ........... SUCCESS [0.256s]
[INFO] org.jboss.tools.common.all.test.source.feature .... SUCCESS [0.229s]
[INFO] org.jboss.tools.common.jdt.feature ................ SUCCESS [0.167s]
[INFO] org.jboss.tools.common.jdt.source.feature ......... SUCCESS [0.258s]
[INFO] common.site ....................................... SUCCESS [4.525s]
[INFO] org.jboss.tools.common.ui.test .................... SUCCESS [0.589s]
[INFO] archives.all ...................................... SUCCESS [0.098s]
[INFO] archives.plugins .................................. SUCCESS [0.022s]
[INFO] org.jboss.ide.eclipse.archives.core ............... SUCCESS [3.341s]
[INFO] org.jboss.ide.eclipse.archives.ui ................. SUCCESS [1.176s]
[INFO] org.jboss.ide.eclipse.archives.jdt.integration .... SUCCESS [0.590s]
[INFO] archives.features ................................. SUCCESS [0.081s]
[INFO] org.jboss.ide.eclipse.archives.feature ............ SUCCESS [0.264s]
[INFO] org.jboss.ide.eclipse.archives.source.feature ..... SUCCESS [0.286s]
[INFO] archives.tests .................................... SUCCESS [0.058s]
[INFO] org.jboss.ide.eclipse.archives.ui.test ............ SUCCESS [0.694s]
[INFO] org.jboss.ide.eclipse.archives.test ............... SUCCESS [0.867s]
[INFO] org.jboss.ide.eclipse.archives.test.feature ....... SUCCESS [0.215s]
[INFO] org.jboss.ide.eclipse.archives.test.source.feature SUCCESS [0.266s]
[INFO] archives.site ..................................... SUCCESS [2.739s]
[INFO] jmx.all ........................................... SUCCESS [0.115s]
[INFO] jmx.plugins ....................................... SUCCESS [0.082s]
[INFO] org.jboss.tools.jmx.core .......................... SUCCESS [0.586s]
[INFO] org.jboss.tools.jmx.ui ............................ SUCCESS [1.308s]
[INFO] jmx.features ...................................... SUCCESS [0.043s]
[INFO] org.jboss.tools.jmx.feature ....................... SUCCESS [0.160s]
[INFO] org.jboss.tools.jmx.source.feature ................ SUCCESS [0.248s]
[INFO] jmx.tests ......................................... SUCCESS [0.081s]
[INFO] org.jboss.tools.jmx.ui.test ....................... SUCCESS [0.279s]
[INFO] org.jboss.tools.jmx.core.test ..................... SUCCESS [0.771s]
[INFO] org.jboss.tools.jmx.test.feature .................. SUCCESS [0.281s]
[INFO] org.jboss.tools.jmx.test.source.feature ........... SUCCESS [0.210s]
[INFO] jmx.site .......................................... SUCCESS [2.765s]
[INFO] as.all ............................................ SUCCESS [0.133s]
[INFO] as.plugins ........................................ SUCCESS [0.071s]
[INFO] org.jboss.ide.eclipse.as.wtp.core ................. SUCCESS [1.372s]
[INFO] org.jboss.ide.eclipse.as.wtp.ui ................... SUCCESS [1.249s]
[INFO] org.jboss.ide.eclipse.as.core ..................... SUCCESS [1.881s]
[INFO] org.jboss.ide.eclipse.as.ui ....................... SUCCESS [1.919s]
[INFO] org.jboss.ide.eclipse.archives.webtools ........... SUCCESS [0.814s]
[INFO] org.jboss.ide.eclipse.as.classpath.core ........... SUCCESS [0.963s]
[INFO] org.jboss.ide.eclipse.as.classpath.ui ............. SUCCESS [0.504s]
[INFO] org.jboss.ide.eclipse.as.doc.user ................. SUCCESS [0.225s]
[INFO] org.jboss.ide.eclipse.as.ui.mbeans ................ SUCCESS [1.794s]
[INFO] org.jboss.ide.eclipse.as.rse.core ................. SUCCESS [0.834s]
[INFO] org.jboss.ide.eclipse.as.rse.ui ................... SUCCESS [0.798s]
[INFO] org.jboss.ide.eclipse.as.jmx.integration .......... SUCCESS [0.651s]
[INFO] org.jboss.ide.eclipse.as.management.as7 ........... SUCCESS [0.487s]
[INFO] as.tests .......................................... SUCCESS [0.092s]
[INFO] org.jboss.ide.eclipse.as.test ..................... SUCCESS [2.352s]
[INFO] org.jboss.ide.eclipse.as.archives.integration.test SUCCESS [0.563s]
[INFO] org.jboss.ide.eclipse.as.management.as7.tests ..... SUCCESS [1.618s]
[INFO] org.jboss.ide.eclipse.as.ui.test .................. SUCCESS [0.559s]
[INFO] as.features ....................................... SUCCESS [0.088s]
[INFO] org.jboss.ide.eclipse.as.serverAdapter.wtp.feature SUCCESS [0.205s]
[INFO] org.jboss.ide.eclipse.as.archives.integration.feature SUCCESS [0.213s]
[INFO] org.jboss.ide.eclipse.as.jmx.integration.feature .. SUCCESS [0.137s]
[INFO] org.jboss.ide.eclipse.as.server.rse.integration.feature SUCCESS [0.128s]
[INFO] org.jboss.ide.eclipse.as.feature .................. SUCCESS [0.150s]
[INFO] org.jboss.ide.eclipse.as.source.feature ........... SUCCESS [0.278s]
[INFO] org.jboss.ide.eclipse.as.test.feature ............. SUCCESS [0.367s]
[INFO] org.jboss.ide.eclipse.as.test.source.feature ...... SUCCESS [0.153s]
[INFO] as.site ........................................... SUCCESS [4.455s]
[INFO] openshift.all ..................................... SUCCESS [0.168s]
[INFO] openshift.plugins ................................. SUCCESS [0.004s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [0.704s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.304s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [0.472s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [1.641s]
[INFO] openshift.tests ................................... SUCCESS [0.031s]
[INFO] org.jboss.tools.openshift.egit.test ............... FAILURE [0.052s]
[INFO] org.jboss.tools.openshift.express.client.test ..... SKIPPED
[INFO] openshift.features ................................ SKIPPED
[INFO] org.jboss.tools.openshift.egit.integration.feature SKIPPED
[INFO] org.jboss.tools.openshift.egit.integration.source.feature SKIPPED
[INFO] org.jboss.tools.openshift.express.feature ......... SKIPPED
[INFO] org.jboss.tools.openshift.express.source.feature .. SKIPPED
[INFO] openshift.site .................................... SKIPPED
[INFO] org.jboss.tools.build ............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
{code}
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
8:05 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10013:
------------------------------------
(1) DONE
(2) DONE
(3) commented out; not yet deleted. Will wait a bit
(4) 2 jobs added; trunk one enabled, _stable_branch pointing at Beta1 branch which
doesn't yet exist set to disabled
ref to openshift git and express features refactored in
~/trunk/build/aggregate/site/site.xml
(5) DONE. successfully built w/ `mvn clean install -f ~/trunk/build/pom.xml
-Popenshift-bootstrap`
(6) DONE
(7) DONE
(8) ...
(9) ...
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
8:09 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/24/11 9:09 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--op...
(enabled and awaiting a free slave)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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
(8) ...
(9) ...
was (Author: nickboldt):
(1) DONE
(2) DONE
(3) commented out; not yet deleted. Will wait a bit
(4) 2 jobs added; trunk one enabled, _stable_branch pointing at Beta1 branch which
doesn't yet exist set to disabled
ref to openshift git and express features refactored in
~/trunk/build/aggregate/site/site.xml
(5) DONE. successfully built w/ `mvn clean install -f ~/trunk/build/pom.xml
-Popenshift-bootstrap`
(6) DONE
(7) DONE
(8) ...
(9) ...
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
8:11 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/24/11 9:10 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--op...
(enabled and awaiting a free slave)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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
TODO:
3) Remove openshift from astools build, including test features
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)
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--op...
(enabled and awaiting a free slave)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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
(8) ...
(9) ...
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
8:11 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/24/11 9:10 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--op...
(enabled and awaiting a free slave)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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 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)
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--op...
(enabled and awaiting a free slave)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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
TODO:
3) Remove openshift from astools build, including test features
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)
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
9:06 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10013:
------------------------------------
Ran the whole thing again from the pom-core.xml file using -Popenshift-bootstrap, and got
one test plugin failing:
{code}
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] BUILD FAILURE
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.13.0:test
(default-test) on project org.jboss.tools.openshift.egit.test: There are test failures.
{code}
So, I've changed that plugin's pom so it's a plugin, not a test-plugin:
{code}
openshift/tests/org.jboss.tools.openshift.egit.test/pom.xml
{code}
When you have actual tests to run in that plugin, please revert these changes in the
pom.xml. I left a TODO in there for you. :)
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
9:56 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/24/11 10:54 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--op... (build
is blue! disabled for now)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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 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)
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--op...
(enabled and awaiting a free slave)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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 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)
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
5:42 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/25/11 6:41 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--op... (build
is blue! disabled for now)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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)
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--op... (build
is blue! disabled for now)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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 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)
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
5:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10013:
------------------------------------
*{color:red}TODO:{color}
3) Remove openshift from astools build, including test features (Rob or Andre will do this
when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– https://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/ in progress, waiting
on >=1035
9) verify new stuff in updates/nightly/trunk site -- added new staging sites to composites
in order to properly create aggregate.
- https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ in progress,
waiting on >=4035
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
5:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/25/11 6:46 PM:
--------------------------------------------------------------
*{color:red}TODO:{color}*
3) Remove openshift from astools build, including test features (Rob or Andre will do this
when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– https://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/ - in progress,
waiting on >=1035
9) verify new stuff in updates/nightly/trunk site -- added new staging sites to composites
in order to properly create aggregate.
- https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ - in progress,
waiting on >=4035
was (Author: nickboldt):
*{color:red}TODO:{color}
3) Remove openshift from astools build, including test features (Rob or Andre will do this
when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– https://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/ in progress, waiting
on >=1035
9) verify new stuff in updates/nightly/trunk site -- added new staging sites to composites
in order to properly create aggregate.
- https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ in progress,
waiting on >=4035
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
5:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/25/11 6:46 PM:
--------------------------------------------------------------
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– https://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/ - in progress,
waiting on >=1035
9) verify new stuff in updates/nightly/trunk site -- added new staging sites to composites
in order to properly create aggregate.
- https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ - in progress,
waiting on >=4035
was (Author: nickboldt):
*{color:red}TODO:{color}*
3) Remove openshift from astools build, including test features (Rob or Andre will do this
when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– https://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/ - in progress,
waiting on >=1035
9) verify new stuff in updates/nightly/trunk site -- added new staging sites to composites
in order to properly create aggregate.
- https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ - in progress,
waiting on >=4035
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
5:48 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
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--op... (build
is blue! disabled for now)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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--op... (build
is blue! disabled for now)
*
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo...
(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
5:48 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/25/11 6:47 PM:
--------------------------------------------------------------
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - in
progress, waiting on >=1035 {color}
9) verify new stuff in updates/nightly/trunk site -- added new staging sites to composites
in order to properly create aggregate.
- {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ -
in progress, waiting on >=4035 {color}
was (Author: nickboldt):
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– https://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/ - in progress,
waiting on >=1035
9) verify new stuff in updates/nightly/trunk site -- added new staging sites to composites
in order to properly create aggregate.
- https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ - in progress,
waiting on >=4035
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
7:37 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/25/11 8:37 PM:
--------------------------------------------------------------
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - in
progress, waiting on >=1035 {color}
9) verify new stuff in http://download.jboss.org/jbosstools/updates/nightly/trunk/ site --
added new staging sites to composites in order to properly create aggregate.
- {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ -
in progress, waiting on >=4035 {color}
- two new openshift features listed and installable. Further verification/testing will be
left to Rob or Andre, or QE.
!snapshot12.png!
was (Author: nickboldt):
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - in
progress, waiting on >=1035 {color}
9) verify new stuff in updates/nightly/trunk site -- added new staging sites to composites
in order to properly create aggregate.
- {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ -
in progress, waiting on >=4035 {color}
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
7:41 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/25/11 8:41 PM:
--------------------------------------------------------------
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - in
progress, waiting on >=1035 {color}
9) verify new stuff in http://download.jboss.org/jbosstools/updates/nightly/trunk/ site --
added new staging sites to composites in order to properly create aggregate.
- {color:red} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ - in
progress, will need a respin >=4036 due to problem below {color}
- two new openshift features listed and installable. Further verification/testing will be
left to Rob or Andre, or QE.
!snapshot12.png!
was (Author: nickboldt):
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - in
progress, waiting on >=1035 {color}
9) verify new stuff in http://download.jboss.org/jbosstools/updates/nightly/trunk/ site --
added new staging sites to composites in order to properly create aggregate.
- {color:red} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ - in
progress, waiting on >=4035 {color}
- two new openshift features listed and installable. Further verification/testing will be
left to Rob or Andre, or QE.
!snapshot12.png!
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
Attachments: snapshot12.png, snapshot13.png
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
7:41 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10013:
-------------------------------
Attachment: snapshot12.png
snapshot13.png
Crap. Update site may be corrupt.
!snapshot13.png!
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
Attachments: snapshot12.png, snapshot13.png
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
7:41 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/25/11 8:41 PM:
--------------------------------------------------------------
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - in
progress, waiting on >=1035 {color}
9) verify new stuff in http://download.jboss.org/jbosstools/updates/nightly/trunk/ site --
added new staging sites to composites in order to properly create aggregate.
- {color:red} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ - in
progress, waiting on >=4035 {color}
- two new openshift features listed and installable. Further verification/testing will be
left to Rob or Andre, or QE.
!snapshot12.png!
was (Author: nickboldt):
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - in
progress, waiting on >=1035 {color}
9) verify new stuff in http://download.jboss.org/jbosstools/updates/nightly/trunk/ site --
added new staging sites to composites in order to properly create aggregate.
- {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ -
in progress, waiting on >=4035 {color}
- two new openshift features listed and installable. Further verification/testing will be
left to Rob or Andre, or QE.
!snapshot12.png!
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
Attachments: snapshot12.png, snapshot13.png
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
7:45 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/25/11 8:44 PM:
--------------------------------------------------------------
Crap. Update site may be corrupt.
!snapshot13.png!
However, I was able to install from
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
after adding that site PLUS these two to get around the corruption:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
was (Author: nickboldt):
Crap. Update site may be corrupt.
!snapshot13.png!
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
Attachments: snapshot12.png, snapshot13.png
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
12:36 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt resolved JBIDE-10013.
--------------------------------
Resolution: Done
Closing. Remaining two TODOs have been moved into subtasks for Rob and Andre to address.
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
Attachments: snapshot12.png, snapshot13.png
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
12:36 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10013 at 10/26/11 1:34 PM:
--------------------------------------------------------------
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - 1035
== BUILD SUCCESS (though other tests failed) {color}
9) verify new stuff in http://download.jboss.org/jbosstools/updates/nightly/trunk/ site --
added new staging sites to composites in order to properly create aggregate.
- {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ -
FIXED >=403 {color}
- two new openshift features listed and installable. Further verification/testing will be
left to Rob or Andre, or QE.
!snapshot12.png!
was (Author: nickboldt):
*{color:red}TODO:{color}*
3) Remove openshift from astools tree in SVN, including test features (Rob or Andre will
do this when they're happy w/ the results of (8) and (9)
8) verify continuous and tests jobs work after this change, and that both AS and OpenShift
components are built
– {color:green} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/ -
2982 is blue, with as and openshift bits == BUILD SUCCESS {color}
– {color:orange} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/ - in
progress, waiting on >=1035 {color}
9) verify new stuff in http://download.jboss.org/jbosstools/updates/nightly/trunk/ site --
added new staging sites to composites in order to properly create aggregate.
- {color:red} https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/ - in
progress, will need a respin >=4036 due to problem below {color}
- two new openshift features listed and installable. Further verification/testing will be
left to Rob or Andre, or QE.
!snapshot12.png!
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
Attachments: snapshot12.png, snapshot13.png
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
12:36 p.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10013:
-------------------------------
Comment: was deleted
(was: Crap. Update site may be corrupt.
!snapshot13.png!
However, I was able to install from
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
after adding that site PLUS these two to get around the corruption:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
)
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
Attachments: snapshot12.png, snapshot13.png
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
4:14 a.m.
[
https://issues.jboss.org/browse/JBIDE-10013?page=com.atlassian.jira.plugi...
]
Stefan Bunciak closed JBIDE-10013.
----------------------------------
OpenShift and EGit plugin has its own component now.
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.M5
Attachments: snapshot12.png, snapshot13.png
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
4544
days inactive
4756
days old
jbosstools-issues@lists.jboss.org
25 comments
6 participants
participants (6)
-
Nick Boldt (Commented) (JIRA) -
Nick Boldt (Issue Comment Edited) (JIRA)
-
Nick Boldt (Resolved) (JIRA)
-
Nick Boldt (Updated) (JIRA)
-
Rob Stryker (Created) (JIRA)
-
Stefan Bunciak (JIRA)