Closed Bug 1796182 Opened 3 years ago Closed 3 years ago

please allow vmactions/freebsd-vm in mozilla/sccache/

Categories

(mozilla.org :: Github: Administration, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Sylvestre, Assigned: cknowles)

References

Details

In sccache, we would like to be able to test FreeBSD builds in the CI.
For this, we are using https://github.com/vmactions/freebsd-vm
and it would be great to have it enabled for sccache
See
https://github.com/mozilla/sccache/pull/1184
for the PR

thanks

Alright, I've checked out list of approved actions here and that isn't in the list - so I will needinfo the fine folks in secops to take a look and ask their questions.

But adding some generic ones - actions aren't enabled on just a repo, they're opened to the whole of the organization, hence the oversight from secops. If possible, you could copy the action into your repo, which would allow you to use it, but bypass the whole org seeing it. (but would prevent you from automagically getting updates.)

Flags: needinfo?(asargent)

Approved by SecOps/Eng, the action is straightforward in allowing the CI pipeline to be ran in FreeBSD. It's in use by nearly 2k other repos/projects and has a number of other similar offerings.

Surprisingly this developer found a niche project in creating a FreeBSD option for Github pipelines, specifically calling out, "The github workflow only supports Ubuntu, Windows and MacOS. But what if you need to use FreeBSD?" I'm surprised Github doesn't offer this natively.

For now, please use 'vmactions/freebsd-vm@v0' as the id and if :Sylvestre and team still have issues, we can look at updating the id.

Flags: needinfo?(asargent)

And I've added that string to the list of allowed actions for the org. :sylvestre, please update us if there are any further concerns.

Assignee: nobody → cknowles
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

Many thanks. I am impressed by your reactivity! :)

Blocks: 1802072
Depends on: 1867948
You need to log in before you can comment on or make changes to this bug.