Merge lp://staging/~canonical-platform-qa/qakit/trigger_jenkins_builds into lp://staging/qakit

Proposed by Santiago Baldassin
Status: Approved
Approved by: Sergio Cazzolato
Approved revision: 157
Proposed branch: lp://staging/~canonical-platform-qa/qakit/trigger_jenkins_builds
Merge into: lp://staging/qakit
Diff against target: 444 lines (+381/-0)
10 files modified
qakit/config/__init__.py (+14/-0)
qakit/config/config.py (+26/-0)
qakit/launchpad/__init__.py (+14/-0)
qakit/launchpad/ppa.py (+49/-0)
qakit/practitest/data/__init__.py (+14/-0)
qakit/practitest/data/domains.json (+8/-0)
qakit/practitest/practitest.py (+19/-0)
qakit/ust/__init__.py (+26/-0)
qakit/ust/worker.py (+180/-0)
start_worker.py (+31/-0)
To merge this branch: bzr merge lp://staging/~canonical-platform-qa/qakit/trigger_jenkins_builds
Reviewer Review Type Date Requested Status
Sergio Cazzolato Approve
Richard Huddie (community) Needs Fixing
Jean-Baptiste Lallement Pending
Review via email: mp+304847@code.staging.launchpad.net

Commit message

Ubuntu system tests worker

Description of the change

This mp includes a worker that could be used by Bileto to trigger the ubuntu system tests. There are only two public apis that should be used and that can be invoked directly with python or via an amqp message. Those apis are

run_ust(ppa)
get_results(ppa)

Every single request in Bileto gets it's own ppa with the source packages involved in the change.

The first api will execute the following steps:
        1. Get the source packages from launchpad that are
        included in the ppa under test
        2. Use the packages versions to create a request id that will be use to track
        the test results for the source packages. The idea is to run the tests for every
        version of the source packages in the ppa
        3. Get the practitest filter id associated to the source packages in the ppa
        4. Get the list of test cases to be run from practitest
        5. Trigger a jenkins build that will:
            a. Flash the device
            b. Update the device with the ppa under test
            c. Setup the device for testing
            d. Run the tests

The second api will retrive the test results for a given ppa

To post a comment you must log in.
Revision history for this message
Sergio Cazzolato (sergio-j-cazzolato) wrote :

Some minor comments inline. In parallel you could start testing it integrated with jenkins to see how it works.

Please make sure in the final solution the jenkins jobs invoked have timeouts set.

review: Needs Fixing
Revision history for this message
Santiago Baldassin (sbaldassin) wrote :

Thanks for your review Sergio. I've addressed all your comments. By the way, I'm already testing this using real Jenkins job. This is the job that I'm using: https://platform-qa-jenkins.ubuntu.com/job/test_alesage_ust_rc-proposed_arale_add_ppa/

154. By Santiago Baldassin

Addressing comments from the reviews

Revision history for this message
Richard Huddie (rhuddie) wrote :

Some minor comments and questions below.

review: Needs Fixing
155. By Santiago Baldassin

Updating the worker and the domains

156. By Santiago Baldassin

Addressing comments from the reviews

157. By Santiago Baldassin

Merge from trunk

Revision history for this message
Sergio Cazzolato (sergio-j-cazzolato) wrote :

Approved, code lgtm

review: Approve

Unmerged revisions

157. By Santiago Baldassin

Merge from trunk

156. By Santiago Baldassin

Addressing comments from the reviews

155. By Santiago Baldassin

Updating the worker and the domains

154. By Santiago Baldassin

Addressing comments from the reviews

153. By Santiago Baldassin

Ubuntu system tests worker

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches

to all changes: