Editing Category:DESHWAL (section)

==Training on Deshwal Live Activity Via Jenkins. Date 11 July 2025- Tetra Support Staff - TUSHAR==

{{#ev:youtube|G-XN2eiZdgQ|640}}

'''Video summary:''' "Deshwal Live Activity Via Jenkins (updated 11 July 2025) - TUSHAR" -- a focused, practical live-demo recording of the actual staging and production deployment steps introduced in Part 2, done by a different presenter (Tushar) as a refresher. Connects via a Deshwal-specific VPN profile, opens Jenkins on the staging server (port 8080), clicks the "DeshwalNew" job and "Build Now," confirms a green/successful build, and repeats the same steps against both production application servers (App1 and App2, each running its own Jenkins instance on the same default port) since the environment has two app servers requiring independent builds. After both builds succeed, verifies the deployment by logging into the staging and production site URLs directly with admin credentials to confirm no errors (e.g. database connectivity) before considering the release complete, followed by a status update to the team. Also opens up the Jenkins job's actual build configuration for a deeper explanation: it pulls from the master branch of the Deshwal Git repo using stored credentials, whichever code developers have most recently pushed; the build step is a shell script that first fixes file/folder ownership and permissions, `rsync`s the pulled code into the Apache document root while excluding an "intact" folder (config/data files that must survive each deployment and are instead separately synced back in from a preserved backup location), and runs the `rsync`/`chmod`/`chown` operations with `sudo` because the Jenkins service account needs elevated rights for those specific operations -- with a matching `sudoers` entry granting Jenkins passwordless access to exactly those three commands.