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

Easy PR Checking - GroningenPHP

Easy PR Checking - GroningenPHP

So your team uses Pull Requests to easily see what goes into the codebase and check the quality of the code. PR’s are also great places to converse over the technical details and implications of a change. But how about the functionality aspect? I’m going to talk about deploying a certain version of your project for easy reviewing. About the challenges this brings and how to overcome them. I’m also going to talk about how to make this more accessible to the less technical members of your team by using ChatOps.

15bd509601f2b058f9d6edf45302dff0?s=128

Pascal de Vink

May 01, 2014
Tweet

Transcript

  1. @ PA S C A L D E V I

    N K E A S Y P R C H E C K I N G
  2. I R O A M W I T H B

    U I L D E R S
  3. I R O A M W I T H B

    U I L D E R S
  4. O H , A N D T H E S

    E P E O P L E
  5. O H , A N D T H E S

    E P E O P L E
  6. I S O M E T I M E S

    B U I L D T H I N G S
  7. T D D

  8. TA L K D R I V E N D

    E V E L O P M E N T
  9. TA L K D R I V E N D

    E V E L O P M E N T • Talk about a project • Develop something for the project • Think about new ideas for the project • Repeat • Profit?
  10. T D T

  11. T E S T D R I V E N

    TA L K I N G
  12. T E S T D R I V E N

    TA L K I N G • Meetup: http://www.meetup.com/GroningenPHP/ events/176028652/ • Or talk to me afterwards!
  13. D I S C L A I M E R

  14. H O W W E W O R K

  15. T E A M R E L AT I O

    N S
  16. J I R A

  17. G I T F L O W

  18. – A U T O T R A C K

    D E F I N I T I O N O F D O N E “A ticket is done when tests are made, a peer review was done and it passed the user acceptance test”
  19. T E S T I N G • PHPUnit •

    Behat • Codeception
  20. P E E R R E V I E W

  21. None
  22. None
  23. FA I L O F T E N , FA

    I L E A R LY
  24. S O , W E H AV E A (

    M A N U A L ) P R O B L E M
  25. None
  26. T H E M A N U A L P

    R O B L E M S O L U T I O N
  27. T H E M A N U A L P

    R O B L E M S O L U T I O N • Most projects already have Vagrant (we do)
  28. T H E M A N U A L P

    R O B L E M S O L U T I O N • Most projects already have Vagrant (we do) • Reuse this?
  29. None
  30. None
  31. None
  32. None
  33. None
  34. None
  35. None
  36. D E M O T I M E !

  37. C H AT O P S : C O N

    V E R S AT I O N D R I V E N D E V E L O P M E N T • Invented (?) at Github • Do ops the chatty way • Everybody can do it and everybody can understand it
  38. S L A C K

  39. S L A C K B O T

  40. N O T A L L T H I N

    G S A R E G R E AT • Vagrant is • slow • large • not easy to configure
  41. D O C K E R A L L T

    H E T H I N G S
  42. D O C K E R • Docker is a

    lot faster and smaller • Contained functionality allows for reuse
  43. – D O C K E R . I O

    “The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more.”
  44. D O C K E R

  45. N O T A L L T H I N

    G S A R E G R E AT ( A G A I N )
  46. Q U E S T I O N S ?

  47. http://www.meetup.com/GroningenPHP/events/176028652/

  48. • https://speakerdeck.com/adamwiggins/an-engineers- guide-to-working-with-product-managers • https://speakerdeck.com/jnewland/chatops-at-github