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

Manage codebase releases and testing #50

Closed
3 of 10 tasks
Davsarper opened this issue Jul 3, 2023 · 11 comments
Closed
3 of 10 tasks

Manage codebase releases and testing #50

Davsarper opened this issue Jul 3, 2023 · 11 comments
Assignees
Labels
Core DSH (ELA) Story Issue of issues, longer than a month

Comments

@Davsarper
Copy link
Contributor

Davsarper commented Jul 3, 2023

Goal Title

What will this work achieve?
Support for deployments of the Data Safe Haven at Turing and beyond

Description

  • Ensure that all aspects of code are working before tagging a release
  • Run manual deployment tests
  • Run penetration tests as needed

Manage codebase releases and testing and Codebase maintenance are closely related but the first one is specifically around fixes/testing of our current code before tagging a release while the second one is generic updates/bug-fixes that aren't tied to us being about to release something

Definition of Done

When will this be considered as succesfully completed?
Ongoing

Details

  • RACI
    • Accountable team or person: @jemrobinson
    • Responsible team or person: Data Safe Haven team
    • Informed and consulted people: TRESA team, Data Safe Haven community
  • Estimated effort in total FTE: 0.1 (approximately 2 weeks work, 3 times annually)

Resourcing

August

  • REG: 0.5

References

Task and issue breakdown

Breakdown in specific tasks of maximum a month duration, tasks and issues may be added as necessary
Issues may span across repositories when necessary

Checklist

  • This Story have been agreed with project members, it tackles prioritised work
    • If not: Label as ForPrioritisation so it discussed in the next monthly meeting, do not set a status
  • I have filled in the Team Accountable field
  • I have included this Story in the agreed upon Milestone, set status as Planned
    • If not: set status as Backlog, to be Planned via weekly meetings or async discussions
  • The work to be done is likely to span over a month
  • I have broken down the work in monthly issues and added them above
  • I have labeled this issue according to its main project: SATRE, TRESA, CORE DSH (ELA) or other (please agree and create a new label if necessary)
  • If known: sum the total effort (points) of tracked issues and add it on the body
  • Select a Story level of effort in the project fields

Report progress

5 February to 8 April 2024

Having completed development of v4.2.0 we prepared the release which included preparing a release branch and deployment in an environment for pen testing.

Extensive time was allocated to deploying and the errors/bugs that arose, as well as preparing for pen testing (this included deployment but also requesting specific tests like the removal of certain hardcoded IPs)

Pen testing was arranged and carried out, managing to spend within the 2023-2024 FY. iStorm kept better communications than last time and did not find concerning issues.

  • Results from the pen test only found issues we had previously seen and are happy to accept as being not of concern or have already mitigated

19 September to 9 October

  • Pen testing done: little found

14 August to 18 Septmber

  • Penetration tested arranged and will be done in September
  • Preparation for release v4.1.0: Deployment of different SRE variants, Security checklist
  • Reviewing v4.1.0: No significant problems is deployment logs, Problems found in security checklist relating to MSRDS

10 July to 14 August 2023

  • Working on Release 4.1.0: fixes bugs and introduces necessary updates
@Davsarper Davsarper added the Story Issue of issues, longer than a month label Jul 3, 2023
@Davsarper Davsarper added this to the End of current funding milestone Jul 3, 2023
@Davsarper
Copy link
Contributor Author

@jemrobinson what would be the headline of what 4.1 release delivers?

@jemrobinson
Copy link
Member

@Davsarper
Copy link
Contributor Author

Davsarper commented Sep 29, 2023

September was heavy with pen test and release, October may be quieter. we may or not do another release, not a priority

@Davsarper
Copy link
Contributor Author

Dec planning

Working on a series of issues associated the last release

@Davsarper
Copy link
Contributor Author

February action for @Davsarper , verify budget for another pen test and get in contact with iStorm

@JimMadge JimMadge added the Priority will be put before other work this month label Feb 26, 2024
@JimMadge
Copy link
Member

March focus:
Make v4.2.0 release
Run pen test on v4.2.0

@Davsarper
Copy link
Contributor Author

Needs to be a priority, work belongs to march but there will be follow up things. for exmaple:

  • announcement: do we want to be loud about a last powershell version?
  • No more support once the next release is out.

@Davsarper Davsarper removed the Priority will be put before other work this month label May 2, 2024
@Davsarper
Copy link
Contributor Author

Davsarper commented May 30, 2024

Patch release this month by @jemrobinson (please add issue). This is a fix for a guacamole problem needed for DSG

@Davsarper Davsarper added the Priority will be put before other work this month label May 30, 2024
@Davsarper
Copy link
Contributor Author

Similar to last month there is a bug that needs fixing and making an associated patch release, not made yet because focus on development but will happen.

Priority yes, not a lot of time spent on it.

We are in patch mode, doing what needs done but not focusing on new releases.

@Davsarper
Copy link
Contributor Author

Hoping to release 5.0.0 this month so this is a priority, work will happen late august after pen test tells us what to fix change

@Davsarper
Copy link
Contributor Author

No longer using this story to track this work, instead tracked within specific milestones/releases

@Davsarper Davsarper removed the Priority will be put before other work this month label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core DSH (ELA) Story Issue of issues, longer than a month
Projects
None yet
Development

No branches or pull requests

5 participants