1. 10 Jan, 2023 1 commit
  2. 09 Jan, 2023 1 commit
  3. 03 Jan, 2023 2 commits
  4. 20 Dec, 2022 2 commits
  5. 21 Nov, 2022 1 commit
  6. 11 Nov, 2022 1 commit
  7. 18 Oct, 2022 2 commits
    • GitBot's avatar
      Integrate gitlab-ci/add-hide-ftp-upload-flag · 67575ced
      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.
      67575ced
    • GitBot's avatar
      Integrate gitlab-ci/add-release-suffix and 3 more · d7b8b1ed
      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.
      d7b8b1ed
  8. 27 Sep, 2022 1 commit
  9. 20 Sep, 2022 1 commit
  10. 14 Sep, 2022 1 commit
  11. 06 Sep, 2022 1 commit
  12. 05 Sep, 2022 1 commit
  13. 31 Aug, 2022 1 commit
  14. 30 Aug, 2022 1 commit
  15. 29 Aug, 2022 1 commit
  16. 02 Aug, 2022 1 commit
  17. 13 Jul, 2022 2 commits
    • GitBot's avatar
      Integrate gitlab-ci/add-test-reporting-to-test-jobs · 31555dad
      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.
      31555dad
    • GitBot's avatar
      Integrate gitlab-ci/run-test-from-gitlab-directly · 39c2a645
      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.
      39c2a645
  18. 12 Jul, 2022 1 commit
  19. 07 Jul, 2022 1 commit
  20. 06 Jul, 2022 3 commits
    • GitBot's avatar
      Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more · e0d47b7f
      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.
      e0d47b7f
    • GitBot's avatar
      Integrate gitlab-ci/CI-readd-allow-failure-true · bec184c5
      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.
      bec184c5
    • GitBot's avatar
      Integrate gitlab-ci/test-artifact-upload · 1e6a8298
      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.
      1e6a8298
  21. 28 Jun, 2022 2 commits
  22. 21 Jun, 2022 2 commits
    • GitBot's avatar
      Integrate gitlab-ci/share-manifest-pipeline and 2 more · 12fd0c94
      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
      12fd0c94
    • GitBot's avatar
      Integrate gitlab-ci/fix-build-merge-request-job and 1 more · 33a5c9c9
      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.
      33a5c9c9
  23. 20 Jun, 2022 2 commits
  24. 13 Jun, 2022 2 commits
  25. 02 Jun, 2022 1 commit
  26. 01 Jun, 2022 2 commits
  27. 31 May, 2022 3 commits