On Monday 03 Feb 2014 13:48:10 Raphaël Badin wrote: > On 02/03/2014 01:10 PM, Jenkins Notification wrote: > > See http://d-jenkins.ubuntu-ci:8080/job/trusty-adt-maas-daily/71/ > > [...] > > The build for the daily Trusty package is now fixed. Let's keep it that > way by being cautious when we land things that have side-effects on the > MAAS package that the unit tests can't properly cover. Don't forget that > we have the manual job at our disposal to test packages [0]. > > [0] http://d-jenkins.ubuntu-ci:8080/view/MAAS/job/trusty-adt-maas-manual/
Raphers can you do me a favour please and write a Google Doc, which lives in the MAAS section of docs, that explains the QA procedure from end to end. I'm thinking along the lines of: * land changes * push the recipe build button * wait for package build * Click button in Jenkins page And then for every card we have on the kanban board, I want to see people putting it through QA using this procedure please. Cheers. -- Mailing list: https://launchpad.net/~maas-builds Post to : [email protected] Unsubscribe : https://launchpad.net/~maas-builds More help : https://help.launchpad.net/ListHelp
