[jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside
Fred Bricon
fbricon at redhat.com
Thu Jun 13 17:21:35 EDT 2013
All done for central
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] central.maven.examples.all ........................ SUCCESS [0.577s]
[INFO] maven.all ......................................... SUCCESS [0.084s]
[INFO] maven.plugins ..................................... SUCCESS [0.051s]
[INFO] org.jboss.tools.maven.core ........................ SUCCESS [3.281s]
[INFO] org.jboss.tools.maven.ui .......................... SUCCESS [1.958s]
[INFO] org.jboss.tools.maven.conversion.ui ............... SUCCESS [1.119s]
[INFO] maven.features .................................... SUCCESS [0.068s]
[INFO] org.jboss.tools.maven.feature ..................... SUCCESS [0.831s]
[INFO] org.jboss.tools.maven.seam ........................ SUCCESS [2.408s]
[INFO] org.jboss.tools.maven.seam.feature ................ SUCCESS [0.414s]
[INFO] org.jboss.tools.maven.cdi ......................... SUCCESS [1.437s]
[INFO] org.jboss.tools.maven.cdi.feature ................. SUCCESS [0.252s]
[INFO] org.jboss.tools.maven.hibernate ................... SUCCESS [1.364s]
[INFO] org.jboss.tools.maven.hibernate.feature ........... SUCCESS [0.318s]
[INFO] org.jboss.tools.maven.portlet ..................... SUCCESS [1.462s]
[INFO] org.jboss.tools.maven.portlet.feature ............. SUCCESS [0.449s]
[INFO] examples.all ...................................... SUCCESS [0.057s]
[INFO] examples.plugins .................................. SUCCESS [0.062s]
[INFO] org.jboss.tools.project.examples .................. SUCCESS [4.969s]
[INFO] org.jboss.tools.maven.project.examples ............ SUCCESS [2.765s]
[INFO] org.jboss.tools.project.examples.cheatsheet ....... SUCCESS [1.313s]
[INFO] examples.features ................................. SUCCESS [0.066s]
[INFO] org.jboss.tools.project.examples.feature .......... SUCCESS [0.309s]
[INFO] org.jboss.tools.maven.project.examples.feature .... SUCCESS [0.342s]
[INFO] maven.tests ....................................... SUCCESS [0.038s]
[INFO] org.jboss.tools.maven.common.test ................. SUCCESS [42.016s]
[INFO] org.jboss.tools.maven.jbosspackaging .............. SUCCESS [1.047s]
[INFO] org.jboss.tools.maven.jdt ......................... SUCCESS [1.010s]
[INFO] org.jboss.tools.maven.configurators.tests ......... SUCCESS
[3:40.889s]
[INFO] org.jboss.tools.maven.conversion.test ............. SUCCESS [49.050s]
[INFO] org.jboss.tools.maven.profiles.core ............... SUCCESS [0.482s]
[INFO] org.jboss.tools.maven.profiles.test ............... SUCCESS [25.455s]
[INFO] org.jboss.tools.maven.sourcelookup.core ........... SUCCESS [0.923s]
[INFO] org.jboss.tools.maven.sourcelookup.ui ............. SUCCESS [1.086s]
[INFO] org.jboss.tools.maven.sourcelookup.test ........... SUCCESS
[2:57.039s]
[INFO] org.jboss.tools.maven.test.feature ................ SUCCESS [2.403s]
[INFO] org.jboss.tools.maven.jbosspackaging.feature ...... SUCCESS [4.318s]
[INFO] org.jboss.tools.maven.profiles.ui ................. SUCCESS [3.816s]
[INFO] org.jboss.tools.maven.profiles.feature ............ SUCCESS [0.569s]
[INFO] org.jboss.tools.maven.gwt ......................... SUCCESS [3.434s]
[INFO] org.jboss.tools.maven.gwt.feature ................. SUCCESS [1.518s]
[INFO] org.jboss.tools.maven.sourcelookup.feature ........ SUCCESS [0.931s]
[INFO] org.jboss.tools.maven.jdt.feature ................. SUCCESS [1.351s]
[INFO] org.jboss.tools.community.project.examples ........ SUCCESS [0.532s]
[INFO] org.jboss.tools.community.project.examples.feature SUCCESS [0.531s]
[INFO] examples.tests .................................... SUCCESS [0.211s]
[INFO] org.jboss.tools.project.examples.test ............. SUCCESS
[6:24.881s]
[INFO] org.jboss.tools.project.examples.test.feature ..... SUCCESS [1.585s]
[INFO] central.all ....................................... SUCCESS [0.120s]
[INFO] central.plugins ................................... SUCCESS [0.077s]
[INFO] org.jboss.tools.central ........................... SUCCESS [11.125s]
[INFO] org.jboss.tools.community.central ................. SUCCESS [0.253s]
[INFO] org.jboss.tools.central.themes .................... SUCCESS [0.857s]
[INFO] central.features .................................. SUCCESS [0.076s]
[INFO] org.jboss.tools.central.feature ................... SUCCESS [0.239s]
[INFO] org.jboss.tools.community.central.feature ......... SUCCESS [18.750s]
[INFO] org.jboss.tools.central.themes.feature ............ SUCCESS [0.876s]
[INFO] central.tests ..................................... SUCCESS [0.122s]
[INFO] org.jboss.tools.central.test ...................... SUCCESS
[1:42.105s]
[INFO] org.jboss.tools.central.test.feature .............. SUCCESS [0.255s]
[INFO] central.maven.examples.site ....................... SUCCESS
[1:23.228s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 21:34.544s
[INFO] Finished at: Thu Jun 13 23:18:01 CEST 2013
[INFO] Final Memory: 194M/667M
[INFO]
------------------------------------------------------------------------
Fred Bricon at FBRICON-WIN /d/Dev/GitHub/jbosstools-central
(jbosstools-4.1.0.Beta2x)
Looks like one Jenkins slave always timeouts one test. Works locally, on
other slaves, couldn't find what really happens so I've extended the
timeout. We'll see how it goes.
Le 11/06/2013 16:12, Max Rydahl Andersen a écrit :
> Hi core-compnent leads,
>
> Thursday 13th is branch/codefreeze day as planned [1].
>
> Special Note:
> Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
> line of defense/attack on this codefreeze.
>
> A quick reminder what branch/codefreeze means for each component/repo owner:
>
> 0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
>
> 1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools parent.
> Should look something like this:
>
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.0.Beta2-SNAPSHOT</version>
> </parent>
>
> 2) Make sure your component builds and passes its tests when run locally.
>
> $ mvn clean verify
>
> 3) Make a branch for the Beta2 builds to use.
>
> Most components uses master, thus the steps would be something like:
>
> $ git checkout master
> $ git pull origin master
> $ git checkout -b jbosstools-4.1.0.Beta2x
> $ git push origin jbosstools-4.1.0.Beta2x
>
> 4) Respond to this mail before end of Thursday with a "All Done for component:
> <your component>" or "<your component> cannot branch/freeze today because of
> <jira issues> must be done first"
>
> Thank you!
>
> [1] https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
More information about the jbosstools-dev
mailing list