Apex Code Development You need to sign in to do that
Don't have an account?
davcondev Continuous integration - what about the configurators?
The examples and how-tos I've seen for continuous integration with Salesforce are based on the deployment of raw metadata pulled from version control. But what about non-developers? I think they would come up to speed with version control ok, but they I doubt they would ever work with metadata - either directly or via a tool like Eclipse.
They know how to build change sets, is it possible to identify the associated metadata?
Would anyone know if the native version control entering pilot is going to cater for configurators?
https://success.salesforce.com/ideaview?id=08730000000BrBKAA0
They know how to build change sets, is it possible to identify the associated metadata?
Would anyone know if the native version control entering pilot is going to cater for configurators?
https://success.salesforce.com/ideaview?id=08730000000BrBKAA0
Yes, CI is geared more towards technical folks, but if it's done correctly, it's a one time set up, and then from there it's either a scheduled process or clicking of a button to perform a build.
To answer your questions around associated metadata. To an extent, some CI is possible with metadata and tooling api's, but you're looking at an even smaller subset of developers and technical folks that understand those apis.
If you haven't already, I'd suggest you follow Daniel Hoechst's blog at http://www.verticalcoder.com. (http://www.verticalcoder.com/) Daniel used to be mostly an administrator, but has become a little more technical with poking around with things like Continuous Integration. He actually ran a presentation on CI at Dreamforce, so also check that out if you're interested.
Hope that helps a little bit.