Better Me

The timeout of Jenkins job P I created is set to 1 hour. But its build timeout in production.

? why it timeout
Build and upload container images - (11 min in block)
Replicating DBR images - (35 min in block)

? why you didn’t know that when set timeout
when set timeout, the job doesn’t include these two steps
when include theses two steps, I checked several(5) successful nightly jobs and realized a build of P should take 20 mins, so I didn’t change the time out
when I test the job, I tested the workflow only rather than execute them because they have side effects in production

? why these successfull nightly jobs take 20 mins
most likely their REPLICATE_IMAGES set to false so they don’t contain the step Replicating DBR images
but Cut RC always set REPLICATE_IMAGES to true

? why their REPLICATE_IMAGES set to false
most versions(’‘ga’ stage) set to false

? why only workflow tested
Create Release Candidate is an independent Jenkins job, and I didn’t modify anything inside
But it turned out that Create Release Candidate is with side effect, it doesn’t switch back to master branch
So I didn’t get the bazel target I want to build

? how we could avoid
it’s fine not to test it, but you have to figure out what will happen, at least you wanted to make sure that it doesn’t have side effects on your work

if you want to figure out how long will X take, you should know what X is through code rather than get random samples, if you see X timeout 7 hour, but samples run 20 min, will you confirm that samples are representative?