Hi all,
Our DevOps team is facing a problem that they take time in mapping the changes required for any release by checking issues and collect that manually , what they really look for any issue is:
1. What parts will need to pull latest changes to.
2. Configuration changes.
3. Steps of applying the release changes:
4. Sometimes it is something like:
a) Do a DB migration.
b) Release device server and restart it.
c) Flush server data.
d) then, and only once all before is done, release lambda changes.
e) restart push , but not changes to pull there..
They need to locate all above in one place that has a clear release structure instead of taking time in checking issues.
We are using JIRA server and we look to have this solved using it or if you have any different/alternative idea please share with us..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.