[CI]: Implement weekly builds on DR site #269
Conversation
vialogi
force-pushed
the
HPCINFRA-2918_weekly_dr_build
branch
30 times, most recently
from
c627cd7 to
ca8cf63
Compare
vialogi
force-pushed
the
HPCINFRA-2918_weekly_dr_build
branch
3 times, most recently
from
1f765a3 to
25707dd
Compare
|
bot:retest |
1 similar comment
|
bot:retest |
.ci/pipeline/dr_weekly_jjb.yaml
Outdated
| - string: | ||
| name: "release_folder" | ||
| default: "/tmp" | ||
| description: "Folder to release packages into. For manual tests use /auto/sw/release/sw_acceleration/xlio/dr/weekly" |
There was a problem hiding this comment.
Didnt we say we will use /tmp ?
There was a problem hiding this comment.
We use /tmp here by default. I left the possibility to use non-default path for testing purposes, e.g NFS testing in DR
vialogi
force-pushed
the
HPCINFRA-2918_weekly_dr_build
branch
5 times, most recently
from
c157992 to
363b86c
Compare
.ci/pipeline/dr_weekly_jjb.yaml
Outdated
| name: "MAIL_TO" | ||
| default: "[email protected]" | ||
| description: "Email address to send the report to" | ||
| # triggers: |
There was a problem hiding this comment.
we need to uncomment this before final merge
There was a problem hiding this comment.
Yes, I moved it to a TEST commit which is to be removed before merge
vialogi
force-pushed
the
HPCINFRA-2918_weekly_dr_build
branch
5 times, most recently
from
3e3d764 to
c0adafd
Compare
.ci/pipeline/dr_weekly.yaml
Outdated
| string(name: 'release_tag', value: RELEASE_TAG), | ||
| string(name: 'release_folder', value: "${release_folder}"), | ||
| string(name: 'notification_email', value: MAIL_TO), | ||
| string(name: 'sha1', value: sha1) |
There was a problem hiding this comment.
Where do you set/define this parameter? this should point to vNext
There was a problem hiding this comment.
We need sha1 to be passed to the upstream job, otherwise, it checks out from a commit associated with the 'release_tag' and it doesn't include changes related to e.g. GeoDNS URL for harbor. So - yes, I added it both in matrix file and jjb, pointing by default to vNext
vialogi
force-pushed
the
HPCINFRA-2918_weekly_dr_build
branch
5 times, most recently
from
938df10 to
6730307
Compare
We add the "weekly_launcher" job which stays unchanged on RD site and performs schedulled runs once a week, triggering the release Job. Issue: HPCINFRA-2918 Signed-off-by: Viacheslav Login <[email protected]>
vialogi
force-pushed
the
HPCINFRA-2918_weekly_dr_build
branch
from
6730307 to
205c168
Compare
Description
This change implements weekly builds on the DR site
What
weekly_laucher Job that stays unchanged and triggers the release job on the DR site
Why ?
We need to do periodic checks of DR Jenkins instance and Infra entities by running CI workloads
How ?
weekly_laucher scheduled job
Change type
What kind of change does this PR introduce?
Check list