[jclouds » jclouds
#1268](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1268/) 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-java-7-pull-requests
#1392](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1392/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/418#issuecomment-46810761
[
https://issues.apache.org/jira/browse/JCLOUDS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zack Shoylev updated JCLOUDS-178:
-
Comment: was deleted
(was: I am on vacation until the 27th. If you have SDK questions, contact
Thanks @jdaggett
Is this going to be backported?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/391#issuecomment-46830444
+ */
+package org.jclouds.openstack.neutron.v2.domain;
+
+import com.google.common.base.Objects;
+import com.google.gson.annotations.SerializedName;
+
+/**
+ */
+public class AddressPair {
+
+ @SerializedName(mac_address)
+ protected final String macAddress;
+
Christopher Dancy created JCLOUDS-610:
-
Summary: reboot, suspend, and resumeNodesMatching methods gain
functionality similar to that of destroyNodesMatching
Key: JCLOUDS-610
URL:
This is the PR for this JIRA issue:
https://issues.apache.org/jira/browse/JCLOUDS-610
New tests have not been written as there are already the tests
quot;testRebootquot; and quot;testSuspendResumequot; of class
quot;BaseComputeServiceLiveTestquot; which already cover these calls. I have
[jclouds-java-7-pull-requests
#1393](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1393/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/419#issuecomment-46852146
Closed #414.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/414#event-134122601
Sigh.
Looks like the node went offline during the build. Check the slave log for
the details.
FATAL: channel is already closed
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/414#issuecomment-46854436
[jclouds » jclouds
#1269](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1269/) 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
#923](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/923/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/419#issuecomment-46856019
[jclouds-pull-requests
#922](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/922/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/419#issuecomment-46856021
Merged and deployed.
Thanks a ton @mikolajz!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/98#issuecomment-46856833
Closed #98.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/98#event-134131264
[jclouds-java-7-pull-requests
#1394](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1394/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/419#issuecomment-46856249
[jclouds-pull-requests
#924](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/924/) 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/414#issuecomment-46859034
@zack-shoylev Yes, I was planning on backporting this fix.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/391#issuecomment-46859836
[jclouds-java-7-pull-requests
#1395](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1395/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/414#issuecomment-46860923
[jclouds » jclouds
#1270](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1270/) 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
#1271](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/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:
[
https://issues.apache.org/jira/browse/JCLOUDS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1404#comment-1404
]
ASF subversion and git services commented on JCLOUDS-558:
-
Commit
[
https://issues.apache.org/jira/browse/JCLOUDS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041113#comment-14041113
]
ASF subversion and git services commented on JCLOUDS-558:
-
Commit
Another transient failure on the UNSTABLE. Going with best 2 out of 3.
Merged to master and 1.7.x
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/414#issuecomment-46884909
Closed #414.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/414#event-134234296
[
https://issues.apache.org/jira/browse/JCLOUDS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Everett Toews closed JCLOUDS-558.
-
Resolution: Fixed
Fix Version/s: 1.7.4
1.8.0
JSON parse error on
[
https://issues.apache.org/jira/browse/JCLOUDS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041176#comment-14041176
]
Jeffrey Nguyen commented on JCLOUDS-603:
hi Zack,
after a lot of head banging
[
https://issues.apache.org/jira/browse/JCLOUDS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Nguyen closed JCLOUDS-603.
--
Resolution: Not a Problem
Close this issue since this is testbed configuration issue.
See
https://jclouds.ci.cloudbees.com/job/jclouds-1.7.x-branch/org.apache.jclouds$jclouds-compute/102/
See https://jclouds.ci.cloudbees.com/job/jclouds-chef/848/
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/375/
I'd rather not commit this to a place where we know isn't its permanent home.
That just means a backwards incompatible change down the road. At the very
least we need to get the names and place right.
I honestly don't know what a better word for magnitude is in this case. I'll
take whatever
[jclouds-java-7-pull-requests
#1396](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1396/)
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/402#issuecomment-46904753
[jclouds-pull-requests
#925](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/925/) 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/402#issuecomment-46904789
[jclouds » jclouds
#1273](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1273/) 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/1273/changes
Changes:
[everett.toews] Factored out some constants
[everett.toews] Moved property constants to BlobStoreProperties
--
[...truncated 16911 lines...]
[INFO] allloadbalancer
Andrew Gaul created JCLOUDS-612:
---
Summary: ScriptBuilder
Statements.extractTargzAndFlattenIntoDirectory uses predictable file names
Key: JCLOUDS-612
URL: https://issues.apache.org/jira/browse/JCLOUDS-612
This commit addresses a potential security issue where an attacker
could hijack the ScriptBuilder payload by predicting the temporary
directory name.
You can merge this Pull Request by running:
git pull https://github.com/andrewgaul/jclouds mktemp
Or you can view, comment on it, or merge it
[
https://issues.apache.org/jira/browse/JCLOUDS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041472#comment-14041472
]
Zack Shoylev commented on JCLOUDS-603:
--
Glad to hear! Thanks for keeping us updated.
[jclouds-pull-requests
#926](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/926/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/420#issuecomment-46916119
[jclouds-java-7-pull-requests
#1397](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1397/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/420#issuecomment-46916209
See https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1274/changes
[jclouds » jclouds
#1274](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/1274/) 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:
43 matches
Mail list logo
