For patches pushed upstream we want builds run on master branch, but
don't want them run on the -maint branches, as we are not keeping the
.travis.yml file on stable branches updated wrt latest needs of travis
CI platforms.

We can't just whitelist 'master' though, because that will prevent
developers triggering their own private travis builds. So we just
blacklist *-maint, since developers will typically use named feature
branches for any work.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
 .travis.yml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/.travis.yml b/.travis.yml
index 01dffaa602..d3f72d46f3 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -2,6 +2,10 @@ sudo: false
 language: c
 cache: ccache
 
+branches:
+  except:
+  - /^.*-maint$/
+
 matrix:
   include:
     - compiler: gcc
-- 
2.14.3

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Wed, Mar 21, 2018 at 02:06:36PM +0000, Daniel P. Berrangé wrote:
> For patches pushed upstream we want builds run on master branch, but
> don't want them run on the -maint branches, as we are not keeping the
> .travis.yml file on stable branches updated wrt latest needs of travis
> CI platforms.
> 
> We can't just whitelist 'master' though, because that will prevent
> developers triggering their own private travis builds. So we just
> blacklist *-maint, since developers will typically use named feature
> branches for any work.
> 
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
>  .travis.yml | 4 ++++
>  1 file changed, 4 insertions(+)

Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list