Re: [foreman-dev] Changes to PR tests on Foreman repo
On 03/09/16 14:02, Dominic Cleal wrote: > I've changed the PR test jobs in Jenkins for the main Foreman repo > (theforeman/foreman) to try and improve performance. You'll see that PRs > now receive "foreman", "upgrade" and "katello" test statuses, replacing > "default". > > The old [test] phrase changes to the following commands: > > 1. "[test foreman]" or "[test upgrade]" to re-test a PR that has failed > tests (as always, use this sparingly please) > 2. "ok to test" to run tests for an unknown user, if the patch is not > malicious (the plugin will unfortunately add three comments to ask, one > per test) > 3. "add to PR whitelist" to always run tests from a trusted user > > If you forget, they're on the wiki at > http://projects.theforeman.org/projects/foreman/wiki/Jenkins#Quick-reference-for-maintainers. > > Aside from these cosmetic changes, the tests should work identically to > before. Two further points: 1. PR tests will no longer be suspended when test_develop is failing, so please expect to rebase or re-test PRs after an issue is fixed on develop instead of relying on it to automatically clear. I don't think this original behaviour is possible with the plugin. 2. Commenting on an existing PR that was tested on the old system for the first time will cause the new PR tests to run too, so expect to see a few more builds over the next few days. You'll see both new and old statuses reported on a PR commit if this happens, simply ignore the old one, it's nothing to worry about. -- Dominic Cleal domi...@cleal.org -- 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.
Re: [foreman-dev] Re: error calling hammer.run() from w/in 'hammer csv subscriptions'
Recently there were some changes in how the translation domains are handled in hammer with new fast_gettext. See the PR [1] for more details. There was hammer 0.8.0 gem released last week containing the changes. What hammer version anf fast_gettext do you use? I checked the hammer-cli-csv PR and I'm not sure why are you adding the domain manualy for the second time and not only with HammerCLI::I18n.add_domain but it was not necessary for hammer-cli-foreman. [1] https://github.com/theforeman/hammer-cli/commit/ 6e28b70ff1a05344b0af7abd5a2f660d74ba6df7 On Fri, Sep 2, 2016 at 9:44 PM, Tom McKay wrote: > Opened a PR that works but I'd like to understand the problem and what > changed, if anyone has any insights. > https://github.com/Katello/hammer-cli-csv/pull/121 > > On Fri, Sep 2, 2016 at 1:14 PM, Tom McKay wrote: > >> I get an error "RuntimeError (Current textdomain (nil) was not added, use >> FastGettext.add_text_domain !" during a call to hammer.run() from w/in >> another hammer command. Effectively 'hammer csv subscriptions' is calling >> 'hammer subscription upload' from w/in itself. If I add this code[1] prior >> to calling hammer.run() then things work as expected (and as it had >> previously). >> >> What is the proper way to config FastGettext in hammer module? >> >> >> [1] https://github.com/thomasmckay/hammer-cli-csv/blob/ >> fastgettext/lib/hammer_cli_csv/subscriptions.rb#L62-L68 >> > > -- > 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. > -- 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.
Re: [foreman-dev] Changes to PR tests on Foreman repo
> script. It has a few advantages, such as running the jobs separately to > reduce the number of slave slots used, and aborting running jobs when a > PR is updated. I hope it will improve the general throughput of PR Thanks! -- 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.
[foreman-dev] CfP entry for CfgMgmt camp in Berlin
I just submitted for the record: Abstract: First, it starts with a DVD with an OS installer, then is a recipe to automate it. And then PXE booting from network which sometimes lead to discovering new bare-metal nodes. Some shops fully automate provisioning and the only action is to power on a server. We all have that. But what's next? Make it fast. Blazing fast. Do it virtualization-like or cloud-like experience with Foreman Discovery and the new image-deployment capabilities. Additional info: Bare-metal remains relevant with upcoming farms of ARM servers. We need to be ready to deploy dozens of bare-metal servers at once. I will show story of provisioning in a typical Foreman shop and then make a demo of bare-metal servers deploying OS using multicast image transfer. The image-deployment scenario is a working in progress (prototype that works), I would like to hear feedback on that and also collect ideas. Links: https://theforeman.org/ https://theforeman.org/plugins/foreman_discovery/6.0/index.html https://github.com/theforeman/foreman-discovery-image/pull/44 40 Min talk and discussion -- 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.
Re: [foreman-dev] Changes to PR tests on Foreman repo
It looks like something weird is going on with the katello PR job. It used to have four individual jobs: http://ci.theforeman.org/job/test_katello_pull_request/10010/ Now it looks like it’s only running the core unit tests: http://ci.theforeman.org/job/test_katello_pull_request/10011/ David On Mon, Sep 5, 2016 at 4:32 AM, Lukas Zapletal wrote: > > script. It has a few advantages, such as running the jobs separately to > > reduce the number of slave slots used, and aborting running jobs when a > > PR is updated. I hope it will improve the general throughput of PR > > Thanks! > > -- > 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. > -- 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.
Re: [foreman-dev] Changes to PR tests on Foreman repo
On Mon, Sep 5, 2016 at 12:21 PM, David Davis wrote: > It looks like something weird is going on with the katello PR job. It used > to have four individual jobs: > > http://ci.theforeman.org/job/test_katello_pull_request/10010/ > > Now it looks like it’s only running the core unit tests: > > http://ci.theforeman.org/job/test_katello_pull_request/10011/ > Has nothing to do with Dominic's changes -- see https://groups.google.com/forum/#!topic/foreman-dev/F2hcVO-utAE > > > > David > > On Mon, Sep 5, 2016 at 4:32 AM, Lukas Zapletal wrote: > >> > script. It has a few advantages, such as running the jobs separately to >> > reduce the number of slave slots used, and aborting running jobs when a >> > PR is updated. I hope it will improve the general throughput of PR >> >> Thanks! >> >> -- >> 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. >> > > -- > 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. > -- Eric D. Helms Red Hat Engineering Ph.D. Student - North Carolina State University -- 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.
Re: [foreman-dev] Expanding Slave Capacity
Am 31.08.16 um 10:09 schrieb Dominic Cleal: Thanks for the offer, I'd gladly take you up on it. Similar specs to the current one would be great, but more disk space if possible - the usage is increasing. http://projects.theforeman.org/projects/foreman/wiki/Jenkins#Slave-requirements lists current specs. A regular EL7 installation with my SSH key (https://m0dlx.com/ssh_redhat.pub) installed for root would be enough for me to set it up. I've setup another slave. Hope, it helps a little. tfmslave01.timogoebel.net You should be able to login with root and your ssh key. I've already run the steps listed on [1]. The system is currently waiting for a puppet certificate. Dominic, do you cover the rest? Timo [1] http://projects.theforeman.org/projects/foreman/wiki/Jenkins#Slave-requirements -- 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.
