oauth thing was just fluff in test (had double-space in authorization header).
re-running live tests.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/86#issuecomment-62261157
[jclouds-labs-google-pull-requests
#253](https://jclouds.ci.cloudbees.com/job/jclouds-labs-google-pull-requests/253/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/86#issuecomment-62261208
[jclouds-labs-google-pull-requests
#254](https://jclouds.ci.cloudbees.com/job/jclouds-labs-google-pull-requests/254/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/86#issuecomment-62261224
See
https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1666/changes
[jclouds » jclouds-labs-google
#1666](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1666/)
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 » jclouds-labs-google
#1667](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1667/)
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-google-pull-requests
#255](https://jclouds.ci.cloudbees.com/job/jclouds-labs-google-pull-requests/255/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/86#issuecomment-62279070
running live tests again. I decided to kill that crazy InstanceTemplate class
and the super-confusing json serializers.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/86#issuecomment-62279102
[jclouds » jclouds-labs-google
#1668](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1668/)
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:
whoot. before we had a ton of separate http requests.. to create a boot disk,
set metadata, set tags twice, and then the instance itself. All of the above
now work in *one* request. Here's an example instance created in one operation.
```json
{
kind: compute#instance,
id: 8935965322994729970,
Same 3 live test errors as always, cannot connect to port 22. This should be
solvable, possibly more easily now.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/86#issuecomment-62280335
[jclouds-labs-google-pull-requests
#256](https://jclouds.ci.cloudbees.com/job/jclouds-labs-google-pull-requests/256/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/86#issuecomment-62280350
[jclouds » jclouds-labs-google
#1669](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1669/)
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:
@ccustine
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/87#issuecomment-62280979
optional injection is one of the scariest things in guice. we have not needed
these extension points in 2 years, so I#39;m guessing we can kill them.
You can merge this Pull Request by running:
git pull https://github.com/adriancole/jclouds-labs-google adrian.oauth-again
Or you can view,
[jclouds-labs-google-pull-requests
#257](https://jclouds.ci.cloudbees.com/job/jclouds-labs-google-pull-requests/257/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/87#issuecomment-62281040
[jclouds » jclouds-labs-google
#1670](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1670/)
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:
public final class BuildTokenRequest implements
FunctionGeneratedHttpRequest, TokenRequest {
private final String assertionTargetDescription;
private final String signatureAlgorithm;
private final SupplierOAuthCredentials credentialsSupplier;
private final long
[jclouds-labs-google-pull-requests
#258](https://jclouds.ci.cloudbees.com/job/jclouds-labs-google-pull-requests/258/)
UNSTABLE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
@@ -67,12 +61,6 @@
.put(ES512, EC)
.put(NO_ALGORITHM, NO_ALGORITHM).build();
- /**
-* The (optional) set of additional claims to use, provided in
MapString,String form
-*/
only used in tests, and only in this module
---
Reply to this email directly or
See
https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1671/changes
[jclouds-labs-google-pull-requests
#259](https://jclouds.ci.cloudbees.com/job/jclouds-labs-google-pull-requests/259/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/87#issuecomment-62291498
@@ -116,7 +116,8 @@ protected BaseGoogleComputeEngineExpectTest() {
@Override
public void configure(Binder binder) {
// Predictable time
-binder.bind(new TypeLiteralSupplierLong()
{}).toInstance(Suppliers.ofInstance(0L));
+
See
https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1672/changes
[jclouds » jclouds-labs-google
#1672](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-google/1672/)
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:
25 matches
Mail list logo
