workin on it.
On 03.03.2015, at 16:57, Levente Uzonyi leves@elte.hu wrote:
We've had this issue before. Everything is there, but not where jenkins is looking for:
/var/lib/jenkins/.rvm/src/ruby-1.9.3-p194/bin/gem /var/lib/jenkins/.rvm/src/ruby-1.9.3-p392/bin/gem /var/lib/jenkins/.rvm/src/ruby-2.0.0-p0/bin/gem /var/lib/jenkins/.rvm/src/rubygems-1.8.25/bin/gem
Levente
On Tue, 3 Mar 2015, Frank Shearar wrote:
On 3 March 2015 at 14:43, Frank Shearar frank.shearar@gmail.com wrote:
On 3 March 2015 at 14:38, Levente Uzonyi leves@elte.hu wrote:
On Tue, 3 Mar 2015, Frank Shearar wrote:
Yep, this is the problem that I was trying to resolve the other week with Eliot. I don't think it's a Cog bug, I think it's a bug in our security settings or something.
I had a look, things looked OK, but this is well beyond my rememberings of Linux security, hence why it's still broken.
Changes of the files in limits.d are only applied to new sessions. The squeak.conf file was created after jenkins was started. So restarting jenkins should fix the problem.
Oh, because Jenkins spins up the VMs, so the Cog processes inherit the permissions that Jenkins had? I'll reboot Jenkins then!
Rebooted, and now I see failures like "bundle gem not installed". So I added a new build step to install that gem, but it seems that the gem package isn't installed on that box? I don't have my credentials with me so I can't look into the problem. I may only be able to dig into the problem a few days from now.
frank
frank
Levente
frank
On 2 March 2015 at 17:37, Levente Uzonyi leves@elte.hu wrote: