canonical-ci-engineering team mailing list archive

[Francis Ginther <francis.ginther@xxxxxxxxxxxxx>]

On Tue, Mar 3, 2015 at 12:08 PM, Nicholas Skaggs <
nicholas.skaggs@xxxxxxxxxxxxx> wrote:

> On 03/02/2015 05:53 PM, Francis Ginther wrote:
>
>> Nicholas,
>>
>> We'd like to add some content to this wiki to include how the autopilot
>> tests are executed in CI (which is a question we often receive). This is to
>> help resolve questions about how developers should run tests now that QA is
>> gating on autopilot test results.
>>
>> We're working on updates to the README file we maintain for describing
>> how to use the CI tools:
>> https://code.launchpad.net/~canonical-ci-engineering/
>> ubuntu-test-cases/testing-docs/+merge/251507 <
>> https://code.launchpad.net/%7Ecanonical-ci-engineering/
>> ubuntu-test-cases/testing-docs/+merge/251507>
>>
>> At a minimum, we like to reference the CI README on the wiki. Do you mind
>> providing some reviews and guidance on messaging this to the community
>> without adding confusion?
>>
>> Thanks,
>> Francis
>> --
>> Francis Ginther
>> Canonical - Ubuntu Engineering - Continuous Integration Team
>>
> I believe our conversation this morning on IRC covered this sufficiently.
> In summary, fully documenting and ensuring it's possible to recreate the
> issues found on the dashboard is a great start. Also consider instructing
> folks how to get and use the subunit file results, how to view them (trv
> perhaps), and linking to the readthedocs site rather than a raw file in
> bzr. Finally, it's important to mention the caveats of attempting to
> recreate old image results and encouraging folks to test and worry about
> results from current images that can be reproduced with the current
> packages.
>

Thanks Nicholas,

I've incorporated your feedback into another update which is now visible
[1] with an MP [2] if you want to see the specific changes:

[1] - http://ubuntu-test-cases-touch.readthedocs.org/en/latest/
[2] -
https://code.launchpad.net/~canonical-ci-engineering/ubuntu-test-cases/readme-updates/+merge/251666


> Also, as suggested we should link this information from developer.u.c to
> make it available to a wider audience, in addition to announcing it
> publicly on the mailing list. Finally, I can help make sure the core app
> developers themselves directly receive this information.
>

We can provide the content if you can give a recommendation on where it
should live. I poked around and found [3] as a possible candidate. These CI
testing tools only apply to the core-apps and internal apps, so pointing
developers working on some other app toward this makes no sense.


> A question for you that is yet unanswered. If someone has trouble, to whom
> or what should they turn for help? This can be different depending on a
> public request vs someone from the core apps developer community who is
> working on shipping code.


I'll have to get back to you on this.


>
> Nicholas


-- 
Francis Ginther
Canonical - Ubuntu Engineering - Continuous Integration Team