![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
shiningpanda-plugin |
|
Created:
|
23/Mar/15 5:53 PM
|
|
Description:
|
See https://bitbucket.org/hpk42/tox/issue/228/tox-doesnt-work-with-older-pip-versions for the description of the breakage.
Two things that can be done:
- Bump the version of virtualenv and pip used in the plugin (should be done anyway IMO)
- Allow to specify the exact version of tox to use - and/or allow the usage of system tox
This change basically renders our tox builds unusable until upstream fixes their problem, which is not great in an environment where all the versions are usually fixed. It would be very very nice to allow the system python (i.e. the python that is going to be used by the tox builder) to be used for all these packages as that would put the burden of maintaining their versions not on the plugin author but on the user of jenkins.
Happy to create a pull request if that's what's necessary ![]()
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Vladimir Lu
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
