(Do Not Merge) test: [M3-8072] - Cloud changes for ad-hoc test pipeline

Open jdamore-linode opened this issue 1 year ago • 1 comments

Description 📝

Opening this to test some pipeline changes. Please ignore for now!

This PR includes a grab bag of improvements for our CI pipeline, primarily to support our ongoing efforts to integrate our tests with the API release.

Docker changes
- Deprecates our Docker Compose e2e, e2e_heimdall, and component Docker Compose services, and replaces them with cypress_local, cypress_remote, and cypress_component, respectively.
Cypress feature flag overriding capability
- Allows LaunchDarkly feature flags to be overridden via the CY_TEST_FEATURE_FLAGS environment variable. This can be used to test Cloud Manager against a specific LaunchDarkly feature flag configuration
Improvements to Slack and GitHub comment formatters
- Show PR title in Slack notification
- Only show a maximum of 6 test failures to prevent Slack message from being truncated
- Allow Slack notification title to be modified
- Allow extra arbitrary messages, warnings, etc. to be added to the bottom of the notification

Changes 🔄

List any change relevant to the reviewer.

Target release date 🗓️

Please specify a release date to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.

Preview 📷

Include a screenshot or screen recording of the change

:bulb: Use <video src="" /> tag when including recordings in table.

Before	After
📷	📷

How to test 🧪

Prerequisites

(How to setup test environment)

Reproduction steps

(How to reproduce the issue, if applicable)

Verification steps

(How to verify changes)

As an Author I have considered 🤔

Check all that apply

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[ ] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿ Providing accessibility support

Commit message and pull request title format standards

Note: Remove this section before opening the pull request Make sure your PR title and commit message on squash and merge are as shown below

<commit type>: [JIRA-ticket-number] - <description>

Commit Types:

feat: New feature for the user (not a part of the code, or ci, ...).
fix: Bugfix for the user (not a fix to build something, ...).
change: Modifying an existing visual UI instance. Such as a component or a feature.
refactor: Restructuring existing code without changing its external behavior or visual UI. Typically to improve readability, maintainability, and performance.
test: New tests or changes to existing tests. Does not change the production code.
upcoming: A new feature that is in progress, not visible to users yet, and usually behind a feature flag.

Example: feat: [M3-1234] - Allow user to view their login history

Oct 10 '24 22:10 jdamore-linode

Coverage Report: ✅
Base Coverage: 87.06%
Current Coverage: 87.06%

Oct 10 '24 22:10 github-actions[bot]