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

Credits for Arm-based GitHub Runners for Quarkus #8

Closed
blafond opened this issue Oct 10, 2024 · 1 comment
Closed

Credits for Arm-based GitHub Runners for Quarkus #8

blafond opened this issue Oct 10, 2024 · 1 comment

Comments

@blafond
Copy link

blafond commented Oct 10, 2024

If you are interested in requesting credits for GitHub Arm Runners,
please fill out the details below.

Proposals will be evaluated on a biweekly basis and responses will be done via email

Name, email, company, job title

Max Rydahl Andersen, [email protected], Red Hat, Inc., Distinguished Engineer

Barry LaFond, [email protected], Red Hat, Inc., Associate Engineering Manager

Project Title and description

Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications.

Describe your use case for these machines

The existing Quarkus integration test suite encapsulates multiple different platforms, frameworks, databases and libraries, but not ARM (see: Quarkus Integration Tests). Because continuous integration does not have access to ARM hardware, the incremental checks on individual pull requests do not have full coverage. ARM capability ends up being sparingly tested during our product release processes via QE.

Access to ARM testing during the development process would allow developers to catch errors and issues earlier in the product life cycle. It also helps them reproduce issues reported by users and provide fixes in the community source.

Which members of the community would benefit from your work?

Anyone using Quarkus applications with ARM hardware. This includes developers creating Quarkus-based applications on ARM-based development machines, and organizations deploying Quarkus applications onto ARM servers.

Is the code that you’re going to run 100% open source?

Yes.

Project code is here: https://github.com/quarkusio/quarkus

Documentation is here: https://quarkus.io/

Please outline your credits requirements at a high level to support Arm builds (purpose, duration, amount, other)

Please share a public URL of the CI dashboard (if applicable).

GitHub Actions are used for the Quarkus CI.

See https://github.com/quarkusio/quarkus/actions for CI dashboard.

Does the project allows the use of your project logo on ARM's developer website freely? Yes / No / Not Sure

Yes

Important reminders and logistics

Approved projects will be encouraged to provide credit back to Works on Arm
in the form of a logo display, blog post, Twitter post, news release, or
some other suitable acknowledgement.

Approved projects are subject to a 90-day review process for termination.

In case a project goes through ownership change or key people leaving, please promptly inform the team by adding comments on this issue. Our team will maintain dialogue with new members.

For more project information, see the following social channels:

@shipra-ps
Copy link
Collaborator

Closing issue for now as no response had been received over email.

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

No branches or pull requests

2 participants