Skip to content

WIP: Move from Azure Pipelines to GitHub Actions #1232

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

joshtriplett
Copy link
Contributor

@joshtriplett joshtriplett commented May 8, 2025

This simplifies the CI setup substantially.

@joshtriplett joshtriplett force-pushed the switch-to-github-actions branch 2 times, most recently from ca30d92 to a7bf658 Compare May 8, 2025 16:44
@joshtriplett
Copy link
Contributor Author

@kkysen Would you mind safelisting Swatinem/rust-cache for GitHub Actions?

@joshtriplett joshtriplett force-pushed the switch-to-github-actions branch 4 times, most recently from 6945fa0 to 1cd2856 Compare May 8, 2025 18:01
@kkysen
Copy link
Contributor

kkysen commented May 8, 2025

@kkysen Would you mind safelisting Swatinem/rust-cache for GitHub Actions?

Do you know how to do that?

@joshtriplett
Copy link
Contributor Author

@kkysen Would you mind safelisting Swatinem/rust-cache for GitHub Actions?

Do you know how to do that?

I believe it'll be in the GitHub actions settings, either for the project or for the organization. There's a setting for where it can run actions from.

@kkysen
Copy link
Contributor

kkysen commented May 8, 2025

@kkysen Would you mind safelisting Swatinem/rust-cache for GitHub Actions?

Do you know how to do that?

I believe it'll be in the GitHub actions settings, either for the project or for the organization. There's a setting for where it can run actions from.

@thedataking, can you see if you're able to do this? I don't see where I can, or I probably don't have permission to do it. See the error message here: https://github.com/immunant/c2rust/actions/runs/14911291371.

@joshtriplett joshtriplett force-pushed the switch-to-github-actions branch 4 times, most recently from e0c2712 to 6dacb8c Compare May 9, 2025 00:42
Comment on lines -23 to -34
arch:
containerImage: immunant/c2rust:archlinux-base-latest
debian10:
containerImage: immunant/c2rust:debian-buster-latest
debian11:
containerImage: immunant/c2rust:debian-bullseye-latest
fedora34:
containerImage: immunant/c2rust:fedora-34-latest
ubuntu20:
containerImage: immunant/c2rust:ubuntu-focal-latest
ubuntu18:
containerImage: immunant/c2rust:ubuntu-bionic-latest
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we test on all of these distros and versions in GitHub Actions, too, instead of just Ubuntu 24?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh wait, GitHub Actions only supports Ubuntu, right? So we'll have to drop testing on all the others. @thedataking is this okay?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kkysen It's theoretically possible to run a custom container of an arbitrary distro on GitHub Actions, but one of the huge benefits of this change to the CI is avoiding the separate (and manual) step of building containers, which makes it impossible for contributors to modify and test (because contributors can't replace those containers). With the new approach, all the packages are installed on the fly, and it's much easier to iterate on the result.

I think that usability improvement would be worth making this change.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we fully inline this in ci.yml? And the other provision scripts, too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd be happy to do that as an additional step, once this builds at all on macOS. Would you mind if that's a follow-up PR?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Of course

@joshtriplett joshtriplett force-pushed the switch-to-github-actions branch from 6dacb8c to 52a98eb Compare May 9, 2025 08:22
This simplifies the CI setup substantially.

Fixes: immunant#1226
@joshtriplett joshtriplett force-pushed the switch-to-github-actions branch from 52a98eb to 71a8069 Compare May 9, 2025 08:24
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.

Move CI from Azure Pipelines to GitHub Actions
2 participants