Source/Version/Change Control

RE: Source/Version/Change Control

Richard Michaelis — Thu, 13 Jan 2022 07:28:04 GMT

hi bipindras,
so its the "organization standard". So you looking for a solution to follow on guidelines. But guidelines have usually a purpose. You can usually serve this purpose in different ways.
Stefan explained a possible approach regarding git, but i would recommend to talk to your client.
Before that, try to be self confident about the appian possibilities if versioning, exporting functions etc.

RE: Source/Version/Change Control

Stefan Helzle — Thu, 13 Jan 2022 07:10:09 GMT

The typical development approach is

A single DEV environment, many developers and iterative sprint based releases. No feature releases, no branching, no merging.

Everything can be done. But IMHO there is no need for.

Some clients store the full application package to Git as it is deployed on the production environment.

RE: Source/Version/Change Control

bipindras0001 — Thu, 13 Jan 2022 07:05:39 GMT

Hi Richard, As per our organization standards we are using Git as source code repository. Also want to use Git branching, versioning features and Azure Devops for Devops practices.

Just want to check, if it is possible and recommended to use third party source control repositories other than Appian?

RE: Source/Version/Change Control

Richard Michaelis — Thu, 13 Jan 2022 06:59:37 GMT

hi bipindras,
why do you want to use git ;) ?
What is the benefit you expect here?

RE: Source/Version/Change Control

Stefan Helzle — Thu, 13 Jan 2022 06:43:51 GMT

I am aware of this. And yes, this can be used. In my experience it is not necessary if the is no specific reason.

Appian exports objects in an XML format. These files would be managed in Git.

RE: Source/Version/Change Control

bipindras0001 — Thu, 13 Jan 2022 04:00:53 GMT

Thanks Stefan, But there is Automated Versioning Manager tool on Appian app market. Can this tool be used to integrate with Git, if yes in which format Appian object would be added to source control.

community.appian.com/w/the-appian-playbook/198/deployment-automation#Using_Git_as_Version_Control_System

RE: Source/Version/Change Control

Stefan Helzle — Wed, 12 Jan 2022 11:05:48 GMT

This topic might become quickly excessive for a format like this here.

In general all Appian objects are versioned. But there is no configuration management in which you could compose a package from specific versions of objects.

In general, my experience with Appian that most of the hassle of why you would want Git+CI/CD just does not exist.

You have a single environment in which all developers work at the same time.

Appian has pretty good built in deployment mechanisms.