Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
R repo_manifest
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • 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
  • cobalt
  • repo_manifest
  • Wiki
  • build stories

build stories · Changes

Page history
mstevens created page: build stories authored Oct 24, 2017 by Mark Stevens's avatar Mark Stevens
Show whitespace changes
Inline Side-by-side
Showing with 29 additions and 0 deletions
+29 -0
  • build-stories.md build-stories.md +29 -0
  • No files found.
build-stories.md 0 → 100644
View page @ c7b3d7a4
# Build and Deploy
### Goals:
Create a build and deploy infrastructure that separates each project into it's own build cycle
* Shift version declaration to developer teams.
* Add runtime declaration to developer teams.
* Differentiate public shared libraries from team convenience libraries through nexus publishing.
* Prevent public library advancement from forcing downstream cascades of code refactoring.
* use build to create and update manifest declarations via REST api calls to platform services.
* use google repo to allow developers to consolidate projects into a single IDE workspace.
Move deployment management to a browser-based tool based on the registered project manifests collected from project builds
### Project responsibilities
* declare Version Name in build.gradle
* integrate the buildcore.gradle script if it is found
* declare targets as `<meta-data name='targets' value='sitehost, adhost' />`
* declare runtime deps as `<meta-data name='rundeps' value='com.buzztime.package:1.00+; .. '/>`
### Build Responsibilities
* embed branch in the version name for DEV builds
* embed project, version name, version code, product (debug/release/androidTest/aar/jar), flavor (skin) in the artifact fname.
* allow local build/installs with DEV buzztime keystore
* allow nexus snapshot publishing by branch
* generate project manifest of debug/release/androidTest x flavor(s), runtime deps and targets for upload to PS
* INT/STG : upload to nexus releases, upload manifest to INT/STG PS
* DEV : upload debug/release apks to nexus SNAPSHOT
Clone repository
  • build stories
  • dev stories
  • fitness testing
  • handshake
  • Home
  • logging
  • provisioning
  • rockchip parameter file format v1.3 (en)
  • secure boot application note
  • secure provisioning
  • sitehub hardening
  • tee readme
  • tee