ml5-library icon indicating copy to clipboard operation
ml5-library copied to clipboard

DevOps: TravisCI credits have run out - leading to failed builds?

Open joeyklee opened this issue 3 years ago • 4 comments

Dear ml5 community,

I'm submitting a new issue. Please see the details below.

→ Step 1: Describe the issue 📝

Did you find a bug? Want to suggest an idea for feature?

I think our TravisCI has run out of open source credits for running our continuous integration. This might be one reason why our CI builds are no longer running 😿 (along with our need to do more mocking of the requests that go to retrieve our big model files 😬 )

→ Step 2: Screenshots or Relevant Documentation 🖼

Here's some helpful screenshots and/or documentation of the new feature

Screen Shot 2022-01-19 at 1 11 50 PM

Possible solutions

  • @shiffman -- we could reach out to TravisCI to see if we might get more credits?
  • We could also adjust our settings for when we run our CI -- maybe we run tests locally for any new PRs until we sort this out in a more robust way?

joeyklee avatar Jan 19 '22 21:01 joeyklee

NOTE: for now I've disabled travis ci builds and tests by doing the following:

  • https://travis-ci.community/t/known-issue-travis-ci-reports-expected-waiting-for-status-to-be-reported-on-the-github-status-api-but-the-status-never-arrives/1154

We can flip these back on once we figure out next steps for this. In the meantime, we should run all tests locally before merges/releases! 🙈

joeyklee avatar Jan 21 '22 00:01 joeyklee

Thanks for looking into this @joeyklee! I'd be happy to request credits, I don't recall how we got them in the first place or did we just run out of a free plan? We could also allocate some of the remaining funds we have for the project to paying for credits if that makes sense!

shiffman avatar Jan 21 '22 16:01 shiffman

Thanks for your reply @shiffman!

We could also allocate some of the remaining funds we have for the project to paying for credits if that makes sense!

  • I think before we go for allocating funding, I would first see if we can get open source creds.
  • Since our CI is almost always failing to build b/c our tests timeout -- requesting those big model files I think is tough! -- we might consider also working on our tests a bit before setting up the CI w/ Travis again?

joeyklee avatar Jan 21 '22 22:01 joeyklee

I agree this makes sense @joeyklee! Let's table this issue until we have more reliable tests and then we can revisit securing additional credits w/ Travis (or a different service if that makes sense.)

shiffman avatar Jan 22 '22 18:01 shiffman