Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

rreich
Copy link
Contributor

@rreich rreich commented Jul 11, 2025

Instead of attaching to the action / the GitHub Release, we now upload the plugin to our OCI registry.
The upload (push) to the registry is performed by the build tooling (mvn, pnpm).
To this end we also updated the coremedia-plugins-maven-plugin which now requires Java 17.
The studio-client part now uses @coremedia/plugin-manager which requires node 22 and allowance for script execution (to install oras tooling) with onlyBuiltDependencies.

The plugin descriptor is now represented as an OCI manifest and is also pushed via mvn (See configuration in the root pom).

The structure in the registry will be:

  • /plugins/content-hub-adapter-filesystem for the descriptor manifest
  • /plugins/content-hub-adapter-filesystem/studio-server.content-hub-adapter-filesystem for the studio-server plugin
  • /plugins/content-hub-adapter-filesystem/studio-client.main.content-hub-adapter-filesystem for the studio-client plugin

Releases are pushed to repository.coremedia.com/public-images/ while developer snapshots are pushed to repository.coremedia.com/ephemeral-images/

@rreich rreich force-pushed the oci-poc branch 4 times, most recently from ddde50d to 485a018 Compare July 17, 2025 08:21
@rreich rreich force-pushed the oci-poc branch 4 times, most recently from b26acdd to 2c9640b Compare July 25, 2025 14:47
@rreich rreich force-pushed the oci-poc branch 3 times, most recently from 1c8d094 to 744891a Compare August 4, 2025 08:00
@rreich rreich force-pushed the oci-poc branch 2 times, most recently from f84b801 to 8f3cf25 Compare August 7, 2025 13:32
Instead of attaching to the action / the GitHub Release, we now upload the plugin to our OCI registry.
The upload (push) to the registry is performed by the build tooling (mvn, pnpm).
To this end we also updated the coremedia-plugins-maven-plugin which now requires Java 17.
The studio-client part now uses @coremedia/plugin-manager which requires node 22 and allowance for script execution (to install oras tooling) with onlyBuiltDependencies.

The plugin descriptor is now represented as an OCI manifest and is also pushed via mvn (See configuration in the root pom).

The structure in the registry will be:
* /plugins/content-hub-adapter-filesystem for the descriptor manifest
* /plugins/content-hub-adapter-filesystem/studio-server.content-hub-adapter-filesystem for the studio-server plugin
* /plugins/content-hub-adapter-filesystem/studio-client.main.content-hub-adapter-filesystem for the studio-client plugin

Releases are pushed to repository.coremedia.com/ephemeral-images/ while developer snapshots are pushed to repository.coremedia.com/ephemeral-images/
@rreich rreich changed the title poc: convert to oci plugin Convert to OCI plugin Sep 29, 2025
@rreich rreich marked this pull request as ready for review September 30, 2025 12:20
@rreich rreich merged commit 78e884c into main Sep 30, 2025
1 of 2 checks passed
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.

1 participant