sfdcignore file which may be needed depending on your configuration.Ĭonnecting Travis CI to your repo is as easy as logging in with your GitHub credentials, and toggling it on for the repo holding your Salesforce metadata. If you do use Solenopsis for personal it will make some things easier such as building out the. The only “requirement” is that is in the src directory so that we can use other directories to hold our build scripts and other build requirements. While I use Solenopsis to pull data down and push it back up during development, there is no requirement on the end user using it in order to get the code in the repo. We’ll be using Solenopsis to deploy to Salesforce via Travis CI. Solenopsis is an extension of the Ant Migration tool that has a bunch of fancy Ant and Python scripts to help deploy code and manage all that pesky XML. Solenopsisis a project that Scot Floess and I have been working on for several years and it has been doing all of the deployment work for our team since it’s inception. They do have support for private GitHub repos, but you will have to pay to access them. Well, it’s free if you’re using it for a open public project on GitHub (which I happen to be doing). Travis CI has most of the features that you would expect from any hosted CI solution, but where it drew me in was it’s pricing. I had heard of Travis CI before, but had never had a chance to look into it. However, this is a public facing project and I needed something that everyone contributing could have access to. This has not been a problem for me in the past because I’ve always had a Jenkins host that was setup and maintained by our admins.

Recently I started working on a project that required a Salesforce CI build system.

Set up ant for salesforce