@andrewgaul This seems to be causing the build to fail now with a Checkstyle
violation:
https://jclouds.ci.cloudbees.com/job/jclouds/2776/org.apache.jclouds$jclouds-resources/violations/file/checkstyle.xml/
---
Reply to this email directly or view it on GitHub:
The first commit (to checkstyle.xml itself) is just cleanup
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds fix-checkstyle
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/537
-- Commit Summary --
*
@@ -1106,6 +1106,8 @@
configLocationresources/checkstyle.xml/configLocation
failOnViolationtrue/failOnViolation
failsOnErrortrue/failsOnError
+ !-- fails on itself as it uses the author tag in a module
definition --
+
[jclouds-pull-requests-java-6
#114](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/114/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/537#issuecomment-57764855
@@ -1106,6 +1106,8 @@
configLocationresources/checkstyle.xml/configLocation
failOnViolationtrue/failOnViolation
failsOnErrortrue/failsOnError
+ !-- fails on itself as it uses the author tag in a module
definition --
+
Unrelated build failure fixed here:
https://github.com/jclouds/jclouds/pull/537. Will close and reopen once that is
merged. Thanks @demobox!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/536#issuecomment-57765119
+ this.driveCloned = checkNotNull(driveCloned, driveCloned);
+ this.serverStopped = checkNotNull(serverStopped, serverStopped);
+ this.destroyDrives = destroyDrives;
+ this.groupNamingConvention = checkNotNull(groupNamingConvention,
groupNamingConvention).create();
+ }
[jclouds » jclouds
#1682](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1682/) 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/1682/changes
[jclouds-pull-requests
#1203](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1203/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/537#issuecomment-57770321
/cc @danbroudy - this sounds pretty similar to what we saw yesterday.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/50#issuecomment-57783517
Closed #537.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/537#event-173798285
but +1 for the current approach excluding the checkstyle.xml file.
Thanks, @nacx! Merged to
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=641bc6fda0527fd828697081b565a0b2a5e3fdec)
---
Reply to this email directly or view it on GitHub:
Who is supposed to close the issue in JIRA?
(https://issues.apache.org/jira/browse/JCLOUDS-611)
me or someone else?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/146#issuecomment-57797789
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-resources/2777/
--
[INFO]
[INFO]
See https://jclouds.ci.cloudbees.com/job/jclouds/2777/changes
Changes:
[Andrew Phillips] Aligning indents in checkstyle config file
[Andrew Phillips] Excluding checkstyle.xml from Checkstyle checking
--
[...truncated 523 lines...]
[INFO] jclouds
[
https://issues.apache.org/jira/browse/JCLOUDS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158033#comment-14158033
]
ASF subversion and git services commented on JCLOUDS-735:
-
Commit
[jclouds-pull-requests-java-6
#115](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/115/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/351#issuecomment-57804207
[
https://issues.apache.org/jira/browse/JCLOUDS-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158056#comment-14158056
]
ASF subversion and git services commented on JCLOUDS-538:
-
Commit
Java 7 PR build looks good. Committed to
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=d949137649a8e9fe7fec4a06fa8a5b2d589a7c63)
and
[1.8.x](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=2cbb5e26c055b53775a2b3bf932e9d99161383ff)
---
Reply to this
Closed #351.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/351#event-173845717
[
https://issues.apache.org/jira/browse/JCLOUDS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Daggett resolved JCLOUDS-611.
Resolution: Done
Changes pushed to
@fbrouille Personally, I close them once the work is pushed. I just resolved
the issue in JIRA, so not to worry. We really appreciate the contribution,
thanks!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/146#issuecomment-57810495
See https://jclouds.ci.cloudbees.com/job/jclouds/2778/changes
Changes:
[Andrew Phillips] JCLOUDS-538: Avoiding a VM crash trying to run live tests for
Swift
--
[...truncated 198 lines...]
Compiler warnings:
WARNING:
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-resources/2779/
--
[INFO]
[INFO]
See https://jclouds.ci.cloudbees.com/job/jclouds/2779/
--
[...truncated 2695 lines...]
[INFO] jclouds ElasticHosts Hong Kong provider ... SKIPPED
[INFO] jclouds ElasticHosts Sydney provider .. SKIPPED
[INFO] jclouds Open Hosting East1
This is now being excluded, but there's still a failure the doesn't seem to be
reproduced in the PR job?!
```
Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-checkstyle-plugin:2.13:checkstyle (default-cli)
on project jclouds-resources:
[jclouds-pull-requests
#1204](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1204/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/351#issuecomment-57813113
[jclouds » jclouds
#1684](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1684/) 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:
[
https://issues.apache.org/jira/browse/JCLOUDS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158117#comment-14158117
]
Adrian Cole commented on JCLOUDS-150:
-
approach I'm taking is to add the
This adds a stop-gap async blobstore SubmissionAsyncBlobStore, which was
copy/pasted from openstack-labs. This simulates what the async client did,
basically defer the call to a future.
Using this, I unasynced s3 and aws-s3, ran the live tests, which had the same
results as before: s3 all
[
https://issues.apache.org/jira/browse/JCLOUDS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158135#comment-14158135
]
Adrian Cole commented on JCLOUDS-150:
-
https://github.com/jclouds/jclouds/pull/538
[jclouds-pull-requests-java-6
#116](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/116/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538#issuecomment-57817439
[jclouds-pull-requests-java-6
#117](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/117/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538#issuecomment-57817531
[jclouds-pull-requests
#1205](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1205/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538#issuecomment-57824864
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-1.8.x-branch/22/
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws-1.8.x-branch/18/
--
Started by upstream project jclouds-labs-1.8.x-branch build number 22
originally caused by:
Started by upstream project jclouds-1.8.x-branch build number 23
originally caused
I haven't seen the problem occur recently
Looks like I was a bit too optimistic, and that is **not** fixed by the change
to longs:
https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1206/console
hanging at:
```
Test suite progress: tests succeeded: 69, failed: 0, skipped: 0.
Starting
[jclouds-pull-requests
#1206](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1206/) ABORTED
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538#issuecomment-57829889
import org.jclouds.s3.reference.S3Headers;
-import com.google.common.collect.ImmutableSet;
-import com.google.common.reflect.TypeToken;
-import com.google.inject.Module;
+import static org.jclouds.Constants.PROPERTY_RELAX_HOSTNAME;
+import static
- ListenableFutureVoid enableBucketLogging(
-@Bucket @EndpointParam(parser =
AssignCorrectHostnameForBucket.class)
@BinderParam(BindAsHostPrefixIfConfigured.class)
@ParamValidators(BucketNameValidator.class) String bucketName,
-
import org.jclouds.s3.reference.S3Headers;
-import com.google.common.collect.ImmutableSet;
-import com.google.common.reflect.TypeToken;
-import com.google.inject.Module;
+import static org.jclouds.Constants.PROPERTY_RELAX_HOSTNAME;
+import static
/**
* Provides access to S3 via their REST API.
- * p/
- * All commands return a Future of the result from S3. Any exceptions
incurred during
- * processing will be backend in an {@link ExecutionException} as documented
in
- * {@link Future#get()}.
- *
+ *
* @see a
/**
* Retrieves the {@link
org.jclouds.s3.domain.internal.BucketListObjectMetadata metadata} of
-* the object associated with the key or
-* {@link
org.jclouds.s3.domain.internal.BucketListObjectMetadata#NOT_FOUND} if not
+* the object associated with the key or
/**
* Retrieves the {@link
org.jclouds.s3.domain.internal.BucketListObjectMetadata metadata} of
-* the object associated with the key or
-* {@link
org.jclouds.s3.domain.internal.BucketListObjectMetadata#NOT_FOUND} if not
+* the object associated with the key or
/**
* Provides access to S3 via their REST API.
- * p/
- * All commands return a Future of the result from S3. Any exceptions
incurred during
- * processing will be backend in an {@link ExecutionException} as documented
in
- * {@link Future#get()}.
- *
+ *
* @see a
*/
- S3Object getObject(String bucketName, String key, GetOptions... options);
+ @Named(GetObject)
[minor] FWIW `@Named(apiName:methodName)` has been an effective naming
convention. In this case: `@Named(s3:getObject)`
---
Reply to this email directly or view it on GitHub:
maybe wrong place to discuss, but at square, we used an annotation @Flakey
which would simply
replay the test on failure.
The thing here is that this test doesn't _fail_, it causes the build to _hang_.
But for some of our other flaky tests...sure!
---
Reply to this email directly or view
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-resources/2780/
See https://jclouds.ci.cloudbees.com/job/jclouds/2780/
--
[...truncated 2646 lines...]
[INFO] jclouds ElasticHosts Peer1 San Antonio provider ... SKIPPED
[INFO] jclouds ElasticHosts BlueSquare London provider ... SKIPPED
[INFO] jclouds ElasticHosts Peer1
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-core/2780/
--
[INFO]
[INFO]
[INFO]
Erm...so that helped, but unfortunately this is not fixed yet. See [this
comment](https://github.com/jclouds/jclouds/commit/641bc6fda0527fd828697081b565a0b2a5e3fdec#commitcomment-8029750)
---
Reply to this email directly or view it on GitHub:
We followed up on this on the inside and looks like this is a bug that will be
rolled back soon.
erjohnso and I say beers on us next time you are in Seattle.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/50#issuecomment-57834250
[
https://issues.apache.org/jira/browse/JCLOUDS-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158294#comment-14158294
]
Daniel Broudy commented on JCLOUDS-740:
---
This is a google bug that will be rolled
+relativePath../../project/pom.xml/relativePath
+ /parent
+ groupIdorg.apache.jclouds.api/groupId
+ artifactIdchef/artifactId
+ packagingbundle/packaging
+ namejclouds Chef api/name
+ descriptionjclouds components to access Chef/description
+
+ properties
+
@@ -26,7 +26,4 @@
@Override
S3BlobStore getBlobStore();
-
- @Override
- S3AsyncBlobStore getAsyncBlobStore();
Nice!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538/files#r18411399
+1 With the above osgi import fix and the fix for #537.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/536#issuecomment-57835484
public abstract class BaseS3ClientExpectTest extends
BaseRestClientExpectTestS3Client {
protected static final String CONSTANT_DATE = 2009-11-08T15:54:08.897Z;
- @ConfiguresRestClient
- private static final class TestS3RestClientModule extends
}
private void addGrantsToACL(AccessControlList acl) {
String ownerId = acl.getOwner().getId();
acl.addPermission(GroupGranteeURI.ALL_USERS, Permission.READ);
- acl.addPermission(new
EmailAddressGrantee(StubS3AsyncClient.TEST_ACL_EMAIL), Permission.READ_ACP);
[jclouds » jclouds
#1686](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1686/) 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/538#issuecomment-57837219
+import org.jclouds.blobstore.domain.StorageMetadata;
+import org.jclouds.blobstore.options.CreateContainerOptions;
+import org.jclouds.blobstore.options.GetOptions;
+import org.jclouds.blobstore.options.ListContainerOptions;
+import org.jclouds.blobstore.options.PutOptions;
+import
+import org.jclouds.blobstore.options.PutOptions;
+import org.jclouds.domain.Location;
+
+import com.google.common.collect.ForwardingObject;
+import com.google.common.util.concurrent.ListenableFuture;
+import com.google.common.util.concurrent.ListeningExecutorService;
+
+/**
+ * Adapter
+1 Looks good based on the other conversions I have done. Just a few minor
comments, thanks @adriancole !
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538#issuecomment-57838532
Thanks for the update. FWIW, I think we should proceed with this change
anyway. There's no real value exposed in having these fields, and this
change makes the ListPage classes more consistent across compute, storage.
sg?
p.s. I will take you up, but maybe with coconut water :)
---
Reply to
[jclouds » jclouds
#1687](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1687/) 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:
Tracking this in
[JCLOUDS-736](https://issues.apache.org/jira/browse/JCLOUDS-736).
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/commit/641bc6fda0527fd828697081b565a0b2a5e3fdec#commitcomment-8033214
[
https://issues.apache.org/jira/browse/JCLOUDS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158447#comment-14158447
]
Andrew Gaul commented on JCLOUDS-736:
-
This actually does not relate to the
[
https://issues.apache.org/jira/browse/JCLOUDS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158456#comment-14158456
]
ASF subversion and git services commented on JCLOUDS-736:
-
Commit
[
https://issues.apache.org/jira/browse/JCLOUDS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul resolved JCLOUDS-736.
-
Resolution: Fixed
Fix Version/s: 2.0.0
snapshot repo mildly screwed
addressed all feedback and re-ran live tests.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538#issuecomment-57851980
[jclouds-pull-requests-java-6
#118](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests-java-6/118/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538#issuecomment-57852319
[
https://issues.apache.org/jira/browse/JCLOUDS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158471#comment-14158471
]
ASF subversion and git services commented on JCLOUDS-150:
-
Commit
[
https://issues.apache.org/jira/browse/JCLOUDS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158485#comment-14158485
]
ASF subversion and git services commented on JCLOUDS-150:
-
Commit
[
https://issues.apache.org/jira/browse/JCLOUDS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Cole resolved JCLOUDS-150.
-
Resolution: Fixed
Remove async interface from AWS APIs/providers, rename *Client to *Api
[
https://issues.apache.org/jira/browse/JCLOUDS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Cole updated JCLOUDS-150:
Fix Version/s: 1.8.1
Remove async interface from AWS APIs/providers, rename *Client to *Api
[
https://issues.apache.org/jira/browse/JCLOUDS-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14158491#comment-14158491
]
Adrian Cole commented on JCLOUDS-150:
-
Note I didn't rename S3Client to S3Api as I
[jclouds » jclouds
#1688](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1688/) 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-pull-requests
#1207](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1207/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/538#issuecomment-57863034
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$ultradns-ws/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-core/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.api$route53/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$serverlove-z1-man/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.api$rackspace-cloudidentity/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$aws-cloudwatch/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-scriptbuilder/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.api$sqs/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.common$openstack-common/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.driver$jclouds-log4j/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$rackspace-cloudloadbalancers-uk/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.api$swift/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$rackspace-cloudblockstorage-uk/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$rackspace-clouddatabases-uk/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.api$jclouds-apis-project/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$elastichosts-sjc-c/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.driver$jclouds-slf4j/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$jclouds-providers-project/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$softlayer/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$aws-s3/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.provider$rackspace-clouddns-uk/2781/
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds.api$cloudstack/2781/
1 - 100 of 205 matches
Mail list logo
