[
https://issues.apache.org/jira/browse/BEAM-14226?focusedWorklogId=753718&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-753718
]
ASF GitHub Bot logged work on BEAM-14226:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/22 21:56
Start Date: 06/Apr/22 21:56
Worklog Time Spent: 10m
Work Description: kennknowles commented on PR #17239:
URL: https://github.com/apache/beam/pull/17239#issuecomment-1090848197
We had cases where the seed job recreated itself and the new seed job was
broken. If the seed job still recreates itself and a bug in the groovy could
break it, we probably still want some back up plan. Perhaps the seed job just
doesn't create itself any more? That would probably be smart.
Issue Time Tracking
-------------------
Worklog Id: (was: 753718)
Time Spent: 0.5h (was: 20m)
> Remove standalone seed job?
> ---------------------------
>
> Key: BEAM-14226
> URL: https://issues.apache.org/jira/browse/BEAM-14226
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Kyle Weaver
> Priority: P3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I'm not sure what the historical reason for having two separate seed jobs is,
> but it looks like today the two are almost identical, so we can probably
> delete one of them.
> $ diff .test-infra/jenkins/job_seed_standalone.groovy
> .test-infra/jenkins/job_00_seed.groovy
> 23c23
> < job('beam_SeedJob_Standalone') {
> ---
> > job('beam_SeedJob') {
> 77c77
> < cron('0 */5 * * *')
> ---
> > cron('H */6 * * *')
> 85c85
> < triggerPhrase('Run Standalone Seed Job')
> ---
> > triggerPhrase('Run Seed Job')
> 90c90
> < context("Jenkins: Standalone Seed Job")
> ---
> > context("Jenkins: Seed Job")
> 110c110
> < python3.8 -m venv ve3 && source ./ve3/bin/activate &&
> ---
> > python3.8 -m venv ve3 && source ve3/bin/activate &&
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
