-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate production_build in favour of upstream_koji_build #1656
Deprecate production_build in favour of upstream_koji_build #1656
Conversation
Build failed. ✔️ pre-commit SUCCESS in 1m 59s |
Deprecate `production_build` in favour of `upstream_koji_build` Deprecate also the build alias since it's too generic. Signed-off-by: Frantisek Lachman [email protected] Related to: #1658 Merge before: packit/packit-service#1656 ... no release notes here, will be covered in the service PR Reviewed-by: Jiri Popelka <None> Reviewed-by: None <None> Reviewed-by: Laura Barcziová <None>
f17f4ee
to
acb6cc2
Compare
Build failed. ✔️ pre-commit SUCCESS in 1m 49s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! would it make sense to write somewhere down how to do the deprecation (the neutral and error statuses) so that we behave consistently in the future? (although, we also want to work on packit/research#159, so I am not sure how relevant it will be)
Signed-off-by: Frantisek Lachman <[email protected]>
acb6cc2
to
b2d60e2
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 3m 00s |
Signed-off-by: Frantisek Lachman <[email protected]>
b2d60e2
to
da4098a
Compare
Ideally, I would go with the automated fixes next time we need to change anything. |
BTW, I've fixed the tests, added a new test case covering the deprecation and restructured the changes across commits to make it more clear... @TomasTomecek @lbarcziova Could you please take another look? |
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: Frantisek Lachman <[email protected]>
Signed-off-by: Frantisek Lachman <[email protected]>
Signed-off-by: Frantisek Lachman <[email protected]>
da4098a
to
5dfbef9
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 3m 00s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
very nice work with the commit split
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 2m 45s |
Deprecate production_build in favour of upstream_koji_build Deprecate also the build alias since it's too generic. Related to packit/packit-service#1656 and packit/packit#1728 Reviewed-by: Jiri Popelka <None>
Deprecate also the
build
alias since it's too generic.Fixes: packit/packit#1658
Requires: packit/packit#1728
Documentation: packit/packit.dev#527
RELEASE NOTES BEGIN
There are two changes in the naming of the service jobs:
The
build
job type name has been deprecated. It aimed to be an alias when Packit supported just one build type.There are currently more types of builds and just
build
can be misleading. Please, be explicit and usecopr_build
instead.The
production_build
name for upstream Koji build is misleading because it is not used to run production/non-scratch builds and because it can be confused with thekoji_build
job that is triggered for dist-git commits.(The
koji_build
job can trigger both scratch and non-scratch/production builds.)To be explicit, use
upstream_koji_build
for builds triggered in upstream andkoji_build
for builds triggered in downstream.Users will get a neutral status describing the change when the old names are in use. The status will become a warning starting in November and the old names will be removed by the end of the year.
RELEASE NOTES END