Hello everyone, I have a question about your day-to-day work. I work as a software engineer, and at my company, we have an internal tool that facilitates the release process for the features we develop, making it easier to deploy features to production. This makes it far from the tools or methods that exist today outside my company. What is the release process like at your companies or in your daily with your projects? From developing a feature locally to deploying it on AWS or GCP?
How is the release process that you use in your work or personal projects?
Created
Active
Viewed
143 times
Renzo
Renzo
- 99
- 6
3 replies
Oldest first — sorts top-level replies by their creation dates, with the oldest at the top.
Newest first — sorts top-level replies by their creation dates, with the newest at the top.
Latest activity — sorts top-level replies with recent threaded replies or edits at the top.
Highest score — sorts top-level replies by their total votes (highest first).
Your sorting method preferences will be saved.
Sorted by:
R.Medhi
R.Medhi
- 55
- 7
Well, to start with I make small projects on GCP specifically using GAS(Google AppScript). What I do generally is deploy the project once I'm happy with the changes from GAS only, it has a feature to maintain versions. I also maintain the changes in Github using clasp. I hope it helps you.
For my small projects on GCP using Google Apps Script (GAS):
I deploy the project once I’m happy with the changes using GAS’s versioning feature. I also maintain the changes in GitHub with `clasp` to keep track of versions and updates.
This captures your approach and might inspire others with similar tools or practices!
I have a Fabric 2 deployment tool which has generalised functions for deploying code (Python) and rsyncing config from an on premise server. This along with scripts for each kind of operation drives deployment, updating servers including load balancer and CouchDB stores.