[
https://issues.apache.org/jira/browse/JCLOUDS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14560161#comment-14560161
]
Ben Piper commented on JCLOUDS-912:
---
For simple uploads, I would suggest that
[
https://issues.apache.org/jira/browse/JCLOUDS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14560174#comment-14560174
]
Andrew Gaul commented on JCLOUDS-912:
-
[~Bhash90] What do you think about [~bpiper]
Rebuild please
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/176#issuecomment-105705365
Actually it seems like a compilation failure
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/176#issuecomment-105705455
@zack-shoylev @iocanel please review
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/67#issuecomment-105708993
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-cli/pull/27
-- Commit Summary --
* JCLOUDS-669: Add support for openstack-swift
* JCLOUDS-669: Add support for rackspace-cloudfiles
-- File Changes --
M assembly/pom.xml (5)
-- Patch
@zack-shoylev @iocanel please review
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-cli/pull/27#issuecomment-105709001
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-karaf/pull/67
-- Commit Summary --
* JCLOUDS-669: Add support for openstack-swift
* JCLOUDS-669: Add support for rackspace-cloudfiles
-- File Changes --
M feature/pom.xml (5)
M
Seems like I imported a java 8 package instead of the guava one. I fixed it and
changed the IDE jdk now.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/176#issuecomment-105766834
[
https://issues.apache.org/jira/browse/JCLOUDS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558717#comment-14558717
]
Andrew Gaul commented on JCLOUDS-912:
-
Great diagnosis [~bpiper]! I corrected the
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/org.apache.jclouds.labs$rackspace-autoscale-uk/829/
--
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/829/
--
[...truncated 4780 lines...]
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: **/src/test/resources/**/*.sh
[INFO] Exclude: **/src/test/resources/**/*.bat
See https://jclouds.ci.cloudbees.com/job/jclouds-labs/976/
--
[...truncated 6458 lines...]
[WARNING] Artifact
org.apache.jclouds.labs:cloudsigma2:javadoc:javadoc:2.0.0-SNAPSHOT already
attached to project, ignoring duplicate
[INFO]
[INFO] ---
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs/org.apache.jclouds.labs$cloudsigma2/976/
--
[...truncated 447 lines...]
[WARNING]
[
https://issues.apache.org/jira/browse/JCLOUDS-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558988#comment-14558988
]
Jakub Bartecek commented on JCLOUDS-900:
It looks it could be the same case as
[
https://issues.apache.org/jira/browse/JCLOUDS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558984#comment-14558984
]
Jakub Bartecek commented on JCLOUDS-857:
Hi,
any progress on this issue?
Tests
@andreaturli Hi. I tested it and it doesn't fix the JCLOUDS-900. I think that
this bug is not related to the version of Docker API. It looks like it is
internal JClouds bug. I found one similar issue:
https://issues.apache.org/jira/browse/JCLOUDS-857
---
Reply to this email directly or view it
yes it is possible, you filed a bug for that already. Be sure to start your
docker engine on `http`
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/174#issuecomment-105510265
@jbartece could you simply run just `ContainerApiLiveTest` and paste the
stacktrace of the error on gist, please?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/174#issuecomment-105497944
I ran it and got error, but it is probably caused by the wrong environment.
Could you check the logs and tell me what should I change, please?
https://gist.github.com/jbartece/4cad0bd49f585a6c004d
---
Reply to this email directly or view it on GitHub:
I really don't have much experience with the security stuff. Do you have any
test certificates generated or some HOW-TO manual?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/174#issuecomment-105509128
I found in IRC logs, that it is possible to run the test without authentication
using: mvn clean install -Plive -Dtest.docker.identity=root
-Dtest.docker.credential=pwd -Dtest.docker.endpoint=http://192.168.59.103:2375
---
Reply to this email directly or view it on GitHub:
The build succeeded; the failure was after the build when Jenkins was
collecting data.
Thanks @stuarthendren! Are you able to run the live tests against the new
regions?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/750#issuecomment-105633641
[
https://issues.apache.org/jira/browse/JCLOUDS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14559547#comment-14559547
]
ASF subversion and git services commented on JCLOUDS-894:
-
Commit
+ */
+package org.jclouds.elastichosts;
+
+import static org.jclouds.compute.config.ComputeServiceProperties.TEMPLATE;
+
+import java.net.URI;
+import java.util.Properties;
+
+import org.jclouds.elasticstack.ElasticStackApiMetadata;
+import org.jclouds.providers.ProviderMetadata;
+version2.0.0-SNAPSHOT/version
+relativePath../../project/pom.xml/relativePath
+ /parent
+ groupIdorg.apache.jclouds.provider/groupId
+ artifactIdelastichosts-dal-a/artifactId
+ namejclouds ElasticHosts Dallas provider/name
+ descriptionElasticHosts implementation targeted to
See https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/830/
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack/org.apache.jclouds.labs$rackspace-autoscale-uk/830/
See https://jclouds.ci.cloudbees.com/job/jclouds-labs/977/
@nacx A big point when discussing the next 1.9.x release was making sure we
have the builders available, as well as any new code that might use them.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/699#issuecomment-105635453
See
https://jclouds.ci.cloudbees.com/job/jclouds-labs/org.apache.jclouds.labs$cloudsigma2/977/
See
https://jclouds.ci.cloudbees.com/job/jclouds-guava-17-18/GUAVA_VERSION=17.0,jdk=OpenJDK%207%20(latest)/273/
--
Started by upstream project jclouds-guava-17-18 build number 273
originally caused by:
Started by upstream project jclouds build number 3140
[
https://issues.apache.org/jira/browse/JCLOUDS-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14559848#comment-14559848
]
Ignasi Barrera commented on JCLOUDS-861:
The failure seems specific to the CoreOS
[
https://issues.apache.org/jira/browse/JCLOUDS-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignasi Barrera updated JCLOUDS-861:
---
Priority: Minor (was: Blocker)
node creation fails due to ssh failure
Sure, I will create the 1.9.x PR.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/139#issuecomment-105678509
Pushed to master. Thanks @danbroudy! Will you create a PR for 1.9.x?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/139#issuecomment-105533739
Closed #139.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/139#event-313795525
I rerun the tests and got: https://gist.github.com/jbartece/c7e4f4b993a344726321
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/174#issuecomment-105532906
Generally I don't think we should upgrade dependencies in minor releases, but
since this one is compile-only it should not matter.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/699#issuecomment-105690540
for range get in a LocalBlobStore, metadata.getSize() has the
original blob size and contentMetadata.getContentLength() has
the actual payload size. Other blobstores have the same size
in both
You can view, comment on, or merge this pull request online at:
…ata due to instance names
Temporary solution related to #139
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs-google/pull/140
-- Commit Summary --
* JCLOUDS-908: Temporary fix to exception thrown in InstanceToNodeMetadata
due to
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-labs/pull/176
-- Commit Summary --
* JCLOUDS-826: Add blob operations
-- File Changes --
M jdbc/pom.xml (12)
M jdbc/src/main/java/org/jclouds/jdbc/config/JPAInitializer.java (4)
@@ -655,7 +655,9 @@ public Blob getBlob(String containerName, String key,
GetOptions options) {
byte[] byteArray = out.toByteArray();
blob.setPayload(byteArray);
HttpUtils.copy(cmd, blob.getPayload().getContentMetadata());
-
43 matches
Mail list logo
