Learn more about these different git repos.
Other Git URLs
It would be nice to be able to create image builds in koji that are throw away builds that are purely used for testing of changes to kickstart files etc.. The idea is that we would use these as a way to test our changes before officially commiting them to the spin-kickstarts repo.
Having this ability would mean it is much easier for contributors to test changes and thus more likely to submit fixes and or suggestions back. We can currently do an image build on our own machines but it does take some setup and it is not the same environment as the one in koji. So, while we can test on our own machines, is it a valid test? Not really.
I would love this functionality. I know it might not technically be possible right now to do, but we shouldn't ignore its value and should perhaps take steps to get there.
There is nothing stopping you from testing today. you would need to run imagefactory, livecd-creator or appliance-creator locally
Replying to [comment:3 ausil]:
Right. I made some points in the original description about why this is not the most desirable solution. We should make it easier on contributors to help "fix" things when they are broken by giving them a way to validate their changes in the environment that matches the production image creations. Doing so should minimize the number of mistakes we make and the amount of time we have to wait before something is fixed.
To be clear I am not asking for this functionality today as you have told me that it doesn't exist. I am asking for this as a future feature. I would expect that any steps we could take to have people outside of releng help contribute would be welcome. You guys are loaded with enough work as it is.
Dennis,
I'm genuinely confused about the underlying issue here. Internally at RH, and in the CBS, it's possible to run scratch image builds more or less at will, provided you have image building permissions (which are granted only to a subset of users, based on their need to test/validate image building).
Why can this not happen in the Fedora koji instance?
Replying to [comment:5 imcleod]:
Dennis, I'm genuinely confused about the underlying issue here. Internally at RH, and in the CBS, it's possible to run scratch image builds more or less at will, provided you have image building permissions (which are granted only to a subset of users, based on their need to test/validate image building). Why can this not happen in the Fedora koji instance?
Every image build done in koji gets uploaded to EC2.
Replying to [comment:6 ausil]:
So that is an issue we should tackle separately? I don't think it should be a requirement that each image gets uploaded to EC2. Or I at least think it should be easily disabled.
Should there be a separate ticket for this item?
Are there any other blockers for this ticket?
Replying to [comment:7 dustymabe]:
Replying to [comment:6 ausil]: Every image build done in koji gets uploaded to EC2. So that is an issue we should tackle separately? I don't think it should be a requirement that each image gets uploaded to EC2. Or I at least think it should be easily disabled.
It should not be a requirement, but it is th reality today, there is no way to turn fedimg off for some images and not for others.
Should there be a separate ticket for this item? It will need a issue filed for fedimg Are there any other blockers for this ticket? Until fedimg is changed we can not make any progress on this
Should there be a separate ticket for this item? It will need a issue filed for fedimg
Are there any other blockers for this ticket? Until fedimg is changed we can not make any progress on this
FYI, there is an upstream tracking ticket in the fedimg repo for removing scratch-build based uploading: https://github.com/fedora-infra/fedimg/issues/48
Commenting so I can track this. My use case needs a build service or we need to beef up docs around doing it locally. If someone can help me by pointing me in the right direction, I can start trying to work on the docs as I have time.
Replying to [comment:10 bex]:
it is documented in teh cloud kickstarts https://pagure.io/fedora-kickstarts/blob/master/f/fedora-cloud-base.ks right at the top
The blocking issue is now closed: https://github.com/fedora-infra/fedimg/issues/48#issuecomment-246455122
Can we open this up for discussion again?
Metadata Update from @dustymabe: - Issue set to the milestone: Fedora 23 Final
Metadata Update from @ausil: - Issue close_status updated to: None - Issue set to the milestone: Fedora 26 Final (was: Fedora 23 Final) - Issue tagged with: meeting
$ koji grant-permission image dustymabe
releng has decided to only allow people actively involved in the Cloud/Atomic WG to have image build permissions. @dustymabe you can now do scratch image builds.
Metadata Update from @ausil: - Issue untagged with: meeting - Issue assigned to ausil - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
It's like christmas in june!
Login to comment on this ticket.