Jenkins 构建流程和构建管道插件
Jenkins Build Flow AND Build Pipeline plugins
请问Build Pipeline plugin still show the sequence of jobs properly if the jobs are run using Build Flow(包括重复作业)?
这是我们构建流程的伪代码:
build("Package")
build("Deploy", destination: "http://test") // deploy to our test environment
build("IntegrationTests", target: "http://test") // run automated tests
build("Deploy", destination: "http://stage") // deploy to stage
- Package 将从源代码管理中提取代码,编译它,并将其存储为工件
- Deploy 将从上游 Package 作业复制工件,然后将其复制到 [=12] 中提供的 URL =]参数
- IntegrationTests 将 运行 一套针对
destination
参数中提供的 URL 的集成测试。
即使重复 Deploy 作业,Build Pipeline plugin 是否会将此管道显示为 4 个步骤?
Package => Deploy (test) => IntegrationTests => Deploy (stage)
新的解决方案,which is being adopted with Jenkins 2.0, is the Pipeline plugin. Also, CloudBees open-sourced their Pipeline Stage View plugin 为 Pipeline 插件提供可视化。
请问Build Pipeline plugin still show the sequence of jobs properly if the jobs are run using Build Flow(包括重复作业)?
这是我们构建流程的伪代码:
build("Package")
build("Deploy", destination: "http://test") // deploy to our test environment
build("IntegrationTests", target: "http://test") // run automated tests
build("Deploy", destination: "http://stage") // deploy to stage
- Package 将从源代码管理中提取代码,编译它,并将其存储为工件
- Deploy 将从上游 Package 作业复制工件,然后将其复制到 [=12] 中提供的 URL =]参数
- IntegrationTests 将 运行 一套针对
destination
参数中提供的 URL 的集成测试。
即使重复 Deploy 作业,Build Pipeline plugin 是否会将此管道显示为 4 个步骤?
Package => Deploy (test) => IntegrationTests => Deploy (stage)
新的解决方案,which is being adopted with Jenkins 2.0, is the Pipeline plugin. Also, CloudBees open-sourced their Pipeline Stage View plugin 为 Pipeline 插件提供可视化。