Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • cerbero cerbero
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 102
    • Issues 102
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 33
    • Merge requests 33
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • cerberocerbero
  • Issues
  • #13
Closed
Open
Issue created Apr 08, 2015 by Bugzilla Migration User@bugzilla-migration

cerbero: Fix recipe status reset for git repositories

Submitted by Robert Swain

Link to original bug (#747514)

Description

Tests show that cerbero seems to reset the status of a recipe based, partially, upon what is fetched from a git repository rather than the HEAD commit hash.

This means that recipe build states get reset unnecessarily when the recipe points to a specific commit and the branch to which that commit belongs is updated. It also means that recipe build states are not updated if the specific commit pointed to is changed within that which is fetched.

Also, I changed the commit hash pointed to by a recipe and I expected that changing the recipe would trigger a rebuild (after running fetch-package --reset-rdeps --full-reset <package>) but it did not. It had even changed the commit that was checked out.

Assignee
Assign to
Time tracking