Re: [eclipse.org-architecture-council] Supporting GitHub Actions / GitHub repositories
|I don't think EMO would have anything against GItHub actions. Note that as noted on the wiki (https://wiki.eclipse.org/CBI#CI_Environment_.28Third-party.29), we don't put any credential on such 3rd party services (as long as we have no automation in place to set/update/remove said credentials). So no GPG keys, ossrh credentials etc... |
Warning: We recommend that you do not use self-hosted runners with public repositories.
Forks of your public repository can potentially run dangerous code on your self-hosted runner machine by creating a pull request that executes the code in a workflow.
Team Lead - Release Engineering | Eclipse Foundation
Signé partie PGP
Apart from not having access to OSSRH, SSH and GPG keys I don't see any issues with using GitHub Actions for Eclipse projects. I don't think there is anything the EMO has to do in order for it to work just fine.
Maybe there is a way we could use "self-hosted runners" when keys etc. are required?
4. des. 2019 kl. 12:34 skrev Jens Reimann <jreimann@xxxxxxxxxx>:
with the GA of GitHub Actions and GitHub repositories, it is possible to get a bit more CPU/RAM with GitHub Action than with Travis. And of course it nicely integrates with GitHub.
GitHub actions also allow you to attach custom compute resources for your build. Which might be interesting for some people.
With GitHub repositories it is possible to host Docker, NPM, Maven, … directly alongside the GitHub repository.
Taking a look at what the Eclipse Foundation supports , I was able to find Travis (supported), CricleCi (not supported).
I think it would be nice to have a general "ok" (also on the Wiki Page) on using GitHub Actions and the repository system, in addition to Travis and our own infrastructure.
Let me know what you think.
Principal Software Engineer / EMEA ENG Middleware
phone: +49 89 2050 71286
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill, Thomas Savage
eclipse.org-architecture-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
Description: Message signed with OpenPGP