1. 23 Dec, 2020 1 commit
  2. 17 Nov, 2020 2 commits
  3. 29 Oct, 2020 1 commit
    • Nirbheek Chauhan's avatar
      gitlab: Fix cannot overwrite directory error when symlinking · b0f5da22
      Nirbheek Chauhan authored
      GitLab doesn't wipe images entirely before reusing them across jobs.
      It relies on the build scripts to not write outside the workdir.
      However, we create symlinks outside of the workdir, which breaks in
      weird ways.
      
      Specifically, when ../../gstreamer/cerbero exists, `ln -sf` creates
      ../../gstreamer/cerbero/cerbero, which is wrong, but doesn't cause an
      error. However, when the image is reused again after this,
      ../../gstreamer/cerbero/cerbero already exists, so `ln -sf` yields:
      
      ln: ../../gstreamer/cerbero/cerbero: cannot overwrite directory
      
      This is fixed in master after overhauling the scripts to never write
      outside of workdir, but for 1.16 we need to hack it by not symlinking
      if the target dir already exists.
      
      Originally commited to the 1.16 branch in
      !370
      
      The proper fix will be backported from master, but let's fix this
      error in the meantime so it doesn't roadblock the 1.18 stable releases
      
      Part-of: <!374>
      b0f5da22
  4. 27 Oct, 2020 1 commit
    • Jordan Petridіs's avatar
      citemplate: remove fdo.expires-after label · 5421bfe6
      Jordan Petridіs authored
      This is meant to be used for containers that are going
      to be periodically rebuilt. For our usecase specifying
      `fdo.upstream-repo` is enough to garbage collect all
      the tags from the forks.
      
      We also need to rebuild the images, so they don't have
      include the label anymore.
      
      Part-of: <!373>
      5421bfe6
  5. 22 Oct, 2020 1 commit
    • Jordan Petridіs's avatar
      citemplate: tweak merge-request rules · 1ba7dd97
      Jordan Petridіs authored
      With the MergeRequest rules template, its was impossible
      to manually create or trigger a pipeline for a branch/commit
      that was not part of a merge request.
      
      This tweaks the workflow:rules such that there will always be
      a pipeline for each commit (which will be set to a manual job trigger).
      
      There is the downside that we will now be triggering 2 pipelines in
      case of merge requests, but they will require manual action to be
      started.
      
      Part-of: <!371>
      1ba7dd97
  6. 14 Oct, 2020 1 commit
  7. 28 Sep, 2020 1 commit
  8. 15 Sep, 2020 1 commit
  9. 14 Sep, 2020 2 commits
  10. 09 Sep, 2020 3 commits
  11. 27 Aug, 2020 2 commits
  12. 05 Aug, 2020 1 commit
  13. 04 Aug, 2020 1 commit
  14. 26 Jul, 2020 2 commits
  15. 24 Jul, 2020 1 commit
  16. 23 Jul, 2020 2 commits
  17. 10 Jul, 2020 1 commit
  18. 09 Jul, 2020 1 commit
  19. 03 Jul, 2020 8 commits
  20. 02 Jul, 2020 1 commit
  21. 01 Jul, 2020 1 commit
  22. 30 Jun, 2020 1 commit
  23. 29 Jun, 2020 3 commits
  24. 26 Jun, 2020 1 commit
    • Jordan Petridіs's avatar
      citemplate: also check the forked registry for image builds · 5c490de1
      Jordan Petridіs authored
      In case you are developing a set of changes in a module, in
      conjunction with a branch in gst-ci, you will end up with
      a template with a different tag than the upstream repo, which
      will be refferencing your gst-ci forked registry.
      
      But that image won't existin in the namespace the
      module would be running at, so we need to copy it from there.
      
      Part-of: <!308>
      5c490de1