{"action":"opened","issue":{"url":"https://api.github.com/repos/SeanKilleen/seankilleen.github.io/issues/208","repository_url":"https://api.github.com/repos/SeanKilleen/seankilleen.github.io","labels_url":"https://api.github.com/repos/SeanKilleen/seankilleen.github.io/issues/208/labels{/name}","comments_url":"https://api.github.com/repos/SeanKilleen/seankilleen.github.io/issues/208/comments","events_url":"https://api.github.com/repos/SeanKilleen/seankilleen.github.io/issues/208/events","html_url":"https://github.com/SeanKilleen/seankilleen.github.io/issues/208","id":184252413,"number":208,"title":"With continuous integration and testing, it's important to \"practice same as you play\".","user":{"login":"SeanKilleen","id":2148318,"avatar_url":"https://avatars.githubusercontent.com/u/2148318?v=3","gravatar_id":"","url":"https://api.github.com/users/SeanKilleen","html_url":"https://github.com/SeanKilleen","followers_url":"https://api.github.com/users/SeanKilleen/followers","following_url":"https://api.github.com/users/SeanKilleen/following{/other_user}","gists_url":"https://api.github.com/users/SeanKilleen/gists{/gist_id}","starred_url":"https://api.github.com/users/SeanKilleen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SeanKilleen/subscriptions","organizations_url":"https://api.github.com/users/SeanKilleen/orgs","repos_url":"https://api.github.com/users/SeanKilleen/repos","events_url":"https://api.github.com/users/SeanKilleen/events{/privacy}","received_events_url":"https://api.github.com/users/SeanKilleen/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/SeanKilleen/seankilleen.github.io/labels/post-idea","name":"post-idea","color":"bfdadc"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-20T14:53:43Z","updated_at":"2016-10-20T14:53:43Z","closed_at":null,"body":"Inertia is a big thing in software projects, and changing core pipelines is perceived as risk.\r\n\r\nIf you don't have a great branching setup to start with, you wont' magically achieve one before production (and it will probably halt work to do so).\r\n\r\nIf you don't have a CI pipeline that covers the concepts of hotfixes, major/minor releases, etc. and you're working on a large project, it's unlikely the project will somehow just develop those prior to production.\r\n\r\nYou should practice how you play. There should be a \"production\" environment always, and the goal should be to apply concepts to making sure that environment stays as stable and well-tested as possible.\r\n\r\nConcepts that need to be covered:\r\n\r\n* How do ensure that only the PR changes you want are the ones getting into the next environment? \r\n * You can't just take the latest chunk of changes, as it might include things you did not want\r\n* Tests are key to confidence. If you don't have the proper test harnesses, you have to be a lot more careful about what makes it into a certain branch / environment. "}}
{"actor":{"display_login":"SeanKilleen"}}