You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+12-11
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,16 @@
1
-
## Simple Automated CI/CD Pipeline for Git Projects
2
-
3
-
This Git-Push-Deploy solution enables automatic delivery of updates within your Git application sources directly to the cloud. The package can be applied as an add-on to **Java**, **PHP**, **Ruby**, **Node.js**, **Python** and **Go** projects, run on top of [the certified stack templates](https://docs.jelastic.com/software-stacks-versions#app-servers).
1
+
# Simple Automated CI/CD Pipeline for Git Projects
4
2
3
+
This Git-Push-Deploy solution enables automatic delivery of updates within your Git application sources directly to the cloud. The package can be applied as an add-on to **Java**, **PHP**, **Ruby**, **Node.js**, **Python** and **Go** projects, run on top of [the certified stack templates](https://www.virtuozzo.com/application-platform-docs/software-stacks-versions/).
The workflow depends on the programming language used in your project:
9
-
-*for Java-based projects*, the package initiates creation of separate environment with a [Maven build node](https://docs.jelastic.com/maven-cloud-hosting-in-jelastic), which will be responsible for interaction with remote Git repository, triggering your application builds and their deployment to application server
10
8
9
+
-*for Java-based projects*, the package initiates creation of separate environment with a [Maven build node](https://www.virtuozzo.com/application-platform-docs/java-vcs-deployment/), which will be responsible for interaction with remote Git repository, triggering your application builds and their deployment to application server
11
10
-*for PHP/Ruby/Node.js/Python/Go apps*, the package sets up a pipeline for project deployment directly to the ROOT context on a web server (consider that Ruby app servers are displayed with a deployment mode instead of a context within dashboard, though the actual project location is the same)
12
11
12
+
All related deployment operations are performed via [Application Platfom API](https://www.virtuozzo.com/application-platform-api-docs/). If a server runs multiple containers, all of them will be restarted sequentially (with a 30-second delay by default) during the update to eliminate possible application downtime. Beside that, a special [ZDT Deployment](https://www.virtuozzo.com/application-platform-docs/php-zero-downtime-deploy/) option is used for PHP applications, ensuring their constant availability even with a single application server node.
13
13
14
-
All related deployment operations are performed via [Jelastic API](https://docs.jelastic.com/api/). Herewith, if a server runs multiple containers, all of them will be restarted [sequentially](https://docs.jelastic.com/release-notes-49#sequential-restart-deploy) (with a 30-second delay by default) during the update to eliminate possible application downtime. Beside that, a special [ZDT Deployment](https://docs.jelastic.com/php-zero-downtime-deploy) option is used for PHP applications, ensuring their constant availability even with a single application server node.
15
14
16
15
## Requirements
17
16
@@ -35,22 +34,24 @@ Before applying the package, please consider the following points:
[](https://www.virtuozzo.com/install/?manifest=https://raw.githubusercontent.com/jelastic-jps/git-push-deploy/master/manifest.jps)
38
+
39
39
40
-
## How to Integrate Git-Push-Deploy Pipeline to Jelastic Environment
40
+
## How to Integrate Git-Push-Deploy Pipeline to PaaS Environment
41
41
42
-
To install the Git-Push-Deploy package, copy link to the **_manifest.jps_** file above and [import](https://docs.jelastic.com/environment-import) it to your Jelastic dashboard.
42
+
To install the Git-Push-Deploy package, copy link to the **_manifest.jps_** file above and [import](https://www.virtuozzo.com/application-platform-docs/environment-import/) it to your application platform dashboard.
Within the opened installation window, specify the following data:
47
+
47
48
-**_Git Repo Url_** - HTTPS link to your application repo
48
49
-**_Branch_** - a project branch to be used
49
50
-**_User_** - your Git account login
50
51
-**_Token_** - personal Git access token for webhook generation (can be created within [GitHub](https://github.com/jelastic-jps/git-push-deploy/wiki/GitHub-Access-Token)/[GitLab](https://github.com/jelastic-jps/git-push-deploy/wiki/GitLab-Access-Token) account settings)
51
52
-**_Environment name_** - target environment your application should be deployed to
52
53
-**_Nodes_** - application server name (is fetched automatically upon selecting the environment)
53
54
54
-
Click **Install** and wait for Jelastic to configure CI/CD pipeline for your project. Once your application is deployed, all the further changes, committed to a source repository, will be automatically delivered to your environment inside Jelastic Cloud.
55
+
Click **Install** and wait for the platform to configure CI/CD pipeline for your project. Once your application is deployed, all the further changes, committed to a source repository, will be automatically delivered to your environment.
55
56
56
-
For more information on the package please refer to the article [GitPushDeploy to Containers](https://jelastic.com/blog/git-push-deploy-to-containers/).
57
+
For more information on the package please refer to the article [Git-Push-Deploy to Containers](https://www.virtuozzo.com/application-platform-docs/git-push-deploy/).
Copy file name to clipboardexpand all lines: text/success.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
3
3
Open your target environment URL **[${env.protocol}://${env.domain}](${env.protocol}://${env.domain}/)** to access your application.
4
4
5
-
If something does not work as expected, please check the logs for more details or submit a question to [Jelastic community](https://stackoverflow.com/questions/tagged/jelastic).
5
+
If something does not work as expected, please check the logs for more details or submit a question to [community](https://stackoverflow.com/questions/tagged/jelastic).
0 commit comments