-
Notifications
You must be signed in to change notification settings - Fork 31
Glossary
Rajan, Sarat edited this page Aug 22, 2019
·
1 revision
Below are some terms that would be seen across all Wiki pages for POET.
Term | Definition |
---|---|
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. |
Bootstrapping | To get started with, mainly to make something up & running. |
Build | Result of a single execution of a Project. |
CI/CD | Continuous Integration/Continuous Development |
Commit | A single point in the Git history; the entire history of a project is represented as a set of interrelated commits. |
Container | A runtime-instance of a docker image. |
Credentials | Mainly a token or authentication used to access an external/internal services like Slack, SCCS, etc. |
Deploy | To host an artifact or application itself onto platforms like on-prem or cloud. |
Docker | A platform for developers and sysadmins to develop, ship, and run applications. |
Docker Compose | A tool for defining and running complex applications with Docker, mainly for multi-container application in a single file. |
Environment | The tag under which all the Environment variables are to be defined for a Pipeline, for a Step or Global level. |
Jenkinsfile | This is what bootstraps Jenkins to run POET pipeline code |
Pipeline | A user-defined model of a continuous delivery pipeline, for more read the Pipeline chapter in this handbook. |
PipelineState | The basic information about the execution status, steps involved, commands and images involved for a Pipeline. |
pipeline.yml | This is the pipeline definition file for POET. |
Pipeline Engine | Mainly the CI/CD tool used for setting up the pipeline, mostly Jenkins (in case of POET). |
Pipeline header | Mandatory header required for every pipeline.yml file. |
Plugin | Mainly a container/package that comes out of the box from Docker Registry used,for steps like Build, Deploy, etc. without needing to make any tweaks. Interchangeably used with Step-Container |
Repository | Code-base for a pipeline or templates mainly on GitHub |
SCCS | Spring Cloud Config Server that provides server and client-side support for externalized configuration in a distributed system. |
Schema | A representation of a plan or theory in the form of an outline or model. |
secrets | Interchangeably used with Credentials |
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 Pipeline Engine what to do inside of aPipeline or Project. |
Step-Container | Interchangeably used with Plugin |
Template | A yaml with pre-defined step or collection of steps grouped together, mostly for reusability. |
Vault | Secure storage for access to tokens, passwords,certificates, encryption keys for protecting secrets. |
Webhook | A mechanism where by a,server-side application can notify a client-side application when a new,event (that the client-side application might be interested in) has,occurred on the server. |
Workspace | A disposable directory on the file system of a Node, where work can be done by a Pipeline or Project. |