Hey,
I’m Adrian and I have an issue
i have a very big jenkins instance
somewhere like 1500 jobs
18 slaves
ok
and i have an old version
after i upgrade to version newer then 1.481 from stable i have a lot of
problem
problems with loadinf view
views...like ALL or other view
Hello!
We have recently created a plugin for Jenkins that allows Jenkins users to
run automated load tests as part of their test suites. We would like to
host this plugin at jenkins-ci.org.
Github: https://github.com/loadimpact/loadimpact-jenkins-plugin
My Github ID is ragnarlonn
Thanks!
I had made a PoC of line numbers plugin a-la-travis some time ago, I just
pushed it on GitHub.
https://wiki.jenkins-ci.org/display/JENKINS/Line+Numbers+Plugin
Vincent
2014-06-02 12:49 GMT+02:00 Tom Fennelly tom.fenne...@gmail.com:
On 30/05/2014 22:38, Surya Gaddipati wrote:
I'd love to
I'm wondering how classes and resources of the acceptance tests should be
stored. Currently we have four different categories of files:
a) framework and adapter classes, these are located in the src folders
b) test cases and resources, these are located in the test folders
c) plug-in specific
This depends on how the project classes will be reused by other
testsuites. I believe it makes sense to reuse page objects for both core
and plugins. So framework and POs + necessary resources should be in src.
I am not sure it makes sense to reuse docker containers we use for
testing,
Let me attempt to prove you wrong,
We are running a slight fork of Jenkins where we have removed the queue widget
and the ajax call from the buildhistory so it doesn’t list queued builds on job
pages. When we did that the UI responsiveness got improved a lot, I don’t know
exactly how many
Hi folks,
I discovered lately an interesting framework, Fluentlenium, for integration
testing. As I'm building Selenium tests for a Jenkins plugin and I'm
considering to use it, because I believe it will be easier to work with
FluentLium over Selenium.
I would find interest in using this in
This seems to supplement capybara we ware using back in selenium tests.
Unfortunately, we have already reimplemented a lot of its features (see
CapybaraPortingLayer, Controll). I don't feel strongly about its inclusion.
--
oliver
--
You received this message because you are subscribed to
Are we talking abut the same thing though? If I read your email
correctly I think you're talking about the current mechanism of periodic
polling requests (coming form 100s of users), right? What the guys were
talking about was something different i.e. SSE, where the 100s of
clients open long
I am mainly commenting on how it behaves today.
I'm not familiar enough with SSE to be able to predict how It would behave
server side if it was implemented, last time I used SSE it was brand new
and we used a specialized app server designed to handle thousands of users,
so I don't know how
On Thu, May 29, 2014 at 3:37 AM, Tom Fennelly tom.fenne...@gmail.com wrote:
These only work however if the API is truly restful. I'm
fairly sure they would not work with the Jenkins API.
What specifically about the Jenkins remote API do you find RESTless?
--
You received this message because
On Fri, May 30, 2014 at 5:08 PM, Stefan Wolf glowwo...@gmail.com wrote:
If I allow ssh to the slave then I do not need the agent - it will be copied
from the master. The tools can mostly also be auto-installed, so that
shouldn't be an issue either...
Exactly. And evarga/jenkins-slave works
On Mon, Jun 2, 2014 at 11:36 AM, oliver gondža ogon...@gmail.com wrote:
I am not sure it makes sense to reuse docker containers we use for testing
I think they need to be in src/main/ for the harness to be usable by
acceptance tests for Jenkins-derived products. (At least CloudBees has
some.)
I would expect Kohsuke to cover it extensively in the CloudBees talk as
well.
On Wednesday, May 14, 2014 9:18:48 AM UTC-7, Jesse Glick wrote:
On Wed, May 14, 2014 at 5:17 AM, James Nord (jnord) jn...@cisco.com
javascript: wrote:
According to the agendas this looks like it is only the
Totally understandable, I don't feel up to the job to follow it up to the
reason it fails within Eclipse.
However, I wonder if it would be a solution to simply extract the relevant
inner classes of Queue into the hudson.model.queue package as Standalone
Classes? I don't quite see why
15 matches
Mail list logo
