You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kyle Weaver (Jira)" <ji...@apache.org> on 2022/04/01 00:10:00 UTC
[jira] [Created] (BEAM-14226) Remove standalone seed job?
Kyle Weaver created BEAM-14226:
----------------------------------
Summary: 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
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)