New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deal with CircleCI 1.0 End of Life on August 31, 2018. #766

Closed
dmitshur opened this Issue Feb 27, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@dmitshur
Member

dmitshur commented Feb 27, 2018

See https://circleci.com/blog/sunsetting-1-0/:

TL;DR: After August 31, 2018, CircleCI 1.0 will no longer be available for Linux and macOS users.

We're currently using CircleCI 1.0 for this project (/cc @neelance):

image

Need to deal with it by the time it's shut down. Options include:

  • migrate to CircleCI 2.0 (if it's still free)
  • migrate to another CI
@myitcv

This comment has been minimized.

Show comment
Hide comment
@myitcv

myitcv Apr 18, 2018

Contributor

Per https://circleci.com/pricing/#faq-section-linux I have contacted CircleCI (copying @shurcooL) asking them what our options are.

We can of course evaluate Travis in parallel.

Contributor

myitcv commented Apr 18, 2018

Per https://circleci.com/pricing/#faq-section-linux I have contacted CircleCI (copying @shurcooL) asking them what our options are.

We can of course evaluate Travis in parallel.

@neelance

This comment has been minimized.

Show comment
Hide comment
@neelance

neelance Apr 18, 2018

Member

Is there any reason against CircleCI 2.0? I'm already using it for another project and it is great.

Member

neelance commented Apr 18, 2018

Is there any reason against CircleCI 2.0? I'm already using it for another project and it is great.

@myitcv

This comment has been minimized.

Show comment
Hide comment
@myitcv

myitcv Apr 18, 2018

Contributor

None at all! Just mentioned that as a hedge; I've got no experience of CircleCI 2, so great to hear it's good!

Contributor

myitcv commented Apr 18, 2018

None at all! Just mentioned that as a hedge; I've got no experience of CircleCI 2, so great to hear it's good!

@myitcv

This comment has been minimized.

Show comment
Hide comment
@myitcv

myitcv Apr 18, 2018

Contributor

Ok, just heard back - unsurprisingly we can keep the free service and just need to follow https://circleci.com/docs/2.0/migrating-from-1-2/ in order to upgrade.

Contributor

myitcv commented Apr 18, 2018

Ok, just heard back - unsurprisingly we can keep the free service and just need to follow https://circleci.com/docs/2.0/migrating-from-1-2/ in order to upgrade.

myitcv added a commit to myitcv/gopherjs that referenced this issue Apr 20, 2018

myitcv added a commit to myitcv/gopherjs that referenced this issue Apr 20, 2018

myitcv added a commit to myitcv/gopherjs that referenced this issue Apr 20, 2018

myitcv added a commit to myitcv/gopherjs that referenced this issue Apr 21, 2018

myitcv added a commit to myitcv/gopherjs that referenced this issue Apr 22, 2018

myitcv added a commit to myitcv/gopherjs that referenced this issue Apr 22, 2018

myitcv added a commit to myitcv/gopherjs that referenced this issue May 4, 2018

myitcv added a commit to myitcv/gopherjs that referenced this issue Jul 5, 2018

@dmitshur dmitshur closed this in #864 Oct 4, 2018

dmitshur added a commit that referenced this issue Oct 4, 2018

CI: Upgrade to CircleCI 2.0. (#864)
This is a minimal diff change to upgrade from CircleCI 1.0 to 2.0
and get it working, since 1.0 has been EOLed. The goal was to keep
the config.yml file as simple as possible for now; we can consider
changes and enhancements to it as part of future work.

Remove os/user package from being tested, since it's failing in the
CircleCI 2.0 environment (see tracking issue #863).

Resolves #766.
Updates #797.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment