On 11 June 2015 at 18:49, Felipe Sateler <fsateler at debian.org> wrote: > On 11 June 2015 at 09:50, Arun Raghavan <arun at accosted.net> wrote: >> On 11 June 2015 at 11:47, Peter Meerwald <pmeerw at pmeerw.net> wrote: >>> >>>> > configuration cannot be tested without commiting to github so it is >>>> > possible that a new iteration would be needed. >>>> > >>>> > Peter is Coverity admin, I do not know who is github admin of pulseaudio. >>>> >>>> I'm the Github admin. I've requested access for Coverity admin stuff >>>> so I can get the token etc. >>> >>> granted >> >> Thanks! It looks like the Travis/Coverity stuff needs to be based on >> the Github project (and just switching the one based on fd.o might not >> work). > > The link with the instructions to link the coverity accounts was given > to me by a coverity help person when I specifically asked if switching > would work. So I guess in principle at least it is supported. > >> We can figure out how to dedup the two, but In the mean time, I >> see to have having trouble getting this to work: >> >> https://travis-ci.org/ford-prefect/pulseaudio >> >> Any ideas? > > It may be that the yaml requires some ordering for keys? That would be > a bit crazy but still... It is either that or the token was not > generated correctly, but we can't see the original ;) > > I've been using the csound .travis.yml for reference[1], and other > than the env key ordering and a notification_email key in the coverity > addon I don't see any difference. > > [1] https://github.com/csound/csound/blob/develop/.travis.yml This started working now (I just set up the API key yet again), so I think we're good to go, soon. The final commit looks something like this, and I'll push it out post freeze: https://github.com/ford-prefect/pulseaudio/commit/67f372a6d983c39b0b8afb0a3a7b50315214f040 Cheers, Arun
