-
Notifications
You must be signed in to change notification settings - Fork 187
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
[full-ci] Set OCS version to up to date values #2918
Conversation
💥 Acceptance test Core-API-Tests-ocis-storage-2 failed. Further test are cancelled... |
40fd0d9
to
32318ee
Compare
I fixed the imports, but otherwise looks great. Building oCIS like in the CI: and querying the version like will return following for tags: {
"major": 1,
"minor": 16,
"micro": 0,
"string": "1.16.0",
"edition": "Community",
"product": "oCIS"
} will return following for non tagged builds: {
"major": 0,
"minor": 0,
"micro": 0,
"string": "32318ee70",
"edition": "Community",
"product": "oCIS"
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Kudos, SonarCloud Quality Gate passed! |
@kulmann is this still on your roadmap? I would love to see this merged, after we update oC Web the next time (and the needed changes have been done in the SDK). |
Yes, we're currently working on bringing the most recent version of the sdk to web. When that finally worked I'll check if we can avoid the version check in sdk and then make this enhancement here possible. |
7224dc4
to
d1d01d0
Compare
Note: ocs.data.capabilities.core.productname has "ownCloud" for the oC10 product. Should that be set to "oCIS" on the oCIS implementation? And if so, then the information will be duplicated in ocs.data.version.product It seems odd to me to have that Maybe oC10 should publish an |
In oC10 there is also:
And that has And we could also publish that stuff at an endpoint |
@kulmann @phil-davis proceed? |
Thanks for the reminder. Created owncloud/owncloud-sdk#1016 just now. That needs to be merged and released, then sdk bumped in web, then web released and bumped in oCIS, and then we can update this PR here. Will try to sneak in an intermediate release within the sprint to not keep this open for too long. |
d1d01d0
to
926c5e1
Compare
To be honest I have no clue why we have those two different sections with versioning information. I added the version string to the core capability as well. You're right, it's probably a good idea to announce the product in |
Also, rebased to current master. |
Related oC10 core PR is owncloud/core#39851 |
332d6aa
to
659affe
Compare
@phil-davis or @individual-it could someone from your team take a look why there are so many unexpected passes in the CI runs of this PR? thanks 🙏 |
I'll take a look on this |
@kulmann The passing tests are Neither does the But In this PR the So all the tests that had the |
yes guys, I get your point 😓 |
b41ce06
to
79b929c
Compare
https://drone.owncloud.com/owncloud/ocis/11550/42/6
Getting really close. "productname" is "oCIS" in capabilities and "Infinite Scale" in |
ee8f0d5
to
99c145c
Compare
Needed to use github.com/Masterminds/semver/v3 instead of v1 to be able to extract major, minor and patch version from a version string. Falling back to 0.0.0 in any error case (e.g. if the version.String is a hash)
@phil-davis Another improvement, the semver checking needs to be more tolerant. |
@phil-davis This gets a green testsuite now. I will merge this as soon as the core pipeline is also green. |
010944d
to
1538222
Compare
Kudos, SonarCloud Quality Gate passed! |
Description
This PR sets the OCS version fields to up to date values and already includes the "product" field, which hopefully gets merged in reva soonish cs3org/reva#2397
With these enhancements we'll be able to see the backend version in the browser console when we merged and released that in web: owncloud/web#6190
I guess setting the hardcoded version information during a release might be feasible for now. I didn't find any place where the current version is written down at the moment. In web we have it in the
package.json
so I was able to include it from there during bundling. Would be nice to have it a little less dirty here as well. Ideas for where to put the current oCIS version are welcome, I'll happily include that in this PR.Related Issue
Results
Dev Debug Build
Local dev build
make -C ocis clean build
1538222a0
is the git commitIDThis is valid semver build metadata https://semver.org/#spec-item-10
Pre Releases
Final Releases
Screenshot from the web console
Motivation and Context
Make bug reports a little bit easier / more precise.
How Has This Been Tested?
Only manually, since it's no code change but only hardcoded values.
Types of changes
Checklist: