Difference between revisions of "Repository Layout"
Jump to navigation
Jump to search
| (25 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
| + | Right layers and branches/revs are always defined in webos-ports-setup/conf/layers.txt. Currently we're using Yocto 3.2 Gatesgarth release through testing (with LTS Qt 5.15) and Yocto 3.3 Hardknott through unstable branch. Next stable build will be with Yocto 3.2 Gatesgarth as well, once we're ready for new release. | ||
| + | The stable, testing, unstable branches in webos-ports-setup are rebased on top of Yocto release branch and the only difference is the branch name in the Makefile. That way if you use e.g. testing branch it will automatically switch between Yocto releases once we switch the testing builds on jenkins. Stable is the same as testing most of the time, but has locked meta-webos-ports and meta-smartphone revisions instead of latest. | ||
| − | + | Layerman will take care of the checkout of right layers with right revisions - just type make update if you want newer. | |
| − | + | The layout of directories on fileserver looks like this: | |
| − | + | Basically jenkins jobs are rsyncing artifacts to | |
| + | a) luneos-stable-staging for stable builds, which are later promoted to luneos-stable by separate jenkins job after testing | ||
| + | drwxrwxr-x 5 jenkins jenkins 4.0K Sep 15 14:57 luneos-stable | ||
| + | drwxrwxr-x 60 jenkins jenkins 4.0K Oct 30 2019 luneos-stable-staging | ||
| + | b) luneos-{testing,unstable} symlinks | ||
| + | lrwxrwxrwx 1 jenkins jenkins 25 Oct 22 09:31 luneos-testing -> luneos-testing-gatesgarth | ||
| + | lrwxrwxrwx 1 jenkins jenkins 25 Nov 1 11:26 luneos-unstable -> luneos-unstable-hardknott | ||
| + | which point to corresponding luneos-{testing,unstable}-<yocto-release> directory: | ||
| + | drwxrwxr-x 4 jenkins jenkins 4.0K Oct 22 09:47 luneos-testing-dunfell | ||
| + | drwxrwxr-x 5 jenkins jenkins 4.0K Nov 1 05:16 luneos-testing-gatesgarth | ||
| + | drwxrwxr-x 3 jenkins jenkins 4.0K Oct 30 2019 luneos-testing-warrior | ||
| + | drwxrwxr-x 4 jenkins jenkins 4.0K Sep 14 17:16 luneos-testing-zeus | ||
| + | drwxrwxr-x 5 jenkins jenkins 4.0K Oct 23 05:51 luneos-unstable-gatesgarth | ||
| + | drwxrwxr-x 2 jenkins jenkins 4.0K Nov 1 11:26 luneos-unstable-hardknott | ||
| − | + | And there is luneos-<yocto-release> convenience symlinks pointing to best LuneOS build for given yocto-release (testing if already available, otherwise unstable). | |
| − | + | lrwxrwxrwx 1 jenkins jenkins 22 Sep 14 17:34 luneos-dunfell -> luneos-testing-dunfell | |
| − | + | lrwxrwxrwx 1 jenkins jenkins 25 Oct 22 09:30 luneos-gatesgarth -> luneos-testing-gatesgarth | |
| − | + | lrwxrwxrwx 1 jenkins jenkins 25 Nov 1 11:33 luneos-hardknott -> luneos-unstable-hardknott | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 12:37, 1 November 2020
Overview
Right layers and branches/revs are always defined in webos-ports-setup/conf/layers.txt. Currently we're using Yocto 3.2 Gatesgarth release through testing (with LTS Qt 5.15) and Yocto 3.3 Hardknott through unstable branch. Next stable build will be with Yocto 3.2 Gatesgarth as well, once we're ready for new release.
The stable, testing, unstable branches in webos-ports-setup are rebased on top of Yocto release branch and the only difference is the branch name in the Makefile. That way if you use e.g. testing branch it will automatically switch between Yocto releases once we switch the testing builds on jenkins. Stable is the same as testing most of the time, but has locked meta-webos-ports and meta-smartphone revisions instead of latest.
Layerman will take care of the checkout of right layers with right revisions - just type make update if you want newer.
The layout of directories on fileserver looks like this:
Basically jenkins jobs are rsyncing artifacts to a) luneos-stable-staging for stable builds, which are later promoted to luneos-stable by separate jenkins job after testing
drwxrwxr-x 5 jenkins jenkins 4.0K Sep 15 14:57 luneos-stable drwxrwxr-x 60 jenkins jenkins 4.0K Oct 30 2019 luneos-stable-staging
b) luneos-{testing,unstable} symlinks
lrwxrwxrwx 1 jenkins jenkins 25 Oct 22 09:31 luneos-testing -> luneos-testing-gatesgarth lrwxrwxrwx 1 jenkins jenkins 25 Nov 1 11:26 luneos-unstable -> luneos-unstable-hardknott
which point to corresponding luneos-{testing,unstable}-<yocto-release> directory:
drwxrwxr-x 4 jenkins jenkins 4.0K Oct 22 09:47 luneos-testing-dunfell drwxrwxr-x 5 jenkins jenkins 4.0K Nov 1 05:16 luneos-testing-gatesgarth drwxrwxr-x 3 jenkins jenkins 4.0K Oct 30 2019 luneos-testing-warrior drwxrwxr-x 4 jenkins jenkins 4.0K Sep 14 17:16 luneos-testing-zeus drwxrwxr-x 5 jenkins jenkins 4.0K Oct 23 05:51 luneos-unstable-gatesgarth drwxrwxr-x 2 jenkins jenkins 4.0K Nov 1 11:26 luneos-unstable-hardknott
And there is luneos-<yocto-release> convenience symlinks pointing to best LuneOS build for given yocto-release (testing if already available, otherwise unstable).
lrwxrwxrwx 1 jenkins jenkins 22 Sep 14 17:34 luneos-dunfell -> luneos-testing-dunfell lrwxrwxrwx 1 jenkins jenkins 25 Oct 22 09:30 luneos-gatesgarth -> luneos-testing-gatesgarth lrwxrwxrwx 1 jenkins jenkins 25 Nov 1 11:33 luneos-hardknott -> luneos-unstable-hardknott