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
Usually that would mean that the PATH on your Windows machine does not
include the maven bin directory.
On Tue, Apr 28, 2015 at 7:25 AM Erick Macedo erickfmac...@gmail.com wrote:
First, thank you for personal help.
I'm trying to configure it with the plugin Send files or execute commands
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
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.
On Tuesday, April 28, 2015 at
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
Adam Retter adam.retter@... writes:
Hi Jan,
Thanks for your reply I have finally solved this, unfortunately it was
not as simple as I hoped (probably due to the fact our platform is on
Windows Server).
The point you raised below, gave me a good hint -
Run a simply svn command like
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
Adam Retter adam.retter@... writes:
Hi Jan,
Thanks for your reply I have finally solved this, unfortunately it was
not as simple as I hoped (probably due to the fact our platform is on
Windows Server).
The point you raised below, gave me a good hint -
Run a simply svn command like
For every nightly SW build, I want it to be tested on available testing
systems. I created Jenkins slaves for these system, and listen to the
completion of Jenkins build. I am trying to use Node label Parameter
plugin to trigger test on particular system, ideally Jenkins can find
whichever
I use the elastic axis plugin to define a multi configuration job which
runs a single job on all available slaves. The platform labeler plugin
makes platform selection easier with the elastic axis plugin.
Mark Waite
On Tue, Apr 28, 2015, 9:23 AM Victoria Wei Lei weile...@gmail.com wrote:
For
Nice, I will try it.
Thank you so much, Mark.
Victoria
On Tue, Apr 28, 2015 at 11:10 AM, Mark Waite mark.earl.wa...@gmail.com
wrote:
I use the elastic axis plugin to define a multi configuration job which
runs a single job on all available slaves. The platform labeler plugin
makes platform
I was trying the get the last successful build that was promoted (promotion
plugin) into a specific environment out of Jenkins, but not sure how.
Gain, not looking for Build Number, but for the build# that was promoted.
Ran into some success using the xml/api, but this quickly ended as it
I can not understand this behavior.
In Exec command: cd test / build-38 / project ls echo $ M2 mvn -v
This command does the following:
1 - cd test / build-38 / project (in this directory on the remote server)
2 - ls (list the remote server content)
3 - echo $ M2 (Prints $ M2 LOCAL server,
It works as the user that you are connecting as? Is there anything in the
.bashrc that would set the path to mvn? Perhaps the Publish Over SSH
doesn't run in such a way that the .bashrc file is loaded? Check into these
things.
On Tue, Apr 28, 2015 at 1:19 PM Erick Macedo erickfmac...@gmail.com
Hi Jennifer,
I'll test out the restarting master node in on Thursday and post the
results... but I feel that Simon and I are having the same issue here.
Thanks for the quick replies!
VJ
On Tuesday, April 28, 2015 at 2:56:23 AM UTC-7, Jennifer Hofmeister wrote:
Hi VJ,
Hi Simon,
Just to
Hi VJ,
Hi Simon,
Just to sum it up… whatever process runs as a service will only load new env
values when restarted. The JNLP and JNLP command line options are spawned from
the Jenkins master service, so you’ll want to restart that one after changing
your envs so it can pick up new values and
Hi,
I'm using the plugin Publish over SSH to run a remote command maven on a
linux machine with properly configured maven.
However when running mvn command is generated an error bash: mvn: command
not found.
The plugin is properly connecting the remote machine, as for testing in the
Exec
According to the Jenkins changelog http://jenkins-ci.org/changelog, Jenkins
1.611 has been out for a few days now.
However, my Jenkins is only offering me an upgrade to 1.610 (I'm currently on
1.609). Going to http://jenkins/pluginManager/advanced and hitting Check
Now makes no difference.
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.
Hi Jennifer,
Just to sum it up… whatever process runs as a service will only load
new env values when restarted.
That is expected behaviour, yes.
The JNLP and JNLP command line options are spawned from the Jenkins
master service, so you’ll want to restart that one after changing your
envs so
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
21 matches
Mail list logo
