Support pull-from-upstream for non-git upstreams #2498
Conversation
|
Build succeeded. ✔️ pre-commit SUCCESS in 2m 16s |
|
Build succeeded. ✔️ pre-commit SUCCESS in 2m 14s |
- rename the attributes related to Anitya in the AnityaUpdateEvent - introduce model for project and new version in Anitya - utilise those for pull-from-upstream for non-git upstreams - change the affected API
lbarcziova
force-pushed
the
non-git-pull
branch
from
a5f0e36 to
1996b57
Compare
|
Build succeeded. ✔️ pre-commit SUCCESS in 2m 08s |
|
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 2m 14s |
softwarefactory-project-zuul
bot
merged commit 30964bf
into
packit:main
| @@ -278,6 +278,7 @@ class ProjectEventModelType(str, enum.Enum): | |||
| release = "release" | |||
| issue = "issue" | |||
| koji_build_tag = "koji_build_tag" | |||
| anitya_version = "anitya_version" | |||
There was a problem hiding this comment.
At first, it looked like a version of Anitya that doesn't make sense, but it might still be worth picking another name?
Maybe anitya_project_version, or is it too verbose?
packit_service/service/api/utils.py
Outdated
| anitya_project_id = anitya_project_name = anitya_package = project_url = ( | ||
| repo_name | ||
| ) = repo_namespace = None |
There was a problem hiding this comment.
This is funnily long... Not sure if I like it.. but why not. I hope the meaning is clear for everyone.
|
I'm curious, what is Anitya? |
Fixes #2203
TODO:
RELEASE NOTES BEGIN
pull-from-upstreamis now supported also without specifyingupstream_project_urlin the configuration. For such cases, the upstream repository will not be detected and cloned during release syncing.RELEASE NOTES END