From: michael.adler@siemens.com (Adler, Michael)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [ANNOUNCE] Introducing gitlab-cloud-ci. Perform ISAR-based CI builds in the cloud.
Date: Mon, 27 May 2019 08:10:09 +0000 [thread overview]
Message-ID: <20190527081008.oddoarkk4zmq6sef@demogorgon> (raw)
In-Reply-To: <20190524143004.usdvezwd46ied6i4@xps.therub.org>
Hi Dan,
> I thought they billed per-second now days, but looking into it, it seems that may only be for amazon linux and ubuntu
> AMIs?
you are right, it looks like they've changed it quite a while back [1] - at least for AMIs outside of the AWS
Marketplace, if I understood that part correctly. Currently, I'm just using the kops default (Debian Jessie, with a 4.4
kernel), but Amazon Linux is supposed to work as well [2].
So yes, I think we can reduce the timeout value dramatically (maybe even down to 1 minute), possibly saving quite some
money over time. Thanks for the input, it's much appreciated!
> Do your builds take advantage of any caching, and if so, how are you making it persistent?
Caching is supported in general and up to the user (or rather their .gitlab-ci.yml [3]). IIRC, Gitlab Runner just
creates a zip file of the files/directories you've specified and uploads it to S3.
> I'm also really curious about your experience with k8s, but mostly I'm
> interested to find out how it works for this project over time in terms
> of stability, cost, complexity, etc.
Well, so am I :)
> Thanks again! If there is any place else I can follow information about
> this let me know.
For now, I can advise following the git repo and this mailing list. Code contributions are welcome as well, of course.
Best regards,
Michael
[1] https://aws.amazon.com/blogs/aws/new-per-second-billing-for-ec2-instances-and-ebs-volumes/
[2] https://github.com/kubernetes/kops/blob/release-1.11/docs/images.md
[3] https://docs.gitlab.com/ee/ci/caching/
--
Michael Adler
Siemens AG, Corporate Technology, CT RDA IOT SES-DE, Otto-Hahn-Ring 6, 81739 Munich, Germany
Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Joe Kaeser, Chairman, President and Chief Executive Officer; Roland Busch, Lisa Davis, Klaus Helmrich, Janina Kugel, Siegfried Russwurm, Ralf P. Thomas; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
prev parent reply other threads:[~2019-05-27 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 13:09 [cip-dev] [ANNOUNCE] Introducing gitlab-cloud-ci. Perform ISAR-based CI builds in the cloud Adler, Michael
2019-05-23 3:00 ` daniel.sangorrin at toshiba.co.jp
2019-05-24 8:37 ` Adler, Michael
2019-05-28 14:20 ` Adler, Michael
2019-05-24 14:30 ` Dan Rue
2019-05-27 8:10 ` Adler, Michael [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190527081008.oddoarkk4zmq6sef@demogorgon \
--to=michael.adler@siemens.com \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox