The DevOps HandbookEVALUATING THE EFFECTIVENESS OF PULL REQUEST PROCESSES i. Review production outages and examine the peer review process for the relevant changes ii. Sampling and examining pull requests from larger population population or those relevant to production incidents 1. Bad pull requests – typically doesn’t have enough context for the reader, little documentation of the changes intended outcome, or explanation of of the thought process behind the change 2. Good pull requests – sufficient detail on why the change is made, how the change was made, and identified risks and resulting countermeasures j. FEARLESSLY0 码力 | 8 页 | 24.02 KB | 5 月前3
Velocity Conference 2015problem to come along Changing the Laws of Engineering with GitHub Pull Requests by Ralph Bodenner (New Relic) https://bit.ly/pull-request-your-culture How you change your process matters Terms: culture0 码力 | 4 页 | 176.79 KB | 5 月前3
git 操作手册com/cof/pro-1.git # git push -uf rmtRepo main #将本地代码库的当前分支(main)推送到远 程的代码库的main分支 # git pull rmtRepo main #从远程代码库下载main分支的最新修改,若未 指定分支名,则默认拉取同本地分支名的分支 # git remote -v ~/cof-sshkey User cof Iden�tyAgent none # ssh git@gitlab.cof-lee.com PTY alloca�on request failed on channel 0 Welcome to GitLab, @cof! #出现这行说明已经登录成功了 Connec�on to0 码力 | 35 页 | 1.69 MB | 1 年前3
k8s操作手册 2.3cof-lee.com:5443/k8s/etcd:3.4.13-0 #可见镜像名已由默认的k8s.gcr.io/换成了配置文件里指定的docker镜像源 # kubeadm config images pull --image-repository="cof-lee.com:5443/k8s" #提前 下载需要的镜像 # kubeadm init --config /etc/kubeadm-init com:5443/k8s/coredns:v1.10.1 #可见镜像名已由默认的k8s.gcr.io/换成了配置文件里指定的docker镜像源 # kubeadm config images pull --image-repository="cof-lee.com:5443/k8s" #提前 下载需要的镜像 # ctr -n k8s.io image ls image-endpoint: unix:///run/containerd/containerd.sock �meout: 10 debug: false EOF ★crictl常用操作 crictl只支持pull拉取镜像及rmi删除镜像操作,不支持push及tag打标签 # crictl images #查看镜像,默认查询k8s.io命名空间,且不可指定命名 空间 # crictl0 码力 | 126 页 | 4.33 MB | 1 年前3
The DevOps Handbook(availability, capacity, security, etc.) ii. Incorporate security hardening testing and evaluation m. PULL OUR ANDON CORD WHEN THE DEPLOYMENT PIPELINE BREAKS i. Keep the build in a green state ii. When a human behaviors and incentives is more challenging than the technical aspects n. WHY WE NEED TO PULL THE ANDON CORD i. If not, it becomes increasing difficult to get back to a deployable state ii.0 码力 | 8 页 | 23.08 KB | 5 月前3
The DevOps Handbookaffected by the problem 6. Anyone else who is interested in attending the meeting iv. Guidance 1. Pull all factual evidence (chat logs, etc.) to help build the timeline; any specific metrics observed0 码力 | 9 页 | 25.13 KB | 5 月前3
The Phoenix Projecta sixty-four-character text box? What idiot built that form?” “When my guys put in a change request, they have to wait a lifetime to get approvals, let alone get on the schedule. We have the business0 码力 | 3 页 | 154.45 KB | 5 月前3
A Seat at the Table - IT Leadership in the Age of Agilitygroup is private so the first time you visit you likely have to wait for an admin to approve your request to join but don’t let that deter you! We value your feedback and we need it to learn and do better0 码力 | 7 页 | 387.48 KB | 5 月前3
python3学习手册反回2字节校验和的反码 def generate_icmp_packet(icmp_data): # inputicmp_type = 8 # echo_request icmp_code = 0 icmp_id = 0x0000 icmp_sequence = 0x0000 icmp_checkum = 0x0000 icmp_header 0 码力 | 213 页 | 3.53 MB | 1 年前3
共 9 条
- 1













