[
https://jira.nuxeo.com/browse/NXBT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Carsique resolved NXBT-357.
----------------------------------
Resolution: Fixed
http://qa.nuxeo.org/jenkins/job/nuxeo-master-fullbuild-permanentCheck/ is
building the whole Nuxeo sources.
FT-nuxeo-master-selenium-cap-tomcat_permanentCheck,
FT-nuxeo-master-selenium-cmf-tomcat_permanentCheck,
FT-nuxeo-master-selenium-dam-tomcat_permanentCheck,
FT-nuxeo-master-selenium-dm-jboss_permanentCheck,
FT-nuxeo-master-selenium-dm-tomcat_permanentCheck,
FT-nuxeo-master-selenium-social-collaboration-tomcat_permanentCheck,
FT-nuxeo-master-webdriver-cap-tomcat_permanentCheck are then testing against
distributions previously built by nuxeo-master-fullbuild-permanentCheck.
> Improve permanentCheck jobs
> ---------------------------
>
> Key: NXBT-357
> URL: https://jira.nuxeo.com/browse/NXBT-357
> Project: Nuxeo ECM Build/Test Environment
> Issue Type: Improvement
> Components: Continuous integration
> Reporter: Julien Carsique
> Assignee: Julien Carsique
>
> Permanent checks
> Permanent checks currently don't wait for nuxeo-features to be built but
> won't raise relevant issues until nuxeo-features is built.
> In cases where there are a lot of commits, nuxeo-features build can take
> several hours.
> => need to change that
> So basically, we could have permanent checks be closer to the IT builds :
> rebuild everything from zero
> do build / no UT / distrib on a fast slave
> dispatch non-reg tests on different hosts
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
