Doors: 5:30pm Start: 6:00pm
Automating source control for Administrators and Developers
Does your team need source control but not the overhead or learning curve? Are developers on your team using source control but administrators are not? We have a tool that can help. Join us to learn how Groupon automated source control with a point and click interface that converts standard change sets into GitHub pull requests without using any Git commands.
Details: Groupon built - and will soon open source - a tool that can convert change sets into GitHub pull requests. I will explain the technical details of how we accomplished this and walk through the creation of a pull request.
Pedro Dal Col is a salesforce.com developer at Groupon Inc. with 7 years of software development experience.
Introduction to Continuous Integration
Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early. By integrating regularly, you can detect errors quickly, and locate them more easily. ( from http://www.thoughtworks.com/continuous-integration)
If you’re willing to suspend some belief and ignore certain aspects, the Production/Sandbox deployment model that Salesforce uses could be considered Continuous Integration. But what about real Continuous Integration with Salesforce? It can be done with the Force Migration tool and Jenkins, along with an open source GitHub alternative called Git Lab. How to set up and configure this functionality will be shows, along with a few other bonus topics like email notifications.
Ben Baker, Senior Software Engineer, Oracle BigMachines Express; 4 years of experience as a Force.com Developer; designed and maintains development operations for Oracle BMX.