Automated Deployment using SVN

Hi All,

I have one requirement where I need to automate the deployment to higher environments. We are currently using SVN for code check in

There are 3 possible use cases:

  • Whenever a developer check in the patch in SVN in Appian repository it should trigger a deployment to the higher environment and we should have ability to control the environment where we want to deploy.
  • Other way can be after code check in SVN using command prompt we should be able to trigger the deployment.
  • After code check in we schedule the deployment and it will automatically deploy the check in patch in specified environment.

I am using one Shared Component "Automated Deployer" but in that also we have to go to link manually, upload the patch and the deploy it but now we need to automate the process completely.

Any help will be appreciated.

Thanks

  Discussion posts and replies are publicly visible

Parents
  • Hi Mike,

    Thank you for the response.
    Can you please elaborate a bit where exactly I need to write a script to trigger deployment and how it will Integrate with Appian Environment.
    Also if you can please provide some examples.

    Thanks
  • 0
    Appian Employee
    in reply to PGarg

    Unfortunately, I do not have an example available but I would suggest using a CI tool like Jenkins to orchestrate your deployments. Check here for a description with Git (there is a Jenkins plugin for SVN as well): 

    Mind you, the end to end process is not as straightforward as it is described. There are additional complications that you need to consider:

    1. Storing the state (start tag) of each environment
    2. Storing of release candidates
    3. Version control of DB scripts
Reply
  • 0
    Appian Employee
    in reply to PGarg

    Unfortunately, I do not have an example available but I would suggest using a CI tool like Jenkins to orchestrate your deployments. Check here for a description with Git (there is a Jenkins plugin for SVN as well): 

    Mind you, the end to end process is not as straightforward as it is described. There are additional complications that you need to consider:

    1. Storing the state (start tag) of each environment
    2. Storing of release candidates
    3. Version control of DB scripts
Children