A new static method has been added to the LinkPredicates utility class to
create predicate which determines whether a given REST link refers to a disk
entity.
You can merge this Pull Request by running:
git pull https://github.com/carlosgarciaibanez/jclouds-labs master
Or you can view,
Could you rebase your branch to the latest master version? Now the repo has
been synched with the ASF one, and your PR should contain only the commit that
adds the predicate.
---
Reply to this email directly or view it on GitHub:
Hi,
As I know jclouds support vcloud 1.5.
I have used jclouds with VCloud (StratoGen). To be precise I used
*1.6.2.incubating
jcloud* version. That version did not work with the vCloud Director
version(5.1 I guess) of the StratoGen. However after some patches to the
jclouds I was able to spawn
[jclouds-labs-pull-requests
#76](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/76/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/32#issuecomment-27760442
Yes, it looks good. Thanks!
To avoid getting in trouble with the master branch sync, when contributing it
is highly recommended that you develop the changes in a specific branch, and
send the PR from your branch to our master branch. This way you have the master
branch clean and you can use it
Merged. All live tests passing in Chef 10, Chef 11 and Enterprise Chef. Great
@noorul !
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/32#issuecomment-27765815
I'll give them a look today, with my Jenkins hat on. =)
A.
On Tue, Nov 5, 2013 at 9:24 AM, Ignasi ignasi.barr...@gmail.com wrote:
Hi Foudil!
It is great to see movement in the plugin! However, we don't manage the
Jenkins repos so you might have to ping the Jenkins people to see progress
[jclouds-java-7-pull-requests
#831](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/831/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/77#issuecomment-27808671
@@ -101,10 +101,20 @@ protected void bindErrorHandlers() {
return
MemoizedRetryOnTimeOutButNotOnAuthorizationExceptionSupplier.create(authException,
compose(new FunctionCredentials, String() {
public String apply(Credentials in) {
-
@abayer: Based on [this
comment](https://github.com/jclouds/jclouds-labs-google/pull/9/files#r7448227),
any thoughts on whether this restriction should actually be enforced..?
---
Reply to this email directly or view it on GitHub:
JCLOUDS-364: Add g2.2xlarge EC2 instance size
You can merge this Pull Request by running:
git pull https://github.com/jollyc/jclouds master
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds/pull/197
-- Commit Summary --
* add g2.2xlarge EC2
[jclouds-java-7-pull-requests
#833](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/833/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/197#issuecomment-27829911
You're right.
Our unit tests test the apis using mocks to aviod sending the requests over
the wire.
Live tests, though, perform real api calls and create real resources (vms,
blobs, networks, etc) to verify that the code actually works as expected
with the different provider apis.
They are
13 matches
Mail list logo
