Describe a plan for downstream part of the workflow #123
Conversation
lachmanfrantisek
changed the title
downstream/README.md
Outdated
|
|
||
| What can be added is providing a feedback during the process: | ||
|
|
||
| - providing a dashboard view for the job |
There was a problem hiding this comment.
we could link to the Fedora developer dashboard: https://packager-dashboard.fedoraproject.org/
although they provide user-based view and not a package-based view
| - I can send a pull-request to a repository containing the list of repositories to build. (The same thing zuul does.) | ||
| - I can add a packit config to the distgit repository and configure the job (can be combined with the previous version so we can filter the projects before checking config presence). | ||
| - A service authenticated by FAS where I can enable the build and, ideally, configure the process. | ||
|
|
There was a problem hiding this comment.
I'm not sure right now if they need to grant packit some extra permissions to be able to create builds and bodhi updates
There was a problem hiding this comment.
Since packit FAS user is a packager, maintainers need to add it as a maintainer to the project.
But we can try getting the rights for building all packages, but that would probably require running service in the Fedora infrastructure.
There was a problem hiding this comment.
yeah, getting proven packager rights wouldn't be trivial to get, I'd say we still need to prove ourself :)
There was a problem hiding this comment.
You can have a "group" or sig to add packager to. F.e. we have @ruby-packagers-sig. That should be enough to have commit bits.
lachmanfrantisek
force-pushed
the
downstream
branch
4 times, most recently
from
d9e2416 to
d07cbfc
Compare
lachmanfrantisek
force-pushed
the
downstream
branch
from
d07cbfc to
bb4e8e9
Compare
|
After a quick read through it seems like a nice list. Thanks |
lachmanfrantisek
force-pushed
the
downstream
branch
2 times, most recently
from
be1a8cb to
7d5ed98
Compare
This is the easiest solution how to do this. See packit/research#123 for more information. Signed-off-by: Frantisek Lachman <flachman@redhat.com>
|
Looks good! As we're already doing this workflow in an automated fashion and I can find all the steps we're currently doing in your description I'm confident to say that your covering our use case :) |
This is the easiest solution how to do this. See packit/research#123 for more information. Signed-off-by: Frantisek Lachman <flachman@redhat.com>
lachmanfrantisek
force-pushed
the
downstream
branch
3 times, most recently
from
8b499ad to
5eacf86
Compare
…nstream-koji-build Add downstream Koji build as new type This is the easiest solution how to do this. See packit/research#123 for more information. Related to packit/packit-service#55 Merge before TBD N/A (will be mentioned in service) Reviewed-by: Tomas Tomecek <tomas@tomecek.net>
Signed-off-by: Frantisek Lachman <flachman@redhat.com>
Signed-off-by: Frantisek Lachman <flachman@redhat.com>
lachmanfrantisek
force-pushed
the
downstream
branch
from
5eacf86 to
0755666
Compare
Upstream issue: pallets/click#2232 Signed-off-by: Frantisek Lachman <flachman@redhat.com>
lachmanfrantisek
changed the title
|
Hi all, thanks for all the feedback. I've tried to update the text to match the current state and mark what we've implemented in the meantime.
|
preview: https://github.com/lachmanfrantisek/research/blob/downstream/downstream/README.md
TODO: