|
|
Issue 0042 in split format
- Summary
- replace concurrent_check with fuego-specific board lock mechanism
; Owner: Tim
; Reporter: Daniel
; Status: open
; Priority: medium
|
; Summary: replace concurrent_check with fuego-specific board lock mechanism
; Owner: Tim
; Reporter: Daniel
; Status: open
; Priority: medium
|
|
|
= Description =
concurrent_check in functions.sh is a routine for preventing two fuego builds
from occurring simultaneously on the same board. However, Jenkins already
serializes the complete test for a board, so this routine is not really needed
to prevent Jenkins from starting another job on the board.
|
|
Also, this routine is specific to Jenkins, using a Jenkins CLI url to manage
the board status.
|
Also, this routine is specific to Jenkins, using a Jenkins CLI url to manage
the board status.
|
|
'ftc' needs a mechanism to avoid running a test while a Jenkins is job is
executing on a board, as well as when ftc is already running a test on a board.
|
'ftc' needs a mechanism to avoid running a test while a Jenkins is job is
executing on a board, as well as when ftc is already running a test on a board.
|
|
Basically, we need a more global board reservation system, to prevent clashes
when running tests on a board (either from Jenkins or from 'ftc').
|
Basically, we need a more global board reservation system, to prevent clashes
when running tests on a board (either from Jenkins or from 'ftc').
|
|
We might be able to use 'ftc reserve-board' for this (based on old
file-based locking done by 'ttc reserve'.
|
We might be able to use 'ftc reserve-board' for this (based on old
file-based locking done by 'ttc reserve'.
|
|
|
= Notes =
Put other free-form comments or notes here
|
- backlink
Fuego Issues List
|
; backlink: [[Fuego Issues List]]
|
|
|