1. 21 Oct, 2021 1 commit
  2. 01 Oct, 2021 1 commit
  3. 30 Sep, 2021 1 commit
  4. 24 Sep, 2021 1 commit
  5. 20 Sep, 2021 1 commit
    • Emanuele Aina's avatar
      updates: Do not fail on updatable branches with no base · 261823c2
      Emanuele Aina authored
      
      
      The `golang-k8s-sigs-yaml` update in `apertis/v2021-updates` broke the
      rendering for downstream instances since it does not have a base branch:
      
          golang-k8s-sigs-yaml:
            git:
              path_with_namespace: pkg/golang-k8s-sigs-yaml
            updates:
            - branch:
                name: apertis/v2021-updates
                version: 1.2.0-2+apertis1
              upstream:
                component: development
                name: golang-k8s-sigs-yaml
                source: apertis/v2021-updates
                version: 1.2.0-3+apertis1
      
      This is due to the fact that `golang-k8s-sigs-yaml` is a new dependency
      introduced by a package that got updated in `apertis/v2021-updates` and
      has not been folded into `apertis/v2021` yet: no `golang-k8s-sigs-yaml`
      exists in `apertis/v2021`, and for this reason there's no `base` object.
      
      In this case it is enough to trigger the pipeline directly on the
      `apertis/v2021-updates` branch.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      261823c2
  6. 17 Sep, 2021 1 commit
  7. 16 Sep, 2021 7 commits
  8. 04 Sep, 2021 3 commits
  9. 02 Sep, 2021 1 commit
  10. 31 Aug, 2021 2 commits
  11. 30 Aug, 2021 1 commit
  12. 12 Aug, 2021 1 commit
  13. 14 Jul, 2021 1 commit
  14. 07 Jul, 2021 1 commit
    • Emanuele Aina's avatar
      check-invariants: Ignore some v2020 issues · a9ace028
      Emanuele Aina authored
      
      
      We never backported the commits adding `debian/apertis/component` files
      to v2020 to avoid unnecessary churn in a stable release but this had two
      drawbacks:
      
      1. pipelines that got re-triggered for any reason would fail
      1. almost all v2020 package lag compared to v2021
      
      Since we're not going to address these issues, explicitly ignore them to
      reduce the amount of noise on the dashboard.
      
      Ignoring lagging packages may cause us to miss some backports, but at
      the moment they'd get drowned in the noise anyway.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      a9ace028
  15. 05 Jul, 2021 1 commit
  16. 04 Jul, 2021 7 commits
  17. 22 Jun, 2021 5 commits
  18. 09 Jun, 2021 1 commit
    • Ritesh Raj Sarraf's avatar
      Script to extract package list per release and write to tsv · 6ed2b25f
      Ritesh Raj Sarraf authored
      
      
      This script extracts the packages list from the respective Apertis
      releases Sources metadata file. It extracts the following fields:
      
      * Source Package Names
      * Package Version
      * Repository Component
      
      It then writes these values in a TSV format to a file per release.
      
      The tsv data is stored in a folder 'tsv/', treated as an artifact by the
      CI.
      
      The same artifact is pushed to the rendered dashboard for serving over
      HTTP
      Signed-off-by: Ritesh Raj Sarraf's avatarRitesh Raj Sarraf <ritesh.sarraf@collabora.com>
      6ed2b25f
  19. 19 May, 2021 3 commits