Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-ci gst-ci
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-cigst-ci
  • Issues
  • #74

Closed
Open
Created May 13, 2020 by Jordan Petridіs@alatiera🌱Maintainer0 of 1 task completed0/1 task

Issue with stale gst-build cache in docker images

The following discussion from !289 (merged) should be addressed:

  • @alatiera started a discussion: (+1 comment)

Scenario, as it cropped up in the 1.16 branch of gst-build.

Current pre-fetched subproject cache (and wrap file) of glib pointed to 2.60 branch. Though after updating our msys2 setup, we needed to bump the subproject to 2.62+ branch for glib to compile again in msys.

But if you have an existing checkout of a subproject, meson will refuse to overwrite it with update, and it will try to rebase the existing checkout on top of the new ref, which doesn't work for stable branches. Example here

This means that if we bump revisions in .wrap files, CI is still building against the old revisions of the cached subprojects.

Assignee
Assign to
Time tracking