New jenkins job needed for fuel-library unit tests
Bug #1396510 reported by
Aleksandr Didenko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Igor Belikov |
Bug Description
As a part of https:/
While we're testing and improving it, it should not put +1/-1 in the gerrit reviews, if it's possible.
Could you please create it and provide me with the access to configure this job?
Changed in fuel: | |
importance: | Undecided → Medium |
Changed in fuel: | |
importance: | Medium → High |
Changed in fuel: | |
status: | Incomplete → In Progress |
Changed in fuel: | |
assignee: | Fuel DevOps (fuel-devops) → Igor Belikov (ibelikov) |
tags: | added: jenkins |
Changed in fuel: | |
milestone: | none → 6.1 |
importance: | Critical → High |
Changed in fuel: | |
assignee: | Fuel DevOps (fuel-devops) → Igor Belikov (ibelikov) |
Changed in fuel: | |
status: | Fix Committed → Won't Fix |
status: | Won't Fix → Fix Released |
tags: | added: system-test-not-required |
To post a comment you must log in.
Access to Fuel Jenkins is limited and we shouldn't use it for tests and temporary configurations. We can create Jenkins job at internal Jenkins for you to play with, but I don't see the purpose of it.
To create Jenkins job we need:
1) requirements - which packages should be installed on the server to run the script,
2) bash script - what we need to run from the checked out fuel-library code.
Both items can be initially tested without Jenkins or Gerrit Trigger involved. Internally Jenkins just produces the source code which you need to test, nothing more.
Once requirements are clear and script is tested, we update our puppet manifest for Jenkins slaves and update our slaves to fit the requirements. After that we can create Jenkins job via Jenkins Job Builder.