The document discusses best practices for continuous integration, continuous delivery, and automation in software development. It recommends automating the entire development cycle from build to test to deployment. Changes should be deployed frequently, such as multiple times a day, to catch errors early. All code, configurations, and dependencies should be stored in version control. A deployment pipeline approach is advocated with separate stages for testing, verification, and release to different environments. Rollback and recovery should be planned and tested.

1. Daniel Pötzinger
CIO AOE media GmbH

2. What is your
cycle
time?

3. are youscared
on release days?

4. late night
bugfixing?

5. there is another
way!

6. How?

7. Automate everything!

8. Automate everything!
build

9. Automate everything!
build
test

10. Automate everything!
build
test
deploy

11. Do it frequently

12. Do it frequently
ys 3
plo .
de
fl ickr a day..
tim es

13. agile
agile
agile
continuous deployment

14. agile development best practice:
agile
test driven / refactoring / ddd
agile
agile
continuous deployment

15. agile development best practice:
agile
test driven / refactoring / ddd
agile
continuous integration
agile
continuous deployment

16. agile development best practice:
agile
test driven / refactoring / ddd
agile
continuous integration
agile
continuous testing
continuous deployment

17. It is not only the
source code!

18. It is not only the
source code!
What else?

20. Source Code

21. Configuration
Source Code

22. Environments
Configuration
Source Code

23. Environments
Configuration Data
Source Code

25. Principle
s

26. Check everything into SVN

27. Check everything into SVN
• all source code (of course)
• each build script
• each important configuration
(apache, cronjobs, loadbalancer...)

28. do continuous integration

29. do continuous integration
t ea rly
mi
com it often
co mm

30. do continuous integration
t ea rly
mio ten
om av tid f
c i o bra
co mm nch
ing

31. do continuous integration
t ea rly
mio ten
om av tid f omprehen sive
c i o brc
c o mm anctestsuite
hing

32. do continuous integration
t ea rly
mio ten
om av tid f omprehen fastsive
c i o brc
mm anctestsuite feed
co hing back

34. use test automation...

35. use test automation...

36. use test automation...

37. use test automation...

38. use test automation...

39. use test automation...

40. use test automation...
...and feel responsible

41. automate deployment

42. automate deployment
sa me
the
loy every
dep
wa y to ent!
nvir onm
e

43. automate deployment
sa me
the
loy every
dep do it frequently
wa y to ent!
nvir onm
e

44. automate deployment
adjust
c onfigurations
on deploy time
sa me
the
loy every
dep o do it frequently
w ayt nt!
iron me
env

45. automate deployment
adjust
c onfigurations
./deme
on de<e y ti ploy.s
plo
nviro h
< ep nme
the sam ack nt>
y age>
de plo ev ery do it frequently
yt o
w a me nt!
env iron

46. Plan and test rollback

48. The
Deployme
nt Pipeline

49. deployment pipeline
test + build
package
test strategy
verification 1
verification II
release to
production

50. deployment pipeline
test + build
package
Version 1
test strategy
verification 1
verification II
release to
production

51. deployment pipeline
test + build
package
test strategy
verification 1
Version 1
verification II
release to
production

52. deployment pipeline
test + build
package
test strategy
verification 1
verification II
Version 1
release to
production

53. deployment pipeline
test + build
package
Version 2
test strategy
verification 1
verification II
Version 1
release to
production

54. deployment pipeline
test + build
package
test strategy
verification 1
Version 2
verification II
Version 1
release to
production

55. deployment pipeline
test + build
package
Version 3
test strategy
verification 1
Version 2
verification II
Version 1
release to
production

56. deployment pipeline
Build Source (SVN, Backups)
Commit
Stage
Version_1234
Artifacts Repository

57. deployment pipeline
Build Source (SVN, Backups)
Acceptance
Commit auto Test Stage
Stage (latest)
Version_1234
Artifacts Repository

58. deployment pipeline
Build Source (SVN, Backups)
Acceptance
Commit auto Test Stage
Stage (latest)
Version_1234
Artifacts Repository

59. deployment pipeline
Build Source (SVN, Backups)
Acceptance Performance
Commit auto Test Stage auto Test
Stage (latest) Stage
Version_1234
Artifacts Repository

60. deployment pipeline
Build Source (SVN, Backups)
Acceptance Performance
Commit auto Test Stage auto Test
Stage (latest) Stage
manual
Manual Test
Version_1234 Stage
Artifacts Repository

61. deployment pipeline
Build Source (SVN, Backups)
Acceptance Performance
Commit Release
auto Test Stage auto Test manual
Stage (latest) Stage Stage
manual
Manual Test
Version_1234 Stage
Artifacts Repository

62. deployment pipeline
Build Source (SVN, Backups)
Acceptance Performance
Commit Release
auto Test Stage auto Test manual
Stage (latest) Stage Stage
manual
Manual Test
Version_1234 Stage
Build Downstream
Artifacts Repository

63. deployment pipeline
Build Source (SVN, Backups)
Acceptance Performance
Commit Release
auto Test Stage auto Test manual
Stage (latest) Stage Stage
manual
Manual Test
Version_1234 Stage
Build Downstream
Feedback
Artifacts Repository

64. view on artifact repository

65. the commit stage
• <5min: Run Unit Tests asap
• <10 min: Build Project (clean, build)
• Result:
• store all binaries required for deployment
• package + releasenotes + unittest xml + deploy scripts

66. build only one package
• pull configuration setting for environment on deploy
• be able to rebuild any build by specifying the project revision

67. acceptance stage

68. acceptance stage
• Define tests in domain specific language

69. acceptance stage
• Define tests in domain specific language
• Deployment to Environment „latest“ or „UAT“

70. acceptance stage
• Define tests in domain specific language
• Deployment to Environment „latest“ or „UAT“
• Run additional Unit-Test (integration...)

71. acceptance stage
• Define tests in domain specific language
• Deployment to Environment „latest“ or „UAT“
• Run additional Unit-Test (integration...)
• Run Selenium Tests

73. Release

75. Source Code

76. Configuration
Source Code

77. Environments
Configuration
Source Code

78. Environments
Configuration Data
Source Code

79. SVN structure for TYPO3
<projectname>
branches
tags
build scripts (ant)
trunk
build
scripts
htdocs
typo3conf Extensions dependencies
are linked
(e.g. svn.external)

80. TYPO3 configuration
- Domains:
- sys_domain
- template: config.baseUrl
- localconf.php
- Database
- Extensionsettings
- Loglevel / Devcontext / Logfiles ...

81. Environments (example)
dev x latest test (UAT)
production

82. Environments (example)
dev x latest test (UAT)
performance
production

83. Environments (example)
dev x latest test (UAT)
performance
integration
production

84. Environments (example)
dev x latest test (UAT)
performance
integration
stage production

85. managing data

86. managing data
Production:
- Content
- Transaction data

87. managing data
Production: Deploy:
- Content - Configuration
- Transaction data - Content

88. managing data
Production: Deploy: UAT:
- Content - Configuration - Testdata
- Transaction data - Content

89. managing data
Backupstorage
Production: Deploy: UAT:
- Content - Configuration - Testdata
- Transaction data - Content

90. managing data
Backupstorage
Production: Deploy: UAT:
- Content - Configuration - Testdata
- Transaction data - Content

91. managing data
Backupstorage
use independent technical IDs
Production: Deploy: UAT:
- Content - Configuration - Testdata
- Transaction data - Content

92. Hot Deployment

93. what to deploy?
- database structure changes
- configuration data
- updated content
- source code

94. build steps
Preparation SVN
Filesystem
backupstorage
Database
Package

95. build steps
Preparation:
- clean
- revision Tag extensions

96. build steps
Filesystem:
- checkout project from SVN
- build TYPO3 source
- get defined extensions
- get assets (fileadmin / uploads)
- create a version file

97. build steps
Database:
- create structure from Master
- import master data
- update database structure
- import data from the systems
- merge data

98. build steps
Database:
- create structure from Master
- import master data
- update database structure
- import data from the systems
- merge data
structure_up.sql
merge.sql

99. package
Package (Delta):
- use files from build process
+ create filesystem delta
+ tar.gz all the stuff

100. deploying a package
- Deploy Database:
- structure_up.sql
- merge.sql
- all full-*.sqls
- Deploy Filesystem
- Apply environment Settings
- Clear Cache
- Run Crawler

101. ...

102. useful extensions
- clearcache (enables „clear all cache“ from
commandline)
- db_sequenzer (seperate technical ids as basis for
merges)
- t3deploy (cli access to installtool > database compare)

103. green / blue deployment
current live
version
previous live
version

104. green / blue deployment
current live
version
previous live
version
Deploy

105. green / blue deployment
previous live
version
current live
version
Deploy

106. Hudson

107. Hudson

108. Hudson

109. Hudson

110. is your deployment still a
gamble?

111. is your deployment still a
gamble?