Version and Repository Policies
Overview
First Tech distributes its TTP solution as an SDK hosted in a Nexus repository. This architecture enables secure distribution through user and password authentication. Integrated as dependencies in Java/Kotlin Android projects, these SDKs allow teams to synchronize efficiently with the latest product version, supporting CI/CD (Continuous Integration and Continuous Delivery) workflows.
However, maintaining a single repository for all clients can create friction. The frequency of updates may disrupt development processes, and misalignments can occur if new features are released without proper communication across all stakeholders.
To mitigate these issues, Nexus supports the creation of client-specific repositories. This allows First Tech to tailor its release management and publication strategy based on each client's unique lifecycle and development pace.
SDK Update Lifecycle
There are six key phases in the SDK update process:
Initial Availability First Tech publishes the latest stable version of the SDK in a cloned Nexus repository, allowing clients to continue operating with their current version.
New Version Communication Upon releasing a new version, First Tech notifies the client and provides documentation outlining changes, enhancements, and instructions for testing and evaluation.
Internal Testing The client’s developer downloads the new version from First Tech’s repository and conducts internal validation to ensure compatibility and quality.
Authorization for Release If testing is successful, the client sends an authorization (via email or agreed-upon channel) to First Tech, signaling approval to release the new version in a dedicated repository.
Repository Creation and Access First Tech then creates a client-specific repository and grants access to the designated standard user. This ensures only the authorized client can interact with the new version.
Client Communication and Integration The client informs its development teams and user base about the update and adjusts the repository configuration so that existing projects can download and integrate the new SDK version.
Connecting to the Repositories
When connecting to repositories (via browser or directly through Android Studio), pay close attention to the access paths. Misconfigurations may lead to connectivity issues.
1. Verify Repository URLs
The client’s repository URL is similar to the general First Tech repository but includes a company-specific suffix after the hyphen (-):
First Tech Repository (All Supported Versions):
https://nexus.first-tech.net/repository/taponphoneClient Repository (Authorized Versions Only):
https://nexus.first-tech.net/repository/taponphone-(Your-Company-Name)
2. User Credentials
Access credentials (username and password) for the general First Tech repository differ from those used in the client-specific repository. If unsure, please contact First Tech to receive updated credentials.
3. Certificate Consistency
Both repositories share the same certificate, which must be installed in the project’s cacerts directory. For configuration details, consult the [Developer Implementation Guide], which contains setup instructions, certificate management guidance, and Gradle dependency configuration.
Final Considerations
This document outlines the key principles for managing SDK repositories and version control at First Tech:
Dynamic Distribution Hosting SDKs on Nexus allows for continuous synchronization with the latest version, enabling fast and frequent updates.
Client-Specific Customization Client-dedicated repositories ensure tailored updates aligned with their internal development lifecycle and release policies.
Structured Update Workflow The six-phase update process ensures every step—from version release to client notification—is executed in a transparent and organized way.
Attention to Technical Details Proper configuration of access paths, distinct credentials, and consistent certificate use ensures reliable integration with development environments.
These guidelines not only streamline SDK lifecycle management but also strengthen collaboration between First Tech and its clients, ensuring a robust and efficient development experience.
Last updated