I added a link to the signer JIRA issue, squashed the commits, and pushed to
master as af86b0187db4c3db76caf1564c664cb46b263dbd.
When trying to deploy with jekyll 1.5.1 and 2.2.0 I encountered some spurious
changes.
@everett-toews Any suggestions on how best to do this?
---
Reply to this email
Closed #121.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/121#event-151225376
Closed #58.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/58#event-151230728
+
+ // Create a container
+ final String containerName = UUID. randomUUID().toString() +
_interruptionExample;
+ blobstore.createContainerInLocation(null, containerName); // Create a
vault
+
+ // Create a blob
+ ByteSource payload =
[jclouds » jclouds-labs
#1400](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1400/)
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-labs/1400/changes
Changes:
[igreenfi] Add vSphere support
[igreenfi] Remove copyright from pom.xml
[igreenfi] Organized imports
[igreenfi] Fix checkstyle
[igreenfi] change the LICENSE header, add notice file
[igreenfield] remove
[jclouds-labs-pull-requests
#225](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/225/)
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-labs/pull/61#issuecomment-51766079
[jclouds » jclouds-labs
#1401](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1401/)
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-labs/1401/changes
Changes:
[igreenfi] Add vSphere support
[igreenfi] Remove copyright from pom.xml
[igreenfi] Organized imports
[igreenfi] Fix checkstyle
[igreenfi] change the LICENSE header, add notice file
[igreenfield] remove
[jclouds-labs-pull-requests
#226](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/226/)
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-labs/pull/61#issuecomment-51767912
[jclouds-labs-pull-requests
#227](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/227/)
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-labs/pull/61#issuecomment-51768231
This requires downgrading maven-checkstyle-plugin to 2.11
The fix version for the
[issue](https://jira.codehaus.org/browse/MCHECKSTYLE-225) also lists 2.12.1,
which is already published. But the dates of the comments in the issue
describing the fix don't seem to line up. Seeing the diff in
@@ -669,7 +669,7 @@
/plugin
plugin
artifactIdmaven-checkstyle-plugin/artifactId
-version2.12.1/version
+version2.11/version
Could you add a comment here that we need a version that fixed MCHECKSTYLE-225?
---
Reply to this email directly or view it on
[jclouds » jclouds-labs
#1402](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1402/)
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-labs/1402/changes
Changes:
[igreenfi] Add vSphere support
[igreenfi] Remove copyright from pom.xml
[igreenfi] Organized imports
[igreenfi] Fix checkstyle
[igreenfi] change the LICENSE header, add notice file
[igreenfield] remove
jclouds-pull-requests #1075 UNSTABLE
This is related to two [Checkstyle
violations](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1075/org.apache.jclouds.provider$softlayer/violations/)
in SoftLayer, i.e. unrelated to this commit.
---
Reply to this email directly or view it on
One minor comment about adding a clarifying comment to explain the reason for
being behind on the Checkstyle plugin version. Otherwise, +1 - looks good to me.
Thanks for figuring this out, @andrewgaul!
---
Reply to this email directly or view it on GitHub:
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/421/
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/org.apache.jclouds.labs$openstack-glance/421/
+1 - looks good to me. Thanks, @andrewgaul!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/473#issuecomment-51771859
See JCLOUDS-622 and https://github.com/jclouds/jclouds/commit/80a0256c
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-chef fix-build
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-chef/pull/49
-- Commit
}
@Override
public byte[] decrypt(InputSupplier? extends InputStream supplier)
throws IOException {
return ByteStreams.toByteArray(new RSADecryptingPayload(crypto,
Payloads.newPayload(supplier.getInput()), privateKey
- .get()));
+
[jclouds » jclouds-chef
#1269](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1269/)
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:
@@ -190,7 +190,7 @@ public boolean apply(Part input) {
public String sign(String toSign) {
try {
- byte[] encrypted = toByteArray(new RSAEncryptingPayload(crypto,
Payloads.newStringPayload(toSign), supplyKey.get()));
+ byte[] encrypted = toByteArray(new
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1269/changes
Changes:
[Andrew Phillips] Fixing compilation errors caused by Payload no longer being
an InputSupplier
--
[...truncated 27 lines...]
[INFO] Error stacktraces are turned on.
[jclouds-chef-pull-requests
#119](https://jclouds.ci.cloudbees.com/job/jclouds-chef-pull-requests/119/)
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-chef/pull/49#issuecomment-51773206
@andrewgaul @nacx Thoughts on the stream closing question?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/49#issuecomment-51773076
Hi @demobox I think it should be ok now with PR
https://github.com/jclouds/jclouds/pull/476
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/472#issuecomment-51773373
You can merge this Pull Request by running:
git pull https://github.com/andreaturli/jclouds fix/sl-checkstyle-violations
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/476
-- Commit Summary --
* fix ASF copyright headers on SoftLayer
--
[jclouds-java-6-pull-requests
#9](https://jclouds.ci.cloudbees.com/job/jclouds-java-6-pull-requests/9/)
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/476#issuecomment-51773766
+1 - looks good to me. But Checkstyle is really what we're waiting for here ;-)
Thanks, @andreaturli!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/476#issuecomment-51774187
I think it should be ok now
Thanks, @andreaturli! @andrewgaul Guess it's worth rebasing this on master once
Andrea's PR is merged?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/472#issuecomment-51774380
[jclouds » jclouds
#1493](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1493/) 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/1493/changes
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1270/
--
[...truncated 21 lines...]
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.jclouds.chef:chef-project:pom:2.0.0-SNAPSHOT
[jclouds-pull-requests
#1080](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1080/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/476#issuecomment-51780299
[jclouds » jclouds-chef
#1271](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1271/)
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/1271/changes
[jclouds » jclouds-labs
#1404](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1404/)
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-labs/pull/61#issuecomment-51796021
[jclouds-labs-pull-requests
#229](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/229/)
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-labs/pull/61#issuecomment-51800308
@@ -52,35 +60,55 @@
/**
* To get a service account and its private key see [TODO: write some
* documentation on the website and put a link to it]
-*
-* The first argument (args[0]) must be your service account email address
-* The second argument (args[1]) must a
@@ -179,7 +215,7 @@ private Image getImage() {
/**
* Always close your service when you're done with it.
*/
- public void close() throws IOException {
+ public final void close() throws IOException {
Is this change needed?
---
Reply to this email directly or view it on
@@ -108,8 +137,15 @@ private void createServer() throws RunNodesException,
TimeoutException {
.locationId(ZONE)
.hardwareId(getHardware().getId())
.imageId(getImage().getId())
-.build();
-
+
@@ -52,35 +60,55 @@
/**
* To get a service account and its private key see [TODO: write some
* documentation on the website and put a link to it]
-*
-* The first argument (args[0]) must be your service account email address
-* The second argument (args[1]) must a
@@ -108,8 +137,15 @@ private void createServer() throws RunNodesException,
TimeoutException {
.locationId(ZONE)
.hardwareId(getHardware().getId())
.imageId(getImage().getId())
-.build();
-
+
+1 to cleaning up litter
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/474#issuecomment-51806500
.addHeader(Date,
CONSTANT_DATE)
- .addHeader(Authorization,
AWS identity:p32RsBr2inawMBeCkkiA228BT2w=)
Why was the change in identity needed?
---
Reply to this email directly or view it on GitHub:
[jclouds » jclouds-labs-openstack
#1544](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-openstack/1544/)
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-openstack-pull-requests
#350](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/350/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
.addHeader(Date,
CONSTANT_DATE)
- .addHeader(Authorization,
AWS identity:p32RsBr2inawMBeCkkiA228BT2w=)
I changed the signature, not the identity. Refer to
@@ -669,7 +669,7 @@
/plugin
plugin
artifactIdmaven-checkstyle-plugin/artifactId
-version2.12.1/version
+version2.11/version
I retested with 2.12.1 and this works as-is. I must have tested this
incorrectly earlier.
---
Reply to this email directly or
Closed #472.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/472#event-151482419
+1 - code change looks fine to me. Curious about the identify change too.
Thanks, @andrewgaul!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/475#issuecomment-51812430
@@ -190,7 +190,7 @@ public boolean apply(Part input) {
public String sign(String toSign) {
try {
- byte[] encrypted = toByteArray(new RSAEncryptingPayload(crypto,
Payloads.newStringPayload(toSign), supplyKey.get()));
+ byte[] encrypted = toByteArray(new
We cannot merge this as-is due to
`S3RedirectionRetryHandlerExpectTest.testRedirectOnHeadBucketChangesRequestToGetBucket`
failures. However I do not understand this test and thus am not sure how to
fix it.
---
Reply to this email directly or view it on GitHub:
@@ -669,7 +669,7 @@
/plugin
plugin
artifactIdmaven-checkstyle-plugin/artifactId
-version2.12.1/version
+version2.11/version
I retested with 2.12.1 and this works as-is.
Ah, good to know!
---
Reply to this email directly or view it on GitHub:
Pushed to master as aa41d489f4c70475d5cbce2ae6e1c773cd7aaa18. Will follow up
with other repositories.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/473#issuecomment-51813577
Closed #473.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/473#event-151487588
Closed #229.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/229#event-151491646
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1272/changes
Changes:
[gaul] Remove maven-license-plugin
--
[...truncated 39 lines...]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed
As previous stated, this PR is superceded by work being done in
jclouds-labs-openstack [PR
77](https://github.com/jclouds/jclouds-labs-openstack/pull/77). Closing.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/258#issuecomment-51815482
Closed #258.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/258#event-151494559
.addHeader(Date,
CONSTANT_DATE)
- .addHeader(Authorization,
AWS identity:p32RsBr2inawMBeCkkiA228BT2w=)
I see.
---
Reply to this email directly or view it on GitHub:
Change looks good to me.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/475#issuecomment-51816730
See https://jclouds.ci.cloudbees.com/job/jclouds-chef/881/changes
Changes:
[Andrew Gaul] Remove maven-license-plugin
--
[...truncated 120 lines...]
[JENKINS] Recording test results[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @
See
https://jclouds.ci.cloudbees.com/job/jclouds-chef/org.apache.jclouds.api$chef/881/
--
[INFO]
[INFO]
[INFO]
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/1406/changes
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1494/changes
See https://jclouds.ci.cloudbees.com/job/jclouds-karaf/660/
--
[...truncated 2581 lines...]
Downloading:
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/provider/rackspace-cloudloadbalancers-uk/2.0.0-SNAPSHOT/maven-metadata.xml
:+1: Thanks for catching this and please backport to 1.8.x since this may allow
users to upgrade their applications to Guava 18.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/49#issuecomment-51823148
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1273/changes
[jclouds » jclouds-chef
#1273](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1273/)
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-chef-pull-requests
#121](https://jclouds.ci.cloudbees.com/job/jclouds-chef-pull-requests/121/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/49#issuecomment-51823974
However I do not understand this test and thus am not sure how to fix it.
It looks like we're supposed to have fallback logic that handles a 301 by
falling back from a HEAD to a GET? I guess you got that too, of course...so if
the question is why are we doing that, I fear we'll need to ping
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1495/changes
I also don't see any obvious logic that resets from HEAD to GET in
[S3RedirectionRetryHandler](https://github.com/jclouds/jclouds/blob/master/apis/s3/src/main/java/org/jclouds/s3/handlers/S3RedirectionRetryHandler.java).
In fact, I also don't see how the _first_ request [in the
Good with removing the Java 6/Java 7 switch. Some [Checkstyle
violations](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/1077/org.apache.jclouds$jclouds-core/violations/),
though.
---
Reply to this email directly or view it on GitHub:
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1274/
--
[...truncated 18 lines...]
Executing Maven: -B -f
https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/ws/pom.xml clean
verify -U -e -Dmaven.javadoc.skip=true
[INFO] Error
Committed to
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds-chef.git;a=commit;h=973c31e3944f3b728afd10b3a9a47fbb3cf7006f)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/49#issuecomment-51830239
Closed #476.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/476#event-151550749
Tested locally and pushed to master as fecedfdb3ff46a57376a4369aa16823862872114.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/476#issuecomment-51830375
backport to 1.8.x since this may allow users to upgrade their applications to
Guava 18
What should I put in the commit message? What's incompatible with other
versions of Guava?
---
Reply to this email directly or view it on GitHub:
Addressed Checkstyle violations and pushed to master as
a10bf3e9c5495b4c8c69e0059b5901266df471dd and
f236e046e3e8a1a882c0762ac017d4570c343346.
@demobox I diffed the Java 7 and 8 tests and they are identical.
---
Reply to this email directly or view it on GitHub:
Closed #49.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/49#event-151552594
Tested locally and pushed to master
Thanks, @andrewgaul!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/476#issuecomment-51830944
@demobox I used this for fb60d76704745317186ad700e9b7ce5a569a614d:
```
JCLOUDS-622: Remove most vestiges of InputSupplier
Guava 16 deprecated InputSupplier and a future release will remove it.
```
---
Reply to this email directly or view it on GitHub:
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/1275/changes
See
https://jclouds.ci.cloudbees.com/job/jclouds-chef/org.apache.jclouds.api$chef/882/changes
See https://jclouds.ci.cloudbees.com/job/jclouds-chef/882/changes
Closed #443.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/443#event-151557704
[
https://issues.apache.org/jira/browse/JCLOUDS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093221#comment-14093221
]
ASF subversion and git services commented on JCLOUDS-658:
-
Commit
[
https://issues.apache.org/jira/browse/JCLOUDS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul resolved JCLOUDS-658.
-
Resolution: Fixed
Add blob metadata support to filesystem blobstore
Pushed to master as 204a6c7f3b3ff8689ad9df9b1084801b89dd901d.
@zack-shoylev Thanks for testing!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/443#issuecomment-51832290
I used this
Ah, you're referring to the adding .openStream() bit rather than the
ByteStreams2 bit. Makes sense!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/49#issuecomment-51835968
```
... mvn clean integration-test
Results :
Tests run: 25, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time:
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/1186/
...tyGroupExtension
added check for to and from port being the same
added test in BaseSecurityGroupExtensionLiveTest
fixes https://issues.apache.org/jira/browse/JCLOUDS-661
You can merge this Pull Request by running:
git pull https://github.com/stuarthendren/jclouds-labs-google dev
Or you
+
+ /**
+* Returns the specified ForwardingRule resource.
+*
+* @param region the name of the region scoping this request.
+* @param forwardingRule the name of the ForwardingRule resource to
return.
+* @return a ForwardingRule resource.
+*/
+
[
https://issues.apache.org/jira/browse/JCLOUDS-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093269#comment-14093269
]
Stuart Hendren commented on JCLOUDS-661:
See
see issue https://issues.apache.org/jira/browse/JCLOUDS-661
You can merge this Pull Request by running:
git pull https://github.com/stuarthendren/jclouds dev
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/477
-- Commit Summary --
* Adding
1 - 100 of 130 matches
Mail list logo
