Skip to content

Latest commit

 

History

History
51 lines (42 loc) · 2.64 KB

Todo.md

File metadata and controls

51 lines (42 loc) · 2.64 KB
Raw

TODO

  • introduce a task being run directly (01), described within a job (02), described via YAML in a resource (03)

  • flesh out running tasks locally; alternate inputs; hijacking

  • fly intercept (hijack)

  • introduce input resources; overview what's available

  • introduce output resources; overview what's available

  • show examples of how inputs to tasks are passed via files

  • trigger a job to build if a resources changes (06 - via timer resource)

  • explicitly introduce the build plan

  • named pipelines

  • aggregate & do steps - all inputs need to be in first aggregate step

  • conditions steps - build plan fails if step fails; but can handle failure explicitly based on previous step results (combine with aggregate to cover success & failure cases); perhaps to determine if you bump semvar

  • get steps with passed: [job-a, job-b]

  • task steps that produce new resources (e.g. a tgz) - 09?

  • update to new concourse in vagrant - vagrant box update & fly sync

  • update to new concourse in bosh-lite

  • passing tasks to other tasks in build plan

Show case resources

  • get git repo
  • fetch and bump semver X.Y.Z numbers (20)
  • push to git repo (bump version, get git, task to update version file, push git)
  • deploy an app to Cloud Foundry (10)
  • running tests of a Golang app (11)
  • building, testing, deploying Java app
  • building, testing, deploying Ruby app
  • build/push a docker image - perhaps automate https://github.com/mmb/bosh_cli_docker_container (35, demo in 41)
  • pull a docker image (36)
  • pull a docker image and use it as image for a task (perhaps drnic/spiff?)
  • get bosh release (44)
  • get bosh stemcell (44)
  • bosh deploy (45)
  • spiff merge (46)
  • spiff merge -> store in git -> bosh deploy (47)

Non-basic

Writing Resources

  • Show resources are available per worker node (via ATC API; ssh in to vagrant)
  • Show that /var/vcap/jobs/groundcrew/config/worker.json describes the per-worker resources available (change worker.json, then monit restart beacon, and resource type shows up in ATC API)
  • use a docker URI docker:///username/imagename#tagname for dev/test of the docker image without forcing re-deploy (41)