Glossary
Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.
Showing 7 of 7 matching “Deploy”
A change that makes existing valid usage stop working.
Removing a field, renaming one, making an optional input required, or changing a type. The problem is that you often cannot fix it by deploying again, because the broken caller is a phone app or a script you do not control.
See also Versioning, Deprecation, Contract
Turning source code into something runnable.
Compiling, bundling and optimising your source into deployable output. A failed build is good news, because the pipeline caught a problem before any user did.
Automation that tests and ships your changes.
Continuous integration runs checks on every change; continuous delivery deploys the ones that pass. The value is that the deploy path is exercised constantly rather than only on the day it matters.
See also Build, Deploy, Preview deployment
Making new code live.
Build, upload, switch traffic, verify. During the switch two versions run simultaneously, which is why changes must be able to coexist with their predecessor for a few seconds.
A temporary live copy of a proposed change.
A working URL for a change before it is accepted, so it can be clicked rather than described. Also means the deploy path is exercised constantly rather than only when it is scary.
See also Environment, CI/CD
Putting the previous version back.
The cheapest available response to a bad deploy and the correct first move in most incidents. Restores your code, not your data: deleted rows and sent emails do not come back.
A process that pulls jobs off a queue and does them.
Separate from your web app, so you can deploy one without interrupting the other and add more workers to drain a backlog faster.
See also Queue, Background job