站酷设计网站官网入口文字设计,seo网站推广工具,关键词优化最好的方法,源码搭建网站功能开发测试#xff1a; 功能性测试 对应开发框架的测试用例代码的漏洞扫描 Web服务器版本应用开发语言的依赖关系和版本信息是否会造成类似内存泄露等影响系统性能的问题压力测试应用的部署 获取应用代码以及应用静态文件的代码包将安装包中的文件按照服务器配置的架构…功能开发测试 功能性测试 对应开发框架的测试用例代码的漏洞扫描 Web服务器版本应用开发语言的依赖关系和版本信息是否会造成类似内存泄露等影响系统性能的问题压力测试应用的部署 获取应用代码以及应用静态文件的代码包将安装包中的文件按照服务器配置的架构将代码文件上传到指定的位置 传统应用开发生命周期中使用一个名为“瀑布式开发”的概念。各个部门的人员各司其职互相之间的工作联系并不紧密。
“敏捷开发”开发人员一边开发一边对已经开发完成的部分进行测试和集成提升开发效率。
持续集成开发人员一边进行开发同时及时进行应用的集成
一旦检测到代码发生变化立刻运行测试自动化出发测试无误的情况下继续进行代码的打包发布自动完成无需人工操作如果测试出现问题将问题通知给相关人员(无需人工操作根据测试结果自动发生)。继续修改相关开发人员针对测试中出现的问题进行修改后此时代码发生变化回到第一步。 持续部署一定那检测到新版本程序包的发布就立刻按照提前规划好的方式进行应用的更新部署。
可以利用puppet chef ansible 等自动化管理软件配置应用的自动化部署应用更新策略的选择 滚动更新以K8S中部署的具有10个副本数量要求的deployment为例 K8S中如果没有设置更新比例的情况下默认使用25%作为控制值10 * 0.25 2.5 取整3 每次更新3个副本的pod更新的批次安排 3 3 3 1K8S维持本身的10个pod不变新调度3个pod新调度的pod使用新发布的应用 此时deployment控制的pod数量为13 10 个旧版本应用 3 个新版本应用等待新调度的3个pod返回状态为running之后移除原本10个pod中的3个 此时deployment控制的pod数量为103个新应用 7 旧的应用 如果新调度的3个pod在指定的时间内没有返回running状态则此时更新中止对应的deployment继续控制10个运行旧版本应用的pod然后回到第三步以3个pod为单位依次更新最后deployment控制到的pod都是新版本的应用
滚动更新是一种更新策略在滚动更新的过程中如果出现任何问题可以进行回滚以实现应用版本回溯恢复到没有问题的版本。而这种更新策略所规划的更新部署可以通过任意方式实现。Shell 剧本 应答文件 灰度发布生产环境下的服务器将被分为两个集群。一个集群用来部署灰度发布的应用一个集群用来部署正常更新的应用。
灰度发布和滚动更新都是为了避免同一个问题即新版本代码发布到生产环境下出现问题后不应该影响用户对于应用的正常访问 蓝绿发布生产环境下服务器被分为两个集群一个集群使用绿色表示一个集群使用蓝色表示这两套集群环境一致一般同时只有一个集群开放给用户访问。 蓝色集群部署了稳定版本的应用绿色集群部署了开发版本的应用绿色集群中的新版本应用经过测试稳定运行后将用户的访问全部转发给绿色集群处理此时蓝色集群不再用户的访问但是蓝色集群可以用来部署最新版本的应用并测试其稳定性。
金丝雀测试在应用更新部署前一定要在生产环境下进行测试以验证没有任何问题才可以进行大规模的应用更新。 代码仓库保存代码的集中仓库。
代码仓库可以使用传统的文件共享协议进行部署也可以使用专门的代码仓库软件进行部署。目前大部分公司的代码仓库都是用了支持版本控制功能的应用来进行管理。
常见的版本控制软件
GitMercurilSVN Git :
git add //文件提交到暂存区已经被追踪的文件也可以提交未追踪的文件
git commit // 将暂存区的文件提交到本地仓库
git log // 查看git commit的提交次数和记录
git rm // 将文件从本地目录和仓库中移除
git mv //对文件进行重命名的操作同时发生在本地和仓库中
Git status // 显示本地目录中文件的状态
文件状态显示 未追踪 //在本地git仓库中不存在该文件
已修改未提交 // 文件的修改已使用git add 命令同步至暂存区但是未提交到比本地git仓库
已修改未暂存 // 文件的修改未提交到暂存区
git reset // 将文件从暂存区移除
git restore // 从本地仓库恢复文件到本地
Git checkout -- 文件名 // 将文件未提交的变更全部移除 课堂演示记录 [studentharbor ~]$ sudo yum -y install git // 包含下面所有的功能同时支持tab 键自动补齐子命令和选项
[studentharbor ~]$ rpm -qa | grep git-core //git核心功能功能完善不影响使用
git-core-2.43.5-1.el9.x86_64
git-core-doc-2.43.5-1.el9.noarch
[studentharbor ~]$
[studentharbor ~]$ sudo git config --system user.email admin123.com
[studentharbor ~]$ cat /etc/gitconfig
[user]email admin123.com
[studentharbor ~]$ git config --list
user.emailadmin123.com
[studentharbor ~]$ git config --list --show-origin
file:/etc/gitconfig user.emailadmin123.com
[studentharbor ~]$ git config --global user.email student123.com
[studentharbor ~]$ git config --list
user.emailadmin123.com
user.emailstudent123.com
[studentharbor ~]$ git config --list --show-origin
file:/etc/gitconfig user.emailadmin123.com
file:/home/student/.gitconfig user.emailstudent123.com
[studentharbor ~]$ cat .gitconfig
[user]email student123.com
[studentharbor ~]$ git config --global core.editor vim
[studentharbor ~]$ git config --global user.name student
[studentharbor ~]$ git config --list
user.emailadmin123.com
user.emailstudent123.com
user.namestudent
core.editorvim
[studentharbor ~]$ git config user.name
student
[studentharbor ~]$ git config user.email
student123.com
[studentharbor ~]$ git config help
error: key does not contain a section: help
[studentharbor ~]$ git help config
[studentharbor ~]$
[studentharbor ~]$ cd practice/demo/
[studentharbor demo]$
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml src target
[studentharbor demo]$ cd ..
[studentharbor practice]$ cp -r demo demo_1
[studentharbor practice]$ cd demo
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml src target
[studentharbor demo]$ ls -a
. .. Dockerfile .gitignore HELP.md .mvn mvnw mvnw.cmd pom.xml src target
[studentharbor demo]$ rm -rf .gitignore
[studentharbor demo]$
[studentharbor demo]$ git init
hint: Using master as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch name
hint:
hint: Names commonly chosen instead of master are main, trunk and
hint: development. The just-created branch can be renamed via this command:
hint:
hint: git branch -m name
Initialized empty Git repository in /home/student/practice/demo/.git/
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml src target
[studentharbor demo]$ ls .git/
branches config description HEAD hooks info objects refs
[studentharbor demo]$
[studentharbor demo]$ git status
On branch masterNo commits yetUntracked files:(use git add file... to include in what will be committed).mvn/DockerfileHELP.mdmvnwmvnw.cmdpom.xmlsrc/target/nothing added to commit but untracked files present (use git add to track)
[studentharbor demo]$ git add Dockerfile
[studentharbor demo]$ git status
On branch masterNo commits yetChanges to be committed:(use git rm --cached file... to unstage)new file: DockerfileUntracked files:(use git add file... to include in what will be committed).mvn/HELP.mdmvnwmvnw.cmdpom.xmlsrc/target/[studentharbor demo]$ git rm --cached Dockerfile
rm Dockerfile
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml src target
[studentharbor demo]$ git status
On branch masterNo commits yetUntracked files:(use git add file... to include in what will be committed).mvn/DockerfileHELP.mdmvnwmvnw.cmdpom.xmlsrc/target/nothing added to commit but untracked files present (use git add to track)
[studentharbor demo]$ vim Dockerfile
[studentharbor demo]$ git status
On branch masterNo commits yetUntracked files:(use git add file... to include in what will be committed).mvn/DockerfileHELP.mdmvnwmvnw.cmdpom.xmlsrc/target/nothing added to commit but untracked files present (use git add to track)
[studentharbor demo]$ git add Dockerfile
[studentharbor demo]$
[studentharbor demo]$ git status
On branch masterNo commits yetChanges to be committed:(use git rm --cached file... to unstage)new file: DockerfileUntracked files:(use git add file... to include in what will be committed).mvn/HELP.mdmvnwmvnw.cmdpom.xmlsrc/target/[studentharbor demo]$ vim Dockerfile
[studentharbor demo]$ git status
On branch masterNo commits yetChanges to be committed:(use git rm --cached file... to unstage)new file: DockerfileChanges not staged for commit:(use git add file... to update what will be committed)(use git restore file... to discard changes in working directory)modified: DockerfileUntracked files:(use git add file... to include in what will be committed).mvn/HELP.mdmvnwmvnw.cmdpom.xmlsrc/target/[studentharbor demo]$ git add Dockerfile
[studentharbor demo]$ git commit
[master (root-commit) 6072b75] Add container image build file1 file changed, 6 insertions()create mode 100644 Dockerfile
[studentharbor demo]$ git status
On branch master
Untracked files:(use git add file... to include in what will be committed).mvn/HELP.mdmvnwmvnw.cmdpom.xmlsrc/target/nothing added to commit but untracked files present (use git add to track)
[studentharbor demo]$ tree src
src
├── main
│ ├── java
│ │ └── com
│ │ └── example
│ │ └── demo
│ │ ├── Application.java
│ │ └── HelloController.java
│ └── resources
│ └── application.properties
└── test└── java└── com└── example└── demo├── HelloControllerITest.java└── HelloControllerTest.java11 directories, 5 files
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml src target
[studentharbor demo]$ vim .gitignore
# mavens working directory
target/
#project default mvn program
mvnw*
#project help file
HELP.md
#but track all readme file
!readme.txt
!README.txt
!README.md
!readme.md[studentharbor demo]$ git status
On branch master
Untracked files:(use git add file... to include in what will be committed).gitignore.mvn/pom.xmlsrc/nothing added to commit but untracked files present (use git add to track)
[studentharbor demo]$ ls .mvn/
wrapper
[studentharbor demo]$ ls .mvn/wrapper/
maven-wrapper.properties
[studentharbor demo]$ vim .gitignore
# ignore git-ignore file
.gitignore
# mavens working directory
target/
#project default mvn program
mvnw*
.mvn/
#project help file
HELP.md
#but track all readme file
!readme.txt
!README.txt
!README.md
!readme.md[studentharbor demo]$ git status
On branch master
Untracked files:(use git add file... to include in what will be committed)pom.xmlsrc/nothing added to commit but untracked files present (use git add to track)
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml src target
[studentharbor demo]$ git add .
[studentharbor demo]$ git commit
[master 78aa0f9] source code and project maven configuration6 files changed, 170 insertions()create mode 100644 pom.xmlcreate mode 100644 src/main/java/com/example/demo/Application.javacreate mode 100644 src/main/java/com/example/demo/HelloController.javacreate mode 100644 src/main/resources/application.propertiescreate mode 100644 src/test/java/com/example/demo/HelloControllerITest.javacreate mode 100644 src/test/java/com/example/demo/HelloControllerTest.java
[studentharbor demo]$ git status
On branch master
nothing to commit, working tree clean
[studentharbor demo]$ vim readme.txt
[studentharbor demo]$ git status -s
?? readme.txt
[studentharbor demo]$ git add readme.txt
[studentharbor demo]$ git commit add readme file
error: pathspec add readme file did not match any file(s) known to git
[studentharbor demo]$ git commit -m add readme file
[master 6acb2a6] add readme file1 file changed, 2 insertions()create mode 100644 readme.txt
[studentharbor demo]$ vim readme.txt
[studentharbor demo]$ git status -sM readme.txt
[studentharbor demo]$ git diff readme.txt
diff --git a/readme.txt b/readme.txt
index a3365b1..2bf0964 100644
--- a/readme.txtb/readme.txt-1,2 1,4 project purpose:practice how to deploy an app base on springboot development infrustracturethis project run on port 8080
[studentharbor demo]$ git add readme.txt
[studentharbor demo]$ git diff readme.txt
[studentharbor demo]$ git diff readme.txt
[studentharbor demo]$ git diff readme.txt --staged
fatal: option --staged must come before non-option arguments
[studentharbor demo]$ git diff --staged readme.txt
diff --git a/readme.txt b/readme.txt
index a3365b1..2bf0964 100644
--- a/readme.txtb/readme.txt-1,2 1,4 project purpose:practice how to deploy an app base on springboot development infrustracturethis project run on port 8080
[studentharbor demo]$ vim Dockerfile
[studentharbor demo]$ vim readme.txt
[studentharbor demo]$ git status
On branch master
Changes to be committed:(use git restore --staged file... to unstage)modified: readme.txtChanges not staged for commit:(use git add file... to update what will be committed)(use git restore file... to discard changes in working directory)modified: Dockerfilemodified: readme.txt[studentharbor demo]$ git commit -am add all changes to repository
[master b7abcf7] add all changes to repository2 files changed, 7 insertions(), 1 deletion(-)
[studentharbor demo]$ git status
On branch master
nothing to commit, working tree clean
[studentharbor demo]$ echo test test.txt
[studentharbor demo]$ git add test.txt
[studentharbor demo]$ git commit -m test
[master 1b64891] test1 file changed, 1 insertion()create mode 100644 test.txt
[studentharbor demo]$ git status
On branch master
nothing to commit, working tree clean
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml readme.txt src target test.txt
[studentharbor demo]$ rm -f test.txt
[studentharbor demo]$ git status
On branch master
Changes not staged for commit:(use git add/rm file... to update what will be committed)(use git restore file... to discard changes in working directory)deleted: test.txtno changes added to commit (use git add and/or git commit -a)
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml readme.txt src target
[studentharbor demo]$ git restore test.txt
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml readme.txt src target test.txt
[studentharbor demo]$ git rm test.txt
rm test.txt
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml readme.txt src target
[studentharbor demo]$ git status
On branch master
Changes to be committed:(use git restore --staged file... to unstage)deleted: test.txt[studentharbor demo]$ git commit
[master 5066a6f] delete unraleted files1 file changed, 1 deletion(-)delete mode 100644 test.txt
[studentharbor demo]$ mv readme.txt README.txt
[studentharbor demo]$ git status
On branch master
Changes not staged for commit:(use git add/rm file... to update what will be committed)(use git restore file... to discard changes in working directory)deleted: readme.txtUntracked files:(use git add file... to include in what will be committed)README.txtno changes added to commit (use git add and/or git commit -a)
[studentharbor demo]$ git mv readme.txt README.txt
fatal: bad source, sourcereadme.txt, destinationREADME.txt
[studentharbor demo]$ git mv readme.txt README.txt
Dockerfile pom.xml readme.txt README.txt src/
[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml README.txt src target
[studentharbor demo]$
[studentharbor demo]$ mv README.txt readme.txt
[studentharbor demo]$ git status
On branch master
nothing to commit, working tree clean
[studentharbor demo]$ git mv readme.txt README.txt
[studentharbor demo]$ git status
On branch master
Changes to be committed:(use git restore --staged file... to unstage)renamed: readme.txt - README.txt[studentharbor demo]$ ls
Dockerfile HELP.md mvnw mvnw.cmd pom.xml README.txt src target
[studentharbor demo]$ git commit
[master 8150f9a] rename readme to README1 file changed, 0 insertions(), 0 deletions(-)rename readme.txt README.txt (100%)
[studentharbor demo]$ git log
commit 8150f9ac7721a074a7bea55f1fa9a321482cfee1 (HEAD - master)
Author: student student123.com
Date: Fri Oct 18 15:03:04 2024 0800rename readme to READMEcommit 5066a6f4e44521ca7ae92f48a482e90d644b8c85
Author: student student123.com
Date: Fri Oct 18 14:58:28 2024 0800delete unraleted filescommit 1b648917cc774f1239a6be2b8ccae2b6a7ca1ac6
Author: student student123.com
Date: Fri Oct 18 14:55:54 2024 0800testcommit b7abcf70832a81e796e1a16a3548038d1d169577
Author: student student123.com
Date: Fri Oct 18 14:54:14 2024 0800add all changes to repositorycommit 6acb2a653db83193e4b7b51ecff39d6d252af457
Author: student student123.com
Date: Fri Oct 18 14:45:55 2024 0800add readme filecommit 78aa0f986c5e4084969b674bea50b20949966250
Author: student student123.com
Date: Fri Oct 18 14:39:25 2024 0800source code and project maven configurationcommit 6072b75fed80c8ab6777dd52c7955ead217e5f8e
Author: student student123.com
Date: Fri Oct 18 14:20:53 2024 0800Add container image build file
[studentharbor demo]$ git log -2
commit 8150f9ac7721a074a7bea55f1fa9a321482cfee1 (HEAD - master)
Author: student student123.com
Date: Fri Oct 18 15:03:04 2024 0800rename readme to READMEcommit 5066a6f4e44521ca7ae92f48a482e90d644b8c85
Author: student student123.com
Date: Fri Oct 18 14:58:28 2024 0800delete unraleted files
[studentharbor demo]$ vim README.txt
[studentharbor demo]$ git status -sM README.txt
[studentharbor demo]$ git add README.txt
[studentharbor demo]$ vim pom.xml
[studentharbor demo]$ git status -s
M README.txtM pom.xml
[studentharbor demo]$ git commit -m modify readme
[master bde40f3] modify readme1 file changed, 2 insertions()
[studentharbor demo]$ git commit --amend
[master 0ae7c5d] modify readmeDate: Fri Oct 18 15:13:04 2024 08001 file changed, 2 insertions()
[studentharbor demo]$ git add pom.xml
[studentharbor demo]$ git commit --amend
[master 4516228] modify readme and pom.xmlDate: Fri Oct 18 15:13:04 2024 08002 files changed, 3 insertions(), 1 deletion(-)
[studentharbor demo]$ git log -3
commit 451622813a89a19b12be78dd6aa9e364bb891164 (HEAD - master)
Author: student student123.com
Date: Fri Oct 18 15:13:04 2024 0800modify readme and pom.xmlcommit 8150f9ac7721a074a7bea55f1fa9a321482cfee1
Author: student student123.com
Date: Fri Oct 18 15:03:04 2024 0800rename readme to READMEcommit 5066a6f4e44521ca7ae92f48a482e90d644b8c85
Author: student student123.com
Date: Fri Oct 18 14:58:28 2024 0800delete unraleted files
