Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins: improve consistency of naming of build directories #8329

Closed
3 tasks done
GRyall opened this issue May 8, 2024 · 0 comments · Fixed by ISISComputingGroup/ibex_utils#196 or ISISComputingGroup/ibex_gui#1722
Closed
3 tasks done
Assignees
Labels
3 Friday no_release_notes Tickets that do not need release notes, use sparingly! rework training

Comments

@GRyall
Copy link
Member

GRyall commented May 8, 2024

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

  • New builds int he client_E4 directory are cretaed in folders named in the fomat 'build-#'
  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 Friday no_release_notes Tickets that do not need release notes, use sparingly! rework training
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

5 participants