![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
So, kind of exhausted again.
In the morning, there was no trace of good deployment to staging. As a result, I finished my library PR, sent it for review; later Karen asked to update the README, which I did. Approved, merged. Now I'll have to create a Jenkins job for that project. That's tomorrow.
Since there was nothing much to do, I've also updated the project that contains our scripts, adding several of my own scripts, sent it for review.
Later today it was disclosed that now jenkins deploys somewhere else. To another pod, or whatever it's called. Another k8s. And I'll have to update this and that in my scripts, to go to something like "server23".
I was clueless; and Chris was also telling me that my service's calls to config server were failing.
Eventually, by the end of the day, I got all the urls, configs, server names, etc, to put into my script. Discovered that actually the deployment succeeded yesterday, but Swathi only disclosed the deployment pod name, or whatever, today. Ok, it's morning over there.
So, everything works for me, and since it's already Thursday evening, rushing with deployment to prod makes no sense (we don't deploy on Fridays), and I have a good slot of time to do performance tests, stress tests, etc. Will just write some code for that, and see how it works. Have to pummel it to get tokens generated for given signing keys, from the real service on staging. We do have some performance tests, but not many.
Tomorrow; I'll have to sleep on it.
Tonight I'd rather go watch "Les Trois Mousquetaires" in our cinéma.
In the morning, there was no trace of good deployment to staging. As a result, I finished my library PR, sent it for review; later Karen asked to update the README, which I did. Approved, merged. Now I'll have to create a Jenkins job for that project. That's tomorrow.
Since there was nothing much to do, I've also updated the project that contains our scripts, adding several of my own scripts, sent it for review.
Later today it was disclosed that now jenkins deploys somewhere else. To another pod, or whatever it's called. Another k8s. And I'll have to update this and that in my scripts, to go to something like "server23".
I was clueless; and Chris was also telling me that my service's calls to config server were failing.
Eventually, by the end of the day, I got all the urls, configs, server names, etc, to put into my script. Discovered that actually the deployment succeeded yesterday, but Swathi only disclosed the deployment pod name, or whatever, today. Ok, it's morning over there.
So, everything works for me, and since it's already Thursday evening, rushing with deployment to prod makes no sense (we don't deploy on Fridays), and I have a good slot of time to do performance tests, stress tests, etc. Will just write some code for that, and see how it works. Have to pummel it to get tokens generated for given signing keys, from the real service on staging. We do have some performance tests, but not many.
Tomorrow; I'll have to sleep on it.
Tonight I'd rather go watch "Les Trois Mousquetaires" in our cinéma.
