Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 576
    • Issues 576
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 115
    • Merge requests 115
  • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #2089
Closed
Open
Issue created Aug 20, 2020 by pgnd@pgnd

isc 'Software Collection' Fedora repo integration -- auto push/build of new releases? or manual intervention?

Are the Fedora 'Software Collection' isc-bind* pkgs

https://copr.fedorainfracloud.org/coprs/isc/bind/packages/

intended to be automatically pushed to & rebuilt on upstream's version bumps? Or do they require manual invervention?

This morning's 9.16.6 maintenance release notice, resolving 5 CVEs, is not shown queued/building

https://copr.fedorainfracloud.org/coprs/isc/bind/builds/

and is not obviously included in the CI/CD pipeline.

Would like to understand the timing/scheduling of new releases to the software collection repos, and, if needed, request the manual build trigger.

Assignee
Assign to
Time tracking