Ubuntu Test Cases

Merge lp://qastaging/~doanac/ubuntu-test-cases/apt-get-update-rerun into lp://qastaging/ubuntu-test-cases/touch

  1. apt-get-update-rerun
  2. Merge into touch
Proposed by Andy Doan
Status: Needs review
Proposed branch: lp://qastaging/~doanac/ubuntu-test-cases/apt-get-update-rerun
Merge into: lp://qastaging/ubuntu-test-cases/touch
Diff against target: 274 lines (+170/-1)
6 files modified
jenkins/production.py (+1/-0)
jenkins/setup_jenkins.py (+24/-0)
jenkins/templates/touch-smoke-rerun.xml.jinja2 (+123/-0)
scripts/assert-image (+4/-0)
scripts/provision.sh (+10/-1)
scripts/run-smoke (+8/-0)
To merge this branch: bzr merge lp://qastaging/~doanac/ubuntu-test-cases/apt-get-update-rerun
Reviewer Review Type Date Requested Status
Ubuntu Test Case Developers Pending
Review via email: mp+208458@code.qastaging.launchpad.net

Description of the change

This adds support for a new "rerun" job. This job is identical to our smoke job except:

 * it doesn't publish results (or do live streaming)
 * it has an option, APT_GET_UPDATE, to allow running apt-get update after provisioning the device.

To post a comment you must log in.
Revision history for this message
Paul Larson (pwlars) wrote :

I think we need a parameter for revision also, and if specified we also pass --revison {rev} in IMAGE_OPTS

Was none of the xml in the rerun job something we could import from other template blocks? If not, fine. I was just wondering.

Also, I'm not sure we want to publish these anywhere on the dashboard do we?

Reply
Revision history for this message
Andy Doan (doanac) wrote :

On 02/26/2014 01:20 PM, Paul Larson wrote:
> I think we need a parameter for revision also, and if specified we also pass --revison {rev} in IMAGE_OPTS

I was thinking we could use the existing INSTALL_URL feature for that.
Is that okay, or should we try and add functionality for --rev (its not
currently supported in provision.sh)

> Was none of the xml in the rerun job something we could import from other template blocks? If not, fine. I was just wondering.

we don't really have template blocks for the smoke job anymore. maybe
its worth copying, but i thought it would be easier to prevent mistakes
this way (ie, not accidententally streaming live results to the dashboard).

> Also, I'm not sure we want to publish these anywhere on the dashboard do we?

The rerun template doesn't do any publishing.

Reply

Unmerged revisions

194. By Andy Doan

add a new "re-run" job

This job will show up like the smoke-daily, but have rerun on the end.
Its a non-publishing job and also includes an option to run
"apt-get upate" after provisioning the device.

193. By Andy Doan

provide a mechanism to perform apt-get update after provisioning device

We have a need for some one-off testing where an apt-get update call
is required.

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