Commits on Source (11)
-
Tim Jaacks authored3d2dbe4d
-
Tim Jaacks authored
This was used in times when the same code was executed from different places. We don't do that anymore, so the variable is obsolete.
1860ca8e -
Tim Jaacks authored
This had been accidentally removed in 5e36715e.
a91baa55 -
Tim Jaacks authored
Rename variable in order to avoid confusion with the original MACHINE variable used everywhere else. Also rename the local Jinja2 variable to include an underscore to make naming consistent.
073ae81e -
Tim Jaacks authored
This adds a machine-independent job "build-version" which populates the RELEASE_VERSION and RELEASE_NAME variables, so that following jobs can use these without depending on the various build jobs. The variables can be set from the trigger job in a project's `.gitlab-ci.yml` file. They are eval'ed before saving them to version.env, so we can use deferred variable expansion or even command execution to construct their values. This mechanism is already used for the Flash-N-Go System variables.
922f49f8 -
Tim Jaacks authored
The RELEASE_NAME variable can be set directly now, so there's no need to have a dedicated RELEASE_SUFFIX anymore. A previous configuration like RELEASE_SUFFIX: "-custom" can now be achieved using: RELEASE_NAME: "Yocto-${RELEASE_VERSION}-custom"
cad30c20 -
Tim Jaacks authored
Instead of passing these variables from stage to stage or regenerating their values in later stages, use the ones set in the build-version job at all places.
372d192b -
Tim Jaacks authored
The expressions to calculate RELEASE_NAME and RELEASE_VERSION cannot be stored within these variables themseselves. If set on the trigger level, they would override the calculated values in build-version.env then, as trigger variables always have the highest precedence. Use separate variables RELEASE_VERSION_EXPRESSION and RELEASE_NAME_EXPRESSION to define how RELEASE_VERSION and RELEASE_NAME are calculated instead.
cdd47023 -
Tim Jaacks authored
Instead of passing MACHINE from stage to stage or loading it from testdata.json, use the original value from the Jinja2 loop and set it directly for each job where it is used.
1d5e479f -
Tim Jaacks authorede136e5e2
-
Tim Jaacks authored
Append it to the configured target at the deploy class level instead. This removes the need for eval'ing the variables before usage. RELEASE_NAME can be used directly at the class level because it is known from build-version.env. This makes the deploy behavior identical to the Azure stage.
f2a29f53
Showing
- build-pipeline-ci-test.yml 0 additions, 1 deletionbuild-pipeline-ci-test.yml
- build-pipeline-yocto.yml.jinja2 36 additions, 20 deletionsbuild-pipeline-yocto.yml.jinja2
- build-pipeline.yml 68 additions, 43 deletionsbuild-pipeline.yml
- docs/manifest-parent-child.png 0 additions, 0 deletionsdocs/manifest-parent-child.png
- docs/manifest-pipeline.md 105 additions, 22 deletionsdocs/manifest-pipeline.md
- manifest-pipeline-ci-test.yml 10 additions, 14 deletionsmanifest-pipeline-ci-test.yml
- manifest-pipeline-yocto.yml 21 additions, 20 deletionsmanifest-pipeline-yocto.yml
- scripts/package_release.py 19 additions, 38 deletionsscripts/package_release.py

| W: | H:
| W: | H:

