Search Knowledge Base by Keyword
How To Auto-Deploy Git/SVN Updates
Our New Cloud Hosting Platform can help you increase your productivity with the deployment of your projects, and ensures seamless integration within your application servers.
The deployments take place based on the changes that were applied to the appropriate remote repository, in which you can simply work via the preferred Git/SVN service.
Update your codes and save; then all the changes to your VCS Project will be pushed automatically to your production server.
This auto-deploy feature does not require any additional settings within the Git repository side and works with SVN.
Preparing your Project
- First of all, prepare the environment for further addition of the intended project with the code from Git/SVN.
Note: Java environments would require an additional Maven node for creating and pushing the code to the application server, while for the rest of the languages this mechanism is handled by the corresponding compute nodes.
2. Once your environment is created, click the “Add Project” button next to the appropriate node (i.e. Maven for Java or your application server for any other language)
3. Within the opened window, switch to the tab with the type of VCS used and fill in the required fields: enter the “URL” to the necessary repository, specify the credentials and assign the name for your application.
Also, in the case of a Maven build node, you’ll need to additionally specify the “Name” for your project and the “Environment” it is intended to be deployed to.
Setting Automatic Project Updates
Now, since all the deployment information is completed, you may proceed with setting up the automatic updates for your project.
- Tick in the “Check and auto-deploy updates” to enable it and get the lower section expanded.
The “Check every (min)” option will then appear, which is used to define the frequency of checking the repository for new updates, that are pushed since the last check.
If you set, for example, a 1-minute interval, the check will be done every minute, and if you specify a 1440-minute interval – the check will be done once per day.
- if the check interval is smaller than the time needed to build and deploy the project, the next task will be lined up in the queue until these tasks are completed
- in the case that your application server layer contains several nodes, please also consider the details on their update sequence
2. As a result of these configurations, if there were any changes made at the application sources, they will be automatically built and deployed (for Java projects), or just applied through updating the project once per the specified period of time. Click “Add” for confirmation.
You can also monitor the automatic deployment processing and its results, which can be done by accessing the appropriate log file (named “vcs_update”) for the application server or Maven node.
Note: You may also re-configure your deployed environment via Git/SVN application settings by navigating to your environment and selecting the “Edit” button next to the appropriate project.
You will then see the frame opened, the same as the one used for the project addition, this is where you can change the state for any of the options, just hit on “Apply” to confirm your new settings.