As a developer I would like us to name our build directories (within \Kits$\CompGroup\ICP) consistently.
Currently most builds are in directories of the form of 'build-#', whilst client_E4 creates directories of the form 'build#' (i.e. without the dash). It would be good for this to be consistent and this would allow the simplification of the script to check stale builds as well.
Acceptance Criteria
[x] New builds int he client_E4 directory are cretaed in folders named in the fomat 'build-#'
[x] The check on stale builds is simplified to remove the hard coded exception and the logic also simplified to take advantage of this havingbeen removed.
[ ] any scripts in ibex_utils that get the latest build of cleint_E4 are updated to look for a directory witha dash in the name
Extra Information
How to Test
verbose instructions for reviewer to test changes
(Add before making a PR)
Time in planning 00:19 23/5/24
As a developer I would like us to name our build directories (within \Kits$\CompGroup\ICP) consistently.
Currently most builds are in directories of the form of 'build-#', whilst client_E4 creates directories of the form 'build#' (i.e. without the dash). It would be good for this to be consistent and this would allow the simplification of the script to check stale builds as well.
Acceptance Criteria
Extra Information
How to Test
verbose instructions for reviewer to test changes (Add before making a PR) Time in planning 00:19 23/5/24