Build & Launch Tools (BLT) Automating best practices for enterprise sites

Transcription

1 Build & Launch Tools (BLT) Automating best practices for enterprise sites

2 Who are you? Matthew on Drupal.org, twitter, etc. Acquia Professional Services, 4yrs Drupalist, 9yrs Maintainer of BLT

3 Let s start with the problem that we re solving.

4

5

6

7 FTP

8 This was good It was fast and simple.

9 But it had problems! We d overwrite each other s files We couldn t track or revert changes It wasn t redundant or resilient

10 FTP

11

12 This was better But also a bit more complicated.

13 Meanwhile... Our backend tools were evolving

14

15

16

17 This was better But also a bit more complicated.

18 Meanwhile... Our front end tools were changing too

19

20

21

22

23 This was better But also a bit more complicated.

24 Meanwhile... We starting getting great testing tools

25

26

27

28

29

30

31 This was better But also a bit more complicated.

32 Meanwhile... Our local environments were changing

33

34

35

36 This was better But also a bit more complicated.

37 Meanwhile... The PHP community continued to evolve

38

39

40 These are all great tools! That we run locally.

41 Teams have many machines And continuous integration requires even more machines

42

43

44

45 At some point it became very complex And painful.

46 This is the problem We re trying to solve.

47 Real world consequences 1. You don t use these tools a. You don t have a build process to manage dependencies b. You don t use automated testing c. You don t have a CI process 2. You spend a long time orchestrating these tools a. You painstakingly create your own build process, for every project b. You configure your own CI setup, for every project c. You maintain it constantly, for every project

48 There has to be a way... To approach this more consistently and efficiently.

49

50

51

52 Build & Launch Tools BLT

53

54

55 Package, integrate, automate A stack of Drupal development tools.

56 What s in the box?

57 BLT high-level features: Open source Standardized template for Drupal 8 sites Set of tools for building, testing, deploying Commands for automating usage of those tools

58 Template

59 What is the template? Pre-defined structure for files and directories Boiler plate code and configuration

60 Opinionated placement of... Settings files Exported configuration Modules, themes, profiles, etc. Drush commands Patches

61 Nothing earth-shattering.

62 Actually, it s kind of a big deal.

63 Why is it helpful? Faster on-boarding Better collaboration Simpler hand-offs

64 Tools

65 We re all using the same things The same tools, the same versions Testing tools PHP Packages Modules Preconfigured to work together

66 Also a big deal.

67 What makes this powerful?

68 Automation!

69 Make complex things simple Create an entire project Boot (& create) a VM Validate all of your code Test you application Sync environments Deploy to cloud in one command

70 Seeing is believing.

71 Warning: we re going CLI.

72 Creating a new project

73 Use composer and then wait a bit.. $ composer create-project acquia/blt-project [project-name] --no-interaction

74 You have a complete project!

75

76 Install blt alias and then you can use blt $ composer blt-alias

77 Setup LAMP stack Dev Desktop, DrupalVM, MAMP, Native LAMP, etc. $ blt vm

78 You have a virtual machine!

79 Let s do the other [local] stuff.

80 Do all the [local] things $ blt setup build dependencies install drupal import configuration set file permissions

81 You have a fully functional Drupal site!

82 That s a lot of work you didn t have to do.

83 Login to Drupal because it s ready to go $ cd docroot && drush uli

84

85 You ve only run 4 commands.

86 Automated testing

87 Don t freak out.

88 We provide the tools and example tests Testing Behat PHPUnit Validation PHPCS Linting (PHP/Twig)

89 Validate code phpcs, lint, composer The right standards, on the right extensions, in the right dirs $ blt validate

90 Run them all! Behat, PHPUnit all rolled up. $ blt tests

91 Let s stop and appreciate this.

92 2016 Acquia Inc. Confidential and Proprietary

93 Let s talk about workflow Not just local development

94 Develop, Build & Test Review Build & Test Deploy Local Machine E.g., GitHub Continuous Integration Cloud BLT BLT

95 With this workflow... Before merging, you: Test your changes automatically Review your changes on GitHub Preview your changes on a dedicated environment

96 Gives the confidence To merge a deploy code

97 Adding Continuous Integration Acquia Cloud CD and Travis CI out-of-the-box.

98 We provide CI config You don t need to figure it out.

99 Acquia Cloud CD pipelines acquia-pipelines.yml $ blt ci:pipelines:init

100 You now have acquia-pipelines.yml pre-configured.

101 Travis CI.travis.yml $ blt ci:travis:init

102 You now have.travis.yml pre-configured.

103 Push $ git commit -a $ git push origin to the Cloud

104 CI + BLT will build & test your site Triggered by a push or pull request

105

106

107

108 Your tests run before merging so you don t break things.

109 After merge, code deploys all by itself.

110 Develop, Build & Test Review Build & Test Deploy Local Machine E.g., GitHub Continuous Integration Cloud BLT BLT

111 Deploying to the Cloud Deployment is special.

112 Only deploy artifacts! Wait what? What s an artifact?

113 Things you need for!= development process <> Things you need for production website

114 Development Artifact

115 Development (SASS) #navbar { width: 80%; border: solid red 1px; float: left; padding: 5px; ul { list-style-type: none; } li { float: right; a{ font-weight: bold; color: red; } } } Artifact (CSS) #navbar { width: 80%; border: solid red 1px; float: left; padding: 5px; } #navbar ul { list-style-type: none; } #navbar ul li { float: right; } #navbar ul li a { font-weight: bold; color: red; }

116 Development.drush-use.git/.gitignore.idea/.travis.yml.vagrant/ README.md Vagrantfile box/ build/ composer.json composer.lock config/ docroot/ drush/ drush.wrapper* example.project.local.yml factory-hooks/ hooks/ patches/ project.local.yml project.yml readme/ reports/ scripts/ tests/ vendor/ Artifact.gitignore composer.json composer.lock config/ docroot/ drush/ factory-hooks/ hooks/ scripts/ vendor/

117 Working Repo Artifact Push Develop Build Artifact & Push Review Build & Test

118 Why are we doing this? Lots of good reasons.

119 Improves process, improves product. Maintainability Performance Prevents hacking contrib & core (not committed). Deployments are scripted and repeatable (update hooks are required). Removes unnecessary tools and libraries. Security Artifacts are sanitized.

120 Show me. Manual deployment is good for debugging.

121 deploying manually from your local machine $ blt deploy

122 What just happened? A deployment artifact was created at your/project/path/deploy Files were copied. Front end assets were compiled. Prod dependencies were built. Directory was sanitized. Everything was committed. The deployment artifact was: Committed to the <original-branch>-build branch. Pushed to ${project.git.remotes}

123 Recap

124 BLT is a box with: Standardized template for Drupal 8 sites Set of tools for building, testing, deploying Commands for automating usage of those tools

125 Make complex things simple Create an entire project Boot (& create) a VM Validate all of your code Test your application Deploy to cloud in one command

126 Develop, Build & Test Review Build & Test Deploy Local Machine E.g., GitHub Continuous Integration Cloud BLT BLT

127 github.com/acquia/blt Thanks! Questions? Reminder: Sprints are /2oa9j1w bit.ly