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

Feat/storage based encryption key location 2 10.9 #40893

Draft
wants to merge 34 commits into
base: master
Choose a base branch
from

Conversation

DeepDiver1975
Copy link
Member

Description

Related Issue

  • Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

  • test environment:
  • test case 1:
  • test case 2:
  • ...

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Database schema changes (next release will require increase of minor version instead of patch)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests only (no source changes)

Checklist:

  • Code changes
  • Unit tests added
  • Acceptance tests added
  • Documentation ticket raised:
  • Changelog item, see TEMPLATE

JammingBen and others added 30 commits December 28, 2021 13:43
Fix getting the file owner for share recipients
Fix issue with wrong version authors being saved
@DeepDiver1975
Copy link
Member Author

it is honestly 💩 that it is impossible to run ci on pr targeting older versions .... that's beyond the purpose of a ci system .... 😠

@phil-davis
Copy link
Contributor

The CI "system" that existed for 10.9 no longer "exists". The drone secrets that were used then have been removed from the drone server and agents.
A similar thing happens if you try to run CI for an old oC10 from when we used Jenkins, or Travis, or... - in that case there is no Jenkins, Travis... server even online at all. So CI will have no chance to start.
The CI "scripts" that go with an old branch always depend on having a similar execution environment available for those "scripts".
If it is needed, then we can apply updated CI scripts and tools to an older branch and get it going.

@DeepDiver1975 DeepDiver1975 force-pushed the feat/storage-based-encryption-key-location-2-10.9 branch from 765e49e to c2e062f Compare August 2, 2023 08:06
@DeepDiver1975 DeepDiver1975 force-pushed the feat/storage-based-encryption-key-location-2-10.9 branch 2 times, most recently from ed3b757 to 3398ae0 Compare August 4, 2023 08:17
@DeepDiver1975 DeepDiver1975 force-pushed the feat/storage-based-encryption-key-location-2-10.9 branch from 0e58c58 to f9b76f6 Compare August 4, 2023 08:24
@IljaN IljaN changed the base branch from 10.9.x to master November 15, 2023 14:42
Additionally this also passes the original restore location
of the inaccessible path before it is rewritten to the path
in home.
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.

6 participants