Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N notebook
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mark Stevens
  • notebook
  • Wiki
  • build server move

build server move · Changes

Page history
mstevens created page: build server move authored Dec 07, 2016 by Mark Stevens's avatar Mark Stevens
Hide whitespace changes
Inline Side-by-side
Showing with 51 additions and 0 deletions
+51 -0
  • build-server-move.md build-server-move.md +51 -0
  • No files found.
build-server-move.md 0 → 100644
View page @ 42abd728
* 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
\ No newline at end of file
Clone repository
  • branch code plan
  • build and test configuration
  • build artifact versioning
  • build server instrumented testing
  • build server move
  • bzt16wifi02 releases
  • bzt18uxa02 releases
  • configuration settings and permissions
  • create a repo from cli in gitlab
  • engineering status
  • feature deployment
  • gitlab installation instructions
  • Home
  • ota update and deployment
  • qbert implementation
View All Pages