[SSSD] [PATCH] CI: Remove Clang analyzer

Michal Židek mzidek at redhat.com
Wed Oct 22 12:34:58 UTC 2014


On 10/22/2014 02:22 PM, Lukas Slebodnik wrote:
> On (22/10/14 11:55), Nikolai Kondrashov wrote:
>> On 10/17/2014 01:11 PM, Nikolai Kondrashov wrote:
>>> The attached patch removes Clang analyzer run from CI as it takes a long time
>>> and its results are ignored.
>>>
>>> I initially expected it to be taken into use quickly, but as that is not
>>> happening, we'd better remove it to save valuable CI server time.
>>>
>>> We can always add it back when a solution to checking it is agreed on and
>>> implemented.
>>
>> Jakub, can we get this merged? It will saves a good deal of time on the CI
>> servers.
>
> BTW: Developers could be still interested in html report from clang.
> This is the reason why execution on "git push instance" and execution on local
> machine are not the same use case. Ticket #2435 would be solution.
>
> I can imagine even better solution than Michal's proposal with --test="a,b,c"
> We could have some templates which would describe order of executed test.
> (for example in YAML). Developer could easily modify order of test. He/she
> could have his/her own templates
>      a) make discheck, mock
>      b) just code coverage
>      c) just static analysis
>      d) all tests.
> It would also allow us to easily disable problematic test on server side.
> (temporary use non default template)
>
>
> Travis CI use similar approach. (but it does not work with fedora)
> Example:
>      template(configuration file)
>          https://github.com/karelzak/util-linux/blob/master/.travis.yml
>      bash function used in template
>          https://github.com/karelzak/util-linux/blob/master/.travis-functions.sh
>
> LS

+1 for something like template file. That would be more flexible
than command line arguments.
If we want we can have something like default/fallback template
file in git that will be used if user does not specify his own
(and could also server as guide to craft custom template files).

Michal



More information about the sssd-devel mailing list