[
https://issues.apache.org/jira/browse/JCLOUDS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul reassigned JCLOUDS-635:
---
Assignee: Shri Javadekar
[~shrinand] Can you look into this?
Incorrect error codes when
Sajith Kariyawasam created JCLOUDS-636:
--
Summary: ComputeService sample given in README is wrong
Key: JCLOUDS-636
URL: https://issues.apache.org/jira/browse/JCLOUDS-636
Project: jclouds
Aled Sage created JCLOUDS-637:
-
Summary: CloudStack uses generateSecurityGroup=false, i.e. uses
default security group
Key: JCLOUDS-637
URL: https://issues.apache.org/jira/browse/JCLOUDS-637
Project:
Aled Sage created JCLOUDS-638:
-
Summary: CloudStackTemplateOptions.securityGroup not supported
correctly
Key: JCLOUDS-638
URL: https://issues.apache.org/jira/browse/JCLOUDS-638
Project: jclouds
Peter created JCLOUDS-639:
-
Summary: Provide methods to get the progress of a running upload
to a blobstore
Key: JCLOUDS-639
URL: https://issues.apache.org/jira/browse/JCLOUDS-639
Project: jclouds
[
https://issues.apache.org/jira/browse/JCLOUDS-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072028#comment-14072028
]
Andrew Gaul commented on JCLOUDS-639:
-
You can hack this in with a InputStream
[
https://issues.apache.org/jira/browse/JCLOUDS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072121#comment-14072121
]
Shri Javadekar commented on JCLOUDS-635:
Pull request out for review:
[jclouds-karaf-pull-requests
#81](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/81/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/50#issuecomment-49917581
This PR deprecates the methods in `RegionScopedBlobStoreContext` that do not
have `get*` prefixes. Provides API consistency. Not sure if this should be
backported...
You can merge this Pull Request by running:
git pull https://github.com/rackerlabs/jclouds-labs-openstack
[jclouds-labs-openstack-pull-requests
#326](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/326/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
[jclouds » jclouds-karaf
#1146](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1146/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1146/changes
[
https://issues.apache.org/jira/browse/JCLOUDS-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14072307#comment-14072307
]
Ignasi Barrera commented on JCLOUDS-639:
Also take into account that the
@jdaggett Sounds good and consistent with `ComputeServiceConstants`.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/402#issuecomment-49949896
[jclouds-java-7-pull-requests
#1496](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1496/)
ABORTED
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/452#issuecomment-49950114
[jclouds-java-7-pull-requests
#1495](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1495/)
ABORTED
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451#issuecomment-49950113
[jclouds-labs-openstack-pull-requests
#327](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/327/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
The documentation for this will probably keep getting updated. But this should
make it in 1.8.
Note: examples will have to be updated/created.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/111#issuecomment-49950900
This change itself looks good to me.
Let's have a separate discussion about whether to deprecate deleteContainer.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451#issuecomment-49951167
+ assertThat(api.describeJob(VAULT_NAME,
inventoryRetrievalJob).getStatusCode()).isEqualTo(JobStatus.SUCCEEDED);
+ }
+
+ @Test(groups = {live, livelong, longtest}, dependsOnMethods =
{testWaitForSucceed})
+ public void testGetJobOutput() throws IOException {
+ InputStream
No, this is my mistake, I fixed this in a previous version but I think I messed
up and lost the changes when introducing the JobStatus.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/41#issuecomment-49964221
[jclouds » jclouds-labs-aws
#1181](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1181/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-aws-pull-requests
#93](https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws-pull-requests/93/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/41#issuecomment-49964602
[jclouds-labs-aws-pull-requests
#94](https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws-pull-requests/94/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/41#issuecomment-49964827
[jclouds » jclouds-labs-aws
#1182](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1182/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
25 matches
Mail list logo
