You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "David Sabater (JIRA)" <ji...@apache.org> on 2018/05/25 15:38:00 UTC
[jira] [Commented] (BEAM-4113) Periodic cleanup and setup of Python
environment on Jenkins machines
[ https://issues.apache.org/jira/browse/BEAM-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16490879#comment-16490879 ]
David Sabater commented on BEAM-4113:
-------------------------------------
What about using the below Gradle extension so local and remote tests in Jenkins are consistent?
[https://github.com/JetBrains/gradle-python-envs]
> Periodic cleanup and setup of Python environment on Jenkins machines
> --------------------------------------------------------------------
>
> Key: BEAM-4113
> URL: https://issues.apache.org/jira/browse/BEAM-4113
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Udi Meiri
> Assignee: Jason Kuster
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Instead of having Python testing scripts tidy up the environment every time they run, let's have a single script that runs once per day and does:
> # Check if pip is installed under ~/.local and is the expected version. If not, install the correct version.
> # Same as above, but for virtualenv.
> # Print a list of packages installed under ~/.local.
> # Optional: Uninstall any unexpected packages under ~/.local. For example, apache-beam shouldn't be installed under ~/.local, since 2 concurrent tests on the same machine will attempt to install to the same location.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)