Resolve "pages:deploy job failed with artifacts for pages are too large"
What does this MR do?
Remove pages publishing of webpack report
We are not consuming the webpack-report via pages anymore, it can be found on: https://gitlab-org.gitlab.io/frontend/playground/webpack-memory-metrics/last-report.html
We stopped consuming it as it's creation was unreliable as not every pipeline runs the webpack compilation. Now it seems to be too large, so let's just remove it.
Reduce size of frontend-coverage artifacts
We are combining the artifacts of multiple jest jobs into one. In the resulting artifacts we keep the original results as well, those are not too meaningful though. Let's stop those from getting published in order to save space and bandwidth.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #297184 (closed)