![]() That advice has freed me to think more about how I want to build the end product, while also doing the product work of interviews and analysis. So then I thought, how could that be turned into a Slack message for our staff?Įven though it might feel overwhelming at times, one good piece of advice I got was that I should lean into the reasons why I wanted to do this fellowship. They were better in their titles, descriptions, and the important information in the story was placed higher than we had it. So we made a Google Sheet and compared all of the available data we saw and realized there were very good reasons, the core information on the stories another newsroom had were better than ours. The inspiration for this project came from an editor who asked me in January “why did we lose out on this story?!”, when our outlet did not make page one of Google. It removed the dependencies between teams working on separate features, etc.SEO is beyond a technical problem, it’s also a user experience problem It is making sure we have more stable features and deliver dates. Having these ephemeral environments allowed us to move quickly to CD. Making the environment "green" is the only way to move forward to the next step. With the same bot, you can also run automation on your environment. After that, the environment is shut down and available for assignment for another branch. We control the cost of these environments by having a smart cluster solution: (I wrote about it here: īy default, environments live for 3 hours. It is 100% similar to production (obviously scaled down). Anything you push with the branch name matching will deploy to the dev6 environment. You ask a slack bot for a dev environment like this: dev for will reply I assigned dev6 to feature/GLOB-1234-feature-name We now have X number of dev environments. Our theory was that this would bring predictability and more stable features. When we started the transition to CD, we knew we need a testing mechanism that will allow engineers to test full features in isolation, without feature X affecting feature Y. Even when we tried to be flexible with the times, it still did not work. We would end up with features that are not fully ready by the rigid cutoff time. This proved to be challenging and frustrating. We would then move to an integration environment with all the changes that were committed to dec in those two weeks. During the 2 weeks, everyone would deploy to a single `dev` environment. The beforeīefore moving to CD, we would deploy every 2 weeks. This is the direction we are heading for, but at this point in time, we have to work with this limitation. In a perfect world, we would not even need this. To fully test a change, you need to deploy or simulate a fully working environment. From the frontend to the backend, through messaging systems and buses. Lots of microservices talking to each other. Prior to this change, our ability to test features in isolation was non-existent. ![]() One of the drivers of this change was our ability to test code changes in isolation, run automation on them, and move on with confidence to the next stage. Obviously, that is the last step in a long process that required very hard work from a lot of talented people. ![]() In one of my recent posts ( ), I shared how we deploy to production.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |