Skip to content
Snippets Groups Projects
  1. Mar 17, 2023
  2. Mar 09, 2023
  3. Feb 28, 2023
  4. Feb 20, 2023
  5. Feb 10, 2023
  6. Feb 07, 2023
  7. Feb 06, 2023
  8. Jan 10, 2023
  9. Jan 09, 2023
  10. Jan 03, 2023
  11. Dec 20, 2022
  12. Nov 30, 2022
  13. Nov 21, 2022
  14. Nov 10, 2022
  15. Oct 18, 2022
    • GitBot's avatar
      Integrate gitlab-ci/add-hide-ftp-upload-flag · 21c3daaa
      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.
      21c3daaa
    • GitBot's avatar
      Integrate gitlab-ci/add-release-suffix and 3 more · a6b9bed5
      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.
      a6b9bed5
  16. Sep 27, 2022
  17. Sep 20, 2022
  18. Sep 14, 2022
  19. Sep 06, 2022
  20. Sep 05, 2022
  21. Aug 31, 2022
  22. Aug 30, 2022
  23. Aug 18, 2022
  24. Aug 02, 2022
  25. Jul 15, 2022
    • Clemens Terasa's avatar
      bball_qml: Pass arguments to internal qmlscene · 8e0e4e6c
      Clemens Terasa authored
      To use the bball_qml sample with a different Qt platform (i.e. linuxfb) 
      we need to pass the @-platform@ parameter. However, this was not 
      possible with the current bball_qml shell script.
      Add pass the script arguments to qmlscene as well. 
      
      BCS 746-000991
      8e0e4e6c
  26. Jul 13, 2022
    • GitBot's avatar
      Integrate gitlab-ci/add-test-reporting-to-test-jobs · 1290134f
      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.
      1290134f
    • GitBot's avatar
      Integrate gitlab-ci/run-test-from-gitlab-directly · d3814d6d
      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.
      d3814d6d
  27. Jul 12, 2022
  28. Jul 07, 2022
  29. Jul 06, 2022
    • Felix Gerking's avatar
      rs485echo: Fix RS485 transmission delays · 113135af
      Felix Gerking authored
      Before, the delay_rts_before_send delay_rts_after_send fields were not
      explicitly initialized. This led to a erroneous transmission behaviour.
      Now the RS485 port settings are read before the half duplex
      configuration is done. This ensures that the delays are set to 0 or to
      a predefined value (device tree).
      
      BCS 746-000908
      113135af
    • GitBot's avatar
      Integrate gitlab-ci/CI-variable-scope-for-CI_PARAM_IMAGE-and-more · 6c671209
      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.
      6c671209
    • GitBot's avatar
      Integrate gitlab-ci/CI-readd-allow-failure-true · 17faf80c
      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.
      17faf80c
    • GitBot's avatar
      Integrate gitlab-ci/test-artifact-upload · b71f5bd4
      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.
      b71f5bd4
  30. Jun 28, 2022
Loading