What are bitbucket pipeline's advance filter ?

[Bikram Tuladhar]

There is a special tooltip in pipeline build time saying

```Advanced features used in this pipeline consumed extra build minutes.```

But I'm not using any 2x capacity, unable to find which special configuration triggers such a double billing time.

Here is my bitbucket pipeline yml

---

definitions:
services:
mysql:
image: mysql:5.7
environment:
MYSQL_DATABASE: 'xxxx'
MYSQL_ROOT_PASSWORD: 'xxx'
js-report:
image: jsreport/jsreport:2.11.0-full-patch1
ports:
- 5488:5488

caches:
admin: .temp_cache/admin
agent: .temp_cache/agent
agent-landing: .temp_cache/agent-landing
client: .temp_cache/client
client-landing: .temp_cache/client-landing
public: .temp_cache/public
admin-dev: .temp_cache/admin-dev
agent-dev: .temp_cache/agent-dev
agent-landing-dev: .temp_cache/agent-landing-dev
client-dev: .temp_cache/client-dev
client-landing-dev: .temp_cache/client-landing-dev
public-dev: .temp_cache/public-dev
steps:
- step: &copy-base
name: copy-base
script:
- ----redacted------
artifacts:
- .env

- step: &yarn
name: Yarn
image: node:16
caches:
- node
script:
- yarn
artifacts:
- node_modules/**
- package.lock.json
- .env

- step: &yarn-agent
name: Yarn Agent
image: node:16
caches:
- agent
- agent-dev
script:
- 'case "$BITBUCKET_BRANCH" in
"master" | "develop")
yarn agent-prod
;;
*)
yarn agent-dev
;;
esac'
artifacts:
- public/**

- step: &yarn-admin
name: Yarn Admin
image: node:16
caches:
- admin
- admin-dev
script:
- 'case "$BITBUCKET_BRANCH" in
"master" | "develop")
yarn admin-prod
;;
*)
yarn admin-dev
;;
esac'
artifacts:
- public/**

- step: &yarn-client
name: Yarn Client
image: node:16
caches:
- client
- client-dev
script:
- 'case "$BITBUCKET_BRANCH" in
"master" | "develop")
yarn client-prod
;;
*)
yarn client-dev
;;
esac'
artifacts:
- public/**

- step: &yarn-client-landing
name: Yarn Client Landing
image: node:16
caches:
- client-landing
- client-landing-dev
script:
- 'case "$BITBUCKET_BRANCH" in
"master" | "develop")
yarn client-landing-prod
;;
*)
yarn client-landing-dev
;;
esac'
artifacts:
- public/**

- step: &yarn-agent-landing
name: Yarn Agent Landing
image: node:16
caches:
- agent-landing
- agent-landing-dev
script:
- 'case "$BITBUCKET_BRANCH" in
"master" | "develop")
yarn agent-landing-prod
;;
*)
yarn agent-landing-dev
;;
esac'
artifacts:
- public/**

- step: &yarn-tailwind
name: tailwind
image: node:16
script:
- 'case "$BITBUCKET_BRANCH" in
"master" | "develop")
yarn tailwind-prod
;;
*)
yarn tailwind-dev
;;
esac'
artifacts:
- public/**

- step: &yarn-public
name: public
image: node:16
caches:
- public
- public-dev
script:
- 'case "$BITBUCKET_BRANCH" in
"master" | "develop")
yarn public-prod
;;
*)
yarn public-dev
;;
esac'
artifacts:
- public/**

- step: &composer-phpunit-test
name: Composer install & PhpUnit Test
image: jobinsjp/jobins:cli-8.0
caches:
- composer
script:
----redacted------
artifacts:
- vendor/**
services:
- mysql
- js-report

- step: &composer-phpunit-test-dev
name: Composer install & PhpUnit Test
image: jobinsjp/jobins:cli-8.0
caches:
- composer
script:
----redacted------
artifacts:
- vendor/**
services:
- mysql
- js-report

- step: &deploy
image: composer:latest
script:
----redacted------

after-script:
----redacted------

pipelines:

pull-requests:
'release/*':
- step: *copy-base
- step: *composer-phpunit-test

'hotfix/*':
- step: *copy-base
- step: *composer-phpunit-test

'JBV1*':
- step: *copy-base
- step: *composer-phpunit-test-dev

'INFRA*':
- step: *copy-base
- step: *composer-phpunit-test-dev

branches:
master:
- step: *copy-base
- step: *yarn
- parallel:
- step: *yarn-agent
- step: *yarn-client
- step: *yarn-admin
- step: *yarn-client-landing
- step: *yarn-agent-landing
- step: *yarn-tailwind
- step: *yarn-public
- step:
<<: *deploy
name: Deploy to staging
deployment: staging
- step:
<<: *deploy
name: Deploy to production
deployment: production
trigger: manual

develop:
- step: *copy-base
- step: *yarn
- parallel:
- step: *yarn-agent
- step: *yarn-client
- step: *yarn-admin
- step: *yarn-client-landing
- step: *yarn-agent-landing
- step: *yarn-tailwind
- step: *yarn-public
- step:
<<: *deploy
name: Deploy to QA
deployment: qa
trigger: automatic

test-server:
- step: *copy-base
- step: *yarn
- parallel:
- step: *yarn-agent
- step: *yarn-client
- step: *yarn-admin
- step: *yarn-client-landing
- step: *yarn-agent-landing
- step: *yarn-tailwind
- step: *yarn-public
- step:
<<: *deploy
name: Deploy to test
deployment: test
trigger: automatic

placeholder:
- step: *copy-base
- step: *yarn
- parallel:
- step: *yarn-agent
- step: *yarn-client
- step: *yarn-admin
- step: *yarn-client-landing
- step: *yarn-agent-landing
- step: *yarn-tailwind
- step: *yarn-public
- step:
<<: *deploy
name: Deploy to ci-test
deployment: ci
trigger: automatic

---

[Theodora Boudale]

Hi Bikram and welcome to the community!

This message will also show when you use parallel steps in your pipeline. If you have a pipeline with two parallel steps, one of them takes 5 minutes and the other one 10 minutes, the duration of the build will be 10 minutes. However, the number of build minutes used is the sum of the duration of each parallel step, so 15 minutes.

It will also show if you use the Redeploy button on a deployment step (from the page of the build log after the build is finished). If you use Redeploy, you are running that step again and the build minutes used will be added to the duration of the first run of this step and any other steps of the pipeline.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora