Announcing upcoming required maintenance for Bitbucket Pipelines

[#1]

Hi all,

We would like to inform our valued customers about the upcoming scheduled maintenance.

This maintenance is set to take place on March 9, 2025, from 20:00 UTC to 23:00 UTC. Please note that this maintenance will temporarily affect write access to Bitbucket Pipelines functionality. However, there will be no impact on read/browse access.

We will keep our StatusPage updated throughout the maintenance. To monitor progress and get notifications please visit and signup to get updates.

During the maintenance period, Bitbucket pipelines will operate in read-only mode. As a result, users may encounter brief interruptions when attempting to perform write operations. Examples of these operations include:

• Manually triggering a new pipeline
• Re-running a failed build
• Initiating a redeploy
• Registering a new self-hosted runner
• Modifying workspace or repository Pipelines admin settings

Automatically scheduled pipeline executions may experience delays of up to 30 minutes, and builds initiated just prior to the maintenance window might fail. We recommend rerunning any failed builds once the maintenance window has concluded.

During the maintenance window, any write attempts for pipelines operations via API will return the following message:

This repository is currently undergoing maintenance. Please try again later. Check status page for further information https://bitbucket.status.atlassian.com/ 

Note: During the scheduled maintenance, customers are not entitled to uptime SLA credit compensation as outlined in our legal agreement.

Thank you for your patience and understanding as we work to improve performance for all our customers.

Bitbucket Cloud team

[jpleteli]

Hello,

We would like to know the details of what will be done during the maintenance on March 9th. Can you publish it to inform our clients?

[Anna Carey]

Hi! Any chance you could give some details about what changed during the maintenance window? My pipeline is failing. I suspect it was a change on Bitbucket's end because rerunning previously successful pipelines fails.

An example from the test logs when running a node app.

```

> react-scripts test --env=jsdom

FAIL src/components/SingleClaim/Sections/CreditActivitiesSummary/CreditActivitiesSummary.test.tsx
● Test suite failed to run

Jest encountered an unexpected token

Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

By default "node_modules" folder is ignored by transformers.

Here's what you can do:
• If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
• If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
• To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
• If you need a custom transformation specify a "transform" option in your config.
• If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/configuration
For information about custom transformations, see:
https://jestjs.io/docs/code-transformation

Details:

/opt/atlassian/pipelines/agent/build/node_modules/axios/index.js:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import axios from './lib/axios.js';
^^^^^^

SyntaxError: Cannot use import statement outside a module

> 1 | import axios, { AxiosInstance } from 'axios';
| ^

````