1. 13 Apr, 2022 2 commits
  2. 30 Mar, 2022 1 commit
    • Jérôme Charaoui's avatar
      fix team#40703 · fbb5bc96
      Jérôme Charaoui authored
      This also add some info messages about which ssh private key is picked
      up, but in short what happened here is that because I added the
      "tor-www@" prefix to the environment URLs, those wouldn't match the
      grep command on review.tpn anymore, and since the project's
      STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY is scoped to the production
      environment only, CI running on branches would end up with an null ssh
      private key. If this happens again hopefully the build log will contain
      a bit more useful info.
  3. 29 Mar, 2022 7 commits
  4. 28 Mar, 2022 3 commits
  5. 23 Feb, 2022 1 commit
  6. 09 Feb, 2022 2 commits
  7. 08 Feb, 2022 5 commits
  8. 07 Feb, 2022 1 commit
  9. 02 Feb, 2022 10 commits
    • Jérôme Charaoui's avatar
      use a single apt/pip cache for the project · 388a2433
      Jérôme Charaoui authored
      There's probably no benefit here of using different caches on every
      branch, so just remove cache:key. Caches are NOT shared between
      different projects.
      And for check_l10n_freshness, assume that the apt cache is already
      sufficiently recent so skip uploading it back to GitLab to relieve
      some pressure.
    • Jérôme Charaoui's avatar
      abandon caching Lektor · ea985b15
      Jérôme Charaoui authored
      I think the buildstate files created there are useless without
      preexisting build artifacts, so unless we want to cache build artifacts,
      which I don't think we do, we can save some space by skipping it. This
      directory is also where Lektor installs plugin packages, but again I
      don't think there are major benefits to caching these, since they
      essentially are copies of files already present in the repository.
    • Jérôme Charaoui's avatar
      add some comments for lektor tests · 205f067b
      Jérôme Charaoui authored
    • Jérôme Charaoui's avatar
    • Jérôme Charaoui's avatar
      re-add check_new_strings test · 5944fa4f
      Jérôme Charaoui authored
      renamed check_l10n_freshness
    • Jérôme Charaoui's avatar
      fix l10n-staging deploying to production · 6faadd8b
      Jérôme Charaoui authored
      This happened on projects that did not scope STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY
      to the production environment, so that sshkey was overriding the job-level
      STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY variable and causing an unwanted
      deployment to production.
      The solution was to change the scope for STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY
      to the production environment instead of All (the default), which was
      done for all projects which use the ci-templates.
      However to make things extra-safe, instead of playing with variable
      overrides, ensure that if the environment URL contains "review.tpn",
      always replace the original STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY with
    • Jérôme Charaoui's avatar
      add after_script to deploy-l10n-staging for debug · fde25684
      Jérôme Charaoui authored
      This job seems to be using the wrong ssh key and is still causing
      the deployment to happen on production...
    • Jérôme Charaoui's avatar
      ensure APT::Clean-Installed is enabled · 5e770352
      Jérôme Charaoui authored
      This makes sure that old versions of packages don't stay in the cache
    • Jérôme Charaoui's avatar
      fix caching in apt snippet · 1fa75a79
      Jérôme Charaoui authored
      This removes /etc/apt/apt.conf.d/docker-clean which was cleaning up
      apt/dpkg completely and preventing any kind of actual caching. Also this
      toggles Binary::apt::APT::Keep-Downloaded-Packages which is needed
      otherwise the .debs are not kept.
    • Jérôme Charaoui's avatar
      fix deploy-l10n-staging · a6a86074
      Jérôme Charaoui authored
      These keys should have been merged from the deploy-review job that we
      extend, but it doesn't appear to be working as expected, and is
      currently instead deploying to prod... yikes!
      At least the fix is simple, just copy the key/value pairs from the
      source job.
  10. 01 Feb, 2022 8 commits