Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Category:DESHWAL
(section)
Category
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Training on Oxypc CICD Deployment KT DESHWAL. Dated 08 JULY 2026 - Tetra Support Staff - PRASHANT== {{#ev:youtube|VjT5H3VY8wA|640}} '''Video summary:''' "Oxypc CICD Deployment KT DESHWAL" -- an English-language KT session on the CI/CD pipeline built for OxyPC, a separate PHP (Yii2 framework) project deployed to `/var/www/html/oxypc`, hosted on GitHub and deployed via Jenkins (chosen over alternatives like GitHub Actions/GitLab CI). Walks through the Jenkins pipeline stage by stage: a checkout-from-SCM stage using stored Git credentials against the main branch (built using Jenkins' "generate pipeline syntax" helper); a code-review/validation stage that runs a PHP lint/syntax check (`php -l`-style check) -- currently commented out on the development pipeline at the developers' request, but still active on staging, demonstrated live by intentionally introducing a PHP parse error and showing the check catch it; a backup stage that snapshots the current deployed code into a dedicated backup directory under `/opt` with its own retention policy before the new code is deployed; the actual deployment stage that syncs the checked-out code to the live path; and a post-deployment stage that emails a designated group (the presenter plus two others) automatically if the build fails. Explains the GitHub webhook integration that makes deployment fully automatic: a developer push to GitHub fires a webhook that Jenkins listens for, which kicks off the entire pipeline (checkout -> validate -> backup -> deploy -> notify) without manual triggering -- noting the presenter doesn't have direct access/credentials to the GitHub webhook config itself (owned by the client's dev team) but can describe the flow. Closes by briefly showing a `sudoers` entry added for the Jenkins user to allow the specific commands the pipeline needs without a password prompt.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)