CircleCI 2.0 will be switching file systems on Monday, December 11, 2017 from AUFS to BTRFS. After extensively testing performance we have found that any projects using heavy I/O operations should see a performance improvement without any action required. The underlying CPU is not changing and therefore your cache will not be impacted. We do not expect any projects to be negatively impacted by thi
In preparation for supporting more architecture types, we’ve introduced a new cache template key {{ arch }}. This is documented here: https://circleci.com/docs/2.0/caching/#using-keys-and-templates This is useful if you rely on cached binary dependencies that you’ve compiled as part of the build process. Such dependencies can have specific optimizations based on the CPU architecture they were comp
We have designed CircleCI 2.0 to provide faster build performance and give users greater control over their environments. Users have full control over their customized build environments and do not have to worry about their build environments being updated without their knowledge or becoming out of date. We utilize the power of Docker to provide our users the flexibility of creating customized env
I’ve had to push a number of builds to get a working 2.0 config on different projects. This trick has helped me to iterate faster. curl --user ${CIRCLECI_CLI_TOKEN}: \ --request POST \ --form config=@.circleci/config.yml \ --form notify=false \ https://circleci.com/api/v1.1/project/github/circleci/discourse/tree/master This assumes: CIRCLECI_CLI_TOKEN is available locally, and the CircleCI user as
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く