Devops: Difference between revisions
From Federal Burro of Information
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
Running Jenkins against you feature branch and then ignoring the build when it turns red is not Continuous Integration | Running Jenkins against you feature branch and then ignoring the build when it turns red is not Continuous Integration | ||
== | == Continuous Deployment == | ||
when the CI build passed it goes to prod automagically | when the CI build passed it goes to prod automagically | ||
* increate dicipline | |||
* increate hygene | |||
* reduce time to market | |||
* decreese feedback loops | |||
* Improve quatly | |||
* Reduce Cost | |||
You should do this if you can, sometime you can't: firemware , mobile apps | |||
== Continuous Delivery == | |||
for firmware | |||
Revision as of 15:17, 5 May 2018
the twelve factor app : http://12factor.net/
https://try.newrelic.com/rs/newrelic/images/The_New_Kingmakers.pdf
DevopsDays 2015 Conference Notes
blogs
Continuous Integration
- Is everyone committing to the same trunk at least once a day?
- Is every commit being tested?
- When the build breaks Is is red fixed in ten minutes?
Running Jenkins against you feature branch and then ignoring the build when it turns red is not Continuous Integration
Continuous Deployment
when the CI build passed it goes to prod automagically
- increate dicipline
- increate hygene
- reduce time to market
- decreese feedback loops
- Improve quatly
- Reduce Cost
You should do this if you can, sometime you can't: firemware , mobile apps
Continuous Delivery
for firmware
