[jira] [Commented] (BEAM-14224) run postcommits continuously on release branch

["Kyle Weaver (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-14224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519173#comment-17519173 ] 

Kyle Weaver commented on BEAM-14224:
------------------------------------

I tried to set this up, but I had difficulty with the Jenkins job DSL. We currently have a job parameter "sha1" which determines the git commit the job will run on, which defaults to master. I was thinking we could set up a "prerelease" version of all precommits and postcommits that set sha1 to the release branch (e.g. release-2.38.0), but it's tricky to change the default value for parameters. As far as I can tell, the job DSL doesn't provide an API to mutate existing parameters, so I think we'd have to manipulate the XML tree (ugh) generated by the job DSL.

> 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
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> 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)