#5843 Create koji plugin to allow building only from whitelisted git branches
Closed: Invalid a year ago Opened 5 years ago by till.

To allow user git branches, koji needs to be able to allow building only from whitelisted git branches such as master or epel-7. This might need to be addressed in a koji plugin.


  • related: ticket:5814 - delete a certain private branch
  • related: ticket:5622 - allow to manage private branches

I will try to figure out something ASAP.

Currently the unwritten policy is not to assign tickets to persons, therefore I just add you to the CC list instead. Thank you for trying to address this issue. If you have any questions, feel free to ask.

Metadata Update from @till:
- Issue set to the milestone: Fedora 23 Alpha
- Issue tagged with: planning

2 years ago

@pingou is this or something like it going to be needed in the future world?

Metadata Update from @ausil:
- Issue assigned to pingou
- Issue close_status updated to: None
- Issue set to the milestone: Fedora 27 Final (was: Fedora 23 Alpha)

2 years ago

It would be needed to allow packagers to delete private branches - probably it would be even more important with pagure for dist-git if we use more private branches there. Or if pagure would not allow private branches for the official repo, it might not be as important.

Or if pagure would not allow private branches for the official repo, it might not be as important.

We added a feature to pagure to "enforce the PR workflow" in which case direct access to the main repo is entirely disabled and everyone needs to go via forks and pull-requests to contribute to the repo.
This can currently be set either at the repo (opt-in) or at the pagure instance level (so forced onto everyone).

@pingou Oh God, that's terrible. I don't want that at all... Can't we just have it so that private branches can only be used for scratch builds?

@pingou Oh God, that's terrible. I don't want that at all...

Thank you for your constructive feedback

@pingou Thank you for omitting the second half of my response and making it sound like I gave nothing useful at all...

@pingou Thank you for omitting the second half of my response

That's just because I pretty much had to take a break after reading the first part.
That's what I do when I encounter such strong language.

Can't we just have it so that private branches can only be used for scratch builds?

If you're willing to work on it and get it accepted upstream, I'm sure this would satisfy all parties involved and solve all three tickets related to this.

closing as invalid, with stream branching we should not do this now

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

a year ago

Login to comment on this ticket.

Metadata