Re: [linux-safety] ci pipeline for clang-analyzer

["Paul Albertella" <paul.albertella@codethink.co.uk>]

This is great Sudip!

I see that Travis CI has a max duration of 120 minutes for jobs. If we 
continue tinyconfig, then I'm guessing that should be enough, but we 
will want to explore other options for when we work on more 
representative configs, which I think Elana is planning to define as 
part of the Dev Process WG's work this quarter.

Another alternative would be to use Github Actions, which doesn't seem 
to have a maximum job duration, but does limit job runtime to 2000 hours 
per month for a free account.

Looking at Github's pricing page (https://github.com/pricing), I think 
ELISA could qualify for free 'Teams' level account, which would increase 
this to 3000 hours per month. However, this is the limit for the whole 
team, not per user, so we might be better off with individual free accounts.


Paul



On 07/10/2020 23:18, Sudip Mukherjee wrote:
> 
> 
> On 07/10/2020 22:19, Sudip Mukherjee wrote:
>> Hi All,
>>
>> I tried to setup a pipeline for clang-analyzer so that all of us
>> interested can get the test result from latest linux-next. The build
>> with "defconfig" timedout but "tinyconfig" does work. You can see the
>> one from next-20201007 at [1].
>>
>> Next, I will try to:
>> 1) set up a cron job so that the pipeline starts as soon as linux-next
>> is published
>> 2) set a pipeline for arm64. looks like travis supports arm64.
>> 3) Add the report-generator to the image.
>> 4) Check if I can push the generated report to a github page.
> 
> Little bit of manual run, but the report from clang-analyzer for
> next-20201007 is now available at https://sudipm-mukherjee.github.io
> 
> 
>>
>>
>> [1].
>> https://travis-ci.org/github/sudipm-mukherjee/linux-test/builds/733790131
>>
>>
>