Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
CircleCI PoC #294
This is what running the build on CircleCI might look like. If you look at my fork there are a couple cool things.
This allows us to make a nice report for "broken" things in linkcheck here: https://3-108794746-gh.circle-artifacts.com/0/home/circleci/project/_build/linkcheck/broken.txt
And we can see the entire build HTML which could be useful for previewing the state of the project at a specific commit: https://3-108794746-gh.circle-artifacts.com/0/home/circleci/project/_build/html/index.html
*note: linkcheck does not fail the build even though it has failures because the command that is run is
Hi Brett, You get 4 builders total for any open source project. (Where open source is any public project).…
Sent from my iPhone
On Nov 2, 2017, at 10:53 AM, Brett Cannon ***@***.***> wrote: The issue with Circle CI is we get a single builder for the entire Python organization. That means your 1 minute build time won't start in 1 minute if another project starts using it. While with Travis we have I think 20 builders across the organization. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Thanks to @levlaz for the Proof of Concept PR.
The conversation about CircleCI and workflow has moved to the core-workflow mailing list.
As an FYI, I have been happily using CircleCI alongside Travis on JupyterHub development for the past 2 years.
Currently, I'm going to close this Proof of Concept PR, and after additional discussion on the core-workflow mailing list, we can submit a formal PR, if needed.
Thanks. - Carol