#11653 Request for 'openscanhub' repository on GitHub
Closed: Fixed a year ago by kevin. Opened a year ago by svashisht.

Describe what you would like us to do:


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.

When do you need this to be done by? (YYYY/MM/DD)


asap


If possible, I should be added there as an admin.

My username on GitHub is 'siteshwar'.

Where the project is hosted now?

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

a year ago

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 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:

  • Push to GitHub should trigger a container image build on quay.io.
  • When the image build is successful, it should be deployed on the fedora infra staging deployment.
  • Tests should be run on the staging deployment.
  • If the tests pass, the same container image that is deployed to staging should be promoted to ready for production.

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.

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.

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.

@kdudka Do you have any objection for having fedora-infra repository in the upstream organization?

@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.

@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

a year ago

I can indeed. Thanks!

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog