Category:DESHWAL: Difference between revisions

Training on Deshwal Project Part 1. Dated 01 JULY 2025 - Tetra Support Staff - TUSHAR

<HTML5video type="youtube" width="640" height="480" autoplay="false">Sjk7CqbGVWk</HTML5video>

Training on Deshwal Project Part 2. Dated 02 JULY 2025 - Tetra Support Staff - TUSHAR

<HTML5video type="youtube" width="640" height="480" autoplay="false">adYZO20f4rc</HTML5video>

Deshwal live activity from dev to staging-sify

        http://172.16.20.21:8080
        username - Tushar
        password - Kalyan123tush@r
        login
       click DeshwalNew
       click Build Now

Deshwal live activity from staging-sify to prod-sify

        app1
        http://172.16.20.16:8080
        username - Tushar
        password - Kalyan123tush@r
        login
        click DeshwalNew
        click Build Now

        app2
        http://172.16.20.17:8080
        username - Tushar
        password - Kalyan123tush@r
        login
        click DeshwalNew
        click Build Now

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

<HTML5video type="youtube" width="640" height="480" autoplay="false">G-XN2eiZdgQ</HTML5video>

Deshwal code revert activity and daily working process from developer side.

======================================================================

ONE TIME CHANGES : changes done on Git and Github : git reset --soft <commit-id-previous-version> git checkout -b production git checkout -b staging git reset --soft <commit-id-latest-version>

======================================================================

REGULAR CHANGES :

Work need to do to Deepika:

======================================================================

When code is mature on development environment and tested in development, Then need to merge code to staging branch. git checkout staging git merge master NOTE : effect of this will be code will get deployed in staging server. NOTE : NO NEED TO DO ANY WORK TO SERVICE TEAM.

=====================================================================

When code is mature on staging environment and tested in staging, Then need to merge code to production branch. git checkout production git merge staging

NOTE : effect of this will be code will be get deployed in production server NOTE : NO NEED TO DO ANY WORK TO SERVICE TEAM.