• Test Jenkins build system

o Disable the CruiseControl DEV job to prevent tagging conflicts.

o Enable Polling of SCM on Jenkins job.

o Make change or merge code to develop or fb_* for:

• Lib

• App

• CommunityGames

o Jenkins should start the build within the specified polling period.

• Verify build artifacts:

• Lib - downstream projects for any changed Libs should be rebuilt

• App

• CommunityGames

• Verify Tablet Manifest Info DEV.csv content is updated correctly.

• Test Jenkins deploy system

o Uncomment stage('Deploy Tablet Release') in Jenkinsfile/job replay for:

• fb_* – to test deploying to a group, see

• develop – to test deploying to "Global"

o Run Jenkins job.

• Verify apks are delivered to:

• dev-filesvr-01

• Group assigned to fb_*

• All tablets (for develop)

• Test Jenkins tagging

o Currently being tested with local tags

o Run Jenkins job with '--tags' appended to the git push command.

• Verify correct tag is applied to the repo – this will begin the process of generating incremental builds in Jenkins and tagging successful runs

Notes

0. Verify if it is possible to reuses artifacts from old build or if all apks will need to be delivered ..

1. QA Branches (release, test, hotfix ) are all located in the INT builds column. naming : qa_, rb_, hf_

2. Rules 0. QA pulls from develop and master. (Team QA's use feature branches for testing) 0. Devs commit into fb_ , hf_ 0. Devs may commit to rb_ (as permitted by qa)