CircleCI Blog

Circle-CI (https://circleci.com/) have a macos system for building things like xcode projects. I've not tried it myself but it's cloud based which saves self hosting. Unless you want to self-host in which case this may not be a great option.

Thoroughly agree that this is a human problem, but I think there are some amazing automated fixes for it, by incorporating code checkers into the continuous integration pipeline. Take a look at how the CII best practices badgeapp [0] uses pronto [1] to run rubocop [2] automatically for free via CircleCI [3] and surface those results via the Github Status API and email. The whole point is to avoid having to manually complain in a code review. Instead, code reviews become a much higher level exercise discussing proper APIs and code structuring, not sphaghetti issues. [0] https://github.com/linuxfoundation/cii-best-practices-badge/commit/9da… [1] https://github.com/mmozuras/pronto [2] https://github.com/bbatsov/rubocop [3] https://circleci.com/

CircleCI (https://circleci.com/) I add this to every new project. Best cloud-based continuous integration platform I've used so far. Sane intelligent defaults, many projects start building out of the box. You can easily link it to Slack (another piece of reliable software) and start getting continuous feedback that your project is working correctly / is getting deployed - as it is being built.

This is a pretty good time to reflect on how reliable Github has become recently. A year ago, GitHub was going down regularly from DDoS. I know because I was on pagerduty for https://circleci.com, and often had to wake up to respond to issues. In the last 6-9 months, GitHub has been pretty flawless, and issues are solved almost immediately. Great job guys, the hard work you put into improving your architecture shows!

This is a great approach, but detecting the user-agent is the wrong way to decide if you should pre-render the page. If you include the following meta tag in the header: <meta content="!" name="fragment"> then Google will request the page with the "_escaped_fragment_" query param. That's when you should serve the pre-rendered version of the page. Google has documentation on this here: https://developers.google.com/webmasters/ajax-crawling/docs/html-snaps… and we've been using this method at https://circleci.com for the past year. Waiting for google to request the page with _escaped_fragment_ should also prevent you from getting penalized for slow load times or showing googlebot different content.

CircleCI is an awesome service that has made testing and continuous integration significantly easier for our small dev team. Highly recommended! https://circleci.com/

I love Travis as well and use it on a lot of open-source projects I'm a contributor to, but I've been using CircleCI for private repos so far and really love what they do. I'd absolutely recommend checking it out: https://circleci.com/ It'll be interesting to see how the hosted CI market takes off - I thought CloudBees was going after it for awhile, but it seems they haven't pushed too hard, while there have been a lot of new entrants over the past year. Good time to be a developer, that's for sure.

CircleCI: SF or REMOTE fulltime (near pacific time), frontend, backend engineers and patio11-style marketing engineers. At CircleCI (https://circleci.com), we're building Heroku for Continuous Integration. We have traction and revenue (and funding!). Our customers love us, because we move quickly and provide amazing support. All employees talk to customers and are on support rotation. We eat our own dogfood, DevOps, A/B test, do Continuous Deployment and Customer Development. We're still a small team, so you'll have a large impact on company culture. We're highly influenced by Valve's Employee handbook. SF-local employees have catered lunch every day. The frontend is a fat javascript client, using HamlCoffee, Less and Knockout. We have a lot of interesting design and data-visualization problems that need to be solved, as well as A/B testing, landing page creation and funnel optimization. The backend is written in Clojure. Backend engineers should know Clojure or another 'weird' language (Haskell, Scala, Scheme, etc), and Linux Devops (C compilation model, make, packaging). Contact us at [email protected]. Include samples of awesome stuff you've done.

Debug with SSH(1) is still one of our (CircleCI) most loved and praised features. I really believe that these little QoL features can make a world of difference for sw developers and engineers, and this stays a strong focus for us. 1: https://circleci.com/docs/guides/execution-managed/ssh-access-jobs/ (Disclaimer: i work at CircleCI)

Everyone is free to use alternative CI/CD workflow pipelines. These are often better than Github Actions. These include - https://circleci.com/ - https://www.travis-ci.com/ - Gitlab Open source: - https://concourse-ci.org/ (discussed in the context of Radicle here https://news.ycombinator.com/item?id=44658820 ) - Jenkins -etc. Anyone can complain as much as they want, but unless they put the money where their mouth is, it's just noise from lazy people.

Yes, they happened in the past. Over 3 years back. Times change. You can use this and crenedials rotation, amazing, I know... https://docs.github.com/en/code-security/secret-scanning/about-secret-… https://docs.gitlab.com/ee/user/application_security/secret_detection/ https://circleci.com/blog/detect-hardcoded-secrets-with-gitguardian/ https://www.gitkraken.com/media/events/azure-spring-clean-2022 edit: used config/secrets management for as long as I can remember doing this cloud stuff (several years), so the excuses are very, very poor imho.

It appeals to me as someone who likes Circle's CI offering but wants to move away from Github. I tried using Gitlab's CI and was surprised at how limited it was. The Gitlab CI syntax was harder to follow, and my integration tests took 17m to run when they ran in almost 1/3 the time on Circle. A big part of the problem was that CircleCI lets me use an instance with 8 CPUs / 16 GB RAM with just a config file change[0], whereas every Gitlab instance is 1 CPU / 3.75 GB RAM unless you host your own runners.[1] But if I'm paying a company to manage CI, I don't want to provision my own hardware infrastructure [0] https://circleci.com/docs/configuration-reference#docker-execution-env… [1] https://docs.gitlab.com/ee/ci/runners/saas/linux_saas_runner.html

Not sure if it is still the case, but Circle used Clojure/Om [1]... when I heard them say they did that so many years ago, I knew right away it would end up being something nobody wanted to work on. Sure enough, just checked, Om was abandoned [2] and the person blogging about how great everything was is long gone [3]. This is the absolute definition of tech debt. [1] https://circleci.com/blog/how-circleci-processes-4-5-million-builds-pe… [2] https://github.com/omcljs/om [3] https://circleci.com/blog/why-we-use-om-and-why-were-excited-for-om-ne…

It's a unfinished work. But It already run in following engines: - gitlab-ci: https://gitlab.com/rosiney.gp/mkdkr/commits/master - actions: https://github.com/rosineygp/mkdkr/actions - travis: https://travis-ci.org/rosineygp/mkdkr - circle-ci: https://circleci.com/gh/rosineygp/mkdkr/tree/master The bagdes on README.md show it. Except for gitlab, you have to write your on .yaml by hand. I not finished the exporters/generators. After write your Makefile, integrated with a engine isn't a big problem. Take a look at .travis.yml, .gitlab-ci.yml, .circleci/config.yml and .github/workflows/main.yml they are very similar and dumb, just call all jobs resolved in Makefile.

i follow stackoverflow's definition https://stackoverflow.blog/2017/02/08/means-remote-first-company/ but i recently read circleci's blogpost on remote first, and it's really good too https://circleci.com/blog/what-almost-failing-the-gre-taught-me-about-…

In regards to needing CI, it appears your project is open sourced. Both Travis [1] and CircleCI [2] both have free tiers for open source projects, worth a look! [1]: https://travis-ci.com/plans [2]: https://circleci.com/pricing/ Edit: Add in links

https://travis-ci.org/, https://circleci.com/ are free for public open source projects. They come with databases pre-installed (or easy to add with one line). You can set configuration values via the user-interface which get added to a build and aren't public.

Just signed up and discovered a vulnerability. Thanks! A quick suggestion, consider adding a full sample configuration along with your config docs: https://pyup.io/docs/configuration/ It's a lot easier to see how it all sits together with a sample. CircleCI has a great example: https://circleci.com/docs/1.0/config-sample/

Great tidbit. Perhaps it's just not well known. Edit: Multiple machines if your build is in parallel. Nice. > Parallelism and SSH Builds > If your build has parallel steps, we launch more than one VM to perform them. Thus, you’ll see more than one ‘Enable SSH’ and ‘Wait for SSH’ section in the build output. [1]: https://circleci.com/docs/ssh-build/#parallelism-and-ssh-builds

So he basically followed it's the future story? (https://circleci.com/blog/its-the-future/)

For what it's worth, CircleCI is going all-in on containers: https://circleci.com/blog/say-hello-to-circleci-2-0/

This is insightful. Of course, the OP is consciously playing off the earlier app-deployment spoof (https://circleci.com/blog/its-the-future/). But this earlier spoof may well be based, intentionally or not, on the SOAP piece you linked -- which was a hit on HN 7 years ago (https://news.ycombinator.com/item?id=2079631). Thus prompting the observation and related question: These three areas - front-end, deployment, RPC - seem to have engendered a churn in standard approaches, and a corresponding cultish devotion to certain toolkits -- leaving them open for satire. But yet, there is also a need for a guru to explain WTF to do, because a lot of practitioners need to get these jobs done. So, what is the deeper parallel between the areas? E.g., a lot of corporate resources suddenly poured into these problems, and everyone is funded to come up with, and promote, their own solution?

Please also read the followup (https://circleci.com/blog/it-really-is-the-future/). I read both articles a year ago and it really helped me grasp the whole container movement.

I completely agree and I wish we could have the best of both worlds. I love Clojure and I love the compiler support with static typing in other languages. Clojure attempted to add static typing with the core.typed projects, but high-profile exits [0] from that framework have made clear that this is a problem that can only properly be implemented at the language level. If I could have a lisp with static types, I might not use anything else again. [0] https://circleci.com/blog/why-were-no-longer-using-core-typed/

Are you referring to continuous integration? Cont delivery? Just stacks? If you're referring to some platforms.. CircleCI http://circleci.com as a continuous integration and deployment platform - they automate the build, test, and deploy process. LaunchDarkly http://launchdarkly.com if you're looking to feature flag your builds and automate rollouts. Gradle http://gradle.org is an open source build automation system that builds upon the concepts of Apache Ant and Apache Maven and introduces a Groovy-based domain-specific language (DSL) instead of the XML form used by Apache Maven of declaring the project configuration.

Love that podcast. I'll check it out later today, thanks. About core.typed, just be aware that it comes with its own set of issues[0]. I've been down that road and it wasn't great. [0] http://blog.circleci.com/why-were-no-longer-using-core-typed/

The team at circleci actually wrote some great blog posts about this. First, a tongue-in-cheek post highlighting the question you're asking here: http://blog.circleci.com/its-the-future/ Followed by a post answering this question: http://blog.circleci.com/it-really-is-the-future/

I've been using it in production for a number of applications for about 6 months now and haven't seen any performance issues. Prismatic http://getprismatic.com/ and CircleCI https://circleci.com/ both use ClojureScript for their front-ends. CircleCI open sourced their front-end here https://github.com/circleci/frontend/tree/master/src-cljs/frontend as you can see it's a decent size app, and Prismatic have blogged about Om and performance here http://blog.getprismatic.com/om-sweet-om-high-functional-frontend-engi… In general, there should be very little overhead compared to regular JavaScript once the advanced compilation option is used.

Circle (https://circleci.com/) is also using Clojure. I usually ctrl-f through "Who's Hiring?" posts for Clojure out of curiosity and there are generally 3-6 companies each month. Most seem to be using Clojure in conjunction with other JVM languages like Scala or Java itself (Circle is an exception).

Storing a list of 1.7 million strings for us takes 70mb stored in memory. Testing for membership is an O(1) op. Very happy with it. We use mongo as a dumb data store as well as a bunch of other infrastructure tools, like http://circleci.com we could have only dreamt of years ago.