@@ -25,7 +25,7 @@ We handle this for you.
Writing tests for cloud endpoints is difficult. We provide you with Stub
connections that simulate a cloud without creating network connections. In
this way, you can write your unit tests without mocking complexity or the
brittleness of remote
You can merge this Pull Request by running:
git pull https://github.com/rcoedo/jclouds-site patch-1
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/64
-- Commit Summary --
* Fixing some typos on what-is-jclouds text.
-- File Changes
[jclouds-site-pull-requests
#215](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/215/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/64#issuecomment-37506719
[jclouds » jclouds
#908](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/908/) 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
#658](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/658/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/316#issuecomment-37511857
[jclouds-java-7-pull-requests
#1128](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1128/)
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/316#issuecomment-37512115
Then some more elaborated configuration will be required. Could you paste the
stack trace, to see the exact exception you're getting? jclouds automatically
retries 300 requests to the host provided in the `Location` header. Just share
the stack trace so we can properly configure jclouds to do
[
https://issues.apache.org/jira/browse/JCLOUDS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933052#comment-13933052
]
Ignasi Barrera commented on JCLOUDS-457:
I plan to start a Developer Guide in the
Ignasi Barrera created JCLOUDS-500:
--
Summary: Create a Docker provider
Key: JCLOUDS-500
URL: https://issues.apache.org/jira/browse/JCLOUDS-500
Project: jclouds
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/JCLOUDS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Branan updated JCLOUDS-498:
Description:
I am attempting to upgrade my application from JClouds 1.5.5 to JClouds 1.7.1.
My
Merged and republished the site. Thanks @rcoedo !
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/64#issuecomment-37531721
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds/909/changes
@@ -25,7 +25,7 @@ We handle this for you.
Writing tests for cloud endpoints is difficult. We provide you with Stub
connections that simulate a cloud without creating network connections. In
this way, you can write your unit tests without mocking complexity or the
brittleness of remote
The stack trace is:
```
org.jclouds.http.HttpResponseException: command: GET
https://proxy.env11.nebula.com:9292/ HTTP/1.1 failed with response: HTTP/1.1
300 Multiple Choices; content: [{versions: [{status: CURRENT, id:
v2.1, links: [{href: http://proxy.env11.nebula.com:9292/v2/;, rel:
Closed #313.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/313
[
https://issues.apache.org/jira/browse/JCLOUDS-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933480#comment-13933480
]
ASF subversion and git services commented on JCLOUDS-486:
-
Commit
Hugo Duncan created JCLOUDS-501:
---
Summary: The clojure namespace org.jclouds.ec2.ebs2 is broken
Key: JCLOUDS-501
URL: https://issues.apache.org/jira/browse/JCLOUDS-501
Project: jclouds
Issue
RiakCS using the S3 interface occasionally surfaces these status
codes.
You can merge this Pull Request by running:
git pull https://github.com/maginatics/jclouds s3-504-retry
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/317
-- Commit
See
https://jclouds.ci.cloudbees.com/job/jclouds-1.7.x-branch/org.apache.jclouds$jclouds-compute/53/
Looks good to me.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/317#issuecomment-37567286
[jclouds » jclouds
#910](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/910/) 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-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933932#comment-13933932
]
Jeremy Daggett commented on JCLOUDS-498:
Hi Bill,
I wanted you to know that I am
[jclouds » jclouds
#911](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/911/) 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/798/
[jclouds-java-7-pull-requests
#1130](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1130/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/44#issuecomment-37580932
This PR removes RestContext from the Rackspace examples as the first step
towards the work to be done in
[JCLOUDS-346](https://issues.apache.org/jira/browse/JCLOUDS-346).
Please refer to
[JCLOUDS-152](https://issues.apache.org/jira/browse/JCLOUDS-152) which
discusses the removal of
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/799/
[
https://issues.apache.org/jira/browse/JCLOUDS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934187#comment-13934187
]
Bill Branan commented on JCLOUDS-498:
-
Hi Jeremy,
I've updated the 1.7.1 test code I
@@ -96,8 +96,9 @@ h3 class=panel-titleBlobStore/h3
blobStore.createContainerInLocation(location, mycontainer);
+ByteSource payload =
ByteSource.wrap(blob-content.getBytes(Charsets.UTF_8));
Done.
---
Reply to this email directly or view it on GitHub:
[jclouds-site-pull-requests
#216](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/216/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/59#issuecomment-37593232
Did you run the SmokeTest with these changes?
When that passes, I'm a +1.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/35#issuecomment-37594984
See
https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-compute/2557/
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/org.apache.jclouds.labs$jclouds-labs-openstack/305/
--
[INFO]
[INFO]
Go to
http://2652f14e5456c7d8a584-84feae4228b9ba60f1e3b03619b50a08.r0.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/59#issuecomment-37612482
Go to
http://50922bbcc0b370760eeb-c5161db033c907f2a461fa4544af29fb.r55.cf1.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/59#issuecomment-37613542
35 matches
Mail list logo
