[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse.org-architecture-council] Supporting GitHub Actions / GitHub repositories
|
Hi,
Thanks - that sounds better than I thought/hoped. I'll file a Bugzilla
and we can discuss there further.
I think having a solid integration story for Eclipse.org-Projects hosted
on github would be very interesting for my of us.
Tom
Am 24.01.20 um 11:39 schrieb Mikael Barbero:
Hi Tom,
Sorry for the late reply. See my comments inline
*
*
Le 15 janv. 2020 à 12:45, Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx
<mailto:tom.schindl@xxxxxxxxxxxxxxx>> a écrit :
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 theEclipse.org
<http://eclipse.org/>-Jenkins do that.
Indeed, currently signing services only run behind our firewall.
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.
Note that if someone volunteers to implement TLS+oauth2 authentication
in
https://git.eclipse.org/c/cbi/org.eclipse.cbi.git/tree/webservice/signing/jar ,
we could expose the jar signing service to the outside world.
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?
We would need to investigate what is needed by your github actions to
trigger a Jenkins job. Note that on Gtihub we have bot accounts that may
be used for that purpose. Again, we would need to investigate.
Cheers,
_______________________________________________
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.