DOCSEARCHbyAlgolia
Submit Docs

Tramline Documentation

website·Indexed 33 days ago

https://docs.tramline.app

A release management platform for mobile apps that coordinates the release life cycle. Tramline provides tools for smart staged rollouts, release health monitoring via bug tracking and monitoring systems, and integrations with CI/CD workflows, version control (GitHub, GitLab), and notification channels like Slack.

Tokens
32.2K
Snippets
43
Records
304
Agent score
62%

What's inside Tramline

  1. Overview of Tramline integration types

    Tramline integrates with external services to track release trains. Integrations are categorized by their role in the release lifecycle. Some are required for core functionality, while others are optional for enhanced visibility and health monitoring.

    Integration TypePurposeRequired?
    Version ControlHosts the application source codeYes
    Build Servers (CI/CD)Generates the application buildYes
    Build DistributionDistributes the application to testers/usersYes
    NotificationSends alerts about release train eventsNo
    Monitoring and AnalyticsProvides application health dataNo

  2. Overview of Tramline release health monitoring integrations

    Tramline integrates with bug tracking and monitoring systems to gather release health metrics. This data is displayed on the ongoing release page once a build has reached the stores, providing a cohesive picture of release health to inform rollout decisions. Currently supported integrations include Bugsnag and Firebase Crashlytics.

  3. Overview of Tramline release coordination platform

    Tramline is a release coordination and deployment platform specifically designed for mobile app teams (iOS and Android). It provides a central dashboard for the mobile DevOps process, integrating build servers, distribution channels, notifications, and approvals. Key capabilities include:

    • Automating release cycle tasks to reduce manual effort.
    • Codifying release policies via release trains to increase confidence.
    • Centralizing sign-offs and approvals for auditability.
    • Providing release analytics, build storage, and post-release monitoring.

  4. Understand and use Reldex for release process scoring

    Reldex is a metric and scoring mechanism used to evaluate the efficacy of the delivery process. It generates a score between 0 and 1 by combining signals such as release duration, hotfixes, rollout time, and fixes made during stabilization. Unlike post-release health monitoring (which uses APM and monitoring tools), Reldex focuses on signals occurring before or during the delivery process. Reldex is enabled by default for all users and appears on the dashboard with pre-configured defaults that can be fine-tuned to weigh specific signals differently.

  5. Access builds via deep links in notifications

    Notifications now include deep links directly to Firebase App Distribution and TestFlight builds, allowing users to access new RC (Release Candidate) builds immediately without manual searching.

  6. Download builds directly from Slack notifications

    When a new build is available for download via Tramline, the build is now attached directly to the Slack notification, allowing users to download it immediately for testing.

  7. Use Tramline mobile views for release management

    Tramline provides dedicated mobile-optimized views allowing release managers to monitor and manage releases on mobile devices. Key capabilities include:

    • Release List View: Browse all releases in a mobile-optimized layout.
    • Release Details: Access essential release summaries.
    • Production Rollout Controls: Manage rollout percentages and status directly from a mobile device.

  8. Analyze release stability and contributions by team

    Tramline allows you to integrate your organization's team structure to correlate team performance metrics with release dynamics. This feature provides analysis on release stability and contributions, identifying which teams are contributing most to a release and which may be impacting release stability. This data is available in real-time for ongoing releases, allowing release managers to identify bottlenecks preventing a release from moving forward.

  9. Manage release notifications

    Notifications are available only if a notification integration (e.g., Slack) is connected in app settings. When enabled, Tramline sends updates about release events.

    By default, notifications go to default and core channels. If 'release-specific channels' are enabled, Tramline creates a new channel for every release and archives it upon completion. The channel naming format is release-{appName}-{platformName}-{versionName}.

  10. Configure notification channels for release events

    Tramline allows you to send significant events from your release life cycle to a configured notification channel. Once the required integrations (such as Slack) are set up, you can select the active notification channel from the list of available channels within the app configuration.

  11. Monitor release health using bug tracking integrations

    Tramline integrates with bug tracking and monitoring systems to gather release health metrics. This data is displayed on the ongoing release page once a build has reached the stores, providing a cohesive picture of release health to inform rollout decisions. Currently supported integrations include Bugsnag and Firebase Crashlytics.

  12. Analyze release process health using aggregated statistics

    Tramline provides a high-level view of aggregated statistics across releases to track the health of the release process. Key metrics available include:

    • DORA metrics: Release Frequency and Fixes During Release (number of store versions generated).
    • Release duration.
    • Time spent by the team in various release process steps.
    • Contributors to the release and contributors to release stability.
    • iOS build review time trends from the app store.