HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
iterative
cml_cloud_case
Python2020–2020
iterative / cml_cloud_case

cml_cloud_case

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
22GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2020-07-07 15:10:33 UTC to 2020-11-18 08:55:29 UTC. Weeks start Monday, UTC.

012020-07-06 00:00:00 UTC to 2020-07-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 62020-07-13 00:00:00 UTC to 2020-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-20 00:00:00 UTC to 2020-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-07-27 00:00:00 UTC to 2020-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-03 00:00:00 UTC to 2020-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-10 00:00:00 UTC to 2020-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-17 00:00:00 UTC to 2020-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-24 00:00:00 UTC to 2020-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-08-31 00:00:00 UTC to 2020-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-09-07 00:00:00 UTC to 2020-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 72020-09-14 00:00:00 UTC to 2020-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-09-21 00:00:00 UTC to 2020-09-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-09-28 00:00:00 UTC to 2020-10-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-10-05 00:00:00 UTC to 2020-10-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-10-12 00:00:00 UTC to 2020-10-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-10-19 00:00:00 UTC to 2020-10-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-10-26 00:00:00 UTC to 2020-11-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-11-02 00:00:00 UTC to 2020-11-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-11-09 00:00:00 UTC to 2020-11-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-11-16 00:00:00 UTC to 2020-11-23 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 16

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 62020-07-06 00:00:00 UTC2020-07-13 00:00:00 UTC101
Jul 132020-07-13 00:00:00 UTC2020-07-20 00:00:00 UTC000
Jul 202020-07-20 00:00:00 UTC2020-07-27 00:00:00 UTC000
Jul 272020-07-27 00:00:00 UTC2020-08-03 00:00:00 UTC000
Aug 32020-08-03 00:00:00 UTC2020-08-10 00:00:00 UTC000
Aug 102020-08-10 00:00:00 UTC2020-08-17 00:00:00 UTC000
Aug 172020-08-17 00:00:00 UTC2020-08-24 00:00:00 UTC000
Aug 242020-08-24 00:00:00 UTC2020-08-31 00:00:00 UTC000
Aug 312020-08-31 00:00:00 UTC2020-09-07 00:00:00 UTC000
Sep 72020-09-07 00:00:00 UTC2020-09-14 00:00:00 UTC000
Sep 142020-09-14 00:00:00 UTC2020-09-21 00:00:00 UTC000
Sep 212020-09-21 00:00:00 UTC2020-09-28 00:00:00 UTC000
Sep 282020-09-28 00:00:00 UTC2020-10-05 00:00:00 UTC000
Oct 52020-10-05 00:00:00 UTC2020-10-12 00:00:00 UTC000
Oct 122020-10-12 00:00:00 UTC2020-10-19 00:00:00 UTC000
Oct 192020-10-19 00:00:00 UTC2020-10-26 00:00:00 UTC000
Oct 262020-10-26 00:00:00 UTC2020-11-02 00:00:00 UTC000
Nov 22020-11-02 00:00:00 UTC2020-11-09 00:00:00 UTC000
Nov 92020-11-09 00:00:00 UTC2020-11-16 00:00:00 UTC000
Nov 162020-11-16 00:00:00 UTC2020-11-23 00:00:00 UTC101

What Hacker News says

2 sources
You should check out this [0] GitHub action workflow. It uses docker machine to create a high resourced runner on demand in the cloud and then runs the subsequent job on it. The workflow is intended for machine learning but I'm sure it could be adapted. I must disclose that I haven't actually used it myself yet (because I haven't felt the need) but it does look very promising. 0: https://github.com/iterative/cml_cloud_case/blob/master/.git...
In Making GitHub CI workflow 3x faster
Thanks, and good questions! 1. Yes! Let me link some reports and example repos: - A basic classification problem with scikit learn: https://github.com/iterative/cml_base_case/pull/2 - CML with DVC & Vega-Lite graphs: https://github.com/iterative/cml_dvc_case/pull/4 - Neural style transfer with EC2 GPU: https://github.com/iterative/cml_cloud_case/pull/2 2. If training fails, you'll be notified that your run failed in the GitHub Action dashboard (or GitLab CI/CD dashboard). See here for some real life examples of failure ;) : https://github.com/iterative/cml_cloud_case/actions 3. CML reports are markdown documents, so you can write any kind of text to them. If your metrics are output in a file `metrics.txt`, you can have your runner execute `cat metrics.txt >> report.md` and then have CML pass on the report to GitHub/GitLab. Likewise, any
Read the rest
graphing library is supported because you can add standard image files (.png, .jpg) to the report. So custom metrics and custom graphs. We like DVC for managing and plotting metrics, but we're biased because we also maintain it. 4. Yep, GitHub Actions is pretty powerful and flexible. Works with whatever external services you can connect to your Action! 5. It's not strictly a Docker technology. We use Docker images preinstalled with the CML library in our examples, but you can just install the library with npm in your own image. https://github.com/iterative/cml#using-your-own-docker-image Let me know if there's anything else I can tell you about
In Show HN: Continuous Machine Learning – CI/CD for Machine Learning Projects

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.