Am 17.11.16 um 23:22 schrieb Robert Munteanu:
On Thu, 2016-11-17 at 14:53 +0100, Julian Sedding wrote:
Hi Sandro
You are right. However, the full build on Jenkins failed too often.
Partly due to issues or flaky tests in Sling, partly due to e.g.
infrastructure issues. This made the Jenkins builds almost useless,
because chances were that it weren't your changes that made the build
fail.
Therefore Robert added configurations to run each module
independently
on Jenkins. That gives us a better overview of which modules are ok
and which ones aren't. However, we lost the full build in the
process.
Maybe we could add it back and run it once every night. WDYT, Robert?
First of all, I think that I should update the documentation :-) With
all the SNAPSHOTs being deployed by the Jenkins jobs the only command
that should be used to build Sling after the SVN checkout is
$ cd launchpad/builder
$ mvn -U clean install
which matches to a large degree what the Jenkins jobs do. There should
be absolutely no need to perform a full reactor build - which takes
time, and is not always stable - to get a launchpad.
Then I'd like to understand exactly why the reactor build fails, as it
should not, at least not when the individual module builds are working.
Robert
I don't know exactly why the reactor build failed.
In the next days I will have a look on that to find out what's the
difference between the reactor build and the launchpad build. But of
course a quick and stable build sounds very very good to me!
Best,
Sandro
Regards
Julian
On Wed, Nov 16, 2016 at 10:02 PM, Sandro Boehme <sandro.boe...@gmx.de
wrote:
According to our Jenkins job
https://builds.apache.org/job/sling-launchpad-builder-1.8/
the launchpad should work without issues.
A couple of additional questions:
- what Java version do you use for building and running Sling?
- what happens if you try to build the project with "-U", to
force
updating the snapshots? The command would then be mvn -U clean
verify
Robert
According to the "Getting and Building Sling" page [1] I just did
"svn co
...", "mvn clean install" (-DskipTests) and "java -jar ..." and
expected to
be able to build and use Sling. But if we don't have a Jenkins job
that does
the same a committer will probably more easily overlook if he
breaks the
build for people who are trying out Sling. But I guess you know
that and I
have the feeling that I miss something here.
I use Java 8. I didn't try -U but Julians changes fixed the problem
for me.
[1] -
http://sling.apache.org/documentation/development/getting-and-build
ing-sling.html
Best,
Sandro
