[ci] upload artifacts of production, rolling or daily

[saw-jan]

Description

This is a POC for deploying docker and binary build artifacts according to #9264.

What is known:

• Production release docker tags: owncloud/ocis:x.x.x
• Rolling release docker tags: owncloud/ocis-rolling:x.x.x (including production tags)
• Production binary builds go to: stable subfolder
• Rolling binary builds go to: rolling subfolder
• Daily binary builds go to: daily subfolder

Q?:

• What kind of builds go to testing subfolder? Pre-releases - alpha, beta, rc?
• Docker tag for daily builds? owncloud/ocis-rolling:latest?
• What should happen to previous docker tags and binary builds? (move to respective docker repo and binary subfolders?) - not related to this PR though

PR implementation: tag release type from #9264 (comment)

• commit push:

  • docker-arm64-daily
  • docker-amd64-daily
  • manifest-daily
  • readme-daily
  • binaries-linux-daily
  • binaries-darwin-daily

• v6.0.0-rc.1:

  • docker-arm64-rolling
  • docker-amd64-rolling
  • manifest-rolling
  • readme-rolling
  • binaries-linux-testing
  • binaries-darwin-testing

• v6.0.0:

  • docker-arm64-rolling
  • docker-amd64-rolling
  • manifest-rolling
  • readme-rolling
  • binaries-linux-rolling
  • binaries-darwin-rolling

• v7.0.0-rc.1:

  • docker-arm64-rolling
  • docker-amd64-rolling
  • manifest-rolling
  • readme-rolling
  • docker-arm64-production
  • docker-amd64-production
  • manifest-production
  • readme-production
  • binaries-linux-testing
  • binaries-darwin-testing

• v7.0.0:

  • docker-arm64-rolling
  • docker-amd64-rolling
  • manifest-rolling
  • readme-rolling
  • docker-arm64-production
  • docker-amd64-production
  • manifest-production
  • readme-production
  • binaries-linux-rolling
  • binaries-darwin-rolling
  • binaries-linux-production
  • binaries-darwin-production

Related Issue

• Technical concept to provide Rolling Releases for ocis #9264

Motivation and Context

How Has This Been Tested?

• ❗ END RESULT NOT TESTED

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• 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:

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[micbar]

Good approach!

Please keep in mind, that all production tags are also rolling tags.

[saw-jan]

Please keep in mind, that all production tags are also rolling tags.

@micbar I have some questions regarding it in the PR description.
#9364 (comment)

Also, I have added about which pipelines will run on which type of events.

[saw-jan]

The PR is complete from my side and the things remaining is to test if it does the required job. I don't know how to confirm it. But I tested pipelines generation using:

drone starlark --max-execution-steps 100000000 --build.event="tag" --build.ref="refs/tags/v6.0.0" --repo.slug="owncloud/ocis" --repo.name="ocis"

drone starlark --max-execution-steps 100000000 --build.event="tag" --build.ref="refs/tags/v5.0.5" --repo.slug="owncloud/ocis" --repo.name="ocis"

drone starlark --max-execution-steps 100000000 --build.event="pull_request" --build.ref="refs/pull/123" --repo.slug="owncloud/ocis" --repo.name="ocis"

[micbar]

Rebased it.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[micbar]

Tested with a rolling tag, prerelease