8261: Use test flag to skip JDP multicast tests in JolokiaTest

[skarsaune]

I just became aware that there is a new flag used to skip JDP tests.
I previously added some env checking to skip similar multicast tests for Jolokia.
Hence it would be a lot cleaner to use the new standardized mechanism for this.
Trying out whether this fixes JMC-8261

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed (1 review required, with at least 1 Committer)

Issue

• JMC-8261: Use test flag to skip JDP multicast tests in JolokiaTest (Enhancement - P5)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jmc.git pull/588/head:pull/588
$ git checkout pull/588

Update a local copy of the PR:
$ git checkout pull/588
$ git pull https://git.openjdk.org/jmc.git pull/588/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 588

View PR using the GUI difftool:
$ git pr show -t 588

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jmc/pull/588.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back skarsaune! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[aptmac]

@skarsaune Here's a jira issue you can use for this PR, and then Skara should pick it up and run the CI. It looks like after the change to use the setup-maven action in the workflow (link) we cannot run CI in our forks.

For example, the action that tried to run on your fork here shows an error:
stcarolas/[email protected] is not allowed to be used in skarsaune/jmc. Actions in this workflow must be: within a repository owned by skarsaune, created by GitHub, verified in the GitHub Marketplace, or matching the following: openjdk/jmc.

[mlbridge]

Webrevs

• 00: Full (9f8dd613)

[skarsaune]

@aptmac : even after referencing the issue. it still does not appear to run the ci tests on the pr. Any way to trigger it? As the pr is speculative, it does not make sense to merge it before we have tested it.

[aptmac]

I'm not sure what's happening here, will have to take a look at why the rest of the checks haven't triggered.

[aptmac]

I took a bit more of a look around some of our forks, and I'm not seeing the issue I posted in the comment above: #588 (comment).

I'm curious what happens if you manually trigger a workflow on the master branch at: https://github.com/skarsaune/jmc/actions

I'm wondering if it's a mis-configuration of the workflow actions in your fork somehow.