Add script to automate Fedora release onboarding #211
Conversation
The script can generate the Packit config for dist-git repo and push it to rawhide or create a PR against rawhide with the config. Fixes packit/packit-service#2301
There was a problem hiding this comment.
opening this PR for some early reviews and feedback
I was thinking about where to put this script (somewhere separately as in here, or create this as a Packit command) and am open for feedback/suggestions, because I see this could be used both by
- maintainers who already used Packit and want to automatically generate the config for lot of packages (we could build upon this script with reading the input values from some JSON or similar)
- for us (Packit devs) if we try to onboard some package to ease our work
| # TODO also make this as input parameter? | ||
| "dist_git_branches": ["fedora-all"], |
There was a problem hiding this comment.
I am not sure here if we got this from input, whether these should be 3 separate arguments then (for each job), or one argument (pull_from_upstream and koji_build would use the input value directly and for bodhi-update we would compute the {targets-from-input} - {rawhide}
There was a problem hiding this comment.
+1 parameter, probably just a single one
doing pull_from_upstream for all fedora releases can even violate guidelines so we should ideally advocate to update only in rawhide, as a safe measure
There was a problem hiding this comment.
thanks for the feedback, agreed!
| # TODO also make this as input parameter? | ||
| "dist_git_branches": ["fedora-all"], |
There was a problem hiding this comment.
+1 parameter, probably just a single one
doing pull_from_upstream for all fedora releases can even violate guidelines so we should ideally advocate to update only in rawhide, as a safe measure
The script can generate the Packit config for dist-git repo and push it to rawhide or create a PR against rawhide with the config.
Fixes packit/packit-service#2301