[JIRA] [shiningpanda-plugin] (JENKINS-28428) Coverage 4.0 renames status.dat to status.json
Title: Message Title Olivier Mansion commented on JENKINS-28428 Re: Coverage 4.0 renames status.dat to status.json an now thanks Ned, coverage 4 also touch status.dat if it detects the JENKINS_URL environment variable to ensure backward compatibility see https://bitbucket.org/ned/coveragepy/issues/404/shiningpanda-jenkins-plugin-cant-find-html Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-27551) tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency
Title: Message Title Olivier Mansion closed an issue as Fixed Jenkins / JENKINS-27551 tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency Change By: Olivier Mansion Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-28428) Coverage 4.0 renames status.dat to status.json
Title: Message Title Olivier Mansion resolved as Fixed just release the 0.22 that checks both status.json and status.dat Jenkins / JENKINS-28428 Coverage 4.0 renames status.dat to status.json Change By: Olivier Mansion Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-27551) tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency
Title: Message Title Olivier Mansion resolved as Fixed just release the 0.22 with the latest virtualenv Jenkins / JENKINS-27551 tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency Change By: Olivier Mansion Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-28428) Coverage 4.0 renames status.dat to status.json
Title: Message Title Olivier Mansion closed an issue as Fixed Jenkins / JENKINS-28428 Coverage 4.0 renames status.dat to status.json Change By: Olivier Mansion Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-30068) Outdated version of pip used
Title: Message Title Olivier Mansion closed an issue as Fixed Jenkins / JENKINS-30068 Outdated version of pip used Change By: Olivier Mansion Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-30068) Outdated version of pip used
Title: Message Title Olivier Mansion resolved as Fixed just released the 0.22 with the latest pip version Jenkins / JENKINS-30068 Outdated version of pip used Change By: Olivier Mansion Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-27551) tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency
Title: Message Title Olivier Mansion started work on JENKINS-27551 Change By: Olivier Mansion Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-27551) tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency
Title: Message Title Olivier Mansion assigned an issue to Olivier Mansion Jenkins / JENKINS-27551 tox builder no longer working with tox 1.9.1 because pip is too old and upstream tox does not include the dependency Change By: Olivier Mansion Assignee: Olivier Mansion Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-30068) Outdated version of pip used
Title: Message Title Olivier Mansion assigned an issue to Olivier Mansion Jenkins / JENKINS-30068 Outdated version of pip used Change By: Olivier Mansion Assignee: Olivier Mansion Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-30068) Outdated version of pip used
Title: Message Title Olivier Mansion started work on JENKINS-30068 Change By: Olivier Mansion Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-28428) Coverage 4.0 renames status.dat to status.json
Title: Message Title Olivier Mansion assigned an issue to Olivier Mansion Jenkins / JENKINS-28428 Coverage 4.0 renames status.dat to status.json Change By: Olivier Mansion Assignee: Olivier Mansion Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda-plugin] (JENKINS-28428) Coverage 4.0 renames status.dat to status.json
Title: Message Title Olivier Mansion started work on JENKINS-28428 Change By: Olivier Mansion Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda] (JENKINS-22902) Cannot create virtualenv with python3.4
Olivier Mansion resolved JENKINS-22902 as Fixed Cannot create virtualenv with python3.4 just released the version 0.21 with the latest virtualenv version, this should fix the issue with python 3.4 Change By: Olivier Mansion (15/Jun/14 8:35 AM) Status: Open Resolved Resolution: Fixed 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda] (JENKINS-22902) Cannot create virtualenv with python3.4
Olivier Mansion assigned JENKINS-22902 to Olivier Mansion Cannot create virtualenv with python3.4 Change By: Olivier Mansion (15/Jun/14 8:34 AM) Assignee: Olivier Mansion 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shiningpanda] (JENKINS-18415) Can't run shining panda jobs in 1.519
Olivier Mansion resolved JENKINS-18415 as Fixed Can't run shining panda jobs in 1.519 fixed in version 0.20 Change By: Olivier Mansion (30/Jun/13 8:29 PM) Status: In Progress Resolved Resolution: Fixed 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shiningpanda] (JENKINS-18415) Can't run shining panda jobs in 1.519
Olivier Mansion assigned JENKINS-18415 to Olivier Mansion Can't run shining panda jobs in 1.519 Change By: Olivier Mansion (27/Jun/13 7:01 PM) Assignee: Olivier Mansion 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shiningpanda] (JENKINS-18415) Can't run shining panda jobs in 1.519
Olivier Mansion started work on JENKINS-18415 Can't run shining panda jobs in 1.519 Change By: Olivier Mansion (27/Jun/13 7:02 PM) Status: Open In Progress 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14188) shiningpanda python plugin doesn't allow choosing name of python executable
Olivier Mansion resolved JENKINS-14188 as Fixed shiningpanda python plugin doesn't allow choosing name of python executable This will be fixed in 0.15. You can now set the path to the Python executable in the "Home" field. Change By: Olivier Mansion (05/Nov/12 9:32 PM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14807) AbstractBuild.getEnvironment does not set EnvVars.platform and breaks EnvVars.override
Olivier Mansion created JENKINS-14807 AbstractBuild.getEnvironment does not set EnvVars.platform and breaks EnvVars.override Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Aug/12 12:21 PM Description: Hi, Since 1.472, calling AbstractBuild.getEnvironment(TaskListener) returns a EnvVars with EnvVars.platform unset. Since EnvVars.override uses EnvVars.platform (and default to UNIX style PATH separator if EnvVars.platform is null), it does not work anymore for Windows slaves. Thanks! Project: Jenkins Priority: Major Reporter: Olivier Mansion 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
[JIRA] (JENKINS-12019) Doesn't work with whitespace in the job name
Olivier Mansion resolved JENKINS-12019 as Won't Fix Doesn't work with whitespace in the job name Change By: Olivier Mansion (04/Jul/12 6:24 AM) Status: Open Resolved Resolution: Won't Fix 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
[JIRA] (JENKINS-14188) shiningpanda python plugin doesn't allow choosing name of python executable
Olivier Mansion assigned JENKINS-14188 to Olivier Mansion shiningpanda python plugin doesn't allow choosing name of python executable Change By: Olivier Mansion (04/Jul/12 6:23 AM) Assignee: Olivier Mansion 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
[JIRA] (JENKINS-14244) virtualenv builder:cannot download requirements from behind a firewall from pypi.python.org
Olivier Mansion assigned JENKINS-14244 to Olivier Mansion virtualenv builder:cannot download requirements from behind a firewall from pypi.python.org Change By: Olivier Mansion (04/Jul/12 6:23 AM) Assignee: Olivier Mansion 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
[JIRA] (JENKINS-14256) buildout builder:cannot download zc.buildout from behind a firewall from pypi.python.org
Olivier Mansion assigned JENKINS-14256 to Olivier Mansion buildout builder:cannot download zc.buildout from behind a firewall from pypi.python.org Change By: Olivier Mansion (04/Jul/12 6:23 AM) Assignee: Olivier Mansion 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
[JIRA] (JENKINS-13339) buildout builder: always use the specified config file
[ https://issues.jenkins-ci.org/browse/JENKINS-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Mansion closed JENKINS-13339. - > buildout builder: always use the specified config file > -- > > Key: JENKINS-13339 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13339 > Project: Jenkins > Issue Type: Bug > Components: shiningpanda >Affects Versions: current >Reporter: Thomas Lotze >Assignee: Olivier Mansion > > Shiningpanda's buildout builder has a configuratin option for specifying a > buildout configuration file. This file is used for bootstrapping the > buildout, but not for building it later on. The same buildout configuration > file needs to be used consistently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13339) buildout builder: always use the specified config file
[ https://issues.jenkins-ci.org/browse/JENKINS-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Mansion resolved JENKINS-13339. --- Resolution: Fixed Thanks! It's fixed in 0.11 (I just released it). > buildout builder: always use the specified config file > -- > > Key: JENKINS-13339 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13339 > Project: Jenkins > Issue Type: Bug > Components: shiningpanda >Affects Versions: current >Reporter: Thomas Lotze >Assignee: Olivier Mansion > > Shiningpanda's buildout builder has a configuratin option for specifying a > buildout configuration file. This file is used for bootstrapping the > buildout, but not for building it later on. The same buildout configuration > file needs to be used consistently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13339) buildout builder: always use the specified config file
[ https://issues.jenkins-ci.org/browse/JENKINS-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Mansion reassigned JENKINS-13339: - Assignee: Olivier Mansion > buildout builder: always use the specified config file > -- > > Key: JENKINS-13339 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13339 > Project: Jenkins > Issue Type: Bug > Components: shiningpanda >Affects Versions: current >Reporter: Thomas Lotze >Assignee: Olivier Mansion > > Shiningpanda's buildout builder has a configuratin option for specifying a > buildout configuration file. This file is used for bootstrapping the > buildout, but not for building it later on. The same buildout configuration > file needs to be used consistently. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
