Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • U updater
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TurrisTurris
  • updater
  • updater
  • Merge requests
  • !301

pkgupdate/main: Always run post update hooks

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Michal Hrusecky requested to merge post-hooks into hasher Oct 21, 2022
  • Overview 6
  • Commits 1
  • Pipelines 1
  • Changes 2

Run postupdate hooks even if we encountered some problematic error. Post update hooks are quite often used even for vital functionality like taking snapshots and deploying the kernel. Thus we need to run them even if everything didn't went as expected.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: post-hooks