Bitbucket Pipelines のインフラストラクチャの変更

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

このページは Bitbucket Pipelines に対する内部インフラストラクチャの変更を追跡します。これがユーザーのビルドに影響することはほとんどありません。

January 2023 - Kubernetes cluster upgrades

Starting on January 30th, we will be progressively rolling out a container runtime upgrade from containerd-v1.5.13 to containerd-v1.6.11 as well as an upgrade to our Kubernetes cluster to upgrade the Ubuntu AMI's Linux kernel version from 5.15.0-1026 to 5.15.0-1028. These changes should be unnoticeable to users.

December 2022 - Kubernetes cluster upgrades

Starting on December 20th, we will be progressively rolling out an upgrade to our Kubernetes cluster to upgrade the Ubuntu AMI's Linux kernel version from 5.15.0-1023.27 to 5.15.0-1026.30. This change should be unnoticeable to users.

December 2022 - Kubernetes cluster upgrades

Starting on December 07th, we will be progressively rolling out some minor patches to our Kubernetes cluster, kernel version would still be 5.15.0-1023.27. This change should be unnoticeable to users.

November 2022 - Kubernetes cluster upgrades

Starting on November 29th, we will be progressively rolling out an upgrade to our Kubernetes cluster which upgrades the Ubuntu AMI’s Linux kernel version from 5.15.0-1022.26 to 5.15.0-1023.27. This change should be unnoticeable to users.

November 2022 - Kubernetes cluster upgrades

Starting on November 9th, we will be progressively rolling out a security upgrade to the network fabric of our Kubernetes cluster. This change should be transparent to users.

October 2022 - Kubernetes cluster upgrades

Starting on October 31st, we will be progressively rolling out an upgrade to our Kubernetes cluster which upgrades the Ubuntu AMI’s Linux kernel version from 5.15.0-1020 to 5.15.0-1022. This change should be unnoticeable to users.

October 2022 - Kubernetes cluster upgrades

Starting on Oct 6th, we will be upgrading our Kubernetes cluster AMI kernel from 5.15.0-1019.23 to 5.15.0-1020.24 for all customers. This change should be transparent to users.

September 2022 - Kubernetes cluster upgrades

Starting on September 26th, we will be upgrading our Kubernetes cluster from v1.21.8 to v1.22.13 for all customers. This change should be transparent to users.

September 2022 - Docker in Docker service upgrade

Starting on September 23rd, we will be progressively rolling out an update to the Pipelines Docker in Docker service and an upgraded version of the Docker client for running docker commands from 20.10.15 to 20.10.18. For details of the security and bug fixes between these docker versions, visit: Docker Docs — Docker Engine release notes.

September 2022 - Kubernetes cluster upgrades

Starting on September 14thwe will be progressively rolling out an upgrade to our Kubernetes cluster to upgrade the Ubuntu AMI's Linux kernel version from 5.15.0-1017.21 to 5.15.0-1019.23. This change should be unnoticeable to users.

August 2022 - Kubernetes cluster upgrades

Starting on August 31stwe will be progressively rolling out an upgrade to our Kubernetes cluster which upgrades the Ubuntu AMI’s Linux kernel version from 5.15.0-1015.19 to 5.15.0-1017.21. This change should be unnoticeable to users.

August 2022 - Kubernetes cluster upgrades

Starting on August 1stwe will be progressively rolling out an upgrade to our Kubernetes cluster which upgrades the Ubuntu AMI’s Linux kernel version from 5.13.0.1031.35 to 5.15.0-1015.19. This change should be unnoticeable to users.

July 2022 - containerd version upgrade

Starting on July 26th, we will be upgrading containerd on the Kubernetes nodes from v1.5.11 to v1.5.13. This change should be unnoticeable to users.

July 2022 - Kubernetes cluster upgrades

Starting on 4th July, we will be progressively rolling out an upgrade to our Kubernetes cluster which upgrades the Ubuntu AMI’s Linux kernel version from 5.13.0.1022.24 to 5.13.0.1031.35. This change should be unnoticeable to users.

June 2022 - Git client upgrade

Starting on June 29th, we will be progressively rolling out an upgrade to Git (2.15.4 to 2.36.1) and Git LFS (2.13.2 to 3.1.4) used when cloning the repository during build setup. For runners users, during the rollout, they may notice the tag of the agent-setup image from prod-stable to stg-stable and switch back to prod-stable at the completion of the rollout. This upgrade does not require any changes from customers except Git LFS users. Users of Git LFS may experience pipeline failures. For information on this issue, visit: 'pre-push hook already exists' error.

June 2022 - Docker in Docker service upgrade

Starting on June 20th, we will be progressively rolling out BuildKit for the Pipelines Docker in Docker service. For details on BuildKit, visit: Docker Docs — Build images with BuildKit.

June 2022 - Docker client upgrade

Starting on June 13th, we will be incrementally rolling out an upgraded version of the Docker client available for running docker commands from v19.03.15 to v20.10.15. For more information about this upgrade, see the Bitbucket Pipelines: Docker client upgrade post.

May 2022 - containerd version upgrade

Starting on May 31st, we will be upgrading containerd on the Kubernetes nodes from v1.5.10 to v1.5.11. This change should be unnoticeable to users.

May 2022 - Kubernetes cluster upgrade

Starting on May 24th, we will be progressively rolling out an upgrade to our Kubernetes cluster which upgrades the Linux kernel to a newer patch version (5.13.0.1022). This change should be unnoticeable to users.

May 2022 - Docker in Docker service upgrade

Starting on May 23rd, we will be progressively rolling out an update to the Pipelines Docker in Docker service from version 20.10.6 to 20.10.15. For details of the security and bug fixes between these docker versions, visit: Docker Docs — Docker Engine release notes.

April 2022 - containerd version upgrade

Starting on April 4th, we will be upgrading containerd on the Kubernetes nodes from v1.5.8 to v1.5.10. This change should be transparent to users.

March 2022 - Kubernetes cluster upgrade

Starting on March 28th, we will be progressively rolling out an upgrade to our Kubernetes cluster which upgrades the Linux kernel from version 5.11 to 5.13. This change should be transparent to users. If you are running behind a corporate firewall and haven’t recently allowlisted pipelines IP addresses, you can review these at What are the IP addresses to configure a corporate firewall?

February 2022 - Docker in Docker service upgrade

Starting on February 22, we will be progressively rolling out an update to the Pipelines Docker in Docker service from version 20.10.5 to 20.10.6. This contains a fix that will validate Dockerfiles containing Buildkit directives which are not yet supported in Bitbucket Pipelines, causing pipelines to fail. If your pipeline contains any Buildkit directives, remove them and run the pipeline again.

February 2022 - Kubernetes cluster upgrade

Starting on February 15, we will be progressively upgrading our Kubernetes cluster from v1.20.11 to v1.21.8 for all customers. This change should be transparent to users. If you are running behind a corporate firewall and haven’t recently allowlisted pipelines IP addresses, you can review these at What are the IP addresses to configure a corporate firewall?

December 2021 - Kubernetes cluster upgrades

Starting 13th December, will be upgrading our Kubernetes infrastructure operating system from Flatcar to Ubuntu. This involves a kernel upgrade from 5.4.92 to 5.11.0, and will be rolled out progressively. We expect this change to be transparent for users.

December 2021 - New outbound IP Addresses

On 8th December 2021, new IP addresses were provisioned for our build infrastructure, allowing for improved resiliency in our Kubernetes infrastructure. These addresses will become active in the next six weeks.

Refer to What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall? for the updated listing of outbound IPs.

November 2021 - containerd patch version upgrade

Starting on November 8, we will be upgrading containerd on the Kubernetes nodes from v1.5.0 to v1.5.7. This change should be transparent to users.

August 2021 - Kubernetes cluster upgrade

Starting on August 30, we will be upgrading our Kubernetes cluster from v1.19.7 to v1.20 for all customers. This change should be transparent to users. If you are running behind a corporate firewall and haven’t recently allowlisted pipelines IP addresses, you can review these at What are the IP addresses to configure a corporate firewall?

August 2021 - Container runtimes upgrade

Starting on August 24th, we will be rolling out an upgraded version of runc1.0.0-rc10 to runc1.0.0-rc95 and containerd1.4.3 to containerd1.5.0. For more information about this upgrade, see the Bitbucket Pipelines: containerd and runc upgrades community post.

May 2021 - Flatcar OS upgrade rollback

After the upgrade to Kubernetes FlatcarOS v2765.2.2, we detected errors with Ruby/Rails failing with ActiveStorage::IntegrityError and yarn builds hanging. Because of this, we are rolling back to Kubernetes FlatcarOS v2605.12.0.

May 2021 - Flatcar OS upgrade

Starting on May 4th, we will be upgrading our Kubernetes FlatcarOS to v2765.2.2 for all customers. This change should be transparent to users.

March 2021 - containerd minor version upgrade

Starting on March 29th, we will be upgrading containerd on the Kubernetes nodes from v1.3.9 to v1.4.3. Within this latest version upgrade, containerd ended support for certain versions of some old images, like python:3.5.1 and redis:2.8.23. Update to the latest version to fix any issues.

March 2021 - Kubernetes cluster upgrade

Starting on March 1st, we will be upgrading our Kubernetes cluster from v1.18.0 to v1.19.7 for all customers. This change should be transparent to users. If you are running behind a corporate firewall and haven’t recently allowlisted pipelines IP addresses, you can review these at What are the IP addresses to configure a corporate firewall?

February 2021 - Runtime environment migration to Kata Container

Starting on March 1st, we will be rolling out the migration from Docker & Containerd to Kata Container lightweight virtual machines for increased isolation and security of customer workloads to our Standard and Premium Bitbucket Cloud customers. Any users on a Free plan have already been migrated. This change should be transparent to users.

February 2021 - Flatcar OS upgrade

Starting on February 17th, we will be upgrading our Kubernetes FlatcarOS to v2605.12.0 for all customers. This change should be transparent to users.

February 2021 - Git LFS client upgrade

As of February 2021, we upgraded the Git LFS client from version 2.6.0 to 2.13.2. This change should be transparent to users.

February 2021 - Changes in docker’s daemon

Starting on February 3rd, we will be incrementally rolling out an upgraded version from 19.03.13 to 19.03.15.

January 2021- FlatcarOS upgrade

Starting on January 27th, we will be upgrading our Kubernetes FlatcarOS to v2605.10.0 for all customers. This change should be transparent to users.

January 2021 - containerd minor version upgrade

Starting on January 20th, we will be upgrading containerd on the Kubernetes nodes from v1.3.4 to v1.3.9.

January 2021 - Kubernetes cluster upgrade

Starting on January 20th, we will be upgrading our Kubernetes cluster from v1.17.9 to v1.18.10 for all customers. This change should be transparent to users. If you are running behind a corporate firewall and haven’t recently allowlisted pipelines IP addresses, you can review these at What are the IP addresses to configure a corporate firewall?

December 2020 - Kubernetes cluster added

We’ve added a new Kubernetes cluster to run builds across some pipelines. This change should be transparent to users. If you are running behind a corporate firewall and haven’t recently allowlisted pipelines IP addresses, you can review these at What are the IP addresses to configure a corporate firewall?

November 2020 - Kubernetes node OS upgrade

Starting on November 11th, we will be rolling out an upgraded version of the operating system that our Kubernetes build nodes run. This involves a change of Linux kernel versions from 4.19.143 to 5.4.72. This change should be transparent to users.

November 2020 - Changes in docker’s daemon

Starting on November 2nd through November 10th, we will be incrementally rolling out an upgraded version from 18.09.9 to 19.03.13.

September 2020 - Changes in docker’s daemon

The docker daemon version used in the docker service has been upgraded from 18.09.1 to the latest 18.09.9

September 2020 - changes to docker in docker container filesystem permissions

Starting on 2nd September the docker in docker container's root filesystem will be read-only except for the directories required to use docker in order to harden security. The BITBUCKET_CLONE_DIR and its subdirectories, any other volumes you create, will remain writable.

2020 年 4 月 - containerd マイナー バージョン アップグレード

4 月 22 日より、Kubernetes ノードの containerd が 1.2.x から 1.3.4 にアップグレードされました。

4 月 29 日より、per-container shim ではなく per-pod shim を使用するために containerd-shim-runc-v2 に切り替えます。

November 2019  - Kubernetes cluster upgrades

Starting on 20th November, we will be progressively rolling out Kubernetes cluster upgrades to all customers. This change should be transparent to users. If you are running behind a corporate firewall and haven’t recently allowlisted pipelines IP addresses, you can review these at What are the IP addresses to configure a corporate firewall?

August 2019  - containerd runtime changes on nodes

Starting from August 7th, the nodes in our kubernetes build cluster will be changed to run with containerd rather than docker. The change should be transparent to most Bitbucket Pipelines users.
Update August 9th: We've identified 2 issues with the rollout:

  • Users with docker images hosted on outdated Sonatype Nexus instances will have trouble pulling images via  containerd. Please file a support ticket at https://support.atlassian.com/ja/contact to be excluded from the migration and consider upgrading the Nexus instance (see https://issues.sonatype.org/browse/NEXUS-12684).

  • Users with private docker images hosted on bintray.com will experience 401 Unauthorized response with containerd. We've identified the issue to be with the provider and are communicating with them on resolution. Please file a support ticket to be excluded from the containerd until the issue is resolved using the following link https://support.atlassian.com/ja/contact.

2019 年 4 月 - SSH キー スキャンをビルド環境内から実行

2019 年 4 月 17 日以降、SSH キー スキャンはビルド環境内から実行されるようになります。つまり、この機能を引き続き使用するには、Bitbucket Pipelines ビルド環境の有効な IP アドレスを許可リストに追加する必要があります。Bitbucket Pipelines サービス で使用されている IP アドレスを許可リストに登録する必要はありません。

See What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall? for details.

2018 年 10 月 - 新しい発信 IP アドレス

2018 年 11 月 8 日以降、Bitbucket Pipelines サービス (アトラシアンのビルド インフラとは異なる) で新しい IP アドレスが使用されます。

See What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall? for details.

2018 年 9 月 - Docker の変更 - Docker ユーザー ネームスペース再マッピング

On 27th September 2018, we rolled out a change to enable user namespace remapping in our docker in docker daemon we provide to users as part of a steps execution to harden the security of pipelines.

2018 年 9 月 - 新しい発信 IP アドレス

2018 年 9 月 12 日、アトラシアンの Kubernetes インフラストラクチャ内で将来マルチリージョン フェイルオーバーを提供するために、ビルド インフラストラクチャに新しい IP アドレスを割り当てました。これらのアドレスは、今後 2 週間以内にアクティブになります。

See What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall? for details.

2018 年 8 月 - EC2 M5d インスタンス タイプへの移行によるパフォーマンスの改善

2018 年 8 月 1 日、Kubernetes ノードを EC2 M4 インスタンスから M5d に変更しました。M5d インスタンスは EBS ボリュームではなく NVMe ドライブを使用します。このドライブははるかに高速で、基盤となるコンピューティング ハードウェア上に存在しているため、ドライブ上でストレージ ネットワークを介してデータを転送する際のオーバーヘッドは発生しません。

2018 年 3 月 - 新しい発信 IP アドレス

2018 年 3 月 15 日、アトラシアンのビルド インフラストラクチャに新しい IP アドレスがプロビジョニングされました。これらのアドレスは、今後 2 週間以内にアクティブになります。

See What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall? for details.

2017 年 11 月 - Docker がサービスに追加 (1 GB のメモリ制限)

On 28 November 2017, as part of implementing docker-run support in Pipelines, we now treat Docker as a Pipelines service. This means commands executed via Docker will have a memory limit of 1 GB, and builds that enable Docker can only use two additional services per build step.

There are a very small number of existing builds that use three services and have Docker enabled that will break with this change. We have directly notified customers who have recently run builds with this configuration.

Our recommendation is to either stop running one of your services or change one service to run using "docker run" instead (see Run Docker commands in Bitbucket Pipelines). Docker run support will also give you the flexibility to start multiple Docker containers in the same build, including via docker-compose files.

2017 年 10 月 - 新しい発信 IP アドレス

2017 年 25 日、アトラシアンのビルド インフラストラクチャに新しい IP アドレスがプロビジョニングされました。

See What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall? for details.

2017 年 9 月 - Docker のアップグレード

2017 年 9 月 7 日、Pipelines ビルド コンテナに提供される Docker デーモンを 1.12.6 から 17.05 に更新しました。

Please see this ticket for more details: https://bitbucket.org/site/master/issues/14333/upgrade-docker-for-multi-stage-builds

2017 年 2 月 - 新しいインフラストラクチャ

As of February 2017, we're rolling out changes to Pipeline's build infrastructure to provide a foundation for upcoming new features. Pipelines still executes your scripts in an isolated Docker container, and most people won't notice any change in behavior.

以下の図のように、一部のユーザーに影響する可能性がある、軽微な変更があります。

ご利用のインフラストラクチャが新しいものかどうかを確認する方法

インフラストラクチャが更新されたものかどうかは、ログ ファイルで確認できます。一番上の "Build setup" セクションが大幅に短くなり、docker run コマンドが除外されるようになりました。

次のように、ログ ファイルの "Build setup" セクションに docker run コマンドが表示される場合、お使いのインフラストラクチャは古いものです。

変更内容

スクリプトは、インタラクティブなシェルでは実行されなくなりました

Pipelines は引き続き、.bashrc ファイルをインタラクティブな非ログイン シェルで実行しているかのように実行しますが、非インタラクティブ シェルとして動作するようになりました。この変更は、stdin を使用するスクリプトや、インタラクティブなシェルとの依存関係があるスクリプトに、影響する可能性があります。このような場合、スクリプトを更新して、非インタラクティブに実行するように変更することをおすすめします。

これにより、Bitbucket Pipelines の使用をさまざまな方法で向上させられるようになりました。

  • ユーザー入力を待機するコマンドは、入力を待機する間にビルドをハングさせるのではなく、直ちに終了してビルドを失敗させるようになります。

  • Some tools, such as Git and Maven, display download progress indicators in an interactive terminal. Now that builds non-interactively, many tools will no longer log verbose progress indicators, streamlining your Pipelines log output.

無効な名前の環境変数がビルド コンテナに渡されなくなりました

無効な変数が新しく作成されるのを防ぐため、Pipelines では 2016 年 11 月から変数に対して有効な C 識別子 (一致する regex /[A-Za-z_][A-Za-z0-9_]*/) を要求するようになりました。ただし、古い無効な変数を構成しているお客様は現在でも少数います。

最近のインフラストラクチャの変更では、無効な名前の変数は、ビルド コンテナに渡されなくなります。無効な名前で作成された新しい変数を使用するには、これらの変数に依存するスクリプトを更新する必要があります。

公開 IP アドレス

These infrastructure changes mean we can now publish IP addresses for Bitbucket Pipelines. You'll want to know these addresses if you want to provide Pipelines access into your AWS VPC or corporate firewall by adding them to an allowlist, for example.

See What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall? for the Bitbucket and Pipelines public IP addresses.

パブリック IP アドレスは将来変更される場合があります。

最終更新日: 2023 年 1 月 29 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.