Merge lp:~canonical-platform-qa/snappy-ecosystem-tests/build-snap into lp:snappy-ecosystem-tests
Proposed by
Omer Akram
Status: | Merged |
---|---|
Approved by: | Omer Akram |
Approved revision: | 38 |
Merged at revision: | 24 |
Proposed branch: | lp:~canonical-platform-qa/snappy-ecosystem-tests/build-snap |
Merge into: | lp:snappy-ecosystem-tests |
Diff against target: |
235 lines (+174/-10) 3 files modified
snappy_ecosystem_tests/helpers/snapcraft/build_snap.py (+140/-0) snappy_ecosystem_tests/helpers/snapd/snapd.py (+1/-4) snappy_ecosystem_tests/utils/ssh.py (+33/-6) |
To merge this branch: | bzr merge lp:~canonical-platform-qa/snappy-ecosystem-tests/build-snap |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Heber Parrucci (community) | Approve | ||
platform-qa-bot | continuous-integration | Approve | |
Santiago Baldassin (community) | Approve | ||
Review via email:
|
Commit message
Build a snap and pull it
Description of the change
We have many test cases that upload a new snap to the store, or upload a new revision of an already existing snap, we could ship snaps in our test suite but I am not sure how will that play out if we have to register and upload a new snap for a random new name. So in such cases we just quickly build a new snap in an isolated environment.
To post a comment you must log in.
PASSED: Continuous integration, rev:31 /platform- qa-jenkins. ubuntu. com/job/ snappy- ecosystem- tests-ci/ 212/ /platform- qa-jenkins. ubuntu. com/job/ generic- update- mp/2004/ console
https:/
Executed test runs:
None: https:/
Click here to trigger a rebuild: /platform- qa-jenkins. ubuntu. com/job/ snappy- ecosystem- tests-ci/ 212/rebuild
https:/