Switch to ubuntu 22.04

[NotMyFault]

Closes #803

[timja]

Seems to be running relatively good, although some scrolling issues.

I tried to run it on my machine but unfortunately mozilla has decided not to publish official arm64 binaries -.-
mozilla/geckodriver#1956

I'll try hack it later on so I can see if I can reproduce the issue

[NotMyFault]

I tried to run it on my machine but unfortunately mozilla has decided not to publish official arm64 binaries -.-

Indeed, unfortunate, maybe we should give our gecko version an update while we're at it? It's almost 3 years old

[timja]

Hacked on it for an hour and it still doesn't run on my machine -.-

But finally got geckodriver to start at least.

[timja]

Hacked on it for an hour and it still doesn't run on my machine -.-

Turns out it ran find I just had a partially downloaded war 🙄.

I can reproduce the CI issues locally at least. haven't had time to dig into them but cleaned up the Dockerfile changes and pushed in 9d06b05

[NotMyFault]

Merging in master with the git client fixes reduced test failures a lot 👀

[NotMyFault]

One test failure occurs in ConfigFileProviderTest#testCustomConfigFile() https://ci.jenkins.io/job/Core/job/acceptance-test-harness/job/PR-878/14/testReport/junit/plugins/ConfigFileProviderTest/java_11_jenkins_lts_split9___testCustomConfigFile/

I suspect this is a real failure this time, because it doesn't occur on the comparison build for the master branch, I used for a different PR: #956
Although I'm not sure why switching to Ubuntu would make this specific test fail...

Additionally, I disabled the pipeline for builds on infra.ci, because of several hadolint violations.

Changes addressed

[jtnord]

Since this change any test that uses docker appears to be skipped as docker is no longer available.

see https://ci.jenkins.io/job/Core/job/acceptance-test-harness/job/master/684/testReport/plugins/WorkflowPluginTest/history/ compare 671 with 672

a couple of tests that require docker seem to also have regressed.

[raul-arabaolaza]

As we are impacted by this in our proprietary suites, I am already checking what James said. I can confirm some tests have been ignored for months, apparently because docker is not installed. And they are failing in our env because we use another images with docker available.

I will update here and try to send a fix asap