NEW description

The old description seems to be wrong.

Jenkins does still what it should. 
Quarantined tests are run - but a failure of a quarantined test will not lead to a failed build.
Hence, the ticket is rather obsolete.
There will be a (kind of) follow-up ticket about what to do with quarantined tests, even more generally how we can phase out JUnit-4-based UI-tests.

OLD description

Methods annotated with info.magnolia.integrationtests.rules.Quarantine should not be executed per default, according to javadoc of info.magnolia.integrationtests.rules.QuarantineRule.

But atm "quarantined methods" are executed on Jenkins. (See slack discussion.)
But locally - using the docker-hybrid-setup - the quarantined methods are not executed (as expected).

We figured this out in the context of MGNLCE-232
As a "quick shot", in MGNLCE-232 methods annotated with Quarantine are now annotated with org.junit.Ignore - tho this was done before we realized the unexpected behavior on Jenkins.

 Note that this annotation and the corresponding rule work on Junit4-based tests only! 
Hence we prbly should phase it out sooner or later.

Acceptance criteria

Step 1

• Make sure Quarantine works on Jenkins again as expected
• Deprecate info.magnolia.integrationtests.rules.Quarantine

Step 2

Completely get rid of the Quarantine annotation.
On "quarantined methods", use org.junit.Ignore instead, or fix the method, or get rid of the method

Step-2 could be part of a follow-up