Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / jenkinsci/pyenv-pipeline-plugin issues and pull requests

#50 - plugin not reglecting

Issue - State: open - Opened by AbhineshPatel about 1 year ago

#49 - Error while creating virtualenv

Issue - State: open - Opened by menvol3 almost 2 years ago

#48 - persistent created venv between different steps

Issue - State: open - Opened by msegura501 almost 2 years ago
Labels: enhancement

#46 - Create virtualenvs via '-m venv' not '-m virtualenv'

Issue - State: open - Opened by tuukkamustonen about 3 years ago - 1 comment

#45 - Support Python3 venv arguments

Issue - State: open - Opened by ian-twilightcoder about 3 years ago - 1 comment

#44 - Python virtual environment isn't "activated" in kubernetes containers

Issue - State: open - Opened by Cetlan about 3 years ago - 5 comments
Labels: bug

#43 - Can't find python exe file

Issue - State: open - Opened by braunman almost 4 years ago

#42 - [JENKINS-62484] Fix env vars handling

Pull Request - State: open - Opened by framillien over 4 years ago - 2 comments

#41 - Unable to find executable in PATH when using the plugin on Windows.

Issue - State: open - Opened by Proksima over 4 years ago - 2 comments

#40 - Try working around setuptools version limits

Pull Request - State: open - Opened by romuald over 4 years ago - 1 comment

#39 - Add option --no-setuptools/--no-pip/--no-wheel

Issue - State: open - Opened by grigouze over 4 years ago - 1 comment

#38 - [Windows 10] Trailing \r in VIRTUAL_ENV

Issue - State: open - Opened by lystor over 4 years ago - 2 comments

#37 - Plugin can fail to use the correct environment when calling the binary python3

Issue - State: open - Opened by Porkepix over 4 years ago - 3 comments

#36 - pyenv-pipeline-plugin-33 Odd pathing for created virtualenv

Pull Request - State: closed - Opened by cstarner about 5 years ago

#35 - Add tool path translation

Pull Request - State: closed - Opened by vctgross over 5 years ago - 1 comment

#34 - Pre-existing venv not applied on node connected via JNLP agent

Issue - State: closed - Opened by eskuat over 5 years ago - 5 comments

#33 - Odd pathing for created virtualenv

Issue - State: closed - Opened by ryanbuhl-auro over 5 years ago - 3 comments

#32 - pyenv-pipeline-plugin-26 Virtual Env doesn't activate with spaces in …

Pull Request - State: closed - Opened by cstarner over 5 years ago

#31 - Unable to migrate out of pyenv-pipeline-plugin 1.0.4 to 2.0.0 #21

Pull Request - State: closed - Opened by cstarner over 5 years ago

#30 - Issue 16

Pull Request - State: closed - Opened by cstarner over 5 years ago

#29 - Modifications to run on python 3.7

Pull Request - State: closed - Opened by gsumalo over 5 years ago - 1 comment

#28 - Commands are not always run in virtualenv

Issue - State: closed - Opened by tsvi over 5 years ago - 4 comments
Labels: bug

#27 - Unable to start virtualenv - fails when downloading setup tools pip wheel

Issue - State: closed - Opened by amuresia almost 6 years ago - 2 comments
Labels: bug

#26 - Virtual Env doesn't activate with spaces in the job path

Issue - State: closed - Opened by callum-george almost 6 years ago - 3 comments
Labels: bug

#25 - Issue 21

Pull Request - State: closed - Opened by cstarner about 6 years ago

#24 - Unable to migrate on windows to 2.0.0

Issue - State: closed - Opened by climblinne about 6 years ago - 15 comments
Labels: bug

#23 - No such DSL method 'pysh' found among steps with version 2.0.0

Issue - State: closed - Opened by ollecoffee about 6 years ago - 1 comment

#22 - Replacement for PYENVPIPELINE_VIRTUALENV_RELATIVE_DIRECTORY in 2.0.0

Issue - State: closed - Opened by mahanhz about 6 years ago - 5 comments

#21 - Unable to migrate out of pyenv-pipeline-plugin 1.0.4 to 2.0.0

Issue - State: closed - Opened by emman27 about 6 years ago - 7 comments
Labels: bug

#20 - pyenv-pipeline-plugin-17 Incorrect drive letter substitution on Windows

Pull Request - State: closed - Opened by cstarner about 6 years ago

#19 - Issue #6

Pull Request - State: closed - Opened by cstarner about 6 years ago

#18 - Error while creating virtualenv with custom python installation

Issue - State: closed - Opened by gyzpunk about 6 years ago - 2 comments

#17 - Incorrect drive letter substitution on Windows

Issue - State: closed - Opened by climblinne over 6 years ago - 1 comment

#16 - Support for unmanaged, pre-existing virtualenvs?

Issue - State: closed - Opened by gregsymons over 6 years ago - 9 comments
Labels: enhancement

#15 - pysh ignores newline

Issue - State: closed - Opened by bezda over 6 years ago - 2 comments

#14 - Spaces in job name cause Shebang PATH problem

Issue - State: closed - Opened by robjsch over 6 years ago - 1 comment

#13 - [JENKINS-48276] Getting the ShiningPanda Python location doesn't work in Windows

Pull Request - State: closed - Opened by cstarner almost 7 years ago - 1 comment

#12 - Getting ShiningPanda Python location does not work on Windows

Issue - State: closed - Opened by torbjoernk almost 7 years ago - 2 comments
Labels: bug

#11 - "No such file or directory" while executing pysh command withing withPythonEnv block

Issue - State: closed - Opened by avovsya almost 7 years ago - 2 comments

#10 - Need an option to start with clean new Env every build

Issue - State: open - Opened by tal5ab almost 7 years ago - 5 comments
Labels: enhancement

#9 - Why does this default to installing tox?

Issue - State: closed - Opened by ilovemysillybanana almost 7 years ago - 5 comments

#7 - Virtualenv with a specific Python version

Issue - State: closed - Opened by LJBD almost 7 years ago - 1 comment

#6 - Can `withPythonEnv` block also affect `sh` steps?

Issue - State: closed - Opened by r4v5 almost 7 years ago - 5 comments

#5 - .pyenv-python.exe/bin/activate: No such file or directory on Windows

Issue - State: closed - Opened by jitbasemartin almost 7 years ago - 2 comments

#4 - Fixes #3

Pull Request - State: closed - Opened by cstarner almost 7 years ago

#3 - "No such file or directory" for any pysh when Jenkins project name contain spaces

Issue - State: closed - Opened by tal5ab almost 7 years ago - 1 comment
Labels: bug

#2 - Fixes #1

Pull Request - State: closed - Opened by cstarner almost 7 years ago

#1 - Specifying python3 doesn't actually use python3

Issue - State: closed - Opened by cstarner almost 7 years ago - 2 comments
Labels: bug