Author: (Russia) Oleg Skrynnik Publisher: Tsinghua University Press Publication year: 2020-05-01 ISBN: 9787302547143 Notes: As the title suggests, the book focuses on DevOps from a business perspective. From its origins to its foundations, from principles to practice, you can take something away at every level. DevOps rests on lean production (the Toyota production line) and agile development, with the value chain at its core.

Using Jenkins always means dealing with all kinds of plugins. To practice DevOps better, we should also be capable of developing plugins ourselves, so the whole process can converge inside Jenkins. 1. Jenkins Plugins 1.1 The Plugin Ecosystem Jenkins’ predecessor Hudson started in 2004, and 16 years on it is still a mainstream CI/CD engine.

1. Thought Drives Behavior Thought drives behavior, and behavior produces results. How we treat people, handle things, and approach affairs all come from culture, and they do not leap forward just because technology advances rapidly. The Chinese nation, with its long history, has accumulated remarkably resilient intellectual wisdom. Dynasties rose and fell, regimes changed, and none of it could bring her down.

When Base64-decoding a JWT, I found that the JSON data was incomplete. This article mainly introduces the relevant knowledge and solves this problem. 1. Introduction to JWT JWT passes authentication by setting Authorization: Bearer <token> in the Header. A JWT Token is a Base64-encoded string joined by dots, something like

1. Raise the Level of Automation Remote builds usually need the help of some CI tool, such as GitHub Actions, Travis CI, and so on. In an intranet environment, you can use GitLab CI and add a CI node for automated builds — see my GitLab documentation. The benefits of automation go without saying: it standardizes processes, saves a great deal of time, and delivers clear returns.