Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/v2/environments export #10

Open
wants to merge 13 commits into
base: feature/v2/local-trigger
Choose a base branch
from

Conversation

jabou
Copy link
Member

@jabou jabou commented Dec 10, 2024

This PR contains logic for exporting environments from the tag trigger.

Changes

  • Added support for silent script installation without confirmation prompt (usage: --silent)
  • Moved main logic (renamed to trigger tag creation) to separate file
  • Moved shared strings and configs into the "constants" file
  • Added support for extracting the environment(s) from the trigger tag (command: environments

Usage

The app-deploy script must create the tag to get environments from the tag, as those two share the same tag format. To get data out, just run:

# Tag example: TAG=ci/internal-staging/internal-development/2024-12-10T15-10-20
app-deploy environments "$TAG"

> output:
internal-staging
internal-development

As this command needs something to parse, the input parameter is mandatory.

Example

Check out the bitrise example project that parses those values from the trigger tag, maps them into the "workflow" name, and executes those workflows (single or both in parallel).
Project: https://app.bitrise.io/app/bcd6a5ad-2570-413c-9c7f-f39e8080d77e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants