Assuming the DNS still points to the restored koji, you need to do this: 34.226.218.207 koji.katello.org kojihub.katello.org
I kicked off scratch builds of all our packages into nightly, looks good so far. It is not yet finished but processing at very good rate of about several tasks per minute (five concurrent builds at one time) and it's all green so far: The first task is http://34.226.218.207/koji/taskinfo?taskID=3637 The last task is http://34.226.218.207/koji/taskinfo?taskID=4138 Current queue: http://34.226.218.207/koji/tasks (450 builds to go) I will report back when this is done. On Sun, Jun 11, 2017 at 10:22 PM, Bryan Kearney <bryan.kear...@gmail.com> wrote: > I am gonna take the optimistic route, and hope that this approach works. > 1.15 should be back up: > > foreman-1.15-fedora24 > foreman-plugins-1.15-fedora24 > foreman-1.15-nonscl-rhel7 > foreman-plugins-1.15-nonscl-rhel7 > foreman-1.15-rhel7 > foreman-plugins-1.15-rhel7 > > Please kick off some builds against these to let me know if there are > issues. Jenkins should be usable. > > -- bk > > > On 06/10/2017 03:11 PM, Bryan Kearney wrote: >> >> Update. >> >> Per Lzap's suggestion, I wrote down the rough approach at [1]. I believe >> that foreman-nightly should be ready to test on this machine. Specifically, >> building into these tags: >> >> foreman-nightly-fedora24 >> foreman-plugins-nightly-fedora24 >> foreman-nightly-nonscl-rhel7 >> foreman-plugins-nightly-nonscl-rhel7 >> foreman-nightly-rhel7 >> foreman-plugins-nightly-rhel7 >> >> There appear to be some issues with passenger which I will need some help >> form folks who know the build process a bit. What I think we need now: >> >> * Test out these targets with foreman nightly builds. Where there are >> failures, please respond with the tasks which have the logs that are >> failing. Jenkins should be set up to run builds. If not, some users are. >> * Lzap, is there an easy way to snapshot where the machine is at right >> now? >> >> -- bk >> >> >> [1] >> https://docs.google.com/document/d/1909hoztG37oWHyzdSWA4U4M9E8ocrk4qy6a57j3P1FE/edit >> >> On 06/10/2017 11:25 AM, Lukas Zapletal wrote: >>> >>> I was trying to rebuild 1.14 in old koji but it did not work well. I >>> am running into several issues. >>> >>> Some packages fails to complete build with: GenericError: Unable to >>> complete build: release mismatch (build: 1.fm1_14.fc24, rpm: >>> 1.fm1_12.fc24) like >>> >>> http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/taskinfo?taskID=522606 >>> - I don't understand, I upload it with fm1_14 tag but it gets rebuild >>> with fm1_12 and I have no idea where this macro is defined in the >>> buildroot, I don't see "tfm" package in there. The last "foreman" >>> package is 1.12, not sure if that matters. >>> >>> Then when a package gets built, koji fails it to import because there >>> is already existing file on FS: >>> >>> http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/taskinfo?taskID=522616 >>> and I have no idea if that means the package is not added to the >>> target or it is. Looks like it is ignored. >>> >>> Also running into other build issues but these are mainly because of >>> dependencies. >>> >>> I think that there's no recovery possible from here. One possible use >>> case for the old koji wold be to bump all package release numbers and >>> do mass rebuild into nightly so we can get nightlies running. But I >>> think it can't be used for 1.14 and 1.15 releasing anymore, unless >>> someone wants to try to fix it. >>> >>> Now to your newkoji, yes repogen will be always slow even on SSD big >>> fat box, but it's much better than what we had on the old koji. Now >>> the trick for massrebuilds is to turn off kojira and trigger >>> repocreate manually after several packages or when necessary. >>> >>> The package you link does provide it see down: npm(babel-core) = 6.7.7 >>> so it's the correct dependency. So you are good. >>> >>> >>> >>> On Sat, Jun 10, 2017 at 5:16 PM, Bryan Kearney <bryan.kear...@gmail.com> >>> wrote: >>>> >>>> ok.. I have builds running >>>> >>>> http://34.226.218.207/koji/taskinfo?taskID=749 >>>> >>>> but what i dont get is the build requires. The foreman spec file for >>>> this >>>> requires npm-babel-core but the package I have >>>> >>>> http://34.226.218.207/koji/buildinfo?buildID=15280 >>>> >>>> provides bundled-npm-babel-core >>>> >>>> so something seems off >>>> >>>> Aslo merge repos are wicked slow. Lzap, youmentioned setting up dmache? >>>> >>>> -- bk >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups >>>> "foreman-dev" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an >>>> email to foreman-dev+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> >> > -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
