Run tests on another machine

[Erick Macedo]

Hii,

I have a build running on jenkins and I'm using maven.

I wonder how I could run my screen test on a different machine that is the jenkins, the bamboo that is setting up a possible agent.

I need this configuration because the machine that is the jenkins is a CentOS without graphics, and my screen tests need to be on a windows machine with a browser.

Could someone help me or have some material for this?

thank 

[Mark Waite]

With Jenkins it is easiest to add a slave on the target platform, then restrict the job to that slave. For greater flexibility, you can assign a label to the slave and restrict the job by label. For even more flexibility, there are plugins that will automatically assign labels by platform or by installed tool.

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3a3f37aa-920f-4c48-b1e3-2e1e296c6b65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Fred G]

There is more information in the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds

In order to run screen tests, Jenkins or a Jenkins slave needs access to the GUI. The easiest way (that I know of) is to start the Jenkins slave as a JNLP agent.

[Simon Richter]

Hi,

Am 28.04.2015 um 15:54 schrieb Fred G:

> In order to run screen tests, Jenkins or a Jenkins slave needs access to
> the GUI. The easiest way (that I know of) is to start the Jenkins slave as
> a JNLP agent.

It is also possible to install it as a service, however you have to go
into the service configuration and explicitly enable GUI access.

Simon

[Erick Macedo]

First, thank you for personal help.

I'm trying to configure it with the plugin "Send files or execute commands over SSH"

In Exec command, I am entering something like:

cd test / project-1 && mvn install

But this error happens on linux

SSH: Connecting from host [web.buy]

SSH: Connecting with configuration [Test Server] ...

SSH: EXEC: STDOUT / STDERR from command [cd test / project-1 && mvn clean install] ...

bash: --command = mvn clean install: command not found

My Maven is configured correctly.

Could someone help me with this?

[Mark Waite]

Usually that would mean that the PATH on your Windows machine does not include the maven bin directory.

--

You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d2f173cf-43d7-40cd-a16e-d19a6c8c9dd6%40googlegroups.com.

[Erick Macedo]

Mark, this test I am running on another linux machine, but when work will move to a Windowns.

Maven is configured correctly, if I go in and finish typing mvn -va version is displayed correctly.

On the tips of staff

I understand that, to have a Slaves I would have to have another server installed jenkins, right? To work with Jenkins (Master and Slave)

And in my case I just wanted to run the test on another server and get the return

Em terça-feira, 28 de abril de 2015 08:37:30 UTC-3, Erick Macedo escreveu:

[Simon Richter]

Hi,

Am 28.04.2015 um 16:30 schrieb Mark Waite:

> Usually that would mean that the PATH on your Windows machine does not
> include the maven bin directory.

There is a bit of a problem right now with the master overwriting the
environment of slaves with an old snapshot of the environment variables.
In case Maven was installed after the slave connected to the master for
the first time, this might be the problem (and deleting the node in the
master and recreating it fixes it).

Simon

[Erick Macedo]

Hi , again thanks for the help.

When you talk master and slave, the Master is a server installed Jenkins and the Slave any other server (even without the installed jenkins)?

More to the point, Maven has been configured on another server before the connection then I do not believe that this is the problem, perhaps a limitation of the plugin?

thank you

Em terça-feira, 28 de abril de 2015 08:37:30 UTC-3, Erick Macedo escreveu: