Cronjob that creates artificial traffic for new preview environments jobs. #12663
Conversation
|
I'm currently failing to configure git in the job 😭 Can you identify anything I'm during wrong? @gitpod-io/platform |
| echo "[Creating new branch|DONE] Trigger new job with preview environment" | ||
|
|
||
| echo "[Trigger new job with-preview|PHASE] Trigger new job with preview environment" | ||
| werft run github -a with-preview=true |
There was a problem hiding this comment.
I think we need to poll for the job to finish so we can delete the branch again, otherwise we'll create a ton of branches
There was a problem hiding this comment.
This is done a few other places, e.g here's how to workspace integration test jobs currently does it - we'd need something slightly different as we don't care if the preview environment failed or not, we still want to delete the branch.
Alternatively we'd need some other mechanism of deleting old branches. E.g. this job could even just start by delete all branches that match the pattern that are more than x hours old (that might be a more robust way to deal with it actually)
There was a problem hiding this comment.
I think we need to poll for the job to finish so we can delete the branch again, otherwise we'll create a ton of branches
☺️
I am creating tons of branches but I'm never pushing them to origin, so it should be fine right? I don't want the previews to stick around anyway, so it will even get cleaned up faster if the branch doesn't get pushed
There was a problem hiding this comment.
Oh nice, I'm surprised this works to be honest 😝 I guess Werft doesn't validate that the Ref actually exist (e.g. refs/heads/platform-artificial-job-7f30eab068977bb4e4d2), and it only really cares about the Revision when checking out the code
The only potential downside I can think of is if we decide to GC the VM because the branch doesn't exist. I can't remember if our heuristics were updated to keep VMs alive for at least 2h
Signed-off-by: ArthurSens <[email protected]>
ArthurSens
force-pushed
the
as/preview-artificial-traffic
branch
from
0c466b0 to
d027176
Compare
Signed-off-by: ArthurSens <[email protected]>
|
We've got an artificial job running 🙂 https://werft.gitpod-dev.com/job/gitpod-build-platform-artificial-job-7f30eab068977bb4e4d2.0 |
| werft log phase "Trigger new job with-preview" "Trigger new job with preview environment" | ||
| sudo chown -R gitpod:gitpod /workspace | ||
| git config --global user.name roboquat | ||
| git config --global user.email [email protected] |
There was a problem hiding this comment.
If we're not pushing to origin I wonder if we even need these three lines at all
There was a problem hiding this comment.
Unfortunately it is still needed :(
Description
Once ready, this PR will create a cronjob that triggers new werft jobs which, in their turn, will create new preview environments.
The final goal is that we get a little more traffic for new preview environments, so we can be more proactive when they start failing.
Related Issue(s)
Fixes #
How to test
Release Notes
Documentation
Werft options: