You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 18:42:39 UTC

[GitHub] [beam] kennknowles opened a new issue, #18520: Provide a signal of a release branch health.

kennknowles opened a new issue, #18520:
URL: https://github.com/apache/beam/issues/18520

   It appears that only committers can trigger an invocation of a Jenkins test suite on a branch, such as release branch. This is inconvenient. In a situation, when I send a PR to a branch and the precommit tests don't pass, I cannot easily identify whether my PR is at fault, or the branch was already unhealthy.
    
   Also, if the release branch for whatever reason becomes unhealthy, we should be able to identify the breakage once it manifests. We have postcommit test runs on master branch. I may be wrong, but I think we don't have them configured for the release branches. 
   
   Imported from Jira [BEAM-3062](https://issues.apache.org/jira/browse/BEAM-3062). Original Jira may contain additional context.
   Reported by: tvalentyn.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [beam] tvalentyn closed issue #18520: Provide a signal of a release branch health.

Posted by GitBox <gi...@apache.org>.
tvalentyn closed issue #18520: Provide a signal of a release branch health.
URL: https://github.com/apache/beam/issues/18520


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org