Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

On Mon, 2016-09-19 at 23:26 +0300, Robert Munteanu wrote: > On Mon, 2016-09-19 at 22:50 +0300, Robert Munteanu wrote: > > > > I want to use the Job DSL plugin to define a large number of jobs > > programatically, rather than maintain them by hand. Here's a more in-depth look at the issue   

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

On Mon, 2016-09-19 at 22:50 +0300, Robert Munteanu wrote: > I want to use the Job DSL plugin to define a large number of jobs > programatically, rather than maintain them by hand. Here's a quick sample of how I intend to use the DSL plugin.  First, I create a 'seed' job, in charge of generating

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

On Mon, 2016-09-19 at 18:02 +0200, Konrad Windszus wrote: > Wouldn’t it make more sense to rely on the pipeline plugin instead of > the Job DSL Plugin? This is by default shipped in Jenkins since 2.0.0 > so probably there is not even the necessity to install an additional > plugin. > For a

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

+1 to the pipeline plugin. Info on the other CI builds. There is a build that builds pull requests from GitHub in Jenkins, IIRC its only JDK8 and doesn't have tests enabled as there were too many false negatives, but I would need to check that. Also there are Travis CI builds for JDK8 and JDK7,

[jira] [Resolved] (SLING-6057) Context-Aware Config: Separate Maven Project for SPI

[ https://issues.apache.org/jira/browse/SLING-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6057. --- Resolution: Fixed Completed: At revision: 1761475 > Context-Aware Config: Separate Maven

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

Was going to write the exact same thing. The pipeline plugin, now just "pipeline" into jenkins 2, is the future and I would recommend using it. Except if there are plugins you want to use that are not supported yet. -Andrei On Mon, Sep 19, 2016 at 6:02 PM Konrad Windszus wrote:

Re: [i18n] IT Tests failing in reactor build

> Hi Carsten, > > It looks like we have a different classpath when it fails and when it > doesn't > Maybe you can put a mvn dependency:tree in the job and check how it looks > in the two cases. > > Also, AFAIK the fact that the maven dependency resolution mechanism puts > the ones defined in the

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

Wouldn’t it make more sense to rely on the pipeline plugin instead of the Job DSL Plugin? This is by default shipped in Jenkins since 2.0.0 so probably there is not even the necessity to install an additional plugin. For a comparison between those two approaches look at

[jira] [Commented] (SLING-6059) Context-Aware Config: Make resource inheritance for configuration collections configurable

[ https://issues.apache.org/jira/browse/SLING-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503820#comment-15503820 ] Stefan Seifert commented on SLING-6059: --- i've renamed this ticket to make it configurable. i think

[jira] [Updated] (SLING-6059) Context-Aware Config: Make resource inheritance for configuration collections configurable

[ https://issues.apache.org/jira/browse/SLING-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6059: -- Summary: Context-Aware Config: Make resource inheritance for configuration collections

Re: [i18n] IT Tests failing in reactor build

Hi Carsten, It looks like we have a different classpath when it fails and when it doesn't Maybe you can put a mvn dependency:tree in the job and check how it looks in the two cases. Also, AFAIK the fact that the maven dependency resolution mechanism puts the ones defined in the project pom and

[jira] [Updated] (SLING-6059) Context-Aware Config: Rethink resource inheritance for configuration collections

[ https://issues.apache.org/jira/browse/SLING-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6059: -- Description: currently and automatic merging/combining of configuration resource items takes

[jira] [Resolved] (SLING-6026) Context-Aware Config: Pluggable configuration persistence

[ https://issues.apache.org/jira/browse/SLING-6026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6026. --- Resolution: Fixed Completed: At revision: 1761468 > Context-Aware Config: Pluggable

[jira] [Resolved] (SLING-6023) Context-Aware Config: Add pluggable context paths strategies

[ https://issues.apache.org/jira/browse/SLING-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6023. --- Resolution: Fixed Completed: At revision: 1761468 > Context-Aware Config: Add pluggable

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

On Mon, 2016-09-19 at 16:39 +0200, Carsten Ziegeler wrote: > > > > On Mon, 2016-09-19 at 15:53 +0200, Carsten Ziegeler wrote: > > > > > > The benefit of the current solution is clear: below or equal to > > > zero. > > > Afaik, Robert look already into having per module jobs in > > > jenkins. > >

[jira] [Created] (SLING-6061) Create per-module Jenkins jobs

Robert Munteanu created SLING-6061: -- Summary: Create per-module Jenkins jobs Key: SLING-6061 URL: https://issues.apache.org/jira/browse/SLING-6061 Project: Sling Issue Type: Improvement

[VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

Hi, These are the first releases for these three modules that depend on each other and there is no explicit component yet. Staging repository:https://repository.apache.org/content/repositories/orgapachesling-1524/ You can use this UNIX script to download the release and verify the

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

> On Mon, 2016-09-19 at 15:53 +0200, Carsten Ziegeler wrote: >> The benefit of the current solution is clear: below or equal to zero. >> Afaik, Robert look already into having per module jobs in jenkins. >> Not >> sure how far this is. > > I pinged infra about this and noone opposed :-) > >

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

On Mon, 2016-09-19 at 15:53 +0200, Carsten Ziegeler wrote: > The benefit of the current solution is clear: below or equal to zero. > Afaik, Robert look already into having per module jobs in jenkins. > Not > sure how far this is. I pinged infra about this and noone opposed :-)   

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

The benefit of the current solution is clear: below or equal to zero. Afaik, Robert look already into having per module jobs in jenkins. Not sure how far this is. Carsten > +1 for openly talking about this. I think the most important thing is > clearly understanding the benefits and drawbacks

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

+1 for openly talking about this. I think the most important thing is clearly understanding the benefits and drawbacks for the different ways of building continuously. On Mon, Sep 19, 2016 at 3:43 PM Stefan Seifert wrote: > > for quiet some time now, it seems that the IT

CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

> for quiet some time now, it seems that the IT tests of the i18n module fail > in reactor build i also had a brief look at the tests of the i18n project and was not able to spot the problem easily. >I suggest we turn off Jenkins completely do we have an alternative? ian invested a good

Re: SLING-6003

> Hi All, > > In case of org.apache.sling.scripting.java.impl. JavaScriptEngineFactory , > What should be the value for 'ResourceChangeListener.PATHS' property, as > current implementation doesn't specify any value for > 'SlingConstants.PROPERTY_PATH'. As per new 'ResourceChangeListener API',

SLING-6003

Hi All, In case of org.apache.sling.scripting.java.impl. JavaScriptEngineFactory , What should be the value for 'ResourceChangeListener.PATHS' property, as current implementation doesn't specify any value for 'SlingConstants.PROPERTY_PATH'. As per new 'ResourceChangeListener API', If

[jira] [Commented] (SLING-5958) Upgrade Jackrabbit to 2.13.1

[ https://issues.apache.org/jira/browse/SLING-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503046#comment-15503046 ] Julian Reschke commented on SLING-5958: --- Well, what can I say? Do not reference unstable

[jira] [Commented] (SLING-5958) Upgrade Jackrabbit to 2.13.1

[ https://issues.apache.org/jira/browse/SLING-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503016#comment-15503016 ] Oliver Lietz commented on SLING-5958: - [~reschke], see discussion in SLING-5520 (no one complained but

[jira] [Commented] (SLING-5958) Upgrade Jackrabbit to 2.13.1

[ https://issues.apache.org/jira/browse/SLING-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502920#comment-15502920 ] Julian Reschke commented on SLING-5958: --- OAK 1.5 and Jackrabbit 2.13 are releases from unstable

[jira] [Resolved] (SLING-6054) JcrEventTrigger aggregation resulting in unconsistent package

[ https://issues.apache.org/jira/browse/SLING-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-6054. Resolution: Fixed fixed in r1761073. > JcrEventTrigger aggregation resulting in

[jira] [Comment Edited] (SLING-4443) Whitespace removal for Sightly HTML output

[ https://issues.apache.org/jira/browse/SLING-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502906#comment-15502906 ] Dirk Rudolph edited comment on SLING-4443 at 9/19/16 9:51 AM: -- What about

[jira] [Commented] (SLING-4443) Whitespace removal for Sightly HTML output

[ https://issues.apache.org/jira/browse/SLING-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502906#comment-15502906 ] Dirk Rudolph commented on SLING-4443: - What about implementing a {{CommandHandler}} similar to

Re: Clarification on https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html

This also does not seem to be 100% correct. Just think about the following example: There is a resource named "/a/b.c". Then the decomposition is as follows: For "/a/b.c.html" the resource path would be "/a/b.c" and the extension would be "html", selectors would be null and suffix null. For

Re: [i18n] IT Tests failing in reactor build

>> Hi, >> >> for quiet some time now, it seems that the IT tests of the i18n module >> fail in reactor build (at least, Jenkins seems to fail all the time). >> Interestingly, I can only reproduce this from time to time. However when >> it fails, it fails with: >> >> Tests run: 3, Failures: 0,

Clarification on https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html

I would like to extend the documentation in https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html a bit. Basically for the Resource Path section it says: Resource Path - The longest substring of the request URL such that the resource path is either the complete

[RESULT] [VOTE] Release Apache Sling JUnit Core 1.0.18, JUnit Tests Teleporter 1.0.8

Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Carsten Ziegeler, Stefan Egli, Daniel Klco I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. stefan

[RESULT] [VOTE] Release Apache Sling Testing Logging Mock 2.0.0, JCR Mock 1.1.16, OSGi Mock 1.8.0, OSGi Mock 2.1.0, Sling Mock 1.8.0, Sling Mock 2.1.0, Sling Mock Oak 2.0.2, Resource Builder 1.0.0, Se

Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Carsten Ziegeler, Stefan Egli I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. stefan

Re: [i18n] IT Tests failing in reactor build

> Hi, > > for quiet some time now, it seems that the IT tests of the i18n module > fail in reactor build (at least, Jenkins seems to fail all the time). > Interestingly, I can only reproduce this from time to time. However when > it fails, it fails with: > > Tests run: 3, Failures: 0, Errors: 2,

[RESULT][VOTE] Release Apache Sling Authentication Service 1.3.20

the vote passed with 5 +1 binding votes regards antonio

[i18n] IT Tests failing in reactor build

Hi, for quiet some time now, it seems that the IT tests of the i18n module fail in reactor build (at least, Jenkins seems to fail all the time). Interestingly, I can only reproduce this from time to time. However when it fails, it fails with: Tests run: 3, Failures: 0, Errors: 2, Skipped: 0,