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

Merge Test Branch jcw/upgrade_to_18 into Feature Branch feature/upgrade_to_18_v2 for Integration Validation #28

Merged
merged 31 commits into from
Sep 30, 2024

Conversation

JaimieWi
Copy link
Contributor

Purpose

This pull request merges the changes from jcw/upgrade_to_18 into the feature/upgrade_to_18_v2 branch. The goal is to test the integration of the feature updates in a staging environment before merging into the main (production) branch.

By merging into the test branch (feature/upgrade_to_18_v2), we can:

  • Validate that the changes made in jcw/upgrade_to_18 are compatible with the current state of the production code (represented by the feature/upgrade_to_18_v2 branch).
  • Run all CI/CD pipeline tests and verify build stability before moving these updates into production.

Changes Included

The key changes from jcw/upgrade_to_18 include:

  1. Updates from the Azure TRE Deployment repo template
  2. [Updates to our user resource templates due to out of date images.
  3. Updates to our OUH VM images.

Process Overview

  1. Merge jcw/upgrade_to_18 into feature/upgrade_to_18_v2 to align the staging branch with the latest feature changes.
  2. Run automated tests and perform any manual integration testing as needed. This will include manual testing from the UI to ensure user resources can be deployed successfully. As well as running through the TRE v18 breaking changes.
  3. Once the tests pass and the merge is validated, feature/upgrade_to_18_v2 will be merged into main for production deployment.

Considerations

  • Ensure that no conflicts arise during the merge.
  • Monitor the CI/CD pipeline for any issues in testing or integration.
  • Perform a thorough review of the changes to ensure everything works as expected before final deployment.

Action Required

Please review the changes, monitor the CI/CD results, and ensure all tests pass. This is a crucial step before merging the tested changes into main and deploying them to production.

@JaimieWi JaimieWi merged commit c4e484c into feature/upgrade_to_18_v2 Sep 30, 2024
8 checks passed
@JaimieWi JaimieWi deleted the jcw/upgrade_to_18 branch September 30, 2024 08:26
JaimieWi added a commit that referenced this pull request Oct 1, 2024
…on (#27)

* new branch - updates

* upgrade pip to avoid dependency issues

* v0.17.0 to v0.17.1- see main repo for details

* see v0.17.2 updates

* v19 api_app req.txt

* see tag 17.4 - update vmss req.txt

* new test - open_telemetry dependancy

* fix to base workspace

* terraform lock update

* update hash terraform lock

* core terraform lock updates

* fix test

* update fix

* Merge Test Branch jcw/upgrade_to_18 into Feature Branch feature/upgrade_to_18_v2 for Integration Validation (#28)

* feature branch for merge TRE

* user resource updates and v18 updates

* lint fixes

* version fix

* update api and vmms req.txt

* fix to base workspace

* fix

* terraform lock update

* bring in ws updates

* manual update to guacamole

* upgrade our user resources

* update to linux locals - fix apt_sku issue

* small edit

* apt_sku fix

* fix

* test update to linux UI install

* test source linux build

* remove custom image and use default MS linux image

* Test message to users

* revert

* revert

* disable colord

* test image updates

* small fix

* test no screensaver

* remove libre office

* remove vscode reinstall

* fix

* revert porter to match main

* lint

---------

Co-authored-by: Jaimie Withers <jaimie.withers@bdi.ox.ac.uk>

* fix windows and porter versions

* update vscode

* updates

* fix

* testing

* revert

* test moving code setup

* fix

---------

Co-authored-by: Jaimie Withers <jaimie.withers@bdi.ox.ac.uk>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants