CI

Problems to solve:

Change version of meta layers

• repo: create another manifest with branch names, not hashes
• kas:
  • use 2 sets of config (1st: pinned.yml 2nd: integration.yml)
  • use lockfiles

Change fixed SRCREV and SRCBRANCH in recipes ? quite problematic. For example recipe name is my_app.bb:

• my_app.bbappend in new meta layer used only during CI ?
• my_app-latest.bb in the same meta layer and use PREFERRED_VERSION_my_app = “latest” ?
• PREFERRED_VERSION_my_app = “latest” ?
  • create new meta layer for CI and

• Possible to pass env variables to bitbake: https://wiki.niziak.spox.org/sw:yocto:bitbake:tips#pass_env_variables_to_bitbake

Already solved in Yocto!

Yocto contains special latest distro poky-bleeding.conf where config file poky-floating-revisions.inc is used:

poky-floating-revisions.inc

SRCREV_pn-oh-puzzles ?= "${AUTOREV}"
SRCREV_pn-libowl ?= "${AUTOREV}"
SRCREV_pn-matchbox-applet-light ?= "${AUTOREV}"

In latest Yocto it looks like:

poky-floating-revisions.inc

#
# Set recipe versions to auto-rev for cutting edge testing
#
 
INHERIT += "poky-bleeding"
 
POKY_AUTOREV_RECIPES = "\
    libmatchbox \
    opkg-utils \
    matchbox-config-gtk \
    matchbox-desktop \
    matchbox-keyboard \
    matchbox-panel-2 \
    matchbox-terminal \
    matchbox-theme-sato \
    matchbox-wm \
    pseudo \
    puzzles \
    sato-icon-theme \
    sato-screenshot \
    settings-daemon \
"

• See: Using an External SCM
• See: Build History Package Information