[
https://issues.apache.org/jira/browse/BEAM-6547?focusedWorklogId=192920&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-192920
]
ASF GitHub Bot logged work on BEAM-6547:
----------------------------------------
Author: ASF GitHub Bot
Created on: 31/Jan/19 16:45
Start Date: 31/Jan/19 16:45
Worklog Time Spent: 10m
Work Description: swegner commented on issue #7668: [BEAM-6547] Release
automation: use virtualenv; use SSH URL
URL: https://github.com/apache/beam/pull/7668#issuecomment-459416023
> later, we should just contribute a trivial change to pygradle to make it
doable in gradle so our gradle virtualenv can be used
Our python build isn't currently using pygradle, right? Do you know the
context on whether it was considered when we migrated the build and why we
didn't choose it? /cc @udim
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 192920)
Time Spent: 0.5h (was: 20m)
> Use virtualenv to peform release Python builds
> ----------------------------------------------
>
> Key: BEAM-6547
> URL: https://issues.apache.org/jira/browse/BEAM-6547
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The cut_release_candidate script does not use a virtualenv to build the
> Python release zip. It should.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
