Release 4.0.0 #6838
Comments
|
@ScharfViktor Current master of the oCIS Helm Chart is on 3.1.0-beta.1 now. The only problem I'm aware of right now is owncloud/ocis-charts#365 |
E2E test local setupAll the tests passed 50scenarios (50 passed)
862 steps (862 passed)
15m47.925s (executing steps: 15m47.346s)
|
Compatibility test between
|
E2E test S3 setupsetup from https://github.com/owncloud/ocis/blob/master/deployments/examples/ocis_s3/docker-compose.yml All the tests passed 50scenarios (50 passed)
862 steps (862 passed)
14m10.905s (executing steps: 14m10.309s)
|
K6 results on intel test machineocis - [3.1.0-beta.1] using ## envs```export SEED_USERS_CREATE=false export ADMIN_LOGIN=admin export POOL_GROUPS=/root/loadtest/instance-one-jfd/pools/group.pool.json export PLATFORM_BASE_URL=https://one.jfd-lasttest.owncloud.works export AUTH_N_PROVIDER_TYPE=keycloak export TEST_KOKO_PLATFORM_010_RAMPING_STAGES_VUS=1000 export TEST_KOKO_PLATFORM_020_RAMPING_SLEEP_AFTER_ITERATION=2s export TEST_KOKO_PLATFORM_030_RAMPING_SLEEP_AFTER_ITERATION=30s export TEST_KOKO_PLATFORM_040_RAMPING_SLEEP_AFTER_ITERATION=60s export TEST_KOKO_PLATFORM_050_RAMPING_SLEEP_AFTER_ITERATION=30s export TEST_KOKO_PLATFORM_070_RAMPING_SLEEP_AFTER_ITERATION=30s export TEST_KOKO_PLATFORM_080_RAMPING_SLEEP_AFTER_ITERATION=30s export TEST_KOKO_PLATFORM_090_RAMPING_SLEEP_AFTER_ITERATION=60s export TEST_KOKO_PLATFORM_100_RAMPING_SLEEP_AFTER_ITERATION=60s export TEST_KOKO_PLATFORM_110_RAMPING_SLEEP_AFTER_ITERATION=30s export TEST_KOKO_PLATFORM_020_RAMPING_SLEEP_AFTER_ITERATION=2s Overview
ocis:3.1.0-beta.1## Test run## Historya different approach: * [2.0.0-beta8](https://github.com//issues/4465#issuecomment-1243691581)with the release of Result:
|
Automated GUI tests with desktop-client 4.1.0 (linux)oCIS: 3.1.0-beta.1
desktop-cleint: 4.1.0
os: LinuxBuild: https://drone.owncloud.com/owncloud/client/16093/5/11 |
Smoke Test with Web OfficeCollabora
Onlyoffice
|
|
@micbar how do you think, should we keep unread notification during the switching ocis version? is it bug or not?
Actual: the user does not have any notifications |
@ScharfViktor Is this bug or an actual plan not to add logo changing feature in this release ❓ Scenario: logo can be changed in the admin settings # tests/e2e/cucumber/features/smoke/admin-settings/general.ocis.feature:3
When "Admin" logs in
And "Admin" opens the "admin-settings" app
And "Admin" navigates to the general management page
Then "Admin" should be able to upload a logo from the local file "filesForUpload/testavatar.png"
✖ failed
Error: expect(received).toContain(expected) // indexOf
Expected substring: "testavatar.png"
Received string: "themes/owncloud/assets/logo.svg"
at Proxy.<anonymous> (/home/amrita/yuna/owncloud/web/node_modules/.pnpm/@playwright+test@1.33.0/node_modules/@playwright/test/lib/matchers/expect.js:135:37)
at Object.uploadLogo (/home/amrita/yuna/owncloud/web/tests/e2e/support/objects/app-admin-settings/general/actions.ts:14:33)
at General.uploadLogo (/home/amrita/yuna/owncloud/web/tests/e2e/support/objects/app-admin-settings/general/index.ts:34:9)
at World.<anonymous> (/home/amrita/yuna/owncloud/web/tests/e2e/cucumber/steps/ui/adminSettings.ts:116:5)
And "Admin" navigates to the general management page
- skipped
And "Admin" should be able to reset the logo
- skipped
And "Admin" logs out
- skipped
|
|
@amrita-shrestha Setup? |
as far as I remember, it's fixable when you hard refresh page. Try to do that, please |
Smoke test: ocis 3.1.0-beta.1 with ldap:Preparation
Test
|
yeah its working now |
e2e tests with ocis-ldapoCIS 3.1.0-beta.1
Web: 7.1.0-rc.1
|
ohh, sorry, here I am a goofball. I can't believe I did that )) |
On a default setup, notifications are kept in memory. They are gone after a restart. But in a prod setup you would configure ocis to persist the notifications. @aduffeck @kobergj @dragonchaser What speaks against it to use NATS as the default? |
|
Nothing. We can use nats or redis or any other store we support. I am not aware of issues with any of those stores For a lightweight single binary I would still suggest to use inmemory stores. |
Cloud Import with Nextcloud Public Link1. Import from Folder link share
2. Import from File link share - ❌ nothing to import (maybe expected)
|
ChangelogoCIS
Web
Reva
|
Changes which could affect the clients
|
ownCloud iOS + Android apps query thumbnails for EVERY file, and they're used to |
Cloud Import with Google Drive
|
Cloud Import with One Drive
Remarks:
|
Docker compose doc dest
|
6bec87f#diff-68d9b078637db7c0af192ec4237e8d332d0b8a269809ddd2ebc79c58e2dabf9dR30-R32 Seems like a breaking change when using a persistent store |
Yes true. It's a breaking change on |
MobileServer version: oCIS 3.0.1-beta.1 AndroidDevice & Android version: Pixel2 - Android 11 (REAL), Pixel 5 - Android 12 (EMU)
iOSDevice & iOS version: iPhone XR - iOS 16.5.1 (REAL), iPhone 14 - iOS 16.5 (SIM)
Final outcome: ✅From mobile side, no regards. |
|
Next steps:
Post-release communication
|
|
Smoke Test with Web OfficeCollabora
Onlyoffice
|
Smoke TestCase 1: admin share folder(with file) to marie: @KarunAtreyaAdmin:
Marie:
Admin:
Admin:
Marie:
Admin:
Case 2: admin share file to marie: @KarunAtreyaAdmin:
Marie:
Admin:
Marie:
Admin:
Case 3: admin create public links to folder @nirajacharya2Admin:
Case 4: admin create link to file @nirajacharya2Admin:
Case 5: space story: @PrajwolAmatyaKatherine:
Marie:
Einstein:
Case 6: create new user via accounts: @Salipa-GurungAdmin:
Case 7: Search @Salipa-Gurung
|
while sharing file and shows on ui but this does not persist locally |
|
^ CC @butonic Can policy service deny editing files by sharee? |
|
hm ... the policy engine is enabled: policies:
enabled: true
engineTimeout: 10s
policies:
- fileName: proxy.rego
content: |-
package proxy
import future.keywords.if
import data.utils
default granted := true
granted = false if {
utils.is_request_type_put
pathPrefixes := [
"/dav",
"/remote.php/webdav",
"/remote.php/dav",
"/webdav",
]
restricted := pathPrefixes[_]
startswith(input.request.path, restricted)
not utils.collection_contains(utils.ALLOWED_FILE_EXTENSIONS, input.request.path)
}
granted = false if {
pathPrefixes := [
"/data",
"/dav",
"/remote.php/webdav",
"/remote.php/dav",
"/webdav",
]
utils.is_request_type_post
restricted := pathPrefixes[_]
startswith(input.request.path, restricted)
not utils.collection_contains(utils.ALLOWED_FILE_EXTENSIONS, input.resource.name)
}
- fileName: postprocessing.rego
content: |-
package postprocessing
import future.keywords.if
import data.utils
default granted = true
granted := false if {
not utils.collection_contains(utils.ALLOWED_FILE_EXTENSIONS, input.resource.name)
}
- fileName: utils.rego
content: |-
package utils
import future.keywords.if
ALLOWED_FILE_EXTENSIONS := [
".apk", ".avi", ".bat", ".bmp", ".css", ".csv", ".doc", ".docm", ".docx",
".docxf", ".dotx", ".eml", ".epub", ".htm", ".html", ".ipa", ".jar", ".java",
".jpg", ".jpeg", ".js", ".json", ".mp3", ".mp4", ".msg", ".odp", ".ods", ".odt", ".oform",
".ots", ".ott", ".pdf", ".php", ".png", ".potm", ".potx", ".ppsm", ".ppsx", ".ppt",
".pptm", ".pptx", ".py", ".rtf", ".sb3", ".sprite3", ".sql", ".svg", ".tif", ".tiff",
".txt", ".xls", ".xlsm", ".xlsx", ".xltm", ".xltx", ".xml", ".zip", ".md"
]
##
is_stage_http {
input.stage == "http"
}
is_stage_pp {
input.stage == "pp"
}
##
is_user_admin {
input.user.username == "admin"
}
##
is_request_type_put {
is_stage_http
input.request.method == "PUT"
}
is_request_type_post {
is_stage_http
input.request.method == "POST"
}
is_request_type_mkcol {
is_stage_http
input.request.method == "MKCOL"
}
##
collection_contains(collection, source) {
current := collection[_]
endswith(source, current)
}but that does allow txt files ... 🤔 |
|
The policies were changed during development |
|
Check with @fschade |
|
@butonic here you can find the latest rego rule files, https://github.com/owncloud/ocis/tree/master/deployments/examples/service_policies/policies we should test it out together. |
|
After updating the rego files saving the txt file as a share recipient works again. Fixed IMO |
|
@butonic 🤝 thanks for speedy support 🤗 |
retested and passed ☑️ |
|
We have successfully completed the testing phase 🏁 . NOTE: The following test case has been done with a local docker-compose setup, since we had trouble loading a large number of users in server https://one.jfd-lasttest.owncloud.works/
|
|
that is expected. the deployment uses external user management so they cannot be created via the graph api. |
Release 4.0.0 is available 🎉Binarieshttps://download.owncloud.com/ocis/ocis/stable/4.0.0/ Docker
|
Template
Release Template
Prerequisites
release-3.1.0-beta.1-> CODEFREEZEchangelog/CHANGELOG.tmplocis-pkg/version/version.gosonar-project.propertieschangelog/x.x.x_????_??_??vx.y.z-rc.xvx.y.z-rc.xtag / BLOCKING for all further activityvx.y.z-rc.xocis.released.owncloud.worksQA Phase
After QA Phase
Brief company-wide heads up via mail @tbsbdr
DEV: Create branch
release-x.x.xocis-pkg/version/version.gosonar-project.propertieschangelog/x.x.x_???Release Notes + Breaking Changes @tbsbdr
Migration + Breaking Changes Admin Doc @mmattel
DEV: Create final signed tag
DEV: Check successful CI run on
vx.y.ztag / BLOCKING for all further activityMerge release notes
Post-release communication
docs-stable-x.ybranch based on the docs folder in the ocis repo @micbarThe text was updated successfully, but these errors were encountered: