#7208 Scratch builds from forked repos?
Closed: Invalid 5 years ago Opened 6 years ago by jarrpa.

Hello!

I'm trying to do scratch builds from the following branch:

https://src.fedoraproject.org/fork/jarrpa/container/glusterfs/branch/private-jarrpa

With some help I managed to figure out the following command:

koji-containerbuild --profile koji build --scratch f27-container-candidate git+https://src.fedoraproject.org/forks/jarrpa/container/glusterfs.git?#bc698113adb8013df859a8c446b8547a5042fbdd

But then I get the following error:

Created task: 23656542
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=23656542
Watching tasks (this may be safely interrupted)...
23656542 build (f27-container-candidate, /forks/jarrpa/container/glusterfs.git:bc698113adb8013df859a8c446b8547a5042fbdd): free
23656542 build (f27-container-candidate, /forks/jarrpa/container/glusterfs.git:bc698113adb8013df859a8c446b8547a5042fbdd): free -> FAILED: BuildError: src.fedoraproject.org:/forks/jarrpa/container/glusterfs.git is not in the list of allowed SCMs
  0 free  0 open  0 done  1 failed
  23656543 buildSRPMFromSCM (/forks/jarrpa/container/glusterfs.git:bc698113adb8013df859a8c446b8547a5042fbdd): FAILED: BuildError: src.fedoraproject.org:/forks/jarrpa/container/glusterfs.git is not in the list of allowed SCMs

23656542 build (f27-container-candidate, /forks/jarrpa/container/glusterfs.git:bc698113adb8013df859a8c446b8547a5042fbdd) failed

Is there any way to do scratch builds from forked repos? Otherwise, is there any way to create private/wip branched on the main repo that I can freely delete or do non-ff pushes to? I just want a repo I can use to do scratch builds using koji for development testing.

Thanks!


AFAIK, no builds are allowed from forks, pinging @puiterwijk for more info. And you can use fedrepo-req tool to request a new branch under container namespace.

@mohanboddu Yeah, just verified that forks are explicitly denied from koji builds. Can I use that same tool to request a deletion of a branch?

@jarrpa You cannot request deletion of a branch as we have no way to track what build came from what branch, assuming a build is submitted from an arbitrary branch.

@mohanboddu I have had no builds coming from this branch I have, I accidentally pushed it not knowing what the repo policy was. If there have been no builds and will never be any builds, can't it be removed?

@jarrpa Sorry, its not possible. I dont know if there is anyway to overrule the current policy.

Wait, I'm not following this here. Builds can't be made from branches and branches can't be deleted because we can't track what builds are submitted from them? Those problems can't both exist at once, can they?

@mattdm Builds can be submitted from arbitrary branches but not from forks. And your second statement is right.

@mohanboddu It's just git, there has to be a way... can we destroy the repo and recreate it? I really don't want this accidental artifact to linger around forever.

@jarrpa I understand but destroying the repo and recreating it means lot of work, but whats stopping you from submitting scratch builds from release branches? Its just a scratch build, right?

On Mon, Dec 18, 2017 at 02:44:28PM +0000, Mohan Boddu wrote:

@jarrpa I understand but destroying the repo and recreating it means lot of work, but whats stopping you from submitting scratch builds from release branches? Its just a scratch build, right?

Re-creating the repo is also not an option. Unfortunately we do not have
a tool to make sure that removing a branch will not leave a commit
unreferenced that was used for a koji build. Therefore it would only be
easily possible to remove branches that were merged into other branches
that are kept.

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

5 years ago

Login to comment on this ticket.

Metadata