-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build package by Dist-Git doesnt't store the dist-git source #3609
Comments
Mind that the problem actually resets the dist-git source to fedora so the fedora git and branch is used instead of the centos-stream git and branch, thus resulting in a rebuild that doesn't work at all, so I currently need to manually set this in the packages through editing the settings (or start by creating the package first) |
|
So the problem is that dist-git settings is not inherited from the initial build right? But when you configure the distgit option (package edit), then you are not able to re-set the dist-git configuration via additional build. Is that correct? |
yes and no :) I'll describe what I did: 1.st way: start a build from scratch, select dist-git, there enter package name, and enter centos-stream as source, c10s as the branch (commitish). Start the build, build picks up the right git repo as advertised and everything works ok.
The source of the problem is, the 1st step stored: dist-git option, branch and the repo it found out, but it didn't store the dist-git source, so it always defaults to fedora as the dist-git source. That can be manually corrected by editing the package options and change the source from fedora to centos-stream. Save the package options, do a rebuild from packages page, now everything works as expected. So the error is not, that it wouldn't work in general but that the easy way to start a build, enter all options, build works, but doesn't store the dist-git source correctly prevents the right rebuilding of the package due to the wrong dist-git source. I manually changed all my packages and to save the steps of correction in the meantime start packaging by creating a new package in the repo first and store all options and press save, then do a rebuild from there. Do you now understand the problem ? :) BR Loise Thanks for taking care of my issues :) |
Yes, I easily reproduced this here. The package info is correctly stored in Database, but the web-UI html form isn't appropriately pre-selecting the right DistGit instance for "rebuild" button. Thank you for the detailed info! This a frontend bug, if you want a work-around, you can do this in command-line: |
The problem is that we only store the clone URL address, not the whole dist-git instance info. And it is not trivial to deduct the DistGit option from git clone URL, well - at least not easy without the dist-git-client code (which is not designed for web-UI). |
When building a package by initially setting the build options (not stored as a package yet), the dist-git source can be selected (fedora, centos, centos-stream etc.) and the build proceeds.
Looking after the settings in the "Packages" section afterwards:
Default Build Source
Source Type:
Build from DistGit
Distgit:
centos-stream
Committish:
c10s
Clone_Url:
https://gitlab.com/redhat/centos-stream/rpms/rubygem-asciidoctor.git
The Distgit: section is not stored when initiated through a build and is therefore re-set to "fedora". I have to manually go into the packages option and set the distgit for the default build again.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: