To greatly increase your productivity as a developer, CirrusGrid provides you with the possibility to set periodical automatic deployment of your project and, in such a way, ensure its continuous integration to the corresponding application server. Such re-deploys take place based on the changes that were applied to the appropriate remote repository, thus you can simply work via the the preferred Git/SVN service, without ever leaving it.
Just update your code, make a commit and all the changes in your VCS project will be automatically pushed to your production environment, after the stated time interval. And as a distinction from Git hooks, the CirrusGrid auto-deploy feature does not require any additional configurations on the Git repository side and works with SVN. So, let’s discover how to get it!
Note: that Java environments require an additional Maven node for building and pushing the code to the appropriate application server, while for the rest of the languages this mechanism is handled by the corresponding compute nodes themselves.
We’ll consider this on the example of Maven build node for Java – however, any other application server can be configured similarly.
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)
In the opened window, switch to the tab with the type of VCS used and fill in the required fields: insert the URL to the necessary repository, specify the authentication details and designate the name for the Context your application should be placed at.
Also, in case of a Maven build node usage, you need to additionally specify the Name for your project and Environment it is intended to be deployed to.
Tip: If you need more detailed information on these options, refer to the relevant instruction from the list below according to the engine your application is running on:
Now, as all the crucial for deployment information is stated, you may proceed to configuring the automatic updating of your project.
1. Tick the Check and auto-deploy updates line to enable it and get the corresponding section expanded.
The Check every (min) option will be revealed, which is used to define the frequency of checking the repository for new commits, pushed since the last verification.
As you can easily guess from the option name, it is stated in minutes. Thus, 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.
2. As a result of these configurations (which, despite of a long description, take less than a minute to specify), 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 (for the rest of the languages) once per the specified period of time.
Click Add for confirmation.
Tip: This frame also includes a number of additional settings, which may come in handy for organizing a proper interaction of the CirrusGrid system with your remote repository:
In order to monitor the auto-deployment processing and its results, you can look through the appropriate log file (named vcs_update) for the corresponding app server or Maven node.
Note: You are also able to re-configure your deployed via Git/SVN app’s settings by navigating to your environment and selecting the Edit button next to the appropriate project. You’ll see the frame opened, similar to the one that was used for the project addition, where you can change the state for any of the options, described above (just click on Apply to confirm the new settings).
That’s all! Just make these simple configurations while adding your project to the CirrusGrid Cloud and feel free to continue working with your code through Git/SVN repository, without having to come back to our dashboard again. Rest assured that everything will stay up-to-date on your production, automatically!
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.