2017-08-10 1:09 GMT+05:00 Steffan Karger <stef...@karger.me>:
> Hi,
>
> On 09-08-17 08:12, Илья Шипицин wrote:
> > 2017-08-09 10:47 GMT+05:00 Илья Шипицин <chipits...@gmail.com
> > <mailto:chipits...@gmail.com>>:
> > 2017-08-09 10:41 GMT+05:00 Илья Шипицин <chipits...@gmail.com
> > <mailto:chipits...@gmail.com>>:
> > 2017-08-08 20:55 GMT+05:00 Steffan Karger
> > <steffan.kar...@fox-it.com <mailto:steffan.kar...@fox-it.com>>:
> >
> > Enable coverity analysis for the release/2.4 branch.
> >
> > We can only do a limited number of coverity scans per week
> > with our FOSS
> > account, but since we only occasionally push commits, that
> > should work out
> > fine. But this limit is the reason we don't use the
> > standard travis addon,
> > because that would cause the coverity script to run on all
> > of our matrix
> > builds. That would cause us to reach our limit faster, and
> > waste travis'
> > resources.
> >
> > Since our FOSS coverity account doesn't handle multiple
> > branches very well,
> > we have to pick one branch to run coverity on. I think it's
> > best to use
> > the most recent stable branch for that (i.e. for now,
> > release/2.4).
> > Though for ease of maintenance, it's probably best to apply
> > the patch to
> > both master and release/2.4.
> >
> > I would refactor it like that
> > https://gist.github.com/chipitsine/
> 8dcae4ff1d59eb43df39f6015c6106fd
> > <https://gist.github.com/chipitsine/
> 8dcae4ff1d59eb43df39f6015c6106fd>
> > however, your is ok as well
> >
> > maybe, "script" would be better here
> > https://gist.github.com/chipitsine/8dcae4ff1d59eb43df39f6015c6106
> fd#file-gistfile1-txt-L74
> > <https://gist.github.com/chipitsine/8dcae4ff1d59eb43df39f6015c6106
> fd#file-gistfile1-txt-L74>
> > than "before_script"
> >
> > oops, travis does not support braches within matrix
> >
> > https://gist.github.com/chipitsine/8dcae4ff1d59eb43df39f6015c6106
> fd#file-gistfile1-txt-L70-L72
> >
> > sorry for that
>
> I like your idea, and toyed with it a bit. But in the end, it needs too
> much fiddling to get right. So I prefer my own suggested approach.
>
nevermind :)
>
> -Steffan
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
