Upgrade to Pro — share decks privately, control downloads, hide ads and more …

WeDeploy

Eduardo Lundgren
December 02, 2016
41

 WeDeploy

Eduardo Lundgren

December 02, 2016
Tweet

Transcript

  1. “Cloud computing is a model for enabling ubiquitous, convenient, on-demand

    network access to a shared pool of configurable computing resources”
  2. We believe developers should dedicate their time and energy to

    what really matters: building great applications, not infrastructure.
  3. Servers  Tables, SQL  Passwords  OAuth  Traditional

    app development Server availability  Scale  SMTP  HTTPS 
  4. var auth = WeDeploy.auth('auth.supermarket.wedeploy.io'); var provider = new auth.provider.Github(); provider.setProviderScope('user:email');

    auth.signInWithRedirect(provider); auth.onSignIn((user) => { // Fires when user is signed in after redirect. }); third-party login
  5. Push to Git Code is pushed to a repository Webhook

    is triggered Build pipeline is started Build Each service built independently and in parallel. Test Submitted code is tested in parallel.
  6. Push to Git Code is pushed to a repository Webhook

    is triggered Build pipeline is started Tested container is packed into an image and pushed to the registry Pack Build Each service built independently and in parallel. Test Submitted code is tested in parallel.
  7. Push to Git Code is pushed to a repository Webhook

    is triggered Build pipeline is started Tested container is packed into an image and pushed to the registry Pack Build Each service built independently and in parallel. Test Submitted code is tested in parallel. Now it’s just a matter of deploying Deploy
  8. Push to Git Code is pushed to a repository Webhook

    is triggered Build pipeline is started Tested container is packed into an image and pushed to the registry Pack Build Each service built independently and in parallel. Test Submitted code is tested in parallel. Now it’s just a matter of deploying the tested code. WeDeploy makes sure only after all containers are marked healthy the deploy is completed. Deploy
  9. Webhook is triggered Build pipeline is started Tested container is

    packed into an image and pushed to the registry Pack Build Each service built independently and in parallel. Test Submitted code is tested in parallel. Now it’s just a matter of deploying the tested code. WeDeploy makes sure only after all containers are marked healthy the deploy is completed. Deploy
  10. Tested container is packed into an image and pushed to

    the registry Pack Each service built independently and in parallel. Now it’s just a matter of deploying the tested code. WeDeploy makes sure only after all containers are marked healthy the deploy is completed. Deploy
  11. Push to Git Code is pushed to a repository Webhook

    is triggered Build pipeline is started Tested container is packed into an image and pushed to the registry Pack Build Each service built independently and in parallel. Test Submitted code is tested in parallel. Now it’s just a matter of deploying the tested code. WeDeploy makes sure only after all containers are marked healthy the deploy is completed. Deploy
  12. “Time spent on infrastructure is time that you aren’t spending

    building solutions to delight your users” Joe Zulli CTO, savings.com