Version Manager

pauls985 over 7 years ago

Can someone just confirm my understanding of the following :
If I use the Version Manager to update source control - I'm able to import separate application zip files into the central repo, for instance AppA and AppB
However lets say I now want to deploy AppB into a new Appian env- I need to build a deployment package. however the BuildPackage function of the tool, seems to build a package containing all the Applications that are found within the central repo. Furthermore the Deployment tool, also doesn't have an option to only deploy individual app's as it only referes to the single zip created in the Version Manager.

Discussion posts and replies are publicly visible

Parents

0 Naresh
Certified Associate Developer
over 7 years ago

Hi Paul,
BuildPackage action will include all files if you don't provide start hash and end hash. If I understand correctly, I can suggest you one thing, export a single application you want to deploy and add the contents to the repo with a commit message explaining about that specific application. Once done, note the start and end hashes of the specific application you have added, later use them to build a package for the specific application contents you are looking for.
There is a clear documentation provided, please have a deep look. forum.appian.com/.../Deployment_Automation.html

Hope this helps!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Mike Cichy
Appian Employee
over 6 years ago in reply to Naresh

Another option is to stop thinking applications as separate entities, since in many situations they are interconnected. The way versioning manager is implemented, it essentially advocates for trunk based development where you do not separate the code since it is not separated in Appian.

Understandably, this does force some heavy changes to whatever SDLC you are using but moving toward a more CI/CD world I think is worth it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Mike Cichy
Appian Employee
over 6 years ago in reply to Naresh

Another option is to stop thinking applications as separate entities, since in many situations they are interconnected. The way versioning manager is implemented, it essentially advocates for trunk based development where you do not separate the code since it is not separated in Appian.

Understandably, this does force some heavy changes to whatever SDLC you are using but moving toward a more CI/CD world I think is worth it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data