Hi Julian,

I like the idea of individual Jenkins jobs for the reasons you pointed out!
If we would have a "nightly" build (whatever time that would be) we could link it at the Getting and building Sling page. We could write there that in case the build does currently not work (e.g. because there is some bigger work in progress or a plain oversight) they could have a look at what revision actually does work and use that. People who would stop trying Sling because of a non working build and who would not ask at the mailing list would then have a chance to get the build working anyways.
WDYT?

Best,

Sandro

Am 17.11.16 um 14:53 schrieb Julian Sedding:
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?

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-building-sling.html

Best,

Sandro


Reply via email to