Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Build] Replace deprecated GabrielBB/xvfb-action by coactions/setup-xvfb #1344

Merged
merged 1 commit into from
Apr 11, 2023

Conversation

HannesWell
Copy link
Contributor

No description provided.

@github-actions
Copy link

github-actions bot commented Apr 11, 2023

Test Results

   198 files  ±0     198 suites  ±0   24m 55s ⏱️ - 4m 24s
   620 tests ±0     613 ✔️ +1    7 💤 ±0  0  - 1 
1 240 runs  ±0  1 226 ✔️ +1  14 💤 ±0  0  - 1 

Results for commit 0894eed. ± Comparison against base commit f5e9cdc.

♻️ This comment has been updated with latest results.

@HannesWell HannesWell merged commit 68ac138 into eclipse-m2e:master Apr 11, 2023
@HannesWell HannesWell deleted the xvfb branch April 11, 2023 23:03
@mickaelistria
Copy link
Contributor

FWIW, I recently managed to get rid of Xvfb in CI with https://github.com/redhat-developer/eclipseide-jdtls/blob/main/.github/workflows/validate.yml#L22..L28 . It can be worth preferring mutter over wayland to Xvfb as Xvfb isn't much maintained any longer and all main Linux distro use mutter and dropped X by default.

@HannesWell
Copy link
Contributor Author

That's interesting. Do you know if there is then an equivalent GH-action like setup-xvfb and a Jenkins Plugin like xvfb?

@mickaelistria
Copy link
Contributor

Back then, I searched and found no GitHub actions; but 4 lines of bash for mutter is IMO more interesting than 1 line of GH action for Xvfb.

@laeubi
Copy link
Member

laeubi commented Apr 16, 2023

Back then, I searched and found no GitHub actions; but 4 lines of bash for mutter is IMO more interesting than 1 line of GH action for Xvfb.

I don't think so, please take into account that the action do much more than "just starting xvfb", e.g. it detects if you run on windows and turn it there into a noop. So if you think mutter is superior it might be good to report it to the people of that action so they can consider using mutter as an alternative.

@mickaelistria
Copy link
Contributor

much more than "just starting xvfb", e.g. it detects if you run on windows and turn it there into a noop

That's not really much more, adding a if: ${{ runner.os == 'Linux' }} should do te trick.

So if you think mutter is superior

It's not just me, it's the consensus for all mainstream recent linux distributions who've stopped using X by default.

it might be good to report it to the people of that action so they can consider using mutter as an alternative.

I don't really care about the action, I'm pretty happy with the steps described above which give more control.

@laeubi
Copy link
Member

laeubi commented Apr 17, 2023

That's not really much more, adding a if: ${{ runner.os == 'Linux' }} should do te trick.

If the trick is to not execute anything at all on other OS (what about mac?) ... also this currently never do any cleanups.

I don't really care about the action, I'm pretty happy with the steps described above which give more control.

Sure if you just need to manage/control exactly one (or maybe two or three) repositories / actions it might be fine, for all other cases it just don't scale very well.

@HannesWell
Copy link
Contributor Author

Back then, I searched and found no GitHub actions; but 4 lines of bash for mutter is IMO more interesting than 1 line of GH action for Xvfb.

I don't think so, please take into account that the action do much more than "just starting xvfb", e.g. it detects if you run on windows and turn it there into a noop. So if you think mutter is superior it might be good to report it to the people of that action so they can consider using mutter as an alternative.

Created an issue: coactions/setup-xvfb#16
Please share your opinion there as I cannot really say much about the topic.

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.

None yet

3 participants