snappy-hwe-snaps

~snappy-hwe-team/snappy-hwe-snaps/+git/ci-build-126:master

  1. Git
  2. lp:~snappy-hwe-team/snappy-hwe-snaps/+git/ci-build-126
  3. master
Last commit made on 2017-12-05
Get this branch:
git clone -b master https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/ci-build-126
Members of Snappy HWE Team can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:
master
Repository:
lp:~snappy-hwe-team/snappy-hwe-snaps/+git/ci-build-126

Recent commits

e9e3e36... by System Enablement CI Bot <email address hidden>

Merge remote tracking branch other/fetch_gadget_tree

782f47f... by Gary.Wang

More unit tests fixes.

b78f744... by Gary.Wang

Make unit tests passed as per the minor change on gadget tree building.

62762e5... by Gary.Wang

Call snapcraft to create a 'built' gadget tree in advance for later
customization.

e4a62c1... by Gary.Wang

Support to specify a branch for remote gadget tree.

27e9d6d... by Gary.Wang

Don't log exception stack when running some units tests.

8090ff0... by Gary.Wang

Merge git+ssh://git.launchpad.net//~snappy-hwe-team/snappy-hwe-snaps/+git/ubuntu-custom-image into last_mile

a3b5714... by Gary.Wang

Add one more unit test for code coverage purpose and some minor change for code conventions.

97a59d3... by System Enablement CI Bot <email address hidden>

Merge remote tracking branch versioning

Merge-Proposal: https://code.launchpad.net/~gary-wzl77/snappy-hwe-snaps/+git/ubuntu-custom-image/+merge/333538

Author: Gary.Wang <email address hidden>

Unify software and spec versioning.

One thing probably confused to end-users is that the version number of u-c-i(0.1) and spec version(1) actually doesn't match at this moment. The easy solution I can see here probably is that u-c-i release and spec sharing a same version number so that people won't mix up spec version with the release number.
Also I changed the way that u-c-i read the version number(from snapcraft yaml file instead of hardcoding).
Meanwhile, version number(spec) can be either float or int data type, so that we don't need to bump major number up once new specs are supported.
TODO: We also need to consider the image spec forward compatibility and backward compatibility.

b35e0ee... by Gary.Wang

Split each state test into different functions(check_xxx) and simplify
shared test function.

Also, we use python built-in next() method to run each state function
instead of explicitly calling the specific state name.