Does the regular build have the same maven repo configuration than the PR one?
Yes, and the DEV@cloud one is different from BuildHive, I think. Interesting.
Might be worth seeing if the artifact is indeed OK..?
---
Reply to this email directly or view it on GitHub:
I did a local build of the jclouds-cli, which pulled the artifact from the
snapshots repo and it works...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-37031090
did a local build of the jclouds-cli, which pulled the artifact from the
snapshots repo and it works...
Oh, I'm also satisfied that it works - I wouldn't spend too much time on it. I
can't see any downloaded version of the JAR in the workspace, though. Do we
know where any logging during
Here's the problem, I think:
```
[INFO] --- features-maven-plugin:2.3.2:add-features-to-repo
(add-features-to-repo) @ jclouds-karaf ---
[INFO] Copying bundle:
org.apache.karaf.assemblies.features:standard:xml:features:2.3.2
[INFO] Copying bundle:
And is there some way to override `[INFO] Base repo:
file:///home/jenkins/.m2/repository/` with a build parameter, so the repository
appears in the workspace? This will pollute other builds...
---
Reply to this email directly or view it on GitHub:
Ahhh, I think adding it
[here](https://github.com/jclouds/jclouds-karaf/blob/master/feature/pom.xml#L107-L161)
should fix it!
Wondering why it works in other builds...
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-37036907
Just beat me to it with [that
link](https://github.com/jclouds/jclouds-karaf/blob/master/feature/pom.xml#L107)!
;-)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-37037201
As regards my other question: it looks like
[`maven.repo.local`](https://github.com/jclouds/jclouds-karaf/blob/master/itests/pom.xml#L179)
controls that. But can we set that property using a `-D...` parameter without
messing up other stuff..?
---
Reply to this email directly or view it on
As regards my other question: it looks like maven.repo.local controls that.
But can we set that property using a -D... parameter without messing up other
stuff..?
Perhaps @iocanel can give some light on this
I've also opened https://github.com/jclouds/jclouds-karaf/pull/38 to see if we
Arhg, f*$#@! I just don't get it. It seems the same again? Does the regular
build have the same maven repo configuration than the PR one? @iocanel?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-36975104
Will do today. My laptop ran out of battery while testing it locally... that
was kinda a sign :)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-36830861
Tested locally with a clean repo (`mvn clean install -U -e
-Dmaven.javadoc.skip=true`):
```
[INFO] Apache jclouds :: Karaf ... SUCCESS [10:22.499s]
[INFO] jclouds :: Karaf :: Core .. SUCCESS [2:47.131s]
[INFO] jclouds :: Karaf :: Utils
I'm tempted to kick this one more time and say it's good to merge. As one final
attempt, I've created a job in DEV@cloud that builds straight against the do
branch. Here
[goes](https://jclouds.ci.cloudbees.com/view/integrations/job/jclouds-karaf-do/1/console)
(`clean install -e -U` - requires
I talked yesterday with @iocanel on the IRC and had a look at this. It seems
that the last commit in https://github.com/jclouds/jclouds-karaf/pull/24 will
fix this one, so I'd rather wait until that one is merged, then rebase and see
if the test gets fixed.
---
Reply to this email directly or
https://jclouds.ci.cloudbees.com/view/integrations/job/jclouds-karaf-do/org.apache.jclouds.karaf$itests/1/
`Finished: SUCCESS`. [No test
failures](https://jclouds.ci.cloudbees.com/view/integrations/job/jclouds-karaf-do/org.apache.jclouds.karaf$itests/1/testReport/).
Closed #36.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36
Reopened #36.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36
I'm running the tests with my existing repo
Let's see what happens this time. Can you reproduce the failure by running the
tests with a *clean* repo?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-35609773
[jclouds-karaf-pull-requests
#38](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/38/)
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-karaf/pull/36#issuecomment-35610696
[jclouds » jclouds-karaf
#758](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/758/)
UNSTABLE
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:
Running locally again after having wiped the repo. Don't get why it is failing
as it is just a copy of the softlayer one. Will have to investigate!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-35612009
I think this might be the problem...it's running [`clean verify -U
-e`](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/758/consoleFull)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-35619052
OK, changed the configuration of the BuildHive job. But since DEV@cloud is
already running `clean install`, I'm not sure that will make any difference.
I'm guessing the Apache snapshots repo is available to the build? Are the
required JAR(s)
Yes, the snapshot artifact is in place. I've been trying different combinations
and I can't reproduce the test failure :S
@iocanel do you have an idea of what I am missing?
---
Reply to this email directly or view it on GitHub:
Note that the digitalocean JARs _do_ appear to have been correctly downloaded
to [local
repository](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/ws/.repository/org/apache/jclouds/labs/digitalocean/1.8.0-SNAPSHOT/)
of the DEV@cloud job.
---
Reply to this email directly or
Yep, and that's what I don't get about the test. It is just like the Softlayer
one, all configured the same way. Even more, locally I am able to run the cli
and the feature install command without issues.
---
Reply to this email directly or view it on GitHub:
Do we need to add a test for this new feature?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-35533504
jclouds-karaf-pull-requests #36 UNSTABLE
No [test
failures](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/36/testReport/)
- that's Checkstyle complaining. Reporting some [new
@demobox I thought the it tests automatically detected the features and tested
them :) Added the missing test. Thx!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/36#issuecomment-35558477
@@ -424,6 +424,11 @@ limitations under the License.
bundlemvn:org.apache.jclouds.provider/softlayer/${jclouds.version}/bundle
/feature
+feature name='jclouds-digitalocean' description='Components to access
DigitalOcean' version='${project.version}' resolver='(obr)'
+
[jclouds-karaf-pull-requests
#37](https://jclouds.ci.cloudbees.com/job/jclouds-karaf-pull-requests/37/)
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-karaf/pull/36#issuecomment-35560359
[jclouds » jclouds-karaf
#757](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-karaf/757/)
UNSTABLE
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:
32 matches
Mail list logo
