[TRNSPRTPCE-663] Adapt TransportPCE CI to a better usage of lighty build Created: 09/May/22 Updated: 20/Sep/23 Resolved: 25/May/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Phosphorus |
| Type: | Story | Priority: | Medium |
| Reporter: | Gilles Thouenon | Assignee: | Gilles Thouenon |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 day | ||
| Original Estimate: | 0 minutes | ||
| Description |
|
Currently, lighty build integrates the TAPI functionality per default, because tapi functional tests are embeded inside functional tests of devices 2.2.1 (although logically they should not be specific to devices 221). And yet, in karaf, Tapi is managed as an optional feature. |