We provide TechOps, DevOps and IT Support Services to Web3 and Blockchain Projects worldwide 24/7/365.
We provide TechOps, DevOps and IT Support Services to Web3 and Blockchain Projects worldwide 24/7/365.
Subscribe to TechOps.Services
Subscribe to TechOps.Services
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
This is a copy of our January newsletter, a short check-in on what’s happening at TechOps and some interesting things worth sharing.
We’ve got out tickets to ETHDenver!
We’re proud sponsors of Pragma Denver! You can win a free ticket.
We published a new Blog post about our experience building Blockchain Keepers.
We’ve launched our partnership program that helps us and our trusted partners expand our networks and reach even more people. If you’re interested in hearing more, come talk to us on Discord.
During one of our team’s knowledge-sharing sessions, Sasha, from our engineering team, showed how he solved a long-lasting issue that many DevOps teams suffer from. We asked him some questions:
What issue were you trying to solve?
We observed issues with Terraform workspaces sometimes being incorrectly attached to GitHub or not updated to the master branch. This could be because someone is working on a test branch or because they forgot to switch back. At TechOps, where we bill by the ticket resolution time and we often pick up where someone left off, this causes delays and complications in software development, as engineers have to spend time rectifying these discrepancies instead of working on new tickets.
What solution did you find so far?
For now, I have created an automation that checks Terraform Cloud's workspaces connection to GitHub, its attachment to the master branch, and whether there are any errors or pending actions. It then creates a report that gets automatically posted to one of our internal Discord Channels at 08:00 am CET as we hand over from APAC to EU work hours.
Are you satisfied with the result?
It’s a step in the right direction and has already proven itself useful by reminding us of something we may have forgotten; or sparked a conversation during our Standup meetings about why something has changed. You can’t beat clear facts with human memory.
What would you like to build next?
I don’t know yet but we’re constantly looking out for ways of improving our efficiency. And it’s often small tools like this that bring us the most value because they take care of the mundane and allow us to focus on bigger and harder things.
If you would like to know more, you can reach Sasha or anyone from our engineering team through the TechOps Discord.
You can find us at ETHDenver between the 24th of February and the 4th of March and at Pragma Denver on the 28th of February (Free Tickets). If you’re not able to make those events, we can meet you in Copenhagen, Melbourne, or online.
-
Thank you for staying connected with TechOps! If you have any questions or feedback or would like to explore collaborations, you can chat with us on Discord or any of our socials or simply reply to this email.
This is a copy of our January newsletter, a short check-in on what’s happening at TechOps and some interesting things worth sharing.
We’ve got out tickets to ETHDenver!
We’re proud sponsors of Pragma Denver! You can win a free ticket.
We published a new Blog post about our experience building Blockchain Keepers.
We’ve launched our partnership program that helps us and our trusted partners expand our networks and reach even more people. If you’re interested in hearing more, come talk to us on Discord.
During one of our team’s knowledge-sharing sessions, Sasha, from our engineering team, showed how he solved a long-lasting issue that many DevOps teams suffer from. We asked him some questions:
What issue were you trying to solve?
We observed issues with Terraform workspaces sometimes being incorrectly attached to GitHub or not updated to the master branch. This could be because someone is working on a test branch or because they forgot to switch back. At TechOps, where we bill by the ticket resolution time and we often pick up where someone left off, this causes delays and complications in software development, as engineers have to spend time rectifying these discrepancies instead of working on new tickets.
What solution did you find so far?
For now, I have created an automation that checks Terraform Cloud's workspaces connection to GitHub, its attachment to the master branch, and whether there are any errors or pending actions. It then creates a report that gets automatically posted to one of our internal Discord Channels at 08:00 am CET as we hand over from APAC to EU work hours.
Are you satisfied with the result?
It’s a step in the right direction and has already proven itself useful by reminding us of something we may have forgotten; or sparked a conversation during our Standup meetings about why something has changed. You can’t beat clear facts with human memory.
What would you like to build next?
I don’t know yet but we’re constantly looking out for ways of improving our efficiency. And it’s often small tools like this that bring us the most value because they take care of the mundane and allow us to focus on bigger and harder things.
If you would like to know more, you can reach Sasha or anyone from our engineering team through the TechOps Discord.
You can find us at ETHDenver between the 24th of February and the 4th of March and at Pragma Denver on the 28th of February (Free Tickets). If you’re not able to make those events, we can meet you in Copenhagen, Melbourne, or online.
-
Thank you for staying connected with TechOps! If you have any questions or feedback or would like to explore collaborations, you can chat with us on Discord or any of our socials or simply reply to this email.
No activity yet