Manage tracks inside a channel

Last updated on February 11, 2025

What Are Tracks?

In the AccelByte Development Toolkit (ADT), Tracks are organizational tools within Channels that allow you to manage and sequence your builds over time. Think of a track as a timeline where each build represents a point in that sequence. The most recent build is at the "head" of the track, while previous builds remain accessible in its history. Tracks are typically used to represent specific configurations, platforms, or other categorizations relevant to your development process.

Examples of Tracks

• By Platform: Windows, Xbox, PlayStation, etc.
• By Configuration: Windows with Lighting, Windows without Lighting, etc.

This structure allows for granular organization, enabling teams to manage builds in a way that aligns with their specific workflows and requirements.

Benefits of Using Tracks

• Organized Build Management: Tracks help in categorizing builds systematically, making it easier to locate and manage them based on specific criteria like platform or configuration.
• Historical Reference: Maintaining a history of builds within a track allows teams to reference or revert to previous versions if needed.

How to Use Tracks

Creating a Track

• Within a Channel, you can create a new Track to represent a specific platform or configuration.
• Name the Track appropriately to reflect its purpose (e.g., "Windows with Lighting").

Assigning Builds to a Track

• Upload your build to ADT.
• Assign the build to the relevant Track within the desired Channel.

Managing Builds Within a Track

• The latest build will appear at the head of the Track.
• Previous builds remain in the Track's history and can be accessed or restored as needed.

For detailed instructions on managing Tracks using the ADT CLI, refer to the Manage Channels and Tracks Using CLI documentation.

Track Settings

Each Track in the Build Channels feature comes with a variety of settings that can be accessed from the hamburger menu on the track card. These settings allow users to manage and configure tracks effectively.

Available Track Settings

1. Rename Track

   • Rename the track to correct typos or update its purpose.

2. Change the Head of Track

   • Select a build from the available versions and builds to designate as the head of the track.

3. Set Launch Arguments

   • Define default launch arguments for the track.
   • These arguments will automatically apply whenever a user launches the game from this track.

4. Track History

   • View a history of builds previously assigned to this track.
   • Set an older build as the head of the track, if needed.

5. Move Track

   • Move the selected track to another channel.

6. Share This Track

   • Generate a URL to share the track with teammates.
   • The link allows teammates to locate the track easily and will auto-launch it (only works for Windows build).

7. Copy Build to Track

   • Copy the build currently assigned to this track to another track in a different channel.

8. Delete Track for All Subscribers

   • Permanently delete the selected track for all users in ADT.

Configure Auto Update

In addition to the above settings, users can enable and manage the Auto Update feature for their tracks. This allows builds to be updated automatically based on configuration settings.

For detailed information on Auto Update Deploy and Delay, refer to the Auto Update Configuration Documentation.

info

Best Practices

• Consistent Naming Conventions: Use clear and consistent names for Tracks to ensure all team members understand their purpose.
• Regular Maintenance: Periodically review and clean up old or unused builds within Tracks to maintain an organized build environment.
• Align with Workflow: Structure Tracks in a way that mirrors your development process, whether that's by platform, feature set, or release stage.

By effectively utilizing Tracks, teams can enhance their build management processes, ensuring a more organized and efficient workflow within ADT.