[foreman-dev] Jenkins slaves not responding

2016-08-16 Thread Dominic Cleal
There are a few Jenkins slaves I've seen this morning that have stopped
responding during jobs, causing IOExceptions and remote channel failure
messages.

I've taken a few of them offline so these should stop occurring. Jenkins
capacity will be much reduced until I can figure out why the hosts are
freezing.

-- 
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] Webpack merged into develop branch

2016-08-16 Thread Tomer Brisker
Hi
Quick update - https://github.com/theforeman/foreman/pull/3722 has been
merged, which allows easy disabling of the webpack development server, in
case you aren't working on the front-end.
If disabled, you can continue running foreman as usual (e.g. `rails s`).
Note that if you disable the dev server, you will need to run `rake
webpack:compile` to generate the js bundle needed for Foreman to run
correctly.

On Fri, Aug 12, 2016 at 1:01 PM, Tomas Strachota 
wrote:

> On 08/12/2016 11:25 AM, Daniel Lobato Garcia wrote:
>
>> On 08/12, Tomas Strachota wrote:
>>
>>> On 08/10/2016 02:01 PM, Tomer Brisker wrote:
>>>
 Please note that running this way will limit the ability to use pry for
 debugging, as foreman prevents stdin echo. To use with pry, you can run
 both servers separately in different terminals - run rails as usual in
 one, and run `./node_modules/.bin/webpack-dev-server --config
 config/webpack.config.js` in the other.

>>>
>>> I noticed that when I run rails in development env, the webpack's
>>> hostname
>>> in assets is set to localhost. So of course it doesn't work when you're
>>> developing on a different host. Can this be tuned right away in some
>>> config
>>> or does it need additional patches to switch the hostname?
>>>
>>
>> I think this should cover that? It was merged just yesterday
>>
>> https://github.com/theforeman/foreman/commit/42ba771cc8bfc09
>> 257c15c5d388542d4d1b69358
>>
>>
> Nice, thanks!
>
>
> --
>> Daniel Lobato Garcia
>>
>> @dLobatog
>> blog.daniellobato.me
>> daniellobato.me
>>
>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
>> Keybase: https://keybase.io/elobato
>>
>>
> --
> 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.
>



-- 
Have a nice day,
Tomer Brisker
Red Hat Engineering

-- 
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] qpid-cpp-client-devel required on slaves?

2016-08-16 Thread Dominic Cleal
On 15/08/16 17:34, Justin Sherrill wrote:
> On 08/12/2016 07:48 AM, Dominic Cleal wrote:
>> On 12/08/16 12:28, Eric D Helms wrote:
>>> Should be good to remove.
>> Thanks, I've removed the Yum repo and the package will be left wherever
>> it's currently installed.
>>
> I believe this is actually required as now seen by the new katello test
> failures:
> 
> *00:03:32.077* An error occurred while installing qpid_messaging (0.34.1), 
> and Bundler cannot
> *00:03:32.077* continue.
> *00:03:32.077* Make sure that `gem install qpid_messaging -v '0.34.1'` 
> succeeds before
> *00:03:32.077* bundling.
> *00:03:32.132* + exit 1
> 
> The EL6 source is now in the copr qpid repo 
> (https://copr.fedorainfracloud.org/coprs/g/qpid/qpid/)

Restored using that repo for EL6 and base OS for EL7.

-- 
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.