beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (BEAM-3255) Update release process to use Gradle
Date Fri, 06 Apr 2018 21:08:00 GMT

     [ https://issues.apache.org/jira/browse/BEAM-3255?focusedWorklogId=88613&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-88613
]

ASF GitHub Bot logged work on BEAM-3255:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Apr/18 21:07
            Start Date: 06/Apr/18 21:07
    Worklog Time Spent: 10m 
      Work Description: swegner opened a new pull request #5048: [BEAM-3255] Updates to support
the release process via Gradle
URL: https://github.com/apache/beam/pull/5048
 
 
   This merges many changes from our Gradle fixit week for publishing and validating releases
from Gradle.
   
   ------------------------
   
   Follow this checklist to help us incorporate your contribution quickly and easily:
   
    - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/projects/BEAM/issues/)
filed for the change (usually before you start working on it).  Trivial changes like typos
do not require a JIRA issue.  Your pull request should address just this issue, without pulling
in other changes.
    - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue.
    - [ ] Write a pull request description that is detailed enough to understand:
      - [ ] What the pull request does
      - [ ] Why it does it
      - [ ] How it does it
      - [ ] Why this approach
    - [ ] Each commit in the pull request should have a meaningful subject line and body.
    - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
    - [ ] If this contribution is large, please file an Apache [Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf).
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 88613)
            Time Spent: 10m
    Remaining Estimate: 0h

> Update release process to use Gradle
> ------------------------------------
>
>                 Key: BEAM-3255
>                 URL: https://issues.apache.org/jira/browse/BEAM-3255
>             Project: Beam
>          Issue Type: Sub-task
>          Components: build-system
>            Reporter: Luke Cwik
>            Assignee: Alan Myrvold
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This task is about configuring Gradle to generate pom's and artifacts required to perform
a release and update the nightly release snapshot Jenkins jobs found here https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_beam_Release_NightlySnapshot.groovy
> We will also require some integration tests to run against the released nightly snapshot
artifacts to ensure that what was built is valid.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message