Skip to main content
Glama

Server Details

MCP Server for Bitrise, enabling app management, build operations, artifact management, and more.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
bitrise-io/bitrise-mcp
GitHub Stars
33
Server Listing
Bitrise MCP Server

See and control every tool call

Log every tool call with full inputs and outputs
Control which tools are enabled per connector
Manage credentials once, use from any MCP client
Monitor uptime and get alerted when servers go down

Available Tools

67 tools
abort_buildInspect

Abort a specific build.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
build_slugYesIdentifier of the build
abort_reasonNoReason for aborting the build
abort_with_successNoIf set to true, the aborted build will be marked as successful
skip_notificationsNoIf set to true, skip sending notifications
skip_git_status_reportNoIf set to true, skip sending git status report
abort_pipelineInspect

Abort a pipeline.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
pipeline_idYesIdentifier of the pipeline
abort_reasonNoReason for aborting the pipeline
abort_with_successNoIf set to true, the aborted pipeline will be marked as successful
skip_notificationsNoIf set to true, skip sending notifications
add_member_to_groupInspect

Add a member to a group.

ParametersJSON Schema
NameRequiredDescriptionDefault
user_slugYesSlug of the user
group_slugYesSlug of the group
add_testers_to_tester_groupInspect

Adds testers to a tester group of a connected app.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe uuidV4 identifier of the tester group to which testers will be added.
user_slugsYesThe list of users identified by slugs that will be added to the tester group.
connected_app_idYesThe uuidV4 identifier of the related Release Management connected app.
create_connected_appInspect

Add a new Release Management connected app to Bitrise.

ParametersJSON Schema
NameRequiredDescriptionDefault
idNoAn uuidV4 identifier for your new connected app. If it is not given, one will be generated.
platformYesThe mobile platform for the connected app. Available values are 'ios' and 'android'.
project_idNoSpecifies which Bitrise Project you want to get the connected app to be associated with. If this field is not given a new project will be created alongside with the connected app.
store_app_idYesThe app store identifier for the connected app. In case of 'ios' platform it is the bundle id from App Store Connect. In case of Android platform it is the package name.
store_app_nameNoIf you have no active app store API keys added on Bitrise, you can decide to add your app manually by giving the app's name as well while indicating manual connection.
workspace_slugYesIdentifier of the Bitrise workspace for the Release Management connected app. This field is mandatory.
manual_connectionNoIf set to true it indicates a manual connection (bypassing using store api keys) and requires giving 'store_app_name' as well.
store_credential_idNoIf you have credentials added on Bitrise, you can decide to select one for your app. In case of ios platform it will be an Apple API credential id. In case of android platform it will be a Google Service credential id.
create_outgoing_webhookInspect

Create an outgoing webhook for an app.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the webhook
eventsYesList of events to trigger the webhook
secretNoSecret for webhook signature verification
headersNoHeaders to be sent with the webhook
app_slugYesIdentifier of the Bitrise app
create_tester_groupInspect

Creates a tester group for a Release Management connected app. Tester groups can be used to distribute installable artifacts to testers automatically. When a new installable artifact is available, the tester groups can either automatically or manually be notified via email. The notification email will contain a link to the installable artifact page for the artifact within Bitrise Release Management. A Release Management connected app can have multiple tester groups. Project team members of the connected app can be selected to be testers and added to the tester group. This endpoint has an elevated access level requirement. Only the owner of the related Bitrise Workspace, a workspace manager or the related project's admin can manage tester groups.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesThe name for the new tester group. Must be unique in the scope of the connected app.
auto_notifyNoIf set to true it indicates that the tester group will receive notifications automatically.
connected_app_idYesThe uuidV4 identifier of the related Release Management connected app.
create_workspace_groupInspect

Create a new group in a workspace.

ParametersJSON Schema
NameRequiredDescriptionDefault
group_nameYesName of the group
workspace_slugYesSlug of the Bitrise workspace
delete_all_cache_itemsInspect

Delete all key-value cache items belonging to an app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
delete_appInspect

Delete an app from Bitrise. When deleting apps belonging to multiple workspaces always confirm that which workspaces' apps the user wants to delete.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
delete_artifactInspect

Delete a build artifact.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
build_slugYesIdentifier of the build
artifact_slugYesIdentifier of the artifact
delete_cache_itemInspect

Delete a key-value cache item.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
cache_item_idYesKey of the cache item
delete_outgoing_webhookInspect

Delete the outgoing webhook of an app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
webhook_slugYesIdentifier of the webhook
finish_bitrise_appInspect

Finish the setup of a Bitrise app. If this is successful, a build can be triggered via trigger_bitrise_build. If you have access to the repository, decide the project type, the stack ID, and the config to use, based on https://stacks.bitrise.io/, and the config should be also based on the project type.

ParametersJSON Schema
NameRequiredDescriptionDefault
configNoThe configuration preset to use for the app.other-config
app_slugYesThe slug of the Bitrise app to finish setup for.
stack_idYesThe stack ID to use for the app.linux-docker-android-22.04
project_typeYesThe type of projectother
generate_installable_artifact_upload_urlInspect

Generates a signed upload url valid for 1 hour for an installable artifact to be uploaded to Bitrise Release Management. The response will contain an url that can be used to upload an artifact to Bitrise Release Management using a simple curl request with the file data that should be uploaded. The necessary headers and http method will also be in the response. This artifact will need to be processed after upload to be usable. The status of processing can be checked by making another request to a different url giving back the processed status of an installable artifact.

ParametersJSON Schema
NameRequiredDescriptionDefault
branchNoOptionally you can add the name of the CI branch the installable artifact has been generated on.
workflowNoOptionally you can add the name of the CI workflow this installable artifact has been generated by.
file_nameYesThe name of the installable artifact file (with extension) to be uploaded to Bitrise. This field is mandatory.
file_size_bytesYesThe byte size of the installable artifact file to be uploaded.
connected_app_idYesIdentifier of the Release Management connected app for the installable artifact. This field is mandatory.
with_public_pageNoOptionally, you can enable public install page for your artifact. This can only be enabled by Bitrise Project Admins, Bitrise Project Owners and Bitrise Workspace Admins. Changing this value without proper permissions will result in an error. The default value is false.
installable_artifact_idYesAn uuidv4 identifier generated on the client side for the installable artifact. This field is mandatory.
get_appInspect

Get the details of a specific app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
get_artifactInspect

Get a specific build artifact.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
build_slugYesIdentifier of the build
artifact_slugYesIdentifier of the artifact
get_bitrise_ymlInspect

Get the current Bitrise YML config file of a specified Bitrise app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app (e.g., "d8db74e2675d54c4" or "8eb495d0-f653-4eed-910b-8d6b56cc0ec7")
get_buildInspect

Get a specific build of a given app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
build_slugYesIdentifier of the build
get_build_bitrise_ymlInspect

Get the bitrise.yml of a build.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
build_slugYesIdentifier of the build
get_build_logInspect

Get the build log of a specified build of a Bitrise app.

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoThe number of lines to read. Defaults to 2000. Set to a high value to read the entire log.
offsetNoThe line number to start reading from. Defaults to 0. Set -1 to read from the end of the log. Failures are usually at the end of the log.
app_slugYesIdentifier of the Bitrise app (e.g., "d8db74e2675d54c4" or "8eb495d0-f653-4eed-910b-8d6b56cc0ec7")
step_uuidNoUUID of the step to get the log for. If not provided, the full build log is returned. Always provide this value whenever possible to avoid large log responses and running out of the LLM context window.
build_slugYesIdentifier of the Bitrise build
get_build_stepsInspect

Get step statuses of a specific build of a given app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
build_slugYesIdentifier of the build
get_cache_item_download_urlInspect

Get the download URL for a cache item.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
cache_item_idYesKey of the cache item
get_connected_appInspect

Gives back a Release Management connected app for the authenticated account.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesIdentifier of the Release Management connected app
get_installable_artifact_upload_and_proc_statusInspect

Gets the processing and upload status of an installable artifact. An artifact will need to be processed after upload to be usable. This endpoint helps understanding when an uploaded installable artifacts becomes usable for later purposes.

ParametersJSON Schema
NameRequiredDescriptionDefault
connected_app_idYesIdentifier of the Release Management connected app for the installable artifact. This field is mandatory.
installable_artifact_idYesThe uuidv4 identifier for the installable artifact. This field is mandatory.
get_pipelineInspect

Get a pipeline of a given app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
pipeline_idYesIdentifier of the pipeline
get_potential_testersInspect

Gets a list of potential testers whom can be added as testers to a specific tester group. The list consists of Bitrise users having access to the related Release Management connected app.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe uuidV4 identifier of the tester group. This field is mandatory.
pageNoSpecifies which page should be returned from the whole result set in a paginated scenario. Default value is 1.
searchNoSearches for potential testers based on email or username using a case-insensitive approach.
items_per_pageNoSpecifies the maximum number of potential testers to return having access to a specific connected app. Default value is 10.
connected_app_idYesThe uuidV4 identifier of the app the tester group is connected to. This field is mandatory.
get_tester_groupInspect

Gives back the details of the selected tester group.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe uuidV4 identifier of the tester group. This field is mandatory.
connected_app_idYesThe uuidV4 identifier of the app the tester group is connected to. This field is mandatory.
get_testersInspect

Gives back a list of testers that has been associated with a tester group related to a specific connected app.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoSpecifies which page should be returned from the whole result set in a paginated scenario. Default value is 1.
items_per_pageNoSpecifies the maximum number of testers to be returned that have been added to a tester group related to the specific connected app. Default value is 10.
tester_group_idNoThe uuidV4 identifier of a tester group. If given, only testers within this specific tester group will be returned.
connected_app_idYesThe uuidV4 identifier of the app the tester group is connected to. This field is mandatory.
get_workspaceInspect

Get details for one workspace

ParametersJSON Schema
NameRequiredDescriptionDefault
workspace_slugYesSlug of the Bitrise workspace
get_workspace_groupsInspect

Get the groups in a workspace

ParametersJSON Schema
NameRequiredDescriptionDefault
workspace_slugYesSlug of the Bitrise workspace
get_workspace_membersInspect

Get the members of a workspace

ParametersJSON Schema
NameRequiredDescriptionDefault
workspace_slugYesSlug of the Bitrise workspace
invite_member_to_workspaceInspect

Invite new Bitrise users to a workspace.

ParametersJSON Schema
NameRequiredDescriptionDefault
emailYesEmail address of the user
workspace_slugYesSlug of the Bitrise workspace
list_appsInspect

List all apps for the currently authenticated user account

ParametersJSON Schema
NameRequiredDescriptionDefault
nextNoSlug of the first app in the response
limitNoMax number of elements per page (default: 50)
titleNoFilter apps by title
sort_byNoOrder of the apps. If set, you should accept the response as sortedlast_build_at
project_typeNoFilter apps by project type (e.g., 'ios', 'android')
list_artifactsInspect

Get a list of all build artifacts.

ParametersJSON Schema
NameRequiredDescriptionDefault
nextNoSlug of the first artifact in the response
limitNoMax number of elements per page (default: 50)
app_slugYesIdentifier of the Bitrise app
build_slugYesIdentifier of the build
list_available_stacksInspect

List available stacks with their machine configurations and version information. When a workspace_slug is provided, returns stacks available for that workspace including any custom stacks. When omitted, returns globally available stacks.

ParametersJSON Schema
NameRequiredDescriptionDefault
workspace_slugNoSlug of the Bitrise workspace. When provided, lists stacks available for that workspace (including custom stacks). When omitted, lists globally available stacks.
list_branchesInspect

List the branches with existing builds of an app's repository.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
list_build_distribution_versionsInspect

Lists Build Distribution versions. Release Management offers a convenient, secure solution to distribute the builds of your mobile apps to testers without having to engage with either TestFlight or Google Play. Once you have installable artifacts, Bitrise can generate both private and public install links that testers or other stakeholders can use to install the app on real devices via over-the-air installation. Build distribution allows you to define tester groups that can receive notifications about installable artifacts. The email takes the notified testers to the test build page, from where they can install the app on their own device. Build distribution versions are the app versions available for testers.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoSpecifies which page should be returned from the whole result set in a paginated scenario. Default value is 1.
items_per_pageNoSpecifies the maximum number of build distribution versions returned per page. Default value is 10.
connected_app_idYesThe uuidV4 identifier of the app the build distribution is connected to. This field is mandatory.
list_build_distribution_version_test_buildsInspect

Gives back a list of test builds for the given build distribution version.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoSpecifies which page should be returned from the whole result set in a paginated scenario. Default value is 1.
versionYesThe version of the build distribution. This field is mandatory.
items_per_pageNoSpecifies the maximum number of test builds to return for a build distribution version per page. Default value is 10.
connected_app_idYesThe uuidV4 identifier of the app the build distribution is connected to. This field is mandatory.
list_buildsInspect

List all the builds of a specified Bitrise app or all accessible builds.

ParametersJSON Schema
NameRequiredDescriptionDefault
nextNoSlug of the first build in the response
limitNoMax number of elements per page (default: 50)
branchNoFilter builds by branch
statusNoFilter builds by status (0: not finished, 1: successful, 2: failed, 3: aborted, 4: in-progress)
sort_byNoOrder of builds: created_at (default), running_firstcreated_at
app_slugNoIdentifier of the Bitrise app
workflowNoFilter builds by workflow
list_build_workflowsInspect

List the workflows of an app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
list_cache_itemsInspect

List the key-value cache items belonging to an app.

ParametersJSON Schema
NameRequiredDescriptionDefault
nextNoGetting cache items created before the given parameter (RFC3339 time format)
limitNoMax number of elements per page (default: 100)
app_slugYesIdentifier of the Bitrise app
list_connected_appsInspect

List Release Management connected apps available for the authenticated account within a workspace.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoSpecifies which page should be returned from the whole result set in a paginated scenario. Default value is 1.
searchNoSearch by bundle ID (for ios), package name (for android), or app title (for both platforms). The filter is case-sensitive.
platformNoFilters for a specific mobile platform for the list of connected apps. Available values are: 'ios' and 'android'.
project_idNoSpecifies which Bitrise Project you want to get associated connected apps for
items_per_pageNoSpecifies the maximum number of connected apps returned per page. Default value is 10.
workspace_slugYesIdentifier of the Bitrise workspace for the Release Management connected apps. This field is mandatory.
list_group_rolesInspect

List group roles for an app

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
role_nameYesName of the role
list_installable_artifactsInspect

List Release Management installable artifacts of a connected app available for the authenticated account.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoSpecifies which page should be returned from the whole result set in a paginated scenario. Default value is 1.
branchNoFilters for the Bitrise CI branch of the installable artifact on which it has been generated on.
searchNoSearch by version, filename or build number (Bitrise CI). The filter is case-sensitive.
sourceNoFilters for the source of installable artifacts to be returned. Available values are 'api' and 'ci'.
versionNoFilters for the version this installable artifact was created for. This field is required if the distribution_ready filter is set to true.
platformNoFilters for a specific mobile platform for the list of installable artifacts. Available values are: 'ios' and 'android'.
workflowNoFilters for the Bitrise CI workflow of the installable artifact it has been generated by.
after_dateNoA date in ISO 8601 string format specifying the start of the interval when the installable artifact to be returned was created or uploaded. This value will be defaulted to 1 month ago if distribution_ready filter is not set or set to false.
before_dateNoA date in ISO 8601 string format specifying the end of the interval when the installable artifact to be returned was created or uploaded. This value will be defaulted to the current time if distribution_ready filter is not set or set to false.
store_signedNoFilters for store ready installable artifacts. This means signed .aab and .ipa (with distribution type app-store) installable artifacts.
artifact_typeNoFilters for a specific artifact type or file extension for the list of installable artifacts. Available values are: 'aab' and 'apk' for android artifacts and 'ipa' for ios artifacts.
items_per_pageNoSpecifies the maximum number of installable artifacts to be returned per page. Default value is 10.
connected_app_idYesIdentifier of the Release Management connected app for the installable artifacts. This field is mandatory.
distribution_readyNoFilters for distribution ready installable artifacts. This means .apk and .ipa (with distribution type ad-hoc, development, or enterprise) installable artifacts.
list_outgoing_webhooksInspect

List the outgoing webhooks of an app.

ParametersJSON Schema
NameRequiredDescriptionDefault
nextNoSlug of the first outgoing webhook in the response
limitNoMax number of elements per page (default: 50)
app_slugYesIdentifier of the Bitrise app
list_pipelinesInspect

List all pipelines and standalone builds of an app.

ParametersJSON Schema
NameRequiredDescriptionDefault
afterNoList pipelines/standalone builds run after a given date (RFC3339 time format)
limitNoMax number of elements per page (default: 10)
beforeNoList pipelines/standalone builds run before a given date (RFC3339 time format)
branchNoFilter by the branch which was built
statusNoFilter by the status of the pipeline/standalone build
app_slugYesIdentifier of the Bitrise app
pipelineNoFilter by the name of the pipeline
workflowNoFilter by the name of the workflow used for the pipeline/standalone build
build_numberNoFilter by the pipeline/standalone build number
commit_messageNoFilter by the commit message of the pipeline/standalone build
trigger_event_typeNoFilter by the event that triggered the pipeline/standalone build
list_tester_groupsInspect

Gives back a list of tester groups related to a specific Release Management connected app.

ParametersJSON Schema
NameRequiredDescriptionDefault
pageNoSpecifies which page should be returned from the whole result set in a paginated scenario. Default value is 1.
items_per_pageNoSpecifies the maximum number of tester groups to return related to a specific connected app. Default value is 10.
connected_app_idYesThe uuidV4 identifier of the app the tester group is connected to. This field is mandatory.
list_workspacesInspect

List the workspaces the user has access to

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

meInspect

Get user info for the currently authenticated user account

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

notify_tester_groupInspect

Notifies a tester group about a new test build.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe uuidV4 identifier of the tester group whose members will be notified about the test build.
test_build_idYesThe unique identifier of the test build what will be sent in the notification of the tester group.
connected_app_idYesThe uuidV4 identifier of the related Release Management connected app.
rebuild_pipelineInspect

Rebuild a pipeline.

ParametersJSON Schema
NameRequiredDescriptionDefault
partialNoWhether to rebuild only unsuccessful workflows and their dependents
app_slugYesIdentifier of the Bitrise app
pipeline_idYesIdentifier of the pipeline
triggered_byNoWho triggered the rebuild
register_appInspect

Add a new app to Bitrise. After this app should be finished on order to be registered completely on Bitrise (via the finish_bitrise_app tool). Before doing this step, try understanding the repository details from the repository URL. This is a two-step process. First, you register the app with the Bitrise API, and then you finish the setup. The first step creates a new app in Bitrise, and the second step configures it with the necessary settings. If the user has multiple workspaces, always prompt the user to choose which one you should use. Don't prompt the user for finishing the app, just do it automatically.

ParametersJSON Schema
NameRequiredDescriptionDefault
titleNoThe title of the application (if not specified, will use the git repository's name)
providerNoThe git provider of the repositorygithub
repo_urlYesRepository URL
is_publicYesWhether the app's builds visibility is "public"
organization_slugYesThe organization (aka workspace) the app to add to
default_branch_nameNoThe default branch of the repository. Verify this branch exists in the remote repository.master
manual_approval_enabledNoToggles whether manual approval should be enabled for the app's builds
register_ssh_keyInspect

Add an SSH-key to a specific app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
auth_ssh_public_keyYesPublic SSH key
auth_ssh_private_keyYesPrivate SSH key
is_register_key_into_provider_serviceNoRegister the key in the provider service
register_webhookInspect

Register an incoming webhook for a specific application.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
replace_group_rolesInspect

Replace group roles for an app.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
role_nameYesName of the role
group_slugsYesList of group slugs
set_installable_artifact_public_install_pageInspect

Changes whether public install page should be available for the installable artifact or not.

ParametersJSON Schema
NameRequiredDescriptionDefault
connected_app_idYesIdentifier of the Release Management connected app for the installable artifact. This field is mandatory.
with_public_pageYesBoolean flag for enabling/disabling public install page for the installable artifact. This field is mandatory.
installable_artifact_idYesThe uuidv4 identifier for the installable artifact. This field is mandatory.
step_inputsInspect

List inputs of a step with their defaults, allowed values etc.

ParametersJSON Schema
NameRequiredDescriptionDefault
step_refYesStep reference formatted as `step_lib_source::step_id@version`. `step_id` and an exact `version` are required, `step_lib_source` is only necessary for custom step sources.
trigger_bitrise_buildInspect

Trigger a new build/pipeline for a specified Bitrise app

ParametersJSON Schema
NameRequiredDescriptionDefault
branchNoThe branch to buildmain
app_slugYesIdentifier of the Bitrise app (e.g., "d8db74e2675d54c4" or "8eb495d0-f653-4eed-910b-8d6b56cc0ec7")
commit_hashNoThe commit hash for the build
pipeline_idNoThe pipeline to build
workflow_idNoThe workflow to build
environmentsNoCustom environment variables for the build.
commit_messageNoThe commit message for the build
update_appInspect

Update an app. Only app_slug is required, add only fields you wish to update

ParametersJSON Schema
NameRequiredDescriptionDefault
titleNoThe new title of the application
app_slugYesIdentifier of the Bitrise app
default_branchNoThe new default branch for the application
repository_urlNoThe new repository URL for the application
update_artifactInspect

Update a build artifact.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app
build_slugYesIdentifier of the build
artifact_slugYesIdentifier of the artifact
is_public_page_enabledYesEnable public page for the artifact
update_bitrise_ymlInspect

Update the Bitrise YML config stored on Bitrise. This has no effect if it is stored in the repository.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugYesIdentifier of the Bitrise app (e.g., "d8db74e2675d54c4" or "8eb495d0-f653-4eed-910b-8d6b56cc0ec7")
bitrise_yml_as_jsonYesThe new Bitrise YML config file content to be updated. It must be a string. Important: these configs are large files, so get these by running: cat <filepath> via the Bash tool.
update_connected_appInspect

Updates a connected app.

ParametersJSON Schema
NameRequiredDescriptionDefault
store_app_idNoThe store identifier for your app. You can change the previously set store_app_id to match the one in the App Store or Google Play depending on the app platform. This is especially useful if you want to connect your app with the store as the system will validate the given store_app_id against the Store. In case of iOS platform it is the bundle id. In case of Android platform it is the package name.
connect_to_storeNoIf true, will check connected app validity against the Apple App Store or Google Play Store (dependent on the platform of your connected app). This means, that the already set or just given store_app_id will be validated against the Store, using the already set or just given store credential id.
connected_app_idYesThe uuidV4 identifier for your connected app.
store_credential_idNoIf you have credentials added on Bitrise, you can decide to select one for your app. In case of ios platform it will be an Apple API credential id. In case of android platform it will be a Google Service credential id.
update_outgoing_webhookInspect

Update an outgoing webhook for an app. Even if you do not want to change one of the parameters, you still have to provide that parameter as well: simply use its existing value.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlNoURL of the webhook
eventsNoList of events to trigger the webhook
headersNoHeaders to be sent with the webhook
app_slugYesIdentifier of the Bitrise app
webhook_slugYesIdentifier of the webhook
update_tester_groupInspect

Updates the given tester group. The name and the auto notification setting can be updated optionally.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe uuidV4 identifier of the tester group to which testers will be added.
nameNoThe new name for the tester group. Must be unique in the scope of the related connected app.
auto_notifyNoIf set to true it indicates the tester group will receive email notifications automatically from now on about new installable builds.
connected_app_idYesThe uuidV4 identifier of the related Release Management connected app.
validate_bitrise_ymlInspect

Validate a Bitrise YML config file. Use this tool to verify any changes made in bitrise.yml.

ParametersJSON Schema
NameRequiredDescriptionDefault
app_slugNoSlug of a Bitrise app (as returned by the list_apps tool). Specifying this value allows for validating the YML against workspace-specific settings like available stacks, machine types, license pools etc.
bitrise_ymlYesThe Bitrise YML config file content to be validated. It must be a string. Important: these configs are large files, so get these by running: cat <filepath> via the Bash tool.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.