Skip to content
Snippets Groups Projects
Select Git revision
  • dunfell default protected
  • kirkstone protected
  • audio_support_demovideo
  • main protected
  • ew2022
  • prepare-for-sw-rendering
6 results
Search by author
  • Any Author
  • Alexander Sterger Alexander Sterger alexander.sterger
  • Andrii Sosiuk Andrii Sosiuk andrii.sosiuk
  • **** **** group_556_bot_74cce396359e27efa6278607a72ef350
  • Bernd Mierzowski Bernd Mierzowski bernd.mierzowski
  • Christian Stimming Christian Stimming christian.stimming
  • Christoph Kutzera Christoph Kutzera christoph.kutzera
  • Christos Christos Karampeazis
  • CI Variables Management Service Account CI Variables Management Service Account service_account_ci_vars_management
  • Davide Cardillo Davide Cardillo davide.cardillo
  • Dietmar Muscholik Dietmar Muscholik dietmar.muscholik
  • Dmitry Petrov Dmitry Petrov dmitry.petrov
  • Felix Gerking Felix Gerking felix.gerking
  • GitBot GitBot gitbot
  • Git Bot Service Account Git Bot Service Account service_account_gitbot
  • Hai Nam Tran Hai Nam Tran hai.nam.tran
  • Hilmar Bode Hilmar Bode hilmar.bode
  • Jan-Ove Korneffel Jan-Ove Korneffel jan-ove.korneffel
  • Jonas Höppner Jonas Höppner jonas.hoeppner
  • Lorenzo Pagliai Lorenzo Pagliai lorenzo.pagliai
  • Lukas Rosky Lukas Rosky lukas.rosky
20 authors
  1. Mar 20, 2023
  3. Mar 09, 2023
  5. Feb 28, 2023
  7. Feb 20, 2023
  9. Feb 10, 2023
  11. Feb 07, 2023
  13. Feb 06, 2023
  15. Jan 10, 2023
  17. Jan 09, 2023
  19. Jan 03, 2023
  21. Dec 20, 2022
  23. Nov 21, 2022
  25. Nov 11, 2022
  27. Oct 18, 2022
    • GitBot's avatar
      Integrate gitlab-ci/add-hide-ftp-upload-flag · 945b3e90
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@a5e27f6e

FTP upload: Add flag to hide FTP upload stage

This is a workaround to prevent customer releases being uploaded to our
public FTP area. It should be removed as soon as we support uploading to
different FTP target folders.
      945b3e90
    • GitBot's avatar
      Integrate gitlab-ci/add-release-suffix and 3 more · 7e7a67c6
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@543a2170

manifest_package: add release suffix

Customer specific manifest projects can now set the RELEASE_SUFFIX
variable, which then gets appended to the deployment folder names.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@c763c43f

alphaplan_fwr: change variable "release_name_local" to "release_name"

Otherwise it can be assumed that it might be correlated with
outputdir_local, which is not the case.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d8d26a5

package_release: more refactoring

- Make output-dir an argument that can be passed multiple times instead
  of hard-coding two dirs with certain meanings.
- Remove LOCALDIR variable from package.env, because it is not used
  anywhere (only occurence was job class ".uploadsdkftp" which wasn't
  used anywhere either).

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc3698c8

package_release: refactoring

Improve readability of package_release.py and its submodule
generate_release_metadata.py.

- Add describing comments throughout the file.
- Remove duplicate code from functions. Simplify them, so that they do
  what their names say (and nothing more).
- Rename variables and function arguments to make their purpose clearer.
- Harmonize variable names with their corresponding command line arguments.
- Add pydoc for functions.
- Add type declarations to function arguments.
- Generate MD5 and metadata files in the source directories so that they
  can be copied along with the rest of the files.
      7e7a67c6
  29. Sep 27, 2022
  31. Sep 20, 2022
  33. Sep 14, 2022
  35. Sep 06, 2022
  37. Sep 05, 2022
  39. Aug 31, 2022
  41. Aug 30, 2022
  43. Aug 02, 2022
  45. Jul 13, 2022
    • GitBot's avatar
      Integrate gitlab-ci/add-test-reporting-to-test-jobs · 26b19877
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@52bae4a1

Lava Testreporting: Add script to generate markdown report for given jobids

Adds scripts for mark down generation.
Adds scripts for lava test result queries.
Adds script to generate a mark down report from this data
Call script from submit_test to generate a report directly
after the testrun.
      26b19877
    • GitBot's avatar
      Integrate gitlab-ci/run-test-from-gitlab-directly · 78777071
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ab09db0b

CI: Lava Test: Allow to install test image directly from gitlab

The images from the build job can be directly installed from gitlab.
To achive this some changes in the complete pipeline have been needed.

1. The variables used in the build job, like CI_PARAM_IMAGE, ... and
   related variables like BUILDPATH are only valid in the build job now.
2. The build job writes every variable needed in a follow up job into
   build.env. This also includes the url to the fng-install.sh of the
   final image.
3. The build.env file is used as dotenv artifact, as well as normal
   file artifact.
   The dotenv make the written variables automatically available in
   follow up jobs, that are using the aritfacts, like the deploy job.
   The normal file artifact is available via artifact download.
   (I did't found a way to download the dotenv file instead)
4. Some scripts have been added:
   - Find a job inside the pipeline by name, as the id is not known in
     advance.
   - Download all artifacts or one file of the artifacts from a given
     job
   - Download one file of the latest job by name
5. The scripts are used to download the build.env into the test job
   (where not artifacts are needed anymore)
6. The script is sourced and all variables are available inside the
   script.

Additionally this adds a fake build job to the ci-test pipeline, that
copies an image from srv73 and stores it as artifact in a way that a
test-job can run on it, like in the normal yocto pipeline.
      78777071
  47. Jul 12, 2022
  49. Jul 07, 2022
  51. Jul 06, 2022
    • GitBot's avatar
      Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more · 5fa72c3b
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@c503a6d4

CI: pipeline yocto: Change scope of CI_PARAM_IMAGE, ... to fix fngsystem build

The variables CI_PARAM_IMAGE, CI_PARAM_DISTRO, CI_MACHINE have been
defined outside the job in the '.gitlab-ci.yml' file. This has a lower
precedence then variables defined inside the job, but it seems that
these variables are used in the scope of 'Trigger variables' when
available in the trigger job. These override the value set in the
template. As main results this made FNGSystem jobs build the normal
yocto.
      5fa72c3b
    • GitBot's avatar
      Integrate gitlab-ci/CI-readd-allow-failure-true · cc174188
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ea3aa816

CI: Readd allow_failure:true to fix not finished pipelines

According to the docs a manual job always has allow_failure set to
true, but we see a lot of jobs staying in an unfinished state since
the removal of the allow_failure: true keyword for the sdk and test
jobs. This should fix the broken behaviour.
      cc174188
    • GitBot's avatar
      Integrate gitlab-ci/test-artifact-upload · d8d9dd44
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc0503b6

CI: Hardcode the artifacts path in the generated job description

Some gitlab update(?) seem to have changed the behaviour in
variable passing. In the scripts the variables are available
but in the artifacts path does not resolve them any more.
May be it has something to do with the introduction of the
trigger:forward keyword.
      d8d9dd44
  53. Jun 28, 2022
  55. Jun 21, 2022
    • GitBot's avatar
      Integrate gitlab-ci/share-manifest-pipeline and 2 more · fa4590d9
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@9b8cf51c

Share manifest pipeline for ci-test and yocto

Combine all common yaml parts in manifest-pipeline.yml and add
manifest-pipeline-yocto.yml and manifest-pipeline-ci-test.yml
containing the different variable assignments for each environment.

This change implicitly introduces parent-child build job generation in
the ci-test pipeline, like it is done in the yocto pipeline already.
The ci-test build jobs have been moved to build-jobs-ci-test.jinja2
accordingly.

Furthermore rename GITLAB_CI_CURRENT_REV to GITLAB_CI_REVISION and
remove the run conditions from all generated build jobs, since these are
already present in the upstream trigger job.

The repos including these files have to be updated with the new file
and variable names.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1b939fe

Use CI variables in build template directly

The job generation script implicitly passes the OS environment to the
template, so that the template has access to all GitLab CI variables.
Hence there is no need to explicitly pass any of them as command line
arguments.

This change makes the "generate-build-jobs" job more generic, so that
it can be shared with the ci-test pipeline in the future.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@775c09c1

Add gitlab_backup script to download all project exports of a gitlab group
      fa4590d9
    • GitBot's avatar
      Integrate gitlab-ci/fix-build-merge-request-job and 1 more · dedd24ea
      GitBot authored 
      --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@7f68f307

Yocto manifest build: re-enable build:merge_request job

This job was accidentally disabled in 2e6c1b4, because it was included
in the generated child pipeline. This pipeline is not created on the
master, though, so the condition for the job was never met.

Move the job to the parent pipeline again, so that it gets executed on
the master like before.

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@970c7fd7

Re-add yamllint stage to ci test manifest pipeline

Was accidentally removed in previous commit.
      dedd24ea
  57. Jun 20, 2022