|
28
|
1 |
In this directory you find some examples of deploy procedures
|
|
|
2 |
for general purposes deploys (single wars, single files, tarballs, list
|
|
|
3 |
of files from a list...) described in a single define.
|
|
|
4 |
|
|
|
5 |
They are made in order to be generic enough to adapt to different
|
|
|
6 |
environments and scenarious but you might need to design your
|
|
|
7 |
own deployment process.
|
|
|
8 |
|
|
|
9 |
In order to do that you can create a new define that includes:
|
|
|
10 |
- All the variables, required or optional, you may want
|
|
|
11 |
- One puppi:project statement
|
|
|
12 |
- All the puppi::deploy statements you need (each one runs a command)
|
|
|
13 |
- All the puppi::rollback statements you need
|
|
|
14 |
- One or more puppi::report statements for reporting
|
|
|
15 |
|
|
|
16 |
The examples provided here make use of the scripts provided in
|
|
|
17 |
puppi/files/scripts and tend to split the deploy procedures in many
|
|
|
18 |
different, reusable, scripts (one gets the source file(s), another
|
|
|
19 |
archives the current content, another one actually copies the files
|
|
|
20 |
to deploy and so on) but you can use just a single new script or
|
|
|
21 |
whatever combination you might prefer.
|
|
|
22 |
|
|
|
23 |
The default puppi scripts and the general ordering of commands
|
|
|
24 |
execution in these sample deploy defines follow this scheme:
|
|
|
25 |
Priority - Kind of operations
|
|
|
26 |
1x - Pre Deploy checks
|
|
|
27 |
2x - Files retrieving and preparation
|
|
|
28 |
3x - Operations to accomplish before the deploy (Archiving, Services stopping..)
|
|
|
29 |
40 - Deploy.sh - The script that actually copied the files on deploy dir
|
|
|
30 |
4x - Operations to accomplish after the deploy (Services start...)
|
|
|
31 |
8x - Post Deploy checks
|