New Assembla + Travis CI Integration: Build and Test Code from your Assembla Repos

Jonathan Lowe Global Account Executive at Assembla
Jonathan Lowe
·
Last updated on November 9, 2023

We’re happy to announce that we have recently expanded our integration with Travis CI. Now, in addition to Git Repositories, you can easily build and test software using Perforce Helix Core (P4) and Subversion (SVN) repositories within Assembla Spaces.

By extending the existing Assembla and Travis CI integration, a major, easy-to-use cloud CI/CD system just became available for SVN, P4 and Git-based builds. Unified Travis CI build instructions syntax and the ability to share standard build configuration snippets helps to standardize and easily maintain build definitions among different kinds of version control systems.  

Travis CI is the original cloud-based CI/CD solution and remains a leading provider of continuous integration and delivery services, empowering development teams to test and deploy their applications with confidence. Travis CI is trusted by a community of over 700,000 users and great companies, including Netflix, Stripe, Nissan, Automattic, MOZ and many others.

How To Integrate Your Assembla Source Code with Travis CI

Firstly, you must have an active account with both Assembla and Travis CI. If you’re an Assembla user who hasn’t signed up for Travis CI yet, please contact our team so we can unify your sign in credentials. Otherwise, sign up for free trials with Assembla here and Travis CI here.

Once your accounts are set up, getting started with Travis CI as a CI/CD tool for SVN and P4 repositories is easy. Simply follow these steps: 

  • Sign in to Travis CI with your Assembla account.
  • In Travis CI: Travis CI will synchronize your Assembla Spaces to Travis CI (displayed as organizations in Travis CI) along with the repositories. You can also use the ‘Sync now’ button in Travis CI Web UI, in your account’s Repositories section to trigger synchronization on demand.
  • In Travis CI: enable the selected repositories with Travis CI – Git, P4, or SVN.
  • In Travis CI: make sure that at least the Trial plan is assigned for the Travis organization named after your Assembla Space.
  • Place build instructions inside the .travis.yml file into the appropriate Assembla repository.
    • For the Assembla Git repository, place the .travis.yml in the root directory.
    • For the Assembla SVN repository, place the .travis.yml in one of the following:
      • /trunk/.travis.yml – this enables automatic builds after commits to the trunk.
      • /branches/[branch name]/.travis.yml – this enables automatic builds after commits to a branch [branch name].
    • For the Assembla P4 repository/depot, place the .travis.yml file in one of the following:
      • /[depotname]/main/.travis.yml  – this enables automatic builds after submits to /[depotname]/main/.  The default is  /depot/main/.travis.yml .
      • /[depotname]/[stream name]/.travis.yml  – this enables automatic builds after submits to a specific stream /[depotname]/[stream name]/ .
  • Commit the source code change in the Assembla repository and see the builds running on Travis CI.

Sample .travis.yml file:

dist: focal
language: ruby
rvm:
  - 2.2
  - jruby

The automatic Travis CI build will be triggered on the next commit after adding the .travis.yml file in the repository enabled within Travis CI.

Watch the Demo Video

Why Integrate Assembla and Travis CI to Build and Test Code?

Cloud-based Platforms: Travis CI allows you to create automatic build and test pipelines for your source code, kept in Assembla, including its P4, Git and SVN repositories. Because both platforms are cloud-based, you don’t have to worry about maintaining the infrastructure or scaling up (or sometimes down) on your own.

Automate Builds and Tests: The primary use case of utilizing Travis CI is to automate the process of building and testing software. If you are part of a team that already has a Travis CI account, you can utilize the pre-existing scripts by invoking them in the build instructions in .travis.yml.

Deploy, Conditionally: Travis CI provides a feature to add a stage for deploying or uploading the artifacts that were built. This stage can be executed conditionally only if the test stage was successful. Additionally, it is easy to schedule nightly or weekly builds for your software using Travis CI.

Run Compute-Heavy Processes: Run compute-heavy processes using larger CPUs or GPUs by leveraging Travis CI’s GPU support. In Travis CI, there are different build environment configurations available at your disposal in terms of available CPU and RAM. If you require a build environment with a GPU, you can use the command line version of Blender to leverage CI/CD for rendering graphics or video. The command line version of TensorFlow may also allow running some machine learning computations using cloud CI/CD.

Easy Syntax: The .travis.yml syntax is easy for developers to learn, enabling each team to maintain their repository build and test recipes as code. This has the advantage of not requiring a specialized crew to maintain your automated CI/CD process – the build instructions update is evolving with the source code, and ownership of these is distributed.

Happy building!

Read more:

Get Source Code Management Tips in Your Inbox
The reCAPTCHA was invalid. try it again.
By filling and submitting this form you understand and agree that the use of Assembla website is subject to the General Website Terms of Use. Additional details regarding Assembla collection and use of your personal information, including information about access, retention, rectification, deletion, security, cross-border transfers and other topics, is available in the Privacy Policy.
Jonathan Lowe Global Account Executive at Assembla
Jonathan Lowe
Jonathan is the Global Account Executive at Assembla.

Comments are closed

© 2024 Assembla - All Rights Reserved

Select AWS Region

Pick the region closest to your team for faster performance.

Select AWS Region

Pick the region closest to your team for faster performance.