Okapi snapshot build tweaks...

[Jim Hargrave]

Out snapshot build config in jenkins was still looking a bit strange. I
made some changes to make sure it mimics what we do locally.

I think this might have something to do with the repo change for SWT
artifacts. I checked the box for "private maven repo". Made some other
changes. Running a build now, we'll see if it works.

Jim

[Jim Hargrave]

Ughh!! Still failing at the same place. I watched the console output and
it did look like the binaries were built OK so rainbow should have been
ready for the app integration tests.

I may force an update of the golden files and try again - after that I'm
out of ideas.

Jim

[Yves Savourel]

The more I look at it the more I think it has to do with RainbowTest: something has changed and we're failing on a problem that is
not related to the actual test, but the calling or reporting of it.

I'll try your suggestion of putting some system.out to see if it shows up in the raw output. Or try to somehow redirect the log to
the console.

-ys

--
You received this message because you are subscribed to the Google Groups "okapi-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to okapi-devel...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Yves Savourel]

I've noticed that the last few build had failed because Sir Jenkins was not able to find the dtdparser dependency anymore:

[[
BUILD FAILED
/scratch/jenkins/workspace/okapi-snapshot/deployment/maven/build.xml:15: The following error occurred while executing this line:
/scratch/jenkins/workspace/okapi-snapshot/deployment/maven/build_okapi-lib.xml:303:
/home/jenkins/.m2/repository/dtdparser/dtdparser/1.21 does not exist.
]]

It looks like the location of it was changed, or the location we used has been nuked (not sure how, but the local build was still
finding it...) in any case: I've updated the group ID and Sir Jenkins finds the dependency again.

I was expecting to see our old issue with the Rainbow-IT test cropping back, but it didn't even get there. The latest build has now
an new unknown class: org.apache.jasper.runtime.JspApplicationContextImpl in Longhorn this time.

After some search it seems we need to add this dependency:

<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jsp-2.1</artifactId>
<version>6.0.0</version>
</dependency>

Presumably we need to do this only for the tests. But still: Why do we suddenly need to have a new dependency?
(BTW: it's not related to the change with dtdparser)

Cheers,
-ys

[Jim Hargrave]

Maybe one of the previous longhorn dependencies has changed its
dependency up stream? I did do some work to upgrade versions, but I
never merged that change. Possible I missed something and a new version
needs some new depdency.

Probably a good idea before a release to delete our .m2 repos - that
will catch these problems early. I never remember to do it, but I have
been troubled by this type of thing before.

Jim

[Yves Savourel]

Good point.
I'll add the new one and try.
Thanks.

-ys

-----Original Message-----
From: okapi...@googlegroups.com [mailto:okapi...@googlegroups.com] On Behalf Of Jim Hargrave

[Yves Savourel]

Now it looks like we can't build because the expected location of the maven artifacts for the dependencies has changed.
It used to be "${user.home}/.m2/repository" and worked for both local and CB builds.
But it seems CB is not using this anymore and our ant script breaks.
Maybe it's time to try to switch to an all maven build...

-ys

-----Original Message-----
From: okapi...@googlegroups.com [mailto:okapi...@googlegroups.com] On Behalf Of Jim Hargrave
Sent: Monday, July 7, 2014 3:47 PM
To: okapi...@googlegroups.com
Subject: Re: [okapi-devel] Okapi snapshot build tweaks...

[Yves Savourel]

Another issue I ran into when I tried to rebuild after clearing my .m2 local cache:
The SDK build is using 0.25-SNAPSHOT references.

Currently we have:

<parent>
<groupId>net.sf.okapi</groupId>
<artifactId>build-okapi-superpom</artifactId>
<version>0.26-SNAPSHOT</version>
<relativePath>../../../superpom/pom.xml</relativePath>
</parent>
<properties>
<!-- The version of okapi that we use to create the framework jar -->
<okapi.version>0.25-SNAPSHOT</okapi.version>
</properties>
<artifactId>build-okapi-framework-sdk</artifactId>
<version>0.25-BETA0</version>

The okapi.version didn't get updated because it wasn't the pattern used when I replaced the versions. I assume it should be
0.26-SNAPSHOT now, is that correct?

And what about <version>0.25-BETA0</version>?

Cheers,
-ys

-----Original Message-----
From: Yves Savourel [mailto:yves.s...@gmail.com]
Sent: Tuesday, July 8, 2014 9:22 AM
To: 'okapi...@googlegroups.com'
Subject: RE: [okapi-devel] Okapi snapshot build tweaks...

Now it looks like we can't build because the expected location of the maven artifacts for the dependencies has changed.
It used to be "${user.home}/.m2/repository" and worked for both local and CB builds.
But it seems CB is not using this anymore and our ant script breaks.
Maybe it's time to try to switch to an all maven build...

-ys

-----Original Message-----
From: okapi...@googlegroups.com [mailto:okapi...@googlegroups.com] On Behalf Of Jim Hargrave
Sent: Monday, July 7, 2014 3:47 PM
To: okapi...@googlegroups.com
Subject: Re: [okapi-devel] Okapi snapshot build tweaks...

[Jim Hargrave]

Right, okapi.version should match the current okapi version tag, so 0.26-SNAPSHOT


version is the version of the SDK jar which can be anything we want. 0.26-SNAPSHOT is probably OK as default. I change this as needed to match our releases.

Jim

On 07/08/2014 09:33 AM, Yves Savourel wrote:
> The okapi.version didn't get updated because it wasn't the pattern used when I replaced the versions. I assume it should be
> 0.26-SNAPSHOT now, is that correct?
>
> And what about <version>0.25-BETA0</version>?

--
Have lots of ideas and throw away the bad ones.
You aren't going to have good ideas unless you have lots of ideas and
some sort of principle of selection.
—LINUS PAULING

[Jim Hargrave]

+1 - we'll need to do this for the new design anyway.

On 07/08/2014 09:22 AM, Yves Savourel wrote:
> Maybe it's time to try to switch to an all maven build...

[Fredrik Liden]

Good news, the snapshot is building/passing on CB now.

There were two issues. First, the path to the maven repo.

We're now passing a parameter to the ant build:
mavenStore=$WORKSPACE/.repository to override the default ${user.home}/.m2/repository.

Secondly, the reason the Rainbow integration tests failed was (lack of) display related.

org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
at org.eclipse.swt.SWT.error(SWT.java:4387)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:914)
at org.eclipse.swt.widgets.Display.create(Display.java:900)
at org.eclipse.swt.graphics.Device.<init>(Device.java:156)
at org.eclipse.swt.widgets.Display.<init>(Display.java:498)
at org.eclipse.swt.widgets.Display.<init>(Display.java:489)
....

Installed the Xvfb plugin according to these instructions:
https://wiki.cloudbees.com/bin/view/DEV/Testing+GUI+applications

I don't see any integration test results in the last successful snapshot build so not sure if we ever ran them on CB or if something changed.

With the snapshot built it we're exceeding the 10 GB quota so we need to clean out something to be able to build again.

Fredrik


________________________________________
From: okapi...@googlegroups.com [okapi...@googlegroups.com] On Behalf Of Yves Savourel [yves.s...@gmail.com]
Sent: Tuesday, July 08, 2014 9:22 AM
To: okapi...@googlegroups.com
Subject: RE: [okapi-devel] Okapi snapshot build tweaks...

[Yves Savourel]

Nice detective work Fredrik!
-yves