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

CircleCI Settings #102

Open
andreazangheri opened this issue Oct 14, 2018 · 14 comments
Open

CircleCI Settings #102

andreazangheri opened this issue Oct 14, 2018 · 14 comments

Comments

@andreazangheri
Copy link

andreazangheri commented Oct 14, 2018

Hello everyone!
CircleCI support page in the wiki page is not updated (404).
So I'm giving a temporary explanation for those struggling with setting up circle ci projects.

circleci-menu

@andreazangheri andreazangheri changed the title CircleCI Temp Workaround CircleCI Settings Oct 14, 2018
@jhirn
Copy link

jhirn commented Nov 20, 2018

My Circle project stopped updating recently for me and a teammate. I tried replacing the token with a fresh one but no matter what it just says my project is sleeping. Not sure if Circle is in the middle of updating something (thus the 404) but I'm up to date with the description here and still not getting any status updates.

@phoet
Copy link

phoet commented Dec 19, 2018

the circle support told me that those endpoints no longer exist:

Cormac O'Riordan (CircleCI) Nov 22, 04:44 PST

Thanks for your patience. The polling-project-status is no longer supported. There are a few options to get these statuses:

https://circleci.com/docs/2.0/enable-checks/
https://circleci.com/docs/2.0/status-badges/

Do let us know if you have other questions or if there's anything else we can assist with!
Cormac O'RiordanSupport Engineer @ CircleCI

i created a feature-request to get it back, feel free to vote: https://circleci.com/ideas/?idea=CCI-I-774

@mszyndel
Copy link

It is possible to still get the status but

  1. It user personal access token now
  2. Only responds in JSON

The endpoint is

https://circleci.com/api/v1.1/project/:vcs/:user/:project/tree/master?circle-token=api_key

where :vcs has to have a value of either github or bitbucket

@erikdoe
Copy link
Member

erikdoe commented Dec 20, 2018

Is the JSON response structured in the same way as the old XML-based format or do they use new field names and values, too? If you have access to a CircleCI build, I'd appreciate it if you could post a sample response here.

@mszyndel
Copy link

@erikdoe oh wow, thanks for a quick response. Here is, slightly sanitized, response

[ {
  "compare" : "https://github.com/user/project/compare/ee6dd61f7792...c90b11921995",
  "previous_successful_build" : {
    "build_num" : 1607,
    "status" : "success",
    "build_time_millis" : 410462
  },
  "build_parameters" : null,
  "oss" : false,
  "committer_date" : "2018-12-20T09:05:47+01:00",
  "body" : "",
  "usage_queued_at" : "2018-12-20T08:14:47.907Z",
  "fail_reason" : null,
  "retry_of" : 1607,
  "reponame" : "reponame",
  "ssh_users" : [ ],
  "build_url" : "https://circleci.com/gh/user/project/1609",
  "parallel" : 1,
  "failed" : false,
  "branch" : "master",
  "username" : "user",
  "author_date" : "2018-12-20T09:05:47+01:00",
  "why" : "retry",
  "user" : {
    "is_user" : true,
    "login" : "username",
    "avatar_url" : "https://avatars3.githubusercontent.com/u/12345?v=4",
    "name" : "First name Last name",
    "vcs_type" : "github",
    "id" : 12345
  },
  "vcs_revision" : "c90b11921995906478fe6dea00fe21d41e854a09",
  "vcs_tag" : null,
  "build_num" : 1609,
  "infrastructure_fail" : false,
  "committer_email" : "[email protected]",
  "has_artifacts" : true,
  "previous" : {
    "build_num" : 1607,
    "status" : "success",
    "build_time_millis" : 410462
  },
  "status" : "success",
  "committer_name" : "First name Last name",
  "retries" : null,
  "subject" : "commit msg",
  "vcs_type" : "github",
  "timedout" : false,
  "dont_build" : null,
  "lifecycle" : "finished",
  "no_dependency_cache" : false,
  "stop_time" : "2018-12-20T08:20:24.164Z",
  "ssh_disabled" : true,
  "build_time_millis" : 334576,
  "picard" : {
    "build_agent" : {
      "image" : "circleci/picard:0.1.1250-22bf9f5d",
      "properties" : {
        "build_agent" : "0.1.1250-22bf9f5d",
        "executor" : "docker"
      }
    },
    "resource_class" : {
      "cpu" : 2.0,
      "ram" : 4096,
      "class" : "medium"
    },
    "executor" : "docker"
  },
  "circle_yml" : {
    "string" : "whole lotta secret stuff in json format"
  },
  "messages" : [ ],
  "is_first_green_build" : false,
  "job_name" : null,
  "start_time" : "2018-12-20T08:14:49.588Z",
  "canceler" : null,
  "all_commit_details" : [ {
    "committer_date" : "2018-12-20T00:42:16+01:00",
    "body" : "",
    "branch" : "master",
    "author_date" : "2018-12-20T00:42:16+01:00",
    "committer_email" : "[email protected]",
    "commit" : "6c832597973786dcb15f72614b22284247be5217",
    "committer_login" : "username",
    "committer_name" : "First name Last name",
    "subject" : "deploy from master",
    "commit_url" : "https://github.com/user/project/commit/6c832597973786dcb15f72614b22284247be5217",
    "author_login" : "username",
    "author_name" : "First name Last name",
    "author_email" : "[email protected]"
  }, {
    "committer_date" : "2018-12-20T09:05:47+01:00",
    "body" : "",
    "branch" : "master",
    "author_date" : "2018-12-20T09:05:47+01:00",
    "committer_email" : "[email protected]",
    "commit" : "c90b11921995906478fe6dea00fe21d41e854a09",
    "committer_login" : "username",
    "committer_name" : "First name Last name",
    "subject" : "commit msg",
    "commit_url" : "https://github.com/user/project/commit/c90b11921995906478fe6dea00fe21d41e854a09",
    "author_login" : "username",
    "author_name" : "First name Last name",
    "author_email" : "[email protected]"
  } ],
  "platform" : "2.0",
  "outcome" : "success",
  "vcs_url" : "https://github.com/user/project",
  "author_name" : "First name Last name",
  "node" : null,
  "queued_at" : "2018-12-20T08:14:47.936Z",
  "canceled" : false,
  "author_email" : "[email protected]"
}]

@mszyndel
Copy link

mszyndel commented Dec 20, 2018

The response includes a number of previous builds for a branch (30?). Certain properties could be looked up from subsequent elements in the array of builds. The attributes needed for ccmenu could be

name: reponame?
activity: status
lastBuildStatus: previous.status or second build in the array status
lastBuildLabel: previous.build_num? second build in the array build_num or subject
lastBuildTime: second build in the array queued_at or start_time or stop_time
nextBuildTime: not available?
webUrl: build_url

@phoet
Copy link

phoet commented Dec 20, 2018

@erikdoe is this going to be a christmas gift? 😸

@kornysietsma
Copy link

I'm confused - I have cirleCI working with the URL:
https://circleci.com/cc.xml?circle-token=my_api_token
and then I can select one of my watched projects to view. Is that sufficient for people's needs?

@phoet
Copy link

phoet commented Jan 25, 2019

@kornysietsma true, that works with your personal api-token. i used to do that the same way.

@johnnylai
Copy link

@kornysietsma thx for the tip. It works for me. But this seems to only work with the default branch for a repo. It seems not able for user to select which branch they want to watch.

Still, thanks for the info.

@erikdoe
Copy link
Member

erikdoe commented Apr 25, 2019

We're in the process of migrating these wiki pages to a website on the cctray format: https://github.com/build-canaries/cctray

It would be fantastic if someone could write up the current approach to making CCMenu work with CircleCI and add this via a pull request over there.

@sikachu
Copy link

sikachu commented May 3, 2019

I'm glad I found this issue! I really didn't know that personal /cc.xml exists!

I opened build-canaries/cctray#10 which updates the documentation regarding how to setup CCMenu/CCTray to use this instead.

Thank you again for this amazing project!

@ospfranco
Copy link

Hey, I've been using:

https://circleci.com/cc.xml?circle-token=my_api_token

For quite some time, but it no longer is enough for my workflow, I need to monitor more than one branch in the project, is there any other possible way to make per branch configurations work?

https://circleci.com/gh/user/project/tree/branch.cc.xml?circle-token=your_token

@hubertjakubiak
Copy link

@ospfranco Any update in 2021 how to dynamically monitor my branches? Did you find another way to achieve that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants