Current Articles | RSS Feed RSS Feed

Looking for a Git Bug Tracker? Look No More.

Posted by Titas Norkunas on Mon, May 20, 2013

Integrated Git issue tracker

Forget about setting up a Git repository and an issue tracker locally only to have an integrated Git repository with a bug tracking system to run your software project.

With Assembla, you have an integrated system at your fingertips - just install a Tickets tool and a Git tool to your Space - that’s it, you are done setting up, let the work begin. Out of the box, you will be able to reference tickets from your commit messages - just write “re #1” in your commit message and a link to the commit will appear on ticket #1.

Git bugtracker - integrated repositories and issue tracking

  • Change ticket statuses - just naming a ticket status - “Fixed #1” - will place a link in the ticket to the commit and change the ticket status to Fixed.
  • Track time - enter a record of how much time you spent working on a particular task by using  “Fixed #1 Time: 1h30min” to your commit message.

Want more integration?

Are people making commits to the repository, which you can’t trace back? Well, we have a solution for you. With our new custom server side hooks feature you don’t need to ask everyone to create a pre-commit hook on their machine. Just install a server side hook to your repository to reject the commits that do not contain a ticket reference - nobody will be able to push a new commit that is not related to a particular ticket.
Server side hooks to integrate git bugtracker and repository

Even more integration?

Need more automation in your workflow? You can write your own server-side hooks, which we will review and put on our servers for you to install. Just send us a merge request!

Get your free Git repository with an issue tracker here.

1 Comments Click here to read comments

Server Side Hooks on a SaaS repository? ✓

Posted by Michael Chletsos on Tue, May 07, 2013

Oh BTW, you can have Server Side Hooks in a SaaS Repository.

Cloud repository hosts have failed us. The power of hosting your repository locally is the ability to implement Server Side Hooks. These hooks allow you to control your repository and the source code contained within.  Its super convenient for an organization with many contributors to a single repository. You can syntax check code, ensure commit messages are proper, add the power of automation or anything else you need your repository to do better than if you were relying on external webhooks.

To add a Server Side Hook in your current Assembla Repository - go to the Settings Page -> Server-Side Hooks:

server side hooks

  • Git: pre-receive, post-receive and update hooks

  • SVN: pre-commit, post-commit, pre-revprop-change and post-revprop-change hooks

  • Community Supported: Submit your own hooks or partake in the fruits of another’s labor

  • Prevent commits that do not comply with your Coding Standards

  • Validate commit messages for status updates and valid ticket reference

  • Create Workflows with specific status and ticket changes or kick off external procs

We are very excited about Server Side Hooks and hope that you find them as useful as we do. Take a look at some of our other available Repository Features.

0 Comments Click here to read comments

Here's the easiest way to collaborate with your designers and share your documentation

Posted by Titas Norkunas on Fri, Mar 08, 2013

What is your usual way of prototyping? Forget the file handoff and the email mess of sending those HTML prototypes. Collaboration with Designers is made easy in Assembla. Just check out the render button on any HTML document:

render resized 600

  • render a file at any revision in Git, Subversion or Perforce
  • get fully rendered HTML page - with CSS and JS

This makes the full-blown HTML prototype be only a commit away and you never lose it, because it is in your repository!

Learn more about collaboration here 

0 Comments Click here to read comments

Your Code: Accessible, Easy, Fast

Posted by Titas Norkunas on Fri, Mar 08, 2013

We haven’t been blogging for a while, but that does not mean we haven’t been busy. As you have seen, one of the things we have been working on is rethinking how code is browsed and how to improve the experience for both developers and other team members.

Dig into your code with the redesigned Code Browser

Code Browser

  • Browse the code faster with our ajax implementation of the source view
  • Merge request, fork (Git-only) and compare controls are easier to find and use
Understand your code’s history with Commits and Previous Versions

Commits / Previous Versions

  • Use Previous Versions to see commits affecting only a specific folder or file
  • Easily understand which tickets are affected by which commits
Keep your codebase sustainable with Inline Comments

Inline Comments

  • Discuss code on a specific commit
  • Mention people when replying to get the focus of that person right where you want it
We’re continuing to improve the Repository tool UI’s. You can read more about our Repository features here

Do you like what we’ve done so far? Let us know in the comments.

0 Comments Click here to read comments

Announcing Perforce On-Demand

Posted by Andy Singleton on Wed, Jul 11, 2012

Today we are announcing the first-ever availability of Perforce depots (repositories) on-demand with integrated ticketing and collaboration tools. Existing Assembla users can add a Perforce depot to any new or existing projects. If you do not have any Assembla account, get started today for free.


We like git for its developer-friendly workflows, and Subversion for its simplicity and multi-subtree scalability. However, Perforce brings some special capabilities:

  • Perforce is the repository of choice for game developers who use big asset files and terabyte-sized repositories.
  • Perforce has mature, commercially supported clients. They include visualizations like “heatmap,” which shows which lines are recently modified and a stream browser that shows the flow of code between streams.
  • Perforce merges on the server, which turns out to be useful. Git merges on the client. Git is a distributed VCS, where you have all of the information and software required to do a merge right on your workstation.  If you want to send code to a different stage of development someone with a different repository usually has to run a manual merge. Subversion is somewhere in between. It merges on the client, using information it requests from the server. This splitting of information places some limitations on the merges that it can do successfully and also requires manual intervention. Perforce is a truly centralized VCS that merges on the server. So you can set up streams and tell the server to merge changes automatically to specific teams, builds, and releases. The stream actions are important if you do a lot of continuous integration at enterprise-scale. You can accelerate development by feeding changes automatically to the various build and deploy points. That’s one reason why big software companies like VMware rely on Perforce.


The Assembla implementation includes all of our normal repository features, including a Web code browser, activity stream, and email alerts. You also get professional server management and backup. You get integrated permissions, which means that every space gets its own p4d server with users that match the space's team and can login with an Assembla username and password.

We added code review with merge requests that are very similar to our git merge requests. A developer can make changes on a “development" stream, and then create a merge request to send them to the “mainline” stream. A mainline owner can use the online review board to make comments and merge the changes.

So, you get four sources of acceleration from Perforce on-demand, hosted by Assembla. First, you can quickly create depots and invite users. Second, you can work together in an Assembla workspace with a highly visible activity stream and tasks. Third, you can use Perforce streams to run continuous integration with merge, build, test, and deploy. Fourth, you can review code from a lot of contributors and make sure that it works correctly, and your mainline stream is always ready to deploy, and you can release multiple times every day.


1) Get a client from the Perforce site.  Add a Perforce depot to any new or existing Assembla project. If you do not have an Assembla account, get started today for free.

2) Follow the instructions on the Assembla Source/P4 tool to set P4PORT and P4HOST. When using non-cloud Perforce you only set P4PORT to point to a server. In our cloud implementation we send P4PORT to a proxy server, and use P4HOST to connect you to the correct depot in our redundant and scalable cloud of servers.

3) You get a mainline stream and you can commit to it directly. Or, you can create development streams where your contributors can work and submit merge requests.


We did a Perforce/Assembla press release.  Assembla received the opportunity to become the FIRST provider of on-demand Perforce repositories after I sent a note to Perforce last year suggesting that we try it. Special thanks go to Randy DeFauw at Perforce for pushing this project forward and providing technical advice. Vladimir Zdorovenco and Sergiy Golub from Assembla figured out how to use the p4 sever in an on-demand, Web product. Thanks go to Nigel Chanter and Chris Seiwald, who run Perforce, for agreeing to try it and allowing Assembla licensing for up to 17 users for free to use with your Assembla project. If more users are necessary, please contact us for details.

4 Comments Click here to read comments

Deprecating Trac and Moving to Integrated Tools

Posted by Michael Chletsos on Wed, Jun 20, 2012

We have stopped offering Trac for new spaces.  We strongly recommend that new users and projects adopt Assembla Tickets with svn or git. We built the integrated Assembla tools as an upgrade to Trac more three years ago.  Now, we will focus on improving the quality of the newer Assembla features.

We will continue to support our existing Trac users with reliable service.  Some of those existing Trac users have been with us for many years.  When we first launched, we wrapped some on-demand features around Trac.  This started as a side project for us that I think was the best on-demand Trac hosting, and eventually attracted more than 100K users.  Now, dozens of vendors provide Trac hosting, and Assembla is no longer the best Trac host.  During the last nine years the Trac Project has helped tens of thousands of teams "write great software while staying out of the way."  We are grateful to the developers, including founders Daniel Lundin and Jonas Borgström, for bringing us this software.

Assembla has outgrown Trac.  We built our own Tickets and Source/repo tools to get better features, integration, localization, multi-tenancy, and spam protection.

Current users of Trac/hg and Trac/git may continue to use these tools for a limited time.  We will no longer offer Trac/hg, Trac/git, and Trac/svn for new installations. We will remove the Trac/hg and the Trac/git tools in the coming months, providing ample time to migrate out of these tools. Trac/svn is very popular at Assembla.  We will maintain it as long as we need to maintain it for existing users.

We highly encourage all users of these tools to switch over to our integrated code browser and ticketing tool.  For more information on migrating from Trac Tool to Tickets Tool, please read Migrating from Trac to Assembla Tickets

We hope that you will find that by removing some tools we are able to deliver a better core product.  If you have any questions or want help migrating to our integrated tools - please contact support (

9 Comments Click here to read comments

All Posts

Follow Assembla

twitter facebook youtube linkedin googleplus

Get Started

blog CTA button

Subscribe by Email

Your email: