Continuous
Delivery
(TooLs)
Team

Development

  • gradle/ant
  • artifactory/yoda
  • orbitz-ci plugins
  • Dev Jenkins
  • Publish Jenkins

Testing

  • Service-Test Framework
  • Host Data Provider
  • Mock Data Framework
  • Orbitz-Selenium
  • Orbitz-ServiceTestNG
  • Performance Jenkins
  • OBI
  • TestRail
  • Traceability

Deployment

  • glu-config
  • glu-tools
  • fabric validation
  • glu-console
  • hostinstall
  • Foundry/JIT-Tool

ELse

  • tarzon
  • Availability Jenkins
  • Likely other Jenkinses we are unaware of
  • Stash...Kind of

Recent Work

  • Orbitz-ci plugins 3.0 and 3.1
    • With new Publish Jenkins Template
  • JIT Fabric Update Prototype
  • Upgrade of Jenkinses

Backlog (3 sprints)

  • Continuing to update Jenkins
  • Dogfooding
  • Glu Performance Evaluation

Road Map (3 months)

  • Foundry/JIT Fabric Updates
  • DR all the things

Vision (1 Year)

  • Release Orchestration
    • Tying all the pieces together
    • Commit flows to artifact
    • Artifact flows to pre-prod deployment
    • Pre-prod deployment to testers
    • Tested artifact to production release train
    • With released artifacts flowing back into the pre-prod environments.
  • Now is the incubation time
  • CD will advice now and take ownership of best of breed.

Lots of little things

  • Continuous Integration
  • Every Commit Deployed to pFQA
    • pFQA kept up to date
  • pFQA certification
  • Minor cut and deployment to FQA
    • With certification
  • Change Management Paperwork
  • Release promotion to ProdSlice
    • With certification
  • Release promotion to all Productions
    • With certification
  • What is running where?

One big thing

Manual Testing

Not Going Away

Cannot remain the same

CD Team has little to say about it

C

By Jacob Tomaw

Made with Slides.com

C

  • 856

More from Jacob Tomaw