On Wed, Feb 12, 2014 at 3:31 PM, Tom Catyb <[email protected]> wrote:
> We are attempting to run Jenkins on Server 1, jMeter on Server 2, Git on
> Server 3, and not having a great week.
> I need to get the results of jMeter testing to be available when I run them.
>
> What I have is as follows for job Setup:
>
> Job Add users:
>
> Source Code Repository setup with Git to get production scripts from Git
> Master Server:
>
> Execution of SSH Command line to jMeter (which works, I have verified) with
> output to the local jMeter Server (which is there)
If you are going to build on one box and test from another, I'd
probably make it two jobs so they can run on separate slaves, and
trigger the test job in the post-build of the first job.
> I use performance reporting tool, to examine the jtl file and it is the last
> iteration of the job.
Do you mean the performance plugin?
> Now, currently, this is in a folder (not for long) where Git is keeping
> track of it for testing purposes, so I know that it is on the git master.
> When I try to move the file to a different location, of course it cannot be
> found because it is out of the workspace.
> And if I try to point the jtl file to $workspace/anything it fails because
> the jmeter server gets lost at that point.
Not sure what you mean here. If the test is its own job, it can get
its own copy from git into the workspace where the plugin will find it
by the path/pattern you configure. The down side of the separate
job is that the status/reports end up there although you get a link on
the upstream job page.
> Anybody done this before, or I am relegated to merging my Jenkins and jMeter
> Servers.
> BTW, I tried making jMeter server a remote node, and it never worked
> (previous posts).
Well, that part should be solvable - slave nodes aren't hard to configure.
--
Les Mikesell
[email protected]
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
