[
https://issues.apache.org/jira/browse/BEAM-8079?focusedWorklogId=302051&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-302051
]
ASF GitHub Bot logged work on BEAM-8079:
----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Aug/19 14:57
Start Date: 27/Aug/19 14:57
Worklog Time Spent: 10m
Work Description: markflyhigh commented on pull request #9434:
[BEAM-8079] Move release Gradle build to a Jenkins job (Part - 2)
URL: https://github.com/apache/beam/pull/9434
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 302051)
Time Spent: 2.5h (was: 2h 20m)
> 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
> 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.2#803003)
