Load tests strategy (servers, pipeline, etc)

[Matias Burni]

Hi all,

I have several load tests and they are launched manually. I would like to automate this but I need some ideas about the how.

SCENARIO

• [optional] Update the version of the App: App-Server and App-Client (with command yum, as we have an internal yum server, yes we´re in Centos 6.5)
• * Optional as I could launch the tests X times on the same version with different configs
• [optional] Update the configuration
•  * Optional as I could launch the tests X times with different version but same config
• Load tests execution START
• Load tests execution STOP

NOTES:

• I won´t define ANY server (client, server or simulation) as Jenkins slave, to avoid impacting the performance
• I will define standard parameters for the scripts but provide the possibility of "launching build with parameters"
• I will send the logs to Logstash to generate my reports
• I will use bash scripts
• I will connect to the servers with SSH

So, what do you consider would be a good solution for the Jenkins implementation? Any Feedback?

• I consider using https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin 

Thanks in advance... :)

[Jorge Peña Cotarelo]

The idea of throwing the tests by SSH and capturing logs by some Logstash seems cool, I would not use the same machines as Jenkins slaves since they could affect performance, so all by ssh. I would also use an isolated data network and similar hardware to the production one, will give you more insight.

I would recommend using pipelines and stages especially if they are going to be long tests. With Jenkinsfile is surprisingly easy to make and will help you to visualize the stages.