[
https://issues.apache.org/jira/browse/BEAM-14224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515624#comment-17515624
]
Kyle Weaver commented on BEAM-14224:
------------------------------------
There are a few different ways we could do this. Ideally we would have separate
jobs so that we could rely solely on Jenkins' scheduling and UI. Postcommits
are configured to run on the master branch currently. We could create a variant
that runs on the release branch instead.
https://github.com/apache/beam/blob/4dddaf9c3d70b5b858c16265abee4cdbf0c72631/.test-infra/jenkins/CommonJobProperties.groovy#L37
> run postcommits continuously on release branch
> ----------------------------------------------
>
> Key: BEAM-14224
> URL: https://issues.apache.org/jira/browse/BEAM-14224
> Project: Beam
> Issue Type: Improvement
> Components: release, testing
> Reporter: Kyle Weaver
> Priority: P2
>
> i.e. running them continuously on the release branch while the release is
> open, instead of manually triggering them. The release manager would spend
> less time pressing buttons, and it'd provide a better signal, helping us
> differentiate between flakes and hard failures.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
