[jclouds » jclouds-labs
#550](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs/550/) 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://github.com/jclouds/jclouds-labs/pull/3
[jclouds-labs-pull-requests
#74](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/74/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/31#issuecomment-27752392
Authentication is done per-request by using the request filters.
If you annotate your method like this, the filters in the class should not
be applied:
@RequestFilters({})
@OverrideRequestFilters
public void unauthenticatedMethod()
You still need to have a context and all the rest, but this way
Specifically for openstack services, if a service supports some unauthenticated
calls, what is a good way to integrate that call with the rest of the service
in jclouds? So there is no authentication, no tenant on the path, and the
method can be executed without providing credentials
Regular
[jclouds-pull-requests
#367](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/367/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/194#issuecomment-27727413
[jclouds-java-7-pull-requests
#830](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/830/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/194#issuecomment-27727447
Modified a bit - had a couple screw-ups in the live tests, and I optimized some
of the AMI-related tests to only look at one region (so as to save about 45
seconds of lookup time per region for no good reason) and to use the new filter
methods for a couple things, for similar time savings. Also,
> +* Retrieve the virtual machine this volume is attached to.
> +*
> +* @return The virtual machine this volume is attached to, or null if it
> is
> +* not attached.
> +*/
> + public VirtualMachine getVirtualMachine() {
> + checkState(ATTACHED == VolumeState.valueOf(tar
> +* Retrieve the virtual machine this volume is attached to.
> +*
> +* @return The virtual machine this volume is attached to, or null if it
> is
> +* not attached.
> +*/
> + public VirtualMachine getVirtualMachine() {
> + checkState(ATTACHED == VolumeState.valueOf(tar
> jclouds-pull-requests #366 UNSTABLE
Spurious [test
failure](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/org.apache.jclouds$jclouds-compute/366/testReport/junit/org.jclouds.compute.callables/BlockUntilInitScriptStatusIsZeroThenReturnOutputTest/testloopUntilTrueOrThrowCancellationE
+1 - looks good to me. Thanks, @carlosgarciaibanez!
@nacx: OK with you?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/31#issuecomment-27707631
> +* Retrieve the virtual machine this volume is attached to.
> +*
> +* @return The virtual machine this volume is attached to, or null if it
> is
> +* not attached.
> +*/
> + public VirtualMachine getVirtualMachine() {
> + checkState(ATTACHED == VolumeState.valueOf(tar
[jclouds-java-7-pull-requests
#829](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/829/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/194#issuecomment-27706736
[jclouds-pull-requests
#366](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/366/) 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/194#issuecomment-27706687
Ok, this is the for real one now. =)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/194#issuecomment-27706228
+1 - links look good to me. Thanks, @nacx!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/26#issuecomment-27696264
Thanks for the changes, @ahgittin. Apart my minor comment on line 104 looks
good to me.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/9#issuecomment-27683201
> @@ -102,9 +102,11 @@ protected void bindErrorHandlers() {
>compose(new Function() {
> public String apply(Credentials in) {
> checkState(in.identity.indexOf("@") != 1,
@ahgittin, as @demobox suggested I think it would be useful to change als
[jclouds-chef-pull-requests
#94](https://jclouds.ci.cloudbees.com/job/jclouds-chef-pull-requests/94/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/32#issuecomment-27679152
[jclouds » jclouds-chef
#570](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-chef/570/) 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://github.com/jclouds/jclouds-chef/pull/3
Merged. Thanks @noorul and @demobox !
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-chef/pull/35#issuecomment-27677071
Looks good to me too.
@noorul, could you change the `fail` method, and move the private helper
methods to the bottom of the class, and leave the setup/teardown and the actual
tests first?
Once that is done I'll merge the PR.
---
Reply to this email directly or view it on GitHub:
https://github.
> +.rootFile(Resource.builder().fromPayload(v1content).build()) //
> +.build();
> +
> + // upload the cookbook to the remote server
> + api.updateCookbook(cookbookName, "1.0.0", cookbook);
> + }
> +
> + @Override
> + protected void initialize() {
> + sup
FYI, just added a comment to the INFRA ticket to get the jclouds.org
domain point to the new jclouds.apache.org domain.
On 2 November 2013 20:15, Andrew Phillips wrote:
>> Mailing lists updated from: d...@jclouds.incubator.apache.org to:
>> dev@jclouds.apache.org although mails seem to forward au
[jclouds-labs-pull-requests
#73](https://jclouds.ci.cloudbees.com/job/jclouds-labs-pull-requests/73/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/31#issuecomment-27671941
> + /**
> +* Retrieve the virtual machine this volume is attached to.
> +*
> +* @return The virtual machine this volume is attached to, or null if it
> is
> +* not attached.
> +*/
> + public VirtualMachine getVirtualMachine() {
> + checkState(ATTACHED == VolumeState.v
[jclouds-site-pull-requests
#88](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/88/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/26#issuecomment-27669905
Addresses some of the comments @demobox made in
https://github.com/jclouds/jclouds-site/pull/24 to unify the mailing list links
and make all them point to the community page.
You can merge this Pull Request by running:
git pull https://github.com/nacx/jclouds-site mailing-fixes
Or you can vie
> + /**
> +* Retrieve the virtual machine this volume is attached to.
> +*
> +* @return The virtual machine this volume is attached to, or null if it
> is
> +* not attached.
> +*/
> + public VirtualMachine getVirtualMachine() {
> + checkState(ATTACHED == VolumeState.v
>
> -## [Subscribe](mailto:jclouds-dev-subscr...@apache.org) to the [jclouds-dev
> mailing list](http://www.mail-archive.com/dev@jclouds.incubator.apache.org/)
> +## [Subscribe](mailto:jclouds-dev-subscr...@apache.org) to the [jclouds-dev
> mailing list](http://www.mail-archive.com/dev@jclouds.
> @@ -53,7 +53,7 @@
>
> https://twitter.com/jclouds";>Twitter
> https://github.com/jclouds";>Source
> - href="http://incubator.apache.org/projects/jclouds.html";>Contact
> + Community
I followed the same reasoning than above. The communit
> @@ -2,4 +2,3 @@
> * [Documentation](/documentation/)
> * [Community](/documentation/community/)
> * [Development](/documentation/devguides/)
> -* [Contact](http://incubator.apache.org/projects/jclouds.html)
I removed it because our community page (two links above) already provides the
links
32 matches
Mail list logo
