Create Guzzle Release and Deploy on Existing Env - ja-guzzle/guzzle_docs GitHub Wiki

Creating the realase

  1. Run guzzle build from the jenking pipeline: a. http://192.168.1.207:15500/job/guzzle_release/ c. Click on Build Now d. Specify the release number (tag) and commit id:

You can take latest commit id from the stable build of Guzzle form the Jenkin testsuite at: http://192.168.1.146:8080/job/guzzle_test_hdp_2.6.4/ (just view the logs for “guzzle_checkout” stage)

Or you can take latest commit id for the develop branch for ingestion project: https://github.com/ja-guzzle/ingestion/commits/develop

Once the build is completed it will take be ready at:

At [email protected]:/guzzle_release

Deploying the release

On the target env (example: singtel_dap) you can scp the file:

  1. Its recommended to keep all the guzzle release binaries in the sub-folder under guzzle_home example: $GUZZLE_HOME/guzzle_release
  2. scp -P 2222 [email protected]:/guzzle_release/guzzle-0.3.6.tar.gz .
  3. Untar the file: tar xzf guzzle-0.3.6.tar.gz
  4. Copy the following binaries in respective location:
  5. go to release folder bin directory example: /guzzle_singtel/guzzle_release/guzzle-0.3.6/bin and copy the files cp *.jar $GUZZLE_HOME/bin
  6. copy jar from release folder to guzzle_home: cp *.jar $GUZZLE_HOME/api
  7. Copy entire web direcotryover and then change index.html to point to correct path:
mv $GUZZLE_HOME/web $GUZZLE_HOME/web_3_3 # rename the existing dir
cp -r web $GUZZLE_HOME/
vi $GUZZLE_HOME/web/index.html # update the ip and port number as per your API service
  1. libs directory is required to copied if there are any new third party libs introduced (which is very rare)
  2. Restart the guzzle services (API and web)
cd $GUZZLE_HOME/tools/elasticsearch-6.2.4/bin
nohup ./elasticsearch -E http.port=19090 & # This is not mandaotry
cd $GUZZLE_HOME/api # this is must
nohup java -jar api-0.0.1-SNAPSHOT.jar &
cd $GUZZLE_HOME/web # this is not mandatory
nohup serve -p 28082 -s . &
⚠️ **GitHub.com Fallback** ⚠️