You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Mark Liu (Jira)" <ji...@apache.org> on 2019/11/13 20:14:00 UTC

[jira] [Resolved] (BEAM-8079) Move verify_release_build.sh to Jenkins job

     [ https://issues.apache.org/jira/browse/BEAM-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Liu resolved BEAM-8079.
----------------------------
    Fix Version/s: Not applicable
       Resolution: Done

> Move verify_release_build.sh to Jenkins job
> -------------------------------------------
>
>                 Key: BEAM-8079
>                 URL: https://issues.apache.org/jira/browse/BEAM-8079
>             Project: Beam
>          Issue Type: Sub-task
>          Components: build-system
>            Reporter: Mark Liu
>            Assignee: Mark Liu
>            Priority: Major
>             Fix For: Not applicable
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> verify_release_build.sh is used for validation after release branch is cut. Basically it does two things: 1. verify Gradle build with -PisRelease turned on. 2. create a PR and run all PostCommit jobs against release branch. However, release manager got many painpoints when running this script:
> 1. A lot of environment setup and some of tooling install easily broke the script.
> 2. Running Gradle build locally too extremely long time.
> 3. Auto-pr-creation (use hub) doesn't work.
> We can move Gradle build to Jenkins in order to get rid of environment setup work.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)