Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
I am interested in seeing if we can have multiple developers use their own dev environments and git. Idea is that we can setup a repo that allows us to automatically track changes to changed objects from your own environment and push to git.
I know we can use patches of your changed stuff and push to git and have other people pull them down using AVM and ADM, but it would be easier to just setup git to track the objects changed.
Discussion posts and replies are publicly visible
Is there a reason why your developers can't work on the same dev box?
We are just exploring options. We are currently on a shared integration dev box. Some developers work in that directly. Others use a docker and merge their code in. We will have some dev teams eventually outside our firewall where we have to merge their code in.
It's fine to bring the code in from other instances if that works for you. But, I'd encourage you to avoid getting to creative, such as toying with your file system. Ideally all the dev will take place on "dev". Over time, you're likely to have integrations and other dependencies that are not practical to scale out to an unlimited number of separate environments.
We already have a huge application and many many plugins. This is a very mature app and as we scale to multiple dislocated dev teams we need to accommodate a better branching and merging strategy than is feasible with patch>avm>branch>merge>adm>import. We need to do this on a daily basis per developer with minimal impact to velocity. Daily automated builds from git and regression testing (automated and manual) needs to occur off this code.
Trying to figure out how to CI/CD and we have a full DevOps team who is well versed in traditional development practices. Appian makes it much more difficult.
Have you found that deployment automation manager does not suit your needs?
https://community.appian.com/b/appmarket/posts/deployment-automation-manager
It works fine, however it is very manual with the config file. Still have to patch up your changes and deploy them, We have not used the tooling for auto import and since we don't get conflict resolution (inspect patch) features it's not ideal for source control by multiple people on the same set of objects.
We are also on premise so the import app for cloud isn't applicable.
To hook into our existing devOps tooling, ability to do true commits from the appian library would be fantastic. Tagging these commits would push them through the build, qa, regression, package tool chain.