Skip to content
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

Update to support v1.1 api #83

Closed
wants to merge 11 commits into from
Closed

Update to support v1.1 api #83

wants to merge 11 commits into from

Conversation

atreat
Copy link

@atreat atreat commented Dec 21, 2016

  • [ y] Tests added
  • [~y ] All tests pass (left some pending)
  • [y] Branch is up to date and mergeable
  • [n] README and documentation updated

Changes

Updates to support Circle's v1.1 API. I also change the style a little such that the Project and Build objects are initialized and have instance methods instead of containing all static methods. This hopefully reduces the redundancy of passing the vcs_type, username, project_name and/or build_num parameters.

Verify

The specs have been updated to use the new style of Project and Build objects. I've marked some tests as pending as I'm getting "you must log in" responses that I believe are caused because the Circle TOKEN env variable needs to be updated.

I also will work on updating the README to give examples of new design, but wanted to open the PR and see if you'd be willing to merge this as a 1.1.0 release. Let me know if you'd like to move forward with this PR, and I'll update anything left outstanding.


@mtchavez
Copy link
Owner

Thanks for working on updating the gem for the new version of the CircleCI API. These changes are a little too invasive and will be a breaking update for previous versions. I had been meaning to get to cleaning up some of the classes since more configuration has been added over the years and it is getting a little dirty. I made a first pass at doing that in #85. The refactor in that pull request keeps existing functionality working and logs out deprecation warnings to preserve a better transition for people updating.

Using those base of changes I think adding in the new API versioning will be a little cleaner, hopefully. Going to close this one out unfortunately. Will get to the new version of the API soon. Thanks again.

@mtchavez mtchavez closed this Feb 19, 2017
@mtchavez mtchavez mentioned this pull request May 23, 2017
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants