Scribd
Upload
23 views2 pages

PL SlackCommandstobuildanddeploy 250422 0140

Uploaded by

shiva
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
23 views2 pages

PL SlackCommandstobuildanddeploy 250422 0140

Uploaded by

shiva
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Slack Commands to build and deploy

From Slack messages we can now below operations , we just need to message as stated in below examples.

Type of Operations supported by Slack commands.

1. Version Whitelist
2. DeviceId Whitelist
3. Build the Backend Source Code
4. Build the Game(Client + Server)
5. Deploy the Backend Artifacts and Game Battle Server.

The commands are in format as below

/jenkins-build <action-type> various options

Below are the action-types

versionwhitelist
devicewhitelist
build-backend
build
deploy
terminate

1. To Whitelist the version : We need to send the Slack message in below style .

/jenkins-build <action-type> --version <version-id> --env qa-03

examples

/jenkins-build versionwhitelist --version T03.02.05-202204190100 --env qa-03

supported Environments are

dev-01 ,dev-02,dev-03,qa-01,qa-02,qa-03,perf-01,ext-01,ext-02,int-01 and int-02

2. To whitelist the DeviceID

/jenkins-build <action-type> --deviceId <device-id> --env qa-03

examples

/jenkins-build devicewhitelist --deviceId 3o4838odjfldj3483 --env qa-03

note: Environments listed in point 1 are suppored here as well.

3. To Build the Backend Code.

/jenkins-build <action-type> [--revision] [Revision Number]

examples

Below example will build the latest revision avialable

/jenkins-build build-backend

Below example will build the sepecific revision

/jenkins-build build-backend --revision 561

4. To Deploy the Backend Code.

/jenkins-build <action-type> [--build-zip-file] [Build Zip File] [--backend-built-revision]


[backend-revision-number] [--env] [supported envs]

examples

Below example will deploy zip file in qa-03 environment with specified revision.
/jenkins-build deploy --build-zip-file Underworld-Global-4075-T03.02.05-202204182106-Linux-
Build.zip --backend-built-revision 561 --env qa-03

Below example will deploy specified zip file and latest backend build revision in specifed supported environment

/jenkins-build deploy --build-zip-file Underworld-Global-4075-T03.02.05-202204182106-Linux-


Build.zip --env qa-01

Below example will deploy latest zip file and latest backend built revision in supported environments

/jenkins-build deploy --env qa-02

Below example will deploy on qa-03 by defualt if not --env is mentioned

/jenkins-build deploy

5. To build the Game Artifacts

/jenkins-build <action-type> [--branch] [SVN Branch relative Path] [--revision] [SVN Revsion
to Build] [--platform] [all | linux | android | windows]

examples

below example will build for all platforms (Linux, windows and Android) for sepcified revision 4005 , if we donot mention
revision or platform it will take latest revsion and all as platform value.

/jenkins-build build --branch Underworld/Trunk/Underworld-Global --revision 4005 --platform


all

OR

/jenkins-build build --branch Underworld/Trunk/Underworld-Global --revision 4005

Below example it will take default revsion latest and platform as android for default branch Underworld/Trunk
/Underworld-Global and

/jenkins-build build --platform android

Below example it will build for defulat platform all for default branch and for default latest revsion

/jenkins-build build

Please note the branch name should alway be in relative Path as below are some example,

Underworld/Trunk/Underworld-Global

Underworld/Trunk/Head/Underworld-LZ

Note: the branch name are case sensitvie , the name should be exactly same as in SVN

You might also like