Create new jenkins job for performance tests

Bug #1394225 reported by Kamil Sambor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Igor Belikov

Bug Description

Tests are a part of fuel-web and they are in nailgun/test/performance. They are normally skipped because you have to set PERFORMANCE_PROFILING_TESTS on 1 in nailgun settings.yaml to run them. For a now there isn't option in run_tests.sh so they should be run using nosetests/pytests directly on path: /test/performance .
Tests should be run in the same enviroment as verify-fuel-web tests in single thread because we measure performance here.
Also this test writes some artifacts so it will be nice to be able to download them from jenkins (for now they are written in tmp/nailgun_performance_tests/results/ but this can also be modified in settings.yaml). There are no standard format xml-file which can be marked as resut on jenkins.
Fails notifications should be sent to fuel-core-team and the tests are quite critical because fails means that nailgun can stop working for 100 nodes.

Tags: devops jenkins
Changed in fuel:
status: New → Confirmed
Igor Shishkin (teran)
tags: added: devops jenkins
Igor Belikov (ibelikov)
Changed in fuel:
assignee: Fuel DevOps (fuel-devops) → Igor Belikov (ibelikov)
Igor Belikov (ibelikov)
Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Igor Belikov (ibelikov) wrote :

Current implementation of job can be seen here https://fuel-jenkins.mirantis.com/view/wip/job/nailgun_performance_tests/
Please take a look and tell if any changes should be made.

Email notifications are disabled for now in testing purposes.

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Igor Belikov (ibelikov) wrote :

Job has been moved to the 'current' view and set to run twice a day, email notifications have been enabled.

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.