What is StratoSource?

Mark Smith edited this page Aug 26, 2016 · 68 revisions

Table of Contents

What does it do?

StratoSource is a backup and change tracking tool for Force.com Projects. It is designed to help fill the void in cloud-based development environments where multiple people are working in close proximity. It:

  • Backs up the environment configuration
  • Tracks what changed
    • Intelligent tracking "understands" Force.com XML files and correctly identifies objects, fields, labels, classes, triggers etc. as created or updated
    • Presents it in an easily readable human-friendly list
  • Imports development stories from Rally or AgileZen (optional)
  • Allows a development team to tag and track which changes go with which stories
    • Stories can be combined to form releases
    • Releases has an area to add notes or manual instructions
    • The manifest view shows a list of all tracked Salesforce assets for the release.
How does StratoSource compare to normal Source Control Workflows?

How does it work?

StratoSource is made up of 3 major subsystems:

  1. CRON jobs that snapshot your Force.com instances
    • Each job runs on some regular interval
    • Snapshots are checked into a GIT Repository. This repo is NOT intended to be commited to by anything other than Stratosource and doing so will break change detection. See Best Practices.
  2. A change detection subsystem
    • Runs after each backup
    • Calculates what has changed since the last snapshot
  3. A Web UI
    • It presents the changes to a user in a grouped list view
    • Changes can then be associated with stories
    • Stories can be created locally or optionally imported from Rally
    • Link integration with cgit is provided to see diffs on individual files

StratoSource Architecture

Who is this for?

StratoSource is designed to be a "bolt on" type system. It does not interfere with your current processes or systems. It simply adds tracking and release management into your existing workflow.

It is geared towards:

  • SalesForce administrators
  • Force.com developers
  • Environment managers


There are a number of ways you can contact us:

  • If you have a success story to share with us on how StratoSource helped you, please send it to success@stratosource.com.
  • Use the Issue Tracker on this site to log problems with the product.
  • If you are lucky you can catch us on our IRC FreeNode channel #StratoSource. Either we or the community will try to help with issues or questions.
  • As a last resort, you can email us at support@stratosource.com. We cannot guarantee turnaround times but will try to answer any questions that come up.


StratoSource is released under the GPLv3 license.

What is with the name?

StratoSource started as a bridge building initiative by a couple of Force.com developers inside of Red Hat. Due to the continued increase in complexity of their SalesForce instance, it was getting harder and harder to track changes and figure out what should and should not be in a release.

A rapid prototype was thrown together to help manage this problem. The tool quickly took on a life of it's own as other groups inside the company, facing the same problem, adopted to the tool as well.

The developers got asked to present the tool at DreamForce 2011 as part of a introduction to GIT session. A decision was made by management that in the typical "Red Hat Way", it was appropriate to open source the tool.

Legal requested a couple of names be chosen to vet for availability. Due to the goal of backing up the "Cloud", one of the names the developers came up with was "Stratus Source" (named after Stratus clouds). Unfortunately the developer that sent that name to legal, mistyped it as "Strato"Source. Well that is what Legal approved, and ultimately what stuck.

That is how the name ended up sounding more like "StratoSaurus" than Stratus Clouds.

Thanks Russ McMullin for designing us a Stratosaurus!

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.