[Development] Becoming a Tier 1 platform and the CI System

[lars.knoll at nokia.com]

On 6/6/12 1:56 PM, "ext Sean Harmer" <sean.harmer at kdab.com> wrote:

>On Wednesday 06 June 2012 13:22:21 Thiago Macieira wrote:
>> On quarta-feira, 6 de junho de 2012 11.46.18, Sean Harmer wrote:
>> > What other gates do we also have to pass to promote QNX to Tier 1?
>> 
>> The major target is that, at release time, you're able to confidently
>>say
>> that this platform is working properly and all the showstopper issues
>>(as
>> judged by the release testing) have been fixed. This, in turn, requires
>> that there are people testing that platform at release time and can
>>report
>> issues. If no one tests, we'll have zero out of zero fixes and we can't
>> give the Tier 1 label out of a division by zero :-)
>> 
>> Being in the CI system is just one of the common ways of achieving
>>that. If
>> you can compile and run unit tests on that platform at every commit, it
>> helps avoiding them at release time. But it's not strictly necessary: it
>> might be acceptable to run the unit tests at release time and say
>>they're
>> passing, along with the rest of the release testing. I wouldn't
>>recommend
>> this, though.
>
>I understand and integrating into the CI system would seem by far the
>most 
>sensible way to go in terms of maintainability, reducing man-power at
>release 
>time and preventing introduction of regressions.

Absolutely. But that requires that someone steps up and creates a CI
infrastructure we can use. The current one is based on a commercial
solution that Nokia unfortunately can't hand out to everybody. It should
however be possible to use the existing scripts (with some modifications)
on Jenkins.
>
>Until such time as the CI integration is completed, we will work to
>ensure 
>that release testing happens in a timely manner.
>
>> I don't know the technical details on how to integrate with the current
>>CI
>> system. But the first thing you're going to need is to have some way
>>for the
>> CI manager to tell you "test this SHA-1 / build number[1]" and then you
>> have to report back a pass or fail, with the logs. Are you able to do
>>that
>> already?
>
>At present we are polling gitorious for new commits. I will take a look
>into 
>how we can get hold of the sha1's that are used for integration testing
>from 
>gerrit.

For packages we currently always use the tested combinations from qt5.git.
>
>Once we have that aspect working we can take a look at feeding back the
>results of the build and eventually tests.

Please also subscribe on releases at qt-project.org where the testing results
should go.

Cheers,
Lars

>
>> [1] the commit that a build IDs refers to can be obtained from the
>>Gerrit
>> repository
>
>OK I will take a look. Thanks for the pointer.
>
>Sean
>--
>Dr Sean Harmer | sean.harmer at kdab.com | Senior Software Engineer
>Klarälvdalens Datakonsult AB, a KDAB Group company
>Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
>KDAB - Qt Experts - Platform-independent software solutions
>_______________________________________________
>Development mailing list
>Development at qt-project.org
>http://lists.qt-project.org/mailman/listinfo/development