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.
- if the verification interval is smaller than the time needed to build and deploy the project, the next task will wait in a queue until these operations are completed
- in case your application server layer contains several nodes, please also consider the details on their update sequence
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.
This frame also includes a number of additional settings, which may come in handy for organizing a proper interaction of the Jelastic system with your remote repository:
- The Checkout now option (present for non-Java languages) is used to indicate whether you’d like to deploy your project immediately after its addition or postpone this operation (for being either initiated manually later or performed automatically during the first further checkout by the enabled auto deploy feature).
- The Auto resolve conflict option is also active by default and represents an analogue of the git reset --hard command. It is used to prevent the occurrence of merge conflicts during subsequent project updates, which can take place if the same file was modified in both the remote repository and your project, hosted at Jelastic Cloud. If such an issue arises, this contradictory file will be updated according to its repository version (which is considered as the correct one), discarding the locally made changes. We recommend not to disable this option unless you know exactly what you are doing.
The Enable zero-downtime deployment option (currently available for PHP only) allows to continuously deploy the updates of applications, located at the ROOT context, without any interruptions in application work. Herewith, if enabled, your choice will be remembered and used during all the ensuing auto-updates.