I need to store dockerfiles, configurations etc. for deployment, so I am requesting for a repository on fedora-infra organization on GitHub. Name of the repository should be 'openscanhub`. If possible, I should be added there as an admin.
asap
If possible, I should be added there as an admin.
My username on GitHub is 'siteshwar'.
Where the project is hosted now?
For experimental purpose, I have it under my namespace. The files related to deployment can be seen in fedora-infra directory.
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
I don't think you need that, everything related to deployment could be directly in ansible. See release-monitoring role for example. Only think that is managed on Github are the deployment webhooks, everything other is in the role.
I would prefer to use GitHub for dockerfiles. The process of building and deploying container images looks like:
Also, I would like to use GitHub Actions CI for running basic tests on each pull request and push to the main branch before a container image is built on quay.io.
main
This is really just on you, how do you want to manage the project upstream. But I don't think it needs to be in fedora-infra namespace, as it is not project that is maintained by Fedora Infrastructure team.
In that case, I would request for a repository under openscanhub GitHub organization.
@kevin Do you have any disagreement with that? I would add you as an admin there as a backup.
admin
@kdudka Do you have any objection for having fedora-infra repository in the upstream organization?
fedora-infra
@svashisht A repository under the openscanhub GitHub organization sounds like a good idea to me.
Sounds very reasonable to me. ;) Feel free to add me...
@kevin I have created https://github.com/openscanhub/fedora-infra/ and added you there as an 'admin`. Please confirm you can access it and close this issue.
Metadata Update from @kevin: - Issue assigned to kevin
I can indeed. Thanks!
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.