Skip to content

Conversation

@MahdiBaghbani
Copy link
Member

@MahdiBaghbani MahdiBaghbani commented Dec 28, 2025

This PR is a part of cs3org/OCM-STA#3
This PR is a part of cs3org/OCM-STA#4

The document for this workflow can be found on OCM Test Suite

A demo of the run can be found in the GitHub Actions, you can also download and review the videos generated by Cypress from artifact section.

This pull request adds a dedicated GitHub Actions workflow that runs the OCM Test Suite against CERNBox and Reva using a small, fixed invite link matrix.

  • The workflow builds and uploads a static revad binary from the current branch, then uses that binary inside the CERNBox containers.
  • A single matrix actor job runs four invite link combinations:
    • Stub v1.1.0 <-> Stub v1.1.0
    • Stub v1.1.0 <-> CERNBox (current Reva build)
    • CERNBox (current Reva build) <-> Stub v1.1.0
    • CERNBox (current Reva build) <-> CERNBox (current Reva build)
  • Each matrix entry prepares a small dev stock root, pulls the required Docker images, mounts the Docker socket, and runs the OCM Test Suite via the dev stock image with scenario invite link.
  • When a combination needs the current Reva code, the workflow downloads the revad binary artifact into a host directory and passes it into the dev stock container via REVA_BINARY_DIR.
  • A summary job reads one row JSON status artifacts for each combination, writes a compact Markdown table into the GitHub Actions summary, and then deletes the status artifacts while keeping the revad binary and all Cypress videos and screenshots.
  • The matrix job is configured as non blocking with continue on error, so all four combinations are attempted and OCM regressions are reported without failing the entire CI run.

This gives CERNBox and Reva a clear, repeatable invite link compatibility check between Stub and the current Reva build.

The OCM-Stub is subject to be developed in the next milestone, and this workflow would also be updated, as of now it is expected that the results for the CERNBox to Stub and Stub to CERNBox to be failure.

Update OCM Test Suite to use ocmstub version 1.1.0 for improved functionality

add: OCM Test Suite workflow_dispatch for manual execution

Enhance OCM Test Suite workflow

Refactor OCM Test Suite workflow to directly pull images

fix: job names

add: better job names for summary and prepare

Signed-off-by: Mahdi Baghbani <mahdi-baghbani@azadehafzar.io>
@update-docs
Copy link

update-docs bot commented Dec 28, 2025

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.

Copy link
Member

@glpatcern glpatcern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is very good work, if you could also look into the comment below I think we can merge it right away (even if the test currently fails)


- name: Extract gaia from DockyPody image
run: |
docker pull ghcr.io/mahdibaghbani/containers/gaia:latest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please use some "upstream" references here and in the following, instead of /mahdibaghbani/...?

ghcr.io/mahdibaghbani/containers/cernbox-revad:mahdi_fix_localhome-development
ghcr.io/mahdibaghbani/containers/cernbox-web:testing
- combo_id: cernbox-stub
display_name: "CERNBox to Stub"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have an option to mark a failure as "warning" as opposed to full red cross? If not, it's fine to have it as is, definitely better than hiding it

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.

2 participants