You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2015/07/01 22:29:04 UTC

[jira] [Commented] (JCLOUDS-953) jclouds should run integration tests on pull requests

    [ https://issues.apache.org/jira/browse/JCLOUDS-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610957#comment-14610957 ] 

Andrew Gaul commented on JCLOUDS-953:
-------------------------------------

Let's start with transient since this will give us some coverage of integration test code paths.  I will enable this in CloudBees.

> jclouds should run integration tests on pull requests
> -----------------------------------------------------
>
>                 Key: JCLOUDS-953
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-953
>             Project: jclouds
>          Issue Type: Bug
>            Reporter: Timur Alperovich
>            Assignee: Andrew Gaul
>
> After submitting changes to add a prefix option to the blob store API, I noticed that a few of the integration tests were failing. It would be great if the jclouds PR verification involved running integration tests. At least for the transient and filesystem blob stores this should be easy to do. For S3, jclouds could possibly use the S3proxy. For openstack-swift, swiftproxy would do the same.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)