[
https://issues.apache.org/jira/browse/MADLIB-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandish Jayaram updated MADLIB-1165:
------------------------------------
Description: The current Jenkins build does give us some continuous
integration (CI) for every commit to MADlib master. Can we extend this to other
databases that MADlib supports (The two latest versions of Greenplum and
Postgres)? (was: The current Jenkins build does give us some CI for every
commit to MADlib master. Can we extend this to other databases that MADlib
supports (The two latest versions of Greenplum and Postgres)?
We also need a wider set of test coverage for MADlib, which can be included in
the MADlib CI build process, to go beyond the install check we currently do on
Jenkins.)
Summary: Add CI support to MADlib for install-check on all supported
databases (was: Add continuous integration support to MADlib)
> Add CI support to MADlib for install-check on all supported databases
> ---------------------------------------------------------------------
>
> Key: MADLIB-1165
> URL: https://issues.apache.org/jira/browse/MADLIB-1165
> Project: Apache MADlib
> Issue Type: New Feature
> Components: Build System
> Reporter: Nandish Jayaram
> Fix For: v1.13
>
>
> The current Jenkins build does give us some continuous integration (CI) for
> every commit to MADlib master. Can we extend this to other databases that
> MADlib supports (The two latest versions of Greenplum and Postgres)?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
