今天写脚本，调用api想着如果一个任务成功，则跑另外任务，但是我看来，一个build结果时unstable，结果也是lastSuccessfulBuild，换成lastStableBuild解决。
同时附录jenkins的术语，主要取自这两个网址，附录上，有时间我整理翻译下：
https://wiki.jenkins.io/display/JENKINS/Terminology
https://www.jenkins.io/doc/book/glossary/
| 英文 | 中文 | 解释 | 其他说明 |
|---|---|---|---|
| Agent | 代理 | An agent is typically a machine, or container, which connects to a Jenkins master and executes tasks when directed by the master. | |
| Artifact | An immutable file generated during a Build or Pipeline run which is archived onto the Jenkins Master for later retrieval by users. | ||
| Build | Result of a single execution of a Project 执行一个project的结果 |
||
| Cloud | A System Configuration which provides dynamic Agent provisioning and allocation, such as that provided by the Azure VM Agents or Amazon EC2 plugins. Handles creation of Nodes to dynamically expand/shrink the number of slave machines |
||
| Core | The primary Jenkins application (jenkins.war) which provides the basic web UI, configuration, and foundation upon which Plugins can be built. | ||
| Downstream | A configured Pipeline or Project which is triggered as part of the execution of a separate Pipeline or Project. | ||
| Executor | A slot for execution of work defined by a Pipeline or Project on a Node. A Node may have zero or more Executors configured which corresponds to how many concurrent Projects or Pipelines are able to execute on that Node. Separated stream of builds to be run on Node in parallel. Node can have 1 or more Executors. Special executors can be created dynamically (one-off executors) to run lightweight jobs used mostly for orchestration purposes. |
||
| Fingerprint | A hash considered globally unique to track the usage of an Artifact or other entity across multiple Pipelines or Projects. | ||
| Folder | An organizational container for Pipelines and/or Projects, similar to folders on a file system. | ||
| Item | An entity in the web UI corresponding to either a: Folder, Pipeline, or Project. | ||
| Jenkins URL | The main url for the jenkins application, as visited by a user. e.g. https://ci.jenkins.io/ jenkins服务器的首页网址 |
||
| Job | A deprecated term, synonymous with Project. 和Project相同，不再使用 |
||
| Label | User-defined text for grouping Agents, typically by similar functionality or capability. For example linux for Linux-based agents or docker for Docker-capable agents. | ||
| Master | The central, coordinating process which stores configuration, loads plugins, and renders the various user interfaces for Jenkins. | ||
| Node | A machine which is part of the Jenkins environment and capable of executing Pipelines or Projects. Both the Master and Agents are considered to be Nodes. | ||
| Project | A user-configured description of work which Jenkins should perform, such as building a piece of software, etc. Jenkins seems to use these terms interchangeably. They all refer to runnable tasks that are controlled / monitored by Jenkins. |
||
| Pipeline | A user-defined model of a continuous delivery pipeline, for more read the Pipeline chapter in this handbook. | ||
| Plugin | 插件 | An extension to Jenkins functionality provided separately from Jenkins Core. | |
| Publisher | Part of a Build after the completion of all configured Steps which publishes reports, sends notifications, etc. A publisher is part of the build process other than compilation, for example JUnit test runs. A publisher may report stable or unstable result depending on the result of its processing. For example, if a JUnit test fails, then the whole JUnit publisher may report unstable. |
||
| Resource Root URL | A secondary url used to serve potentially untrusted content (especially build artifacts). This url is distinct from the Jenkins URL. | ||
| Stage | stage is part of Pipeline, and used for defining a conceptually distinct subset of the entire Pipeline, for example: “Build”, “Test”, and “Deploy”, which is used by many plugins to visualize or present Jenkins Pipeline status/progress. | ||
| Step | A single task; fundamentally steps tell Jenkins what to do inside of a Pipeline or Project. | ||
| Trigger | A criteria for triggering a new Pipeline run or Build. | ||
| Update Center | Hosted inventory of plugins and plugin metadata to enable plugin installation from within Jenkins. | ||
| Upstream | A configured Pipeline or Project which triggers a separate Pipeline or Project as part of its execution. | ||
| Workspace | A disposable directory on the file system of a Node where work can be done by a Pipeline or Project. Workspaces are typically left in place after a Build or Pipeline run completes unless specific Workspace cleanup policies have been put in place on the Jenkins Master. Disposable directory on Node used as a working directory for building. It is preserved on best effort bases after build completion. |
Node/Slave
Slaves are computers that are set up to build projects for a master. Jenkins runs a separate program called “slave agent” on slaves. When slaves are registered to a master, a master starts distributing loads to slaves. Term Node is used to refer to all machine that are part of Jenkins grid, slaves and master.
Upstream project
A project can have one or several upstream projects, which means that a build for the current project may be scheduled when an upstream build is finished. Per default every stable upstream build will schedule a build in the downstream project, but there are several options and plugins which can customize this behaviour.
Downstream project
A project can have one or several downstream projects. The current project is then known as an upstream project of the downstream project. See Upstream project for what this means regarding scheduling of builds.
构建结果大概时这样的