Skip to content

Conversation

@mergify
Copy link

@mergify mergify bot commented Feb 25, 2025

Proposed Changes

This PR makes small tweaks to Management UI + Selenium workflows. The changes to the workflows
are mainly tidying up. There is an important change to run the full suite of Selenium tests
on main. Prior to this PR, on main we run the "short" suite. This was not intended. The
short suite is meant for PRs.

Types of Changes

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI

Checklist

Put an x in the boxes that apply.
You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask on the mailing list.
We're here to help!
This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • I have added tests that prove my fix is effective or that my feature works
  • All tests pass locally with my changes
  • If relevant, I have added necessary documentation to https://github.com/rabbitmq/rabbitmq-website
  • If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it

Further Comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution
you did and what alternatives you considered, etc.


This is an automatic backport of pull request #13420 done by [Mergify](https://mergify.com).

CI can configure this variable to use a dynamic variable e.g. `${{
worker.temp }}`

(cherry picked from commit c2b9fec)
Those branches were for Bazel builds. Bazel was replaced in main and
4.0+

(cherry picked from commit e581b16)
The workflow to tests PRs is meant to run the short suite for management
UI tests. On commits, we want to run the full suite to ensure that
management UI tests are passing.

(cherry picked from commit 73279a8)
(cherry picked from commit 6c10cea)
In certain environments, we may want to customise the docker image e.g.
to use a proxy to avoid docker hub rate limiting. The default behaviour
remains unchanged.

The `if` logic was broken because `uname -a` returns the entire uname,
including OS, Kernel version, machine type and what not. The string
always starts with the OS i.e. Linux or Darwin, therefore, the matching
for `arm*` was always false; therefore, it was always defaulting to the
`else` image, which happens to be multi-arch. However, it was using
`seleniarm`, which is a community driven effort, not the official
Selenium account.

In the official OSS image, version 123.0 is too old. The oldest
available is 127.0. This commit bumps to the latest available. We could
consider depending on version `4`. Version `4` refers to Selenium
version, whilst version 123.0/133.0 refer to the browser version.

(cherry picked from commit ef8b4fc)
[skip ci]

(cherry picked from commit a5b8d19)
@mergify mergify bot assigned Zerpet Feb 25, 2025
@Zerpet Zerpet merged commit e3cc01f into v4.1.x Feb 25, 2025
1 check passed
@Zerpet Zerpet deleted the mergify/bp/v4.1.x/pr-13420 branch February 25, 2025 16:49
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