sh -c "$(curl -fsSL https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/master/tools/install.sh)"
- Download zsh-autosuggestions by
platform: Centos 7 x86_64 bbr
python 2.7.5 (system embedded)
yum install shadowsocks-libev met dependencies error, using python module instead
reference: https://www.crifan.com/linode_centos_7_install_and_config_shadowsocks/
| // A Declarative Pipeline is defined within a 'pipeline' block. | |
| pipeline { | |
| // agent defines where the pipeline will run. | |
| agent { | |
| // This also could have been 'agent any' - that has the same meaning. | |
| label "" | |
| // Other possible built-in agent types are 'agent none', for not running the | |
| // top-level on any agent (which results in you needing to specify agents on | |
| // each stage and do explicit checkouts of scm in those stages), 'docker', |
https://dev.to/pencillr/jenkins-pipelines-and-their-dirty-secrets-1
In case it is necessary you can actually create an embedded Scripted Pipeline block IN a Declarative Pipeline step! We use the script{} block for this. Here's how it is:
#!/usr/bin/env groovy
pipeline {
agent any| * take precedence over * | |
| Exclude branches - a regular expression to specify branches to exclude; note that this will take precedence over includes | |
https://feifeiyum.github.io/2017/01/23/base-vimusage/ 推荐: 关闭 vim 扩展的 useCtrlKeys, 保留一些 VS Code 自身的一些常用快捷键, 在 settings.json 里面添加配置 “vim.useCtrlKeys”: false
| # -*- coding: utf-8 -*- | |
| """ | |
| auther = tdss | |
| date = 17-9-7 | |
| time = 08:39 | |
| 一个基于二叉树的大根堆, 无扩容负担, 增加和弹出为O(logN) | |
| """ | |
| import random |
stackoverflow上的一个回答https://stackoverflow.com/questions/2092527/what-happens-when-you-type-in-a-url-in-browser
In an extremely rough and simplified sketch, assuming the simplest possible HTTP request, no proxies, IPv4 and no problems in any step:
1 browser checks cache; if requested object is in cache and is fresh, skip to #9 2 browser asks OS for server's IP address 3 OS makes a DNS lookup and replies the IP address to the browser 4 browser opens a TCP connection to server (this step is much more complex with HTTPS) 5 browser sends the HTTP request through TCP connection 6 browser receives HTTP response and may close the TCP connection, or reuse it for another request