Re: [eclipse.org-architecture-council] Supporting GitHub Actions / GitHu

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

Hi,

I was about to file a bug but as it looks like this is discussed on this
list, I thought i could directly reply.

We are doing cross-platform builds for efxclipse-driftfx using
github-actions but our problem is that naturally we can not sign our
artifacts there so we need a way to make the Eclipse.org-Jenkins do that.

Our thought was that we could make github-actions trigger the
efxclipse-jiro-jenkins instance who fetches the build result, sign it
and uploading that to github-releases.

If I get you right this won't be possible because you will never allow
github to trigger our jenkins instance because that would require user
credentials available on github, right?

Tom

On 15.01.20 11:53, Mikael Barbero wrote:
> 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... 
> 
> self-hosted runners are not an options, see GH Warning about it
> (https://help.github.com/en/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners): 
> 
> 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.
> 
> Cheers,
> *
> Mikaël Barbero *
> *Team Lead - Release Engineering | Eclipse Foundation*
> 🐦 @mikbarbero
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open
> Innovation and Collaboration
> 
>> Le 4 déc. 2019 à 13:55, Torkild U. Resheim <torkildr@xxxxxxxxx
>> <mailto:torkildr@xxxxxxxxx>> a écrit :
>>
>> Signé partie PGP
>> Hi,
>>
>> 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?
>>
>> Best regards,
>> Torkild
>>
>>> 4. des. 2019 kl. 12:34 skrev Jens Reimann <jreimann@xxxxxxxxxx
>>> <mailto:jreimann@xxxxxxxxxx>>:
>>>
>>> Hi everyone,
>>>
>>> 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 [1], 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.
>>>
>>> Cheers
>>>
>>> Jens
>>>
>>> [1] https://wiki.eclipse.org/CBI#CI_Environment_.28Third-party.29
>>>
>>> --
>>> Jens Reimann
>>> Principal Software Engineer / EMEA ENG Middleware
>>> Werner-von-Siemens-Ring 14
>>> 85630 Grasbrunn
>>> Germany
>>> phone: +49 89 2050 71286
>>> _____________________________________________________________________________
>>>
>>> Red Hat GmbH, www.de.redhat.com <http://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 <http://eclipse.org>-architecture-council mailing list
>>> eclipse.org-architecture-council@xxxxxxxxxxx
>>> <mailto:eclipse.org-architecture-council@xxxxxxxxxxx>
>>> https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
>>>
>>> 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.
>>
>>
> 
> 
> _______________________________________________
> eclipse.org-architecture-council mailing list
> eclipse.org-architecture-council@xxxxxxxxxxx
> https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
> 
> 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.
> 

-- 
Tom Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Salurnerstrasse 15. A-6020 Innsbruck
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck