We have a pre-build step which copies the files from an external source into our build environment.
You have to init gmail-tester on your machine, upload the credentials files to the build machine, then define the pre-build step.
Another solution is to have templates of the credentials files and to inject the tokens from env. variables. This solution requires some coding/scripting.
How do i extend the interval of the token? as far as i understood the token will not refresh if older then 24h, so injecting the old token from .env doesnt solve our problem, correct?
Hi Marco,
We have a pre-build step which copies the files from an external source into our build environment.
You have to init gmail-tester on your machine, upload the credentials files to the build machine, then define the pre-build step.
Another solution is to have templates of the credentials files and to inject the tokens from env. variables. This solution requires some coding/scripting.
How do i extend the interval of the token? as far as i understood the token will not refresh if older then 24h, so injecting the old token from .env doesnt solve our problem, correct?
Thanks for your quick response Lev!
I think my solution corresponds to your second suggestion and works well so far. Thank you!