Skip to content
Snippets Groups Projects
  1. Jul 13, 2023
  2. Jun 02, 2023
  3. Apr 24, 2023
    • Tim Jaacks's avatar
      Fix check for branch protection state · 23680f48
      Tim Jaacks authored
      Since the changes of 939ade2b we observe
      that pipelines are executed on non-protected branches, which is not what
      we want.
      
      GitLab's documentation was a bit unclear on the according CI variables
      CI_COMMIT_REF_PROTECTED and CI_MERGE_REQUEST_TARGET_BRANCH_PROTECTED, as
      stated in this stack overflow answer:
      https://stackoverflow.com/a/59023344/3018229
      
      We need to explicitly check for the variable values to be "true" instead
      of just checking whether they are set.
      23680f48
  4. Apr 04, 2023
    • Tim Jaacks's avatar
      Depend intgration pipeline execution on branch protection state · 939ade2b
      Tim Jaacks authored
      Previously we had the master branch hard-coded in a variable in order to
      determine whether to run the integration pipeline (on non-master branch)
      or the merge pipeline (on master branch). This variable had to be
      adapted everytime we copy a branch, which can potentially be forgotten
      and lead to problems.
      
      Remove the hard-coded branch and use the branch protection state for
      this decision instead in order to make this more flexible.
      939ade2b
  5. Apr 03, 2023
    • Tim Jaacks's avatar
      Simplify yamllint job rules · dbc49ad0
      Tim Jaacks authored
      The rules for the yamllint jobs have been defined in the .yamllint class
      before. They were overridden in the manifest pipeline's yamllint job,
      though, which has its own rules, so we don't need them to be inherited
      in this case. And in the manifest integration pipeline the rules can be
      much easier, so define them there instead of at the class-level.
      dbc49ad0
  6. Mar 27, 2023
  7. Mar 21, 2023
    • Tim Jaacks's avatar
      Use project path instead of name in integration branch name · e943a55e
      Tim Jaacks authored
      Usually project name and path are identical after project creation. It
      is possible, though, to change the name of a project without changing
      its path.
      When triggering a pipeline on the integration branch, we are using the
      CI_PROJECT_NAME variable to reference the project. Unexpectedly, this
      variable contains the *path*, not the *name* of the project (see
      https://gitlab.com/gitlab-org/gitlab/-/issues/20030).
      Hence we have to use the project path in all other places where the
      integration branch name is constructed in our Python code.
      e943a55e
  8. Mar 20, 2023
  9. Mar 07, 2023
  10. Feb 28, 2023
  11. Feb 20, 2023
  12. Feb 14, 2023
  13. Feb 10, 2023
  14. Feb 06, 2023
  15. Jan 10, 2023
  16. Jan 09, 2023
  17. Jan 03, 2023
  18. Dec 21, 2022
  19. Dec 20, 2022
  20. Dec 19, 2022
Loading