CitconWiki - User contributions [en]

Continuous Full System Deployment

2013-08-24T21:04:17Z

Citconjoe: Created page with "'''Tips''' * Your snapshots should be as bare as possible * Use Puppet or Chef to configure it (use the exact same thing that you used to configure production) * Do basic test..."

'''Tips'''
* Your snapshots should be as bare as possible
* Use Puppet or Chef to configure it (use the exact same thing that you used to configure production)
* Do basic tests (ping, ssh and the web server is available)

'''Ensure QA and Production are the same'''
* Deployable unit was a system image - it has to be in a Debian package
* Issue: If you do an apt-get on QA and pull down packages, that's fine. But 2 days later when deploying again to production, that package may have changed and this can introduce issues with your application. Solution: Have your own repo and cache that version. Rather than

'''Packages with no dependencies'''

'''Live Updating Thousands of Servers'''
* Image takes too long

'''Pain Points'''
* Getting different systems deployed is no problem. How do we
* Clone image/install OS/ get manifests and run them, install app, wait for system to start, run tests. 10 minute delay if you need to test something immediately

CITCONNA2013Sessions

2013-08-24T20:55:56Z

Citconjoe: /* 4:30 Topics */

CITCON NA 2013 Boston Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# [[Reproducible CI]]
# [[From 0 percent to greater than 0 percent Test Coverage]]
# [[To Branch or Not to Branch?]]
# [[Property Based Developer Testing]]
# [[Test Expressivity]]

== 11:15 Topics ==

# [[End to end Continuous Delivery tools]]
# [[Test Triage and Intermittent Test techniques]]
# ---
# ---
# [[Managing Test Data All The Way To Production]]

== Lunch Topics ==

# ---

== 2:00 Topics ==

# [[CI Feedback & Metrics]]
# ---
# [[Feature Toggling Strategies]]
# [[CI Challenges With Multiple Branches]]
# ---

== 3:15 Topics ==

# [[NextGen CI Toolkit Wishlist]]
# [[Dead Sea Effect]]
# ---
# ---
# ---

== 4:30 Topics ==

# [[Performance testing, automating]]
# [[Continuous Full System Deployment]]
# ---
# ---
# ---

== Table View ==

{| class="wikitable"
|-
! Room name
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Horace Mann
| ---
| [[End to end Continuous Delivery tools]]
| ---
| ---
| ---
|-
| Deborah Sampson
| ---
| [[Test Triage and Intermittent Test techniques]]
| ---
| ---
| ---
|-
| Thomas Paul
| [[From 0 percent to greater than 0 percent Test Coverage]]
| ---
| [[CI Challenges With Multiple Branches]]
| ---
| ---
|-
| Abigail Adams
| [[Property Based Developer Testing]]
| ---
| ---
| ---
| ---
|-
| Crispus Attucks
| [[Test Expressivity]]
| [[Managing Test Data All The Way To Production]]
| ---
| ---
| ---
|}

Dead Sea Effect

2013-08-24T20:34:32Z

Citconjoe:

As the CTO, I want us to get better at something. How? Do I need to hire an expert? If I cannot hire an expert, how do I make my team members better themselves. How do we improve talent throughout the organization? This session explores theories, stories and experiences.

==Characteristics Needed to Grow==
* '''Focus''' - If you're 100% utilized, you can't grow. You need to focus on a specific problem
* '''Slack''' - Employees also need a certain level of freedom and access to change processes and make improvements.
* '''Belief''' - The person must be self motivated and believe that there are areas for improvement
* '''Humility'''

==User Stories==

'''Mentoring/Coaching'''
--someone was not a coder, this person wanted to learn and he ended up with a dev position
-gave the book to someone and it worked well. another person read the same book and did not do well. must be intrinsic.
--start slow - gave a java book, learned basic concepts, code reviews, small projects,

'''Worked with good people, hired awesome people, hired awesome interns'''
* Coaching and mentoring
* Need the right mindset

''' Hands Off Managers''' 
* Doesn't tell you what to do
* Says he knew someone else who had a similar problem: try this...

'''Good interview questions''' 
* What do you do to learn?
* What was the last tech book you read?

'''Relevant Reading ''' 
* Code complete
* Rapid development
* Software as a profession. For example, you can't have engineer in your title unless you're licensed. Constructs - what different levels of engineers should be. 10-15% ever read a tech book, journal articles, conferences, speak at conferences, write an article,

'''Things to try'''
* Encourage systems thinking and architecture
* Risk analysis (think of each component in the system and what overall effect failure of that component would cause)

'''Don't hire better people. Hire someone with the ability to make someone better.'''
* But what if they can't do it themselves?

'''Organization Pushing for Features'''
* This is exactly how not how to grow a stronger engineer
* Didn't explore new ways of doing things
* More about not being noticed
* Just getting things done and not caring

Another Team was given more freedom was a lot more successful

''' How Do you define what better is? ''' 

'''Send Your Devs to Learn from Others'''
* Send devs to other companies and learn processes.
* Send their developers to clients and to other companies and see how they work
* Collect disaster stories, failure stats

Dead Sea Effect

2013-08-24T20:25:18Z

Citconjoe:

As the CTO, I want us to get better at something. How? Do I need to hire an expert? If I cannot hire an expert, how do I make my team members better themselves. How do we improve talent throughout the organization? This session explores theories, stories and experiences.

==User Stories==

'''Mentoring/Coaching'''
--someone was not a coder, this person wanted to learn and he ended up with a dev position
-gave the book to someone and it worked well. another person read the same book and did not do well. must be intrinsic.
--start slow - gave a java book, learned basic concepts, code reviews, small projects,

'''Worked with good people, hired awesome people, hired awesome interns'''
* Coaching and mentoring
* Need the right mindset

''' Hands Off Managers''' 
* Doesn't tell you what to do
* Says he knew someone else who had a similar problem: try this...

'''Good interview questions''' 
* What do you do to learn?
* What was the last tech book you read?

'''Relevant Reading ''' 
* Code complete
* Rapid development
* software as a profession. For example, you can't have engineer in your title unless you're licensed. Constructs - what different levels of engineers should be. 10-15% ever read a tech book, journal articles, conferences, speak at conferences, write an article,

Things we tried:
Encourage systems thinking and architecture
Risk analysis (think of each component in the system and what overall effect failure of that component would cause)

'''Don't hire better people. Hire someone with the ability to make someone better.'''
But what if they can't do it themselves?

Org Pushing for Features
-Didn't explore new ways
-More about not being noticed
-Just getting things done and not caring

Another Team was given more freedom
- Did better

How do you define what "better" is?

==Characteristics Needed to Grow==
* '''Focus''' -
* '''Slack''' - You need to give your employee the freedom and access to change processes and make improvements.
* '''Belief''' - The person must be self motivated and believe
* '''Humility'''

Sometimes, people can have these three

Send people to other companies and learn processes. Send their developers to clients and to other companies and see how they work.
-collect disaster stories, failure stats

Dead Sea Effect

2013-08-24T20:24:38Z

Citconjoe: /* User Stories */

As the CTO, I want us to get better at something. How? Do I need to hire an expert? If I cannot hire an expert, how do I make my team members better themselves. How do we improve talent throughout the organization? This session explores theories, stories and experiences.

==User Stories==

'''Mentoring/Coaching'''
--someone was not a coder, this person wanted to learn and he ended up with a dev position
-gave the book to someone and it worked well. another person read the same book and did not do well. must be intrinsic.
--start slow - gave a java book, learned basic concepts, code reviews, small projects,

'''Worked with good people, hired awesome people, hired awesome interns'''
* Coaching and mentoring
* Need the right mindset

''' Hands Off Managers''' 
* Doesn't tell you what to do
* Says he knew someone else who had a similar problem: try this...

'''Good interview questions''' 
* What do you do to learn?
* What was the last tech book you read?

'''Relevant Reading ''' 
* Code complete
* Rapid development
* software as a profession. For example, you can't have engineer in your title unless you're licensed. Constructs - what different levels of engineers should be. 10-15% ever read a tech book, journal articles, conferences, speak at conferences, write an article,

Things we tried:
Encourage systems thinking and architecture
Risk analysis (think of each component in the system and what overall effect failure of that component would cause)

'''Don't hire better people. Hire someone with the ability to make someone better.'''
But what if they can't do it themselves?

Org Pushing for Features
-Didn't explore new ways
-More about not being noticed
-Just getting things done and not caring

Another Team was given more freedom
- Did better

How do you define what "better" is?

Send people to other companies and learn processes. Send their developers to clients and to other companies and see how they work.
-collect disaster stories, failure stats

Dead Sea Effect

2013-08-24T20:23:51Z

Citconjoe: /* User Stories */

As the CTO, I want us to get better at something. How? Do I need to hire an expert? If I cannot hire an expert, how do I make my team members better themselves. How do we improve talent throughout the organization? This session explores theories, stories and experiences.

==User Stories==

'''Mentoring/Coaching'''
--someone was not a coder, this person wanted to learn and he ended up with a dev position
-gave the book to someone and it worked well. another person read the same book and did not do well. must be intrinsic.
--start slow - gave a java book, learned basic concepts, code reviews, small projects,

'''Worked with good people, hired awesome people, hired awesome interns'''
* Coaching and mentoring
* Need the right mindset

''' Hands Off Managers''' 
* Doesn't tell you what to do
* Says he knew someone else who had a similar problem: try this...

'''Good interview questions''' 
* What do you do to learn?
* What was the last tech book you read?

'''Relevant Reading ''' 
* Code complete
* Rapid development
* software as a profession. For example, you can't have engineer in your title unless you're licensed. Constructs - what different levels of engineers should be. 10-15% ever read a tech book, journal articles, conferences, speak at conferences, write an article,

Things we tried:
Encourage systems thinking and architecture
Risk analysis (think of each component in the system and what overall effect failure of that component would cause)

'''Don't hire better people. Hire someone with the ability to make someone better.'''
But what if they can't do it themselves?

Org Pushing for Features
-Didn't explore new ways
-More about not being noticed
-Just getting things done and not caring

Another Team was given more freedom
- Did better

How do you define what "better" is?

Send people to other companies and learn processes. Send their developers to clients and to other companies and see how they work.
-collect disaster stories, failure stats

==Characteristics Needed to Grow== 
* '''Focus''' -
* '''Slack''' - You need to give your employee the freedom and access to change processes and make improvements.
* '''Belief''' - The person must be self motivated and believe
* '''Humility'''

Sometimes, people can have these three

Dead Sea Effect

2013-08-24T20:23:16Z

Citconjoe: Created page with "As the CTO, I want us to get better at something. How? Do I need to hire an expert? If I cannot hire an expert, how do I make my team members better themselves. How do we impr..."

As the CTO, I want us to get better at something. How? Do I need to hire an expert? If I cannot hire an expert, how do I make my team members better themselves. How do we improve talent throughout the organization? This session explores theories, stories and experiences.

==User Stories==

'''Mentoring/Coaching'''
--someone was not a coder, this person wanted to learn and he ended up with a dev position
-gave the book to someone and it worked well. another person read the same book and did not do well. must be intrinsic.
--start slow - gave a java book, learned basic concepts, code reviews, small projects,

'''Worked with good people, hired awesome people, hired awesome interns'''
* Coaching and mentoring
* Need the right mindset

''' Hands Off Managers''' 
* Doesn't tell you what to do
* Says he knew someone else who had a similar problem: try this...

'''Good interview questions''' 
* What do you do to learn?
* What was the last tech book you read?

'''Relevant Reading ''' 
* Code complete
* Rapid development
* software as a profession. For example, you can't have engineer in your title unless you're licensed. Constructs - what different levels of engineers should be. 10-15% ever read a tech book, journal articles, conferences, speak at conferences, write an article,

Things we tried:
Encourage systems thinking and architecture
Risk analysis (think of each component in the system and what overall effect failure of that component would cause)

'''Don't hire better people. Hire someone with the ability to make someone better.'''
But what if they can't do it themselves?

Org Pushing for Features
-Didn't explore new ways
-More about not being noticed
-Just getting things done and not caring

Another Team was given more freedom
- Did better

How do you define what "better" is?

Send people to other companies and learn processes. Send their developers to clients and to other companies and see how they work.
-collect disaster stories, failure stats

==Characteristics Needed to Grow== 
* '''Focus''' -
* '''Slack''' - You need to give your employee the freedom and access to change processes and make improvements.
* '''Belief''' - The person must be self motivated and believe
* '''Humility'''

Sometimes, people can have these three

CITCONNA2013Sessions

2013-08-24T19:51:26Z

Citconjoe: /* 3:15 Topics */

CITCON NA 2013 Boston Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# ---
# [[From 0 percent to greater than 0 percent Test Coverage]]
# [[To Branch or Not to Branch?]]
# [[Property Based Developer Testing]]
# [[Test Expressivity]]

== 11:15 Topics ==

# [[End to end Continuous Delivery tools]]
# [[Test Triage and Intermittent Test techniques]]
# ---
# ---
# [[Managing Test Data All The Way To Production]]

== Lunch Topics ==

# ---

== 2:00 Topics ==

# [[CI Feedback & Metrics]]
# ---
# [[Feature Toggling Strategies]]
# [[CI Challenges With Multiple Branches]]
# ---

== 3:15 Topics ==

# [[NextGen CI Toolkit Wishlist]]
# [[Dead Sea Effect]]
# ---
# ---
# ---

== 4:30 Topics ==

# ---
# ---
# ---
# ---
# ---

== Table View ==

{| class="wikitable"
|-
! Room name
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Horace Mann
| ---
| [[End to end Continuous Delivery tools]]
| ---
| ---
| ---
|-
| Deborah Sampson
| ---
| [[Test Triage and Intermittent Test techniques]]
| ---
| ---
| ---
|-
| Thomas Paul
| [[From 0 percent to greater than 0 percent Test Coverage]]
| ---
| [[CI Challenges With Multiple Branches]]
| ---
| ---
|-
| Abigail Adams
| [[Property Based Developer Testing]]
| ---
| ---
| ---
| ---
|-
| Crispus Attucks
| [[Test Expressivity]]
| [[Managing Test Data All The Way To Production]]
| ---
| ---
| ---
|}

CITCONNA2013Sessions

2013-08-24T19:18:09Z

Citconjoe: /* Table View */

CITCON NA 2013 Boston Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# ---
# [[From 0 percent to greater than 0 percent Test Coverage]]
# [[To Branch or Not to Branch?]]
# [[Property Based Developer Testing]]
# [[Test Expressivity]]

== 11:15 Topics ==

# [[End to end Continuous Delivery tools]]
# [[Test Triage and Intermittent Test techniques]]
# ---
# ---
# [[Managing Test Data All The Way To Production]]

== Lunch Topics ==

# ---

== 2:00 Topics ==

# [[CI Feedback & Metrics]]
# ---
# [[Feature Toggling Strategies]]
# [[CI Challenges With Multiple Branches]]
# ---

== 3:15 Topics ==

# ---
# ---
# ---
# ---
# ---

== 4:30 Topics ==

# ---
# ---
# ---
# ---
# ---

== Table View ==

{| class="wikitable"
|-
! Room name
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Horace Mann
| ---
| [[End to end Continuous Delivery tools]]
| ---
| ---
| ---
|-
| Deborah Sampson
| ---
| [[Test Triage and Intermittent Test techniques]]
| ---
| ---
| ---
|-
| Thomas Paul
| [[From 0 percent to greater than 0 percent Test Coverage]]
| ---
| [[CI Challenges With Multiple Branches]]
| ---
| ---
|-
| Abigail Adams
| [[Property Based Developer Testing]]
| ---
| ---
| ---
| ---
|-
| Crispus Attucks
| [[Test Expressivity]]
| [[Managing Test Data All The Way To Production]]
| ---
| ---
| ---
|}

CI Challenges With Multiple Branches

2013-08-24T18:50:24Z

Citconjoe: Created page with "How do we handle CI with multiple branches? '''Questions/ Problems to Solve''' * How do we handle CI/builds/deployments if there are multiple branches that exist? * Dev..."

How do we handle CI with multiple branches?

'''Questions/ Problems to Solve''' 
* How do we handle CI/builds/deployments if there are multiple branches that exist?
* Developers have no idea which branch to check the fix/feature into
* How do we discover merge conflicts sooner?

'''Auto-Merge Tool''' 
This worked well for one organization. The challenge was that main bug fixes or features need to get merged into multiple branches as soon as possible and automatically. Waiting too long can lead to merge conflicts and other issues and lost time.
* Devs check code into one branch
* Release engineer configures the additional branches that will be merged from trunk.
* The utility performs an auto merge and pushes. This allows each branch to be updated, even though the dev pushed once
* Send email to devs when a merge happened or if it failed.

This process requires setup. It depends which tool you're using for version control and bug tracking. Perforce can be configured to do the auto merge, but one clever solution was to write a JIRA plugin

CITCONNA2013Sessions

2013-08-24T18:26:55Z

Citconjoe: /* 2:00 Topics */

CITCON NA 2013 Boston Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# ---
# ---
# [[To Branch or Not to Branch?]]
# [[Property Based Developer Testing]]
# [[Test Expressivity]]

== 11:15 Topics ==

# [[End to end Continuous Delivery tools]]
# [[Test Triage and Intermittent Test techniques]]
# ---
# ---
# ---

== Lunch Topics ==

# ---

== 2:00 Topics ==

# [[CI Feedback & Metrics]]
# ---
# [[Feature Toggling Strategies]]
# [[CI Challenges With Multiple Branches]]
# ---

== 3:15 Topics ==

# ---
# ---
# ---
# ---
# ---

== 4:30 Topics ==

# ---
# ---
# ---
# ---
# ---

== Table View ==

{| class="wikitable"
|-
! Room name
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Horace Mann
| ---
| [[End to end Continuous Delivery tools]]
| ---
| ---
| ---
|-
| Deborah Sampson
| ---
| [[Test Triage and Intermittent Test techniques]]
| ---
| ---
| ---
|-
| Thomas Paul
| ---
| ---
| ---
| ---
| ---
|-
| Abigail Adams
| [[Property Based Developer Testing]]
| ---
| ---
| ---
| ---
|-
| Crispus Attucks
| [[Test Expressivity]]
| ---
| ---
| ---
| ---
|}

To Branch or Not to Branch?

2013-08-24T16:31:44Z

Citconjoe: Created page with "This session discussed whether no not code should be branched and its impact on CI. '''Don't branch!''' * Jeff Frederick: "Branching is deferred integration" You are deferri..."

This session discussed whether no not code should be branched and its impact on CI.

'''Don't branch!'''
* Jeff Frederick: "Branching is deferred integration" You are deferring the discovering of problems. There is a deliberate choice of stability over early discovery of problems.
* The only needs to branch are habit and because the tools make it possible
* Everyone thinks all the time. Any commits go to prod

'''Good Reasons to Branch''' 
* Feedback on multiple commits
* Branching structure mirrors org strucutre, so if one branch goes red, you know.
* If you're devoliping something that's not a web app and users subscribe to a release / dev channel (ie. Firefox)
* Need a version deployed to a separate environments for separate business purposes
* To backport features and forward port bugfixes.

'''Additional Topics Discussed''' 
* Use feature toggles
* A few examples of how branching works in
* Jenkins will kick off tests and only promote to the QA if the tests pass.
* Pipe Organ theory if there is one branch

CITCONNA2013Sessions

2013-08-24T16:26:56Z

Citconjoe: /* 10:00 Topics */

CITCON NA 2013 Boston Sessions

Back to the [[Main Page]]

== 10:00 Topics ==

# ---
# ---
# [[To Branch or Not to Branch?]]
# [[Property Based Developer Testing]]
# [[Test Expressivity]]

== 11:15 Topics ==

# [[End to end Continuous Delivery tools]]
# [[Test Triage and Intermittent Test techniques]]
# ---
# ---
# ---

== Lunch Topics ==

# ---

== 2:00 Topics ==

# ---
# ---
# ---
# ---
# ---

== 3:15 Topics ==

# ---
# ---
# ---
# ---
# ---

== 4:30 Topics ==

# ---
# ---
# ---
# ---
# ---

== Table View ==

{| class="wikitable"
|-
! Room name
! 10:00
! 11:15
! 2:00
! 3:15
! 4:30
|-
| Horace Mann
| ---
| [[End to end Continuous Delivery tools]]
| ---
| ---
| ---
|-
| Deborah Sampson
| ---
| [[Test Triage and Intermittent Test techniques]]
| ---
| ---
| ---
|-
| Thomas Paul
| ---
| ---
| ---
| ---
| ---
|-
| Abigail Adams
| [[Property Based Developer Testing]]
| ---
| ---
| ---
| ---
|-
| Crispus Attucks
| [[Test Expressivity]]
| ---
| ---
| ---
| ---
|}

End to end Continuous Delivery tools

2013-08-24T16:25:10Z

Citconjoe:

Idea: A tool to open up, input the CD workflow. Does this exist? Does it need to exist?

'''General workflow'''
* Someone checks code in to version control
* Checkin gets picked up by build server
* Artifact repository or source control or build tool
* Script infrastructure: chef/puppet/custom scripts (should be version controlled)
* Deploy (Chef, Capistrano, shell scripts, manually)
* Testing
* UAT /(business sign off)
* Deployment to Production
* Monitoring/Logging (Nagios/PagerDuty/New Relic/Custom Built Solutions)

'''Thoughts''' 
Teams use their own build tools and they come together in an artifact repo. For example, 1000 people working on the app(s). Do we want everything to go to a centralized CI server, or do we want devs to be more involved? Teams can have a local CI server, but it would be nice to still have a CD workflow on the ops level.

The pipeline is broken. Unless the app is architected so that any component can be changed along the way, the workflow won't be useful

Deployment contract: All apps must follow it. If so, our orchestration tool can handle it.

Facebook's deployment example: One gigantic binary and use bittorrent to get it to all of the servers and extract there. Rsync could work but it would not work sending it to thousands of machines.

Rationally Unified Process. There are documented processes at different contexts.

Are we okay with stitching together a bunch of tools? Over time, this may change. Use the cloud? There should be a standardized tool to deploy to the cloud.

Monitoring: Who finds issues first - the monitoring tools or the users?

Rollbacks: Stored in the artifact repo - easy unless there is a DB schema change?

These tools can be misused and used for generic automation.

'''Questions?'''
* Should this be a process tool that integrates others? Plugin/template based?

End to end Continuous Delivery tools

2013-08-24T16:24:37Z

Citconjoe:

Idea: A tool to open up, input the CD workflow. Does this exist? Does it need to exist?

'''General workflow'''
* Someone checks code in to version control
* Checkin gets picked up by build server
* Artifact repository or source control or build tool
* Script infrastructure: chef/puppet/custom scripts (should be version controlled)
* Deploy (Chef, Capistrano, shell scripts, manually)
* Testing
* UAT /(business sign off)
* Deployment to Production
* Monitoring/Logging (Nagios/PagerDuty/New Relic/Custom Built Solutions)

'''Thoughts'''
Teams use their own build tools and they come together in an artifact repo. For example, 1000 people working on the app(s). Do we want everything to go to a centralized CI server, or do we want devs to be more involved? Teams can have a local CI server, but it would be nice to still have a CD workflow on the ops level.

The pipeline is broken. Unless the app is architected so that any component can be changed along the way, the workflow won't be useful

Deployment contract: All apps must follow it. If so, our orchestration tool can handle it.

Facebook's deployment example: One gigantic binary and use bittorrent to get it to all of the servers and extract there. Rsync could work but it would not work sending it to thousands of machines.

Rationally Unified Process. There are documented processes at different contexts.

Are we okay with stitching together a bunch of tools? Over time, this may change. Use the cloud? There should be a standardized tool to deploy to the cloud.

Monitoring: Who finds issues first - the monitoring tools or the users?

Rollbacks: Stored in the artifact repo - easy unless there is a DB schema change?

These tools can be misused and used for generic automation.

'''Questions?'''
* Should this be a process tool that integrates others? Plugin/template based?

End to end Continuous Delivery tools

2013-08-24T16:15:12Z

Citconjoe:

Idea: A tool to open up, input the CD workflow. Does this exist? Does it need to exist?

'''General workflow'''
-Someone checks code in to version control
-Checkin gets picked up by build server
-Artifact repository or source control or build tool
-Script infrastructure: chef/puppet/custom scripts (should be version controlled)
-Deploy (Chef, Capistrano, shell scripts, manually)
-Testing
-UAT /(business sign off)
-Deployment to Production
-Monitoring/Logging (Nagios/PagerDuty/New Relic/Custom Built Solutions)

'''Thoughts'''
Teams use their own build tools and they come together in an artifact repo. For example, 1000 people working on the app(s). Do we want everything to go to a centralized CI server, or do we want devs to be more involved? Teams can have a local CI server, but it would be nice to still have a CD workflow on the ops level.

The pipeline is broken. Unless the app is architected so that any component can be changed along the way, the workflow won't be useful

Deployment contract: All apps must follow it. If so, our orchestration tool can handle it.

Facebook's deployment example: One gigantic binary and use bittorrent to get it to all of the servers and extract there. Rsync could work but it would not work sending it to thousands of machines.

Rationally Unified Process. There are documented processes at different contexts.

Are we okay with stitching together a bunch of tools? Over time, this may change. Use the cloud? There should be a standardized tool to deploy to the cloud.

Monitoring: Who finds issues first - the monitoring tools or the users?

Rollbacks: Stored in the artifact repo - easy unless there is a DB schema change?

These tools can be misused and used for generic automation.

'''Questions?'''
Should this be a process tool that integrates others? Plugin/template based?

End to end Continuous Delivery tools

2013-08-24T15:41:23Z

Citconjoe: Created page with "Idea: A tool to open up, input the CD workflow and it's done. Does this exist? Does it need to exist? '''General workflow''' -Someone checks code in to version control -Chec..."

Idea: A tool to open up, input the CD workflow and it's done. Does this exist? Does it need to exist?

'''General workflow'''
-Someone checks code in to version control
-Checkin gets picked up by build server
-artifact repository or source control or build tool
-Script infrastructure: chef/puppet/custom scripts (should be version controlled)
-Deploy (chef, Capistrano, shell scripts, manually
-Testing
-UAT /(business sign off)
-Roll to Production

'''Thoughts'''
Teams use their own build tools and they come together in an artifact repo. For example, 1000 people working on the app(s). Do we want everything to go to a centralized CI server, or do we want devs to be more involved? Teams can have a local CI server, but it would be nice to still have a CD workflow on the ops level.

'''What are people doing today?'''