- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
With the synthetics-test-automation-bitrise-step-upload-application
step, you can upload a new version of your application to Datadog to run Synthetic tests against during your Bitrise CI, ensuring that all your teams using Bitrise can benefit from Synthetic tests at every stage of the software lifecycle. This step uses the Datadog CI Synthetics command, and requires that your application already exists.
This step is not available on the official Bitrise Step Library. To get started:
bitrise.yml
file.- git::https://github.com/DataDog/synthetics-test-automation-bitrise-step-upload-application.git@1.5.0:
bitrise.yml
file. The only required inputs are the two secrets you configured earlier. For a comprehensive list of inputs, see the Inputs section.You can run this step directly using the Bitrise CLI.
To run this step locally:
git clone
the Bitrise repository.cd
into the directory of the step (the one you just git clone
d)..bitrise.secrets.yml
file in the same directory of bitrise.yml
. The .bitrise.secrets.yml
file is a Git-ignored file, so you can store your secrets in it.bitrise.yml
file for any secret you should set in .bitrise.secrets.yml
..bitrise.secrets.yml
file, run this step with the Bitrise CLI with bitrise run test
.An example .bitrise.secrets.yml
file:
envs:
- A_SECRET_PARAM_ONE: the value for secret one
- A_SECRET_PARAM_TWO: the value for secret two
configPath
This task overrides the path to the global datadog-ci.config.json
file.
- git::https://github.com/DataDog/synthetics-test-automation-bitrise-step-upload-application.git@1.5.0:
inputs:
- api_key: <DATADOG_API_KEY>
- app_key: <DATADOG_APP_KEY>
- config_path: './synthetics-config.json'
For an example configuration file, see the global.config.json
file.
For reference, this is an example of a complete configuration:
- git::https://github.com/DataDog/synthetics-test-automation-bitrise-step-upload-application.git@1.5.0:
inputs:
- api_key: <DATADOG_API_KEY>
- app_key: <DATADOG_APP_KEY>
- config_path: './global.config.json'
- latest: true
- mobile_application_version_id: '123-123-123'
- mobile_application_version_file_path: 'path/to/application.apk'
- site: 'datadoghq.com'
- version_name: 'example 1.0'
Name | Requirement | Description |
---|---|---|
apiKey | required | Your Datadog API key. This key is created by your Datadog organization and will be accessed as an environment variable. |
appKey | required | Your Datadog application key. This key is created by your Datadog organization and will be accessed as an environment variable. |
configPath | optional | The global JSON configuration is used when launching tests. See the example configuration for more details. |
latest | optional | Marks the application as latest . Any tests that run on the latest version will use this version on their next run. |
mobileApplicationVersionId | required | ID of the application you want to upload the new version to. |
mobileApplicationVersionFilePath | required | Override the application version for Synthetic mobile application tests. |
site | optional | The Datadog site to send data to. Your Datadog site is . . If the DD_SITE environment variable is set, it takes precedence. |
versionName | required | Name of the new version. It has to be unique. |
Name | Description |
---|---|
DATADOG_UPLOADED_APPLICATION_VERSION_ID | The version ID of the application that was just uploaded. Pass it to the datadog-mobile-app-run-tests step with the mobile_application_version input to test this version of the application. |
Additional helpful documentation, links, and articles: