[tests-only][full-ci]Cache playwright chromium

[amrita-shrestha]

Description

This PR

• update PLUGINS_S3 = "plugins/s3:1.5" version
• cache chromium with respect to playwright version
• Use cached chromium to run e2e tests
• add script to get playwright version to store cache

Note

• can't upgrade minio version because some command are not available in the latest minio image

Related Issue

• Fixes [QA] download chromium in Ci only after updating playwright #11921

Motivation and Context

How Has This Been Tested?

• CI

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
• Documentation
• Maintenance (e.g. dependency updates or tooling)

Open tasks:

• ...

[saw-jan]

Consider using browsers instead of chromium

[ScharfViktor]

thank you Amrita, that is great job 👍
I'm fine with chromium naming if we use only chromium. when we use multi-browser testing in the CI -> we can use abstract name IMHO
I have questions:

• do we know how long we keep data in the MINIO_MC? what happens if we don't update playwright in for example 30 days and cache will be deleted? should we check that chromium cache is exist?
• in your PR we install chromium https://drone.owncloud.com/owncloud/web/49324/5/5 but we don't update playwright. it happened since we didn't have the cache, correct? in normal case we don't need install chromium when no playwright update

[amrita-shrestha]

• do we know how long we keep data in the MINIO_MC? what happens if we don't update playwright in for example 30 days and cache will be deleted? should we check that chromium cache is exist?
• in your PR we install chromium https://drone.owncloud.com/owncloud/web/49324/5/5 but we don't update playwright. it happened since we didn't have the cache, correct? in normal case we don't need install chromium when no playwright update

@ScharfViktor, I believe the cache lifespan is 30 days.

check_chromium_cache method verifies the existence of the Chromium cache during each build, based on the Playwright version specified in the package.json file. If the cache is missing, the installChromium and cacheChromium steps are triggered, aligned with the specified Playwright version.

If the bot updates the Playwright version, a new Chromium version will be installed and cached, while the old Chromium cache will remain until its lifespan expires.

It seems adding a script to remove the old cache when a new one is uploaded could interfere with other running builds, so that idea has been dropped to avoid potential disruptions.

As shown in the image above, 1.49.0 represents the Playwright version. Currently, the Chromium cached tar file is stored in a directory named after the Playwright version.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[saw-jan]

👍