[Jenkins-infra] Exploring alternatives to Azure Functions for serverless needs

[R. Tyler Croy]

(replies inline)

On Sat, 18 Aug 2018, Craig Rodrigues wrote:

> The Buildbot project does has their main CI server at
> https://nine.buildbot.net, and
> for each of their CI jobs, they spin up containers on Hyper (
> https://hyper.sh ), and then
> bring down the containers once they are done.
> They have used it for a few years, and the service is solid, and cheap:
> https://hyper.sh/hyper/pricing.html
> 
> In addition to spinning up plain containers, Hyper has introduced a new
> Kubernetes service as well,
> but I haven't tried it.


I think there's some ambiguity in what "serverless" means to different people
here :)

I'm referring to serverless a la AWS Lambda, Google Cloud Functions, and Azure
Functions. Whose typical workloads are small bits of glue JavaScript (or other
languages) which respond to webhooks, and send back http data.

For things like running Docker instances, we already have Kubernetes deployed
and if that wasn't enough, we also have Azure Container Instances (which are
pretty good) at our disposal.


The main use-case our functions
(https://github.com/jenkins-infra/community-functions) have is to bridge little
bits of http-based workflow together, which Azure Functions or Fission are
ideally suited for (assuming they work of course).

:)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20180819/0153e71b/attachment.asc>