Need to change the trigger logic for periodic Tempest-based CI jobs
Bug #1487383 reported by
Timur Nurlygayanov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Dmitry Kaigarodеsev |
Bug Description
We need to run Tempest jobs for the same ISO which was selected be the latest SWARM job
because now we are looking for some BVT jobs results and sometime one Tempest job started on one iso and another Tempest job started on another iso
More details:
Aleksandra Fedorova 12:12 PM #1 can be solved by triggering periodic job shortly after the swarm is triggered and fetching data from 7.0.swarm.timer artifact http://
Changed in fuel: | |
importance: | Undecided → High |
assignee: | nobody → MOS Infra (mos-infra) |
milestone: | none → 7.0 |
status: | New → Confirmed |
tags: | added: jenkins non-release |
Changed in fuel: | |
assignee: | MOS Infra (mos-infra) → Fuel CI team (fuel-ci) |
Changed in fuel: | |
assignee: | Fuel CI team (fuel-ci) → Dmitry Kaigarodеsev (dkaiharodsev) |
tags: | added: fuel-ci |
To post a comment you must log in.
Fix proposed to branch: master /review. fuel-infra. org/10838
Change author: Alexander Evseev <email address hidden>
Review: https:/