Github action docker login1/6/2024 There was nothing I could do, except take a coffee break to absorb more energy from the universe so that I could refocus and rethink the problem at hand. At that exact time, though, I started to question my intelligence level, because as a genius as myself, how on earth was I not able to figure out the logic behind a bloody pipeline? I mean, really? How did the pipeline even trigger the library execution? In what order did all the tasks run? How could I know which stage was included in which pipelines, and not included in other pipelines?ĭon't get me wrong, I'm not arrogant, but I do often think of myself as a "not too stupid" guy. After half an hour, when I was looking at the pipeline code, I didn't have a single clue of how the heck everything was glued together. Then, somehow, my colleague started jumping around between pieces of code within the same big repo full of Groovy libraries. How hard can it be? As a pro myself, I reckoned that I would finish it in hours, if not tens of minutes. Everything was implemented in Groovy and running in Jenkins nothing that I hadn't already been familiar with. Since I was new to the team, another teammate was kind enough to spare 30 minutes to give me a quick introduction to the CI pipelines and libraries they were using. Until I was tasked to add another stage in our existing CI pipelines. So we were already achieving something truly great, I thought. Before that, I had worked in real start-ups, but even there we didn't release half as often. The team was meant to be at the same time an experiment to quickly build something cool in an unconventional way, and an “A-team” so that the culture and the way of working could be preached to other teams, as to kick-off digital transformation in a traditional business.Īt that time, we were handling more than 25 microservices and releasing as often as 100 times per week. I was once working in an agile team within a big corporation. Or simply download our GitHub Actions security cheat sheet! 1. Harden your pipeline by scanning your Docker image for leaked secrets and credentials with the help of GitGuardian's ggshield action. Learn how to build a modern CI pipeline using GitHub Actions to achieve testing, building, and pushing Docker images. Tiexin Guo Senior DevOps Consultant, Amazon Web Services
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |