[
https://issues.apache.org/jira/browse/JCLOUDS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070016#comment-14070016
]
Chris Custine commented on JCLOUDS-343:
---
Please try with jclouds 1.8.0-SNAPSHOT or
[
https://issues.apache.org/jira/browse/JCLOUDS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070025#comment-14070025
]
Chris Custine commented on JCLOUDS-337:
---
I tried, but was unable to reproduce this.
[
https://issues.apache.org/jira/browse/JCLOUDS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070058#comment-14070058
]
Chris Custine commented on JCLOUDS-268:
---
The new hpcloud-blockstorage provider uses
Chris Custine created JCLOUDS-633:
-
Summary: Support passing bearer token directly for OAuth2
Key: JCLOUDS-633
URL: https://issues.apache.org/jira/browse/JCLOUDS-633
Project: jclouds
Issue
https://issues.apache.org/jira/browse/JCLOUDS-633
Work in progress, I will be adding some tests soon but wanted to expose this
for review.
You can merge this Pull Request by running:
git pull https://github.com/ccustine/jclouds-labs-google features/oauthtoken
Or you can view, comment on it,
[
https://issues.apache.org/jira/browse/JCLOUDS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070065#comment-14070065
]
Chris Custine commented on JCLOUDS-633:
---
Work in progress is at
[jclouds » jclouds-labs-google
#1150](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1150/)
UNSTABLE
Looks like there's a problem with this pull request
[(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-labs-google/1150/changes
[
https://issues.apache.org/jira/browse/JCLOUDS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070058#comment-14070058
]
Chris Custine edited comment on JCLOUDS-268 at 7/22/14 9:39 AM:
[jclouds-labs-google-pull-requests
#98](https://jclouds.ci.cloudbees.com/job/jclouds-labs-google-pull-requests/98/)
UNSTABLE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
I forgot to update the googleblockstorage part, and this is causing the build
failures. I will update the other provider tomorrow.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/34#issuecomment-49717932
@everett-toews Seems like a good start. I spent some time trying to figure out
if some of that can be automated during testing, but didn't look too promising.
My other idea is trying to use an admin account during testing.
---
Reply to this email directly or view it on GitHub:
Uncovered by 370194b
See #444 and especially [this
comment](https://github.com/jclouds/jclouds/pull/444#issuecomment-49675241)
Results on Windows (Java 6):
```
...\jclouds\jcloudsgt; mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T12:37:52-05:00)
Maven home:
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1151/
I know the deprecation comment says to be removed in 1.7 but can you hold off
on merging this until just before 2.0 so it's more in line with semver?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/448#issuecomment-49755990
@everett-toews Yes, absolutely. :+1:
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/448#issuecomment-49756633
The long live tests have been added. These tests takes several
hours and will leave traces in your AWS account.
You can merge this Pull Request by running:
git pull https://github.com/rcoedo/jclouds-labs-aws longlivetestsup
Or you can view, comment on it, or merge it online at:
[jclouds » jclouds-labs-aws
#1173](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1173/)
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
#89](https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws-pull-requests/89/)
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-49760175
+ * under the License.
+ */
+package org.jclouds.openstack.neutron.v2.domain;
+
+import com.google.common.base.Objects;
+import com.google.gson.annotations.SerializedName;
+
+import java.beans.ConstructorProperties;
+
+import static com.google.common.base.Preconditions.checkNotNull;
+
[jclouds-pull-requests
#1019](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1019/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/450#issuecomment-49760616
+ public static Properties defaultProperties() {
+ Properties properties = BaseHttpApiMetadata.defaultProperties();
+ properties.setProperty(SERVICE_TYPE, ServiceType.NETWORK);
+ properties.setProperty(CREDENTIAL_TYPE,
CredentialTypes.PASSWORD_CREDENTIALS);
+ return
[jclouds-java-7-pull-requests
#1491](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1491/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/450#issuecomment-49761566
:+1: Thanks for fixing this @demobox!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/450#issuecomment-49764358
[jclouds-java-7-pull-requests
#1483](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1483/)
ABORTED
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/390#issuecomment-49766768
[jclouds-java-7-pull-requests
#1484](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1484/)
ABORTED
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/442#issuecomment-49767337
[jclouds » jclouds
#1407](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1407/) ABORTED
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/450#issuecomment-49771468
So you mean (looking at the above config) `1 1 1`?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/431#issuecomment-49773443
Closed #450.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/450#event-144286553
[jclouds-pull-requests
#1020](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1020/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/450#issuecomment-49774745
[jclouds » jclouds
#1408](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1408/) 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/1409/changes
See https://jclouds.ci.cloudbees.com/job/jclouds-labs/517/
--
Started by upstream project jclouds build number 2694
originally caused by:
Started by an SCM change
Building remotely on s-899ce019 (m1.small swarm) in workspace
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/org.apache.jclouds.labs$openstack-glance/392/
[
https://issues.apache.org/jira/browse/JCLOUDS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett reassigned JCLOUDS-559:
--
Assignee: Jeremy Daggett
Upgrade to JAX-RS 2.0
-
This matches how most blobstores operate: delete container is a single
operation, not a compound operation which recursively deletes blobs.
You can merge this Pull Request by running:
git pull https://github.com/andrewgaul/jclouds delete-container-if-empty
Or you can view, comment on it, or
A subsequent commit will deprecate `deleteContainer`.
@jdaggett @shri Can you review this?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451#issuecomment-49797687
deleteContainerIfEmpty seems useful. However, I'm not sure about deprecating
deleteContainer itself. I think of deleteContainerIfEmpty as rm and
deleteContainer as rm -rf. Both are useful.
---
Reply to this email directly or view it on GitHub:
@@ -272,10 +274,10 @@ public void deleteContainerWithContents() throws
InterruptedException {
String containerName = getContainerName();
try {
addBlobToContainer(containerName, test);
- view.getBlobStore().deleteContainer(containerName);
-
@@ -144,6 +144,14 @@
void deleteContainer(String container);
/**
+* Delete a container if empty.
[minor] Deletes
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451/files#r15257446
Jeremy Daggett created JCLOUDS-634:
--
Summary: Support Swift Account ACLs
Key: JCLOUDS-634
URL: https://issues.apache.org/jira/browse/JCLOUDS-634
Project: jclouds
Issue Type: New Feature
@@ -272,10 +274,10 @@ public void deleteContainerWithContents() throws
InterruptedException {
String containerName = getContainerName();
try {
addBlobToContainer(containerName, test);
- view.getBlobStore().deleteContainer(containerName);
-
@@ -189,6 +189,15 @@ public void deleteContainer(String container) {
deletePathAndEnsureGone(container);
}
+ @Override
+ public boolean deleteContainerIfEmpty(String container) {
+ try {
+ return deleteAndVerifyContainerGone(container);
Stupid question...I'm
[jclouds-pull-requests
#1021](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1021/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451#issuecomment-49806635
[jclouds-java-7-pull-requests
#1493](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1493/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451#issuecomment-49807309
[jclouds » jclouds
#1410](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1410/) ABORTED
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451#issuecomment-49811442
@@ -272,10 +274,10 @@ public void deleteContainerWithContents() throws
InterruptedException {
String containerName = getContainerName();
try {
addBlobToContainer(containerName, test);
- view.getBlobStore().deleteContainer(containerName);
-
@@ -144,6 +144,14 @@
void deleteContainer(String container);
/**
+* Delete a container if empty.
Done.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451/files#r15261096
@@ -189,6 +189,15 @@ public void deleteContainer(String container) {
deletePathAndEnsureGone(container);
}
+ @Override
+ public boolean deleteContainerIfEmpty(String container) {
+ try {
+ return deleteAndVerifyContainerGone(container);
Not a stupid question;
@shrinandj `deleteContainer` is the only method that works on *both* containers
and blobs; all other methods work on *either* containers or blobs. If it helps
to think about this, `clearContainer` is like rm -rf while
`deleteContainerIfEmpty` is more like umount, fdisk delete partition, or
public class GlacierClientLongLiveTest extends
BaseApiLiveTestGlacierClient{
+ private static final long PART_SIZE = 1;
+ private static final long INITIAL_WAIT = 1080L; //3 hours
+ private static final long TIME_BETWEEN_POLLS = 90L; //15 minutes
Make these
This method breaks the contract of ByteSource which specifies that
openStream can produce multiple independent streams.
You can merge this Pull Request by running:
git pull https://github.com/andrewgaul/jclouds remove-asbytesource
Or you can view, comment on it, or merge it online at:
Note that `ByteSources` is annotated @Beta so we need not go through a
deprecation cycle.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/452#issuecomment-49815146
@rcoedo Related to discussion in jclouds/jclouds-labs-aws#41.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/452#issuecomment-49815213
+ * under the License.
+ */
+package org.jclouds.openstack.neutron.v2.domain;
+
+import com.google.common.base.Objects;
+import com.google.gson.annotations.SerializedName;
+
+import java.beans.ConstructorProperties;
+
+import static com.google.common.base.Preconditions.checkNotNull;
+
Need to track this change in jclouds-labs-openstack `SubmissionAsyncBlobStore`.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451#issuecomment-49816374
[jclouds-pull-requests
#1024](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1024/) 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/pull/452#issuecomment-49817450
[jclouds » jclouds
#1411](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1411/) 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:
This produces the same infinite-length input with deterministic
contents with less setup and memory.
You can merge this Pull Request by running:
git pull https://github.com/andrewgaul/jclouds-labs-aws randombytesource
Or you can view, comment on it, or merge it online at:
@rcoedo What do you think about this change?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/42#issuecomment-49817641
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1411/changes
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1205/changes
Changes:
[gaul] Prefer ByteStreams2 over ByteSources.asByteSource
--
[...truncated 16 lines...]
Executing Maven: -B -f
See
https://jclouds.ci.cloudbees.com/job/jclouds-chef/org.apache.jclouds.api$chef/862/changes
Changes:
[Andrew Gaul] Prefer ByteStreams2 over ByteSources.asByteSource
--
[...truncated 115 lines...]
Downloading:
See https://jclouds.ci.cloudbees.com/job/jclouds-chef/862/changes
Changes:
[Andrew Gaul] Prefer ByteStreams2 over ByteSources.asByteSource
--
[...truncated 2198 lines...]
Downloading:
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1206/
--
[...truncated 15 lines...]
===[JENKINS REMOTING CAPACITY]=== channel started
log4j:WARN No appenders could be found for logger
[jclouds-labs-aws-pull-requests
#90](https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws-pull-requests/90/)
UNSTABLE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/393/changes
See
https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1176/changes
[jclouds » jclouds-labs-aws
#1176](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1176/)
UNSTABLE
Looks like there's a problem with this pull request
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-pull-requests
#1023](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1023/)
UNSTABLE
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/pull/451#issuecomment-49818997
[jclouds-java-7-pull-requests
#1494](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1494/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/451#issuecomment-49819240
(Would need to update the hashes.)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/42#issuecomment-49819253
[jclouds-pull-requests
#1025](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1025/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/452#issuecomment-49819387
[jclouds-java-7-pull-requests
#1497](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1497/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/452#issuecomment-49819749
[jclouds » jclouds
#1412](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1412/) 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-chef/1207/
--
[...truncated 4 lines...]
Fetching changes from the remote Git repository
Fetching upstream changes from git://github.com/jclouds/jclouds-chef.git
Checking out Revision
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1177/
[jclouds » jclouds
#1413](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1413/) FAILURE
Looks like there's a problem with this pull request
[(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/1413/changes
Changes:
[gaul] Remove ByteSources.asByteSource
--
[...truncated 17000 lines...]
[INFO] jclouds Rackspace Next Generation Cloud DNS UK provider SKIPPED
[INFO] jclouds Rackspace
@demobox : It's been a while and I dropped the tracking on this, but in the
interest of clearing this out, could you clarify a couple things for me here?:
https://github.com/jclouds/jclouds/pull/326#discussion_r12566182
---
Reply to this email directly or view it on GitHub:
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1414/changes
81 matches
Mail list logo
