How to use this repo

The plugins in this repo do not provide strong API guarantees or backwards compatibility. You should use a specific commit in your project and update it manually as needed.

You are recommended to import these plugins into your project using the junction plugins feature of BuildStream 2.0 so you can control exactly what Git commit is used. Please note that using it this way requires at least BuildStream 2.2. This is done in several stages documented below:

plugins:
- origin: pip
  package-name: buildstream-plugins
  sources:
  - git

kind: junction

sources:
- kind: git
  url: https://gitlab.com/BuildStream/buildstream-plugins-community.git
  track: master

plugins:
- origin: junction
  junction: buildstream-plugins-community.bst
  sources:
  - pypi
  elements:
  - pep517

BuildStream Release Compatibility

We aim to maintain compatibility with the oldest version of BuildStream supported by freedesktop-sdk stable branches. To achieve this, we test against the following versions of BuildStream:

• A fixed version of BuildStream. It should not be newer than the oldest version supported by freedesktop-sdk stable branches. You can see the currently tested fixed release in the setenv section in tox.ini.

• BuildStream master branch to track compatibility with upcoming releases of BuildStream. The CI job for this version is allowed to fail as it is not a fixed version of BuildStream and could break at any time.

We don’t have the CI resources to test against all the releases, but encourage developers to test these locally. We welcome patches to maintain compatibility with older releases of BuildStream, but due to CI resource constraints won’t be able to test them regularly. Support for other dependencies (e.g. supported python versions) are derived from the supported Buildstream releases and their respective EOL cycles