[jira] [Commented] (SLING-9389) Distribution Event Packages should contain queue item creation time
[ https://issues.apache.org/jira/browse/SLING-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17117406#comment-17117406 ] Harsh Chiki commented on SLING-9389: [~marett], request you to kindly review the PRs shared, or please let us know if you have questions/concerns with the requirement. cc: [~cschneider], [~ashishc], [~shgu...@adobe.com] > Distribution Event Packages should contain queue item creation time > --- > > Key: SLING-9389 > URL: https://issues.apache.org/jira/browse/SLING-9389 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Harsh Chiki >Assignee: Timothee Maret >Priority: Major > Attachments: image-2020-04-30-10-28-58-011.png, scdapi.patch, > scdcore.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > > Currently the Distribution Event package contains the following details: > * Distribution Component Name > * Distribution Component Kind > * Distribution Type > * Distribution Paths > > Improvement aims at adding the queue item creation time, essentially when the > the item was creation for the first time, and enqueue into the queue. The > value does not change over retries (on failure). > > The purpose to get this detail is to be able to capture metrics at the > consumer level. The consumers could have an event handler, which can capture > the duration which turns out to be (NOW MINUS queue item creation time thrown > in the distribution event package); NOW being the current time in the event > handler (consumer). > > \cc: [~shgu...@adobe.com], [~ashishc] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [sling-org-apache-sling-distribution-core] harshchiki edited a comment on pull request #41: SLING-9389: Distribution Event Packages should contain queue item creation time
harshchiki edited a comment on pull request #41: URL: https://github.com/apache/sling-org-apache-sling-distribution-core/pull/41#issuecomment-634441515 This PR is failing on the missing `DistributionEventProperties.DISTRIBUTION_ENQUEUE_TIMESTAMP`(compilation error), which is proposed in https://github.com/apache/sling-org-apache-sling-distribution-api/pull/7 - IIUC, once that is merged, this should pass fine. Request the owners of the repo to kindly review. cc: @tmaret @cschneider This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-distribution-core] harshchiki commented on pull request #41: SLING-9389: Distribution Event Packages should contain queue item creation time
harshchiki commented on pull request #41: URL: https://github.com/apache/sling-org-apache-sling-distribution-core/pull/41#issuecomment-634441515 This PR is failing on the missing `DistributionEventProperties.DISTRIBUTION_ENQUEUE_TIMESTAMP`, which is proposed in https://github.com/apache/sling-org-apache-sling-distribution-api/pull/7 Request the owners of the repo to kindly review. cc: @tmaret @cschneider This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (SLING-9389) Distribution Event Packages should contain queue item creation time
[ https://issues.apache.org/jira/browse/SLING-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096378#comment-17096378 ] Harsh Chiki edited comment on SLING-9389 at 5/27/20, 5:42 AM: -- Hi [~marett], [~ashishc], I have raised the PRs: * [-https://github.com/apache/sling-org-apache-sling-distribution-api/pull/2-] * [https://github.com/apache/sling-org-apache-sling-distribution-api/pull/7] * [https://github.com/apache/sling-org-apache-sling-distribution-core/pull/41] Kindly review and share your feedback. Thanks _edit_: Updated PR links above. \cc: [~shgu...@adobe.com] was (Author: harshchiki): Hi [~marett], [~ashishc], I have raised the PRs: * [https://github.com/apache/sling-org-apache-sling-distribution-api/pull/2] * [https://github.com/apache/sling-org-apache-sling-distribution-core/pull/41] Kindly review and share your feedback. Thanks \cc: [~shgu...@adobe.com] > Distribution Event Packages should contain queue item creation time > --- > > Key: SLING-9389 > URL: https://issues.apache.org/jira/browse/SLING-9389 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Harsh Chiki >Assignee: Timothee Maret >Priority: Major > Attachments: image-2020-04-30-10-28-58-011.png, scdapi.patch, > scdcore.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently the Distribution Event package contains the following details: > * Distribution Component Name > * Distribution Component Kind > * Distribution Type > * Distribution Paths > > Improvement aims at adding the queue item creation time, essentially when the > the item was creation for the first time, and enqueue into the queue. The > value does not change over retries (on failure). > > The purpose to get this detail is to be able to capture metrics at the > consumer level. The consumers could have an event handler, which can capture > the duration which turns out to be (NOW MINUS queue item creation time thrown > in the distribution event package); NOW being the current time in the event > handler (consumer). > > \cc: [~shgu...@adobe.com], [~ashishc] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [sling-org-apache-sling-distribution-api] harshchiki commented on pull request #2: SLING-9389: Distribution Event Properties enhanced for holding queue item creation time stamp
harshchiki commented on pull request #2: URL: https://github.com/apache/sling-org-apache-sling-distribution-api/pull/2#issuecomment-634440712 Closing this PR in favour of https://github.com/apache/sling-org-apache-sling-distribution-api/pull/7. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-distribution-api] harshchiki opened a new pull request #7: SLING-9389: Distribution Event Properties enhanced for holding queue item creation time stamp
harshchiki opened a new pull request #7: URL: https://github.com/apache/sling-org-apache-sling-distribution-api/pull/7 In general, - Improvement aims at adding the queue item creation time, essentially when the the item was creation for the first time, and enqueue into the queue. - The purpose to get this detail is to be able to capture metrics at the consumer level. The consumers could have an event handler, which can capture the duration which turns out to be (NOW MINUS queue item creation time thrown in the distribution event package); NOW being the current time in the event handler (consumer). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-distribution-api] harshchiki closed pull request #2: SLING-9389: Distribution Event Properties enhanced for holding queue item creation time stamp
harshchiki closed pull request #2: URL: https://github.com/apache/sling-org-apache-sling-distribution-api/pull/2 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-superimposing] sonarcloud[bot] commented on pull request #1: API Upgrade
sonarcloud[bot] commented on pull request #1: URL: https://github.com/apache/sling-org-apache-sling-superimposing/pull/1#issuecomment-633727742 SonarCloud Quality Gate failed. [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=VULNERABILITY) (and [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=SECURITY_HOTSPOT) to review) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=CODE_SMELL) [10 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-superimposing=1=new_coverage=list) [45.7% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-superimposing=1=new_coverage=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-superimposing=1=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-superimposing=1=new_duplicated_lines_density=list) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-superimposing] rombert commented on pull request #1: API Upgrade
rombert commented on pull request #1: URL: https://github.com/apache/sling-org-apache-sling-superimposing/pull/1#issuecomment-633604698 Thanks for the update @saurabh-khare . As mentioned in the Jira issue, please use separate commits and individual Jira issues. I'll resume the review then. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-superimposing] sonarcloud[bot] removed a comment on pull request #1: API Upgrade
sonarcloud[bot] removed a comment on pull request #1: URL: https://github.com/apache/sling-org-apache-sling-superimposing/pull/1#issuecomment-633311013 SonarCloud Quality Gate failed. [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=BUG) [1 Bug](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=VULNERABILITY) (and [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=SECURITY_HOTSPOT) to review) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=CODE_SMELL) [15 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-superimposing=1=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-superimposing=1=new_coverage=list) [44.2% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-superimposing=1=new_coverage=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-superimposing=1=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-superimposing=1=new_duplicated_lines_density=list) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SLING-9447) Add packageId property to distribution events
[ https://issues.apache.org/jira/browse/SLING-9447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116967#comment-17116967 ] Timothee Maret commented on SLING-9447: --- [~cschneider] ping > Add packageId property to distribution events > - > > Key: SLING-9447 > URL: https://issues.apache.org/jira/browse/SLING-9447 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution API 0.4.0 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution API 0.4.2 > > > For all distribution events it is useful to track the package id. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SLING-9442) Complete the semantic definition of distribution events
[ https://issues.apache.org/jira/browse/SLING-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret resolved SLING-9442. --- Resolution: Fixed Resolved as fixed. > Complete the semantic definition of distribution events > - > > Key: SLING-9442 > URL: https://issues.apache.org/jira/browse/SLING-9442 > Project: Sling > Issue Type: Bug > Components: Content Distribution >Reporter: Timothee Maret >Assignee: Timothee Maret >Priority: Major > Fix For: Content Distribution API 0.4.2 > > > The description of [distribution > events|https://github.com/apache/sling-org-apache-sling-distribution-api/blob/master/src/main/java/org/apache/sling/distribution/event/DistributionEventTopics.java] > does not clearly document the conditions for raising the events. We should > extend the documentation both in the API and in the published documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9397) SAML2 Authentication Handler [initial submission]
[
https://issues.apache.org/jira/browse/SLING-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116944#comment-17116944
]
Robert Munteanu commented on SLING-9397:
[~cris_rockwell] - I'd like to create a local testing setup first. I think we
should also consider adding some integration tests against an external SAML IDP
running on localhost, either via docker or some sort of JUnit setup.
> SAML2 Authentication Handler [initial submission]
> -
>
> Key: SLING-9397
> URL: https://issues.apache.org/jira/browse/SLING-9397
> Project: Sling
> Issue Type: New Feature
> Components: Authentication
> Environment: localhost
>Reporter: Cris Rockwell
>Priority: Major
> Labels: SAML, authentification, security, user_management
> Original Estimate: 168h
> Time Spent: 1h
> Remaining Estimate: 167h
>
> Here is a pull request which adds an authentication handler for a SAML2
> Service Provider via the embedded OpenSAML V3 dependencies
> [https://github.com/apache/sling-whiteboard/pull/51]
>
> *TODO Before Initial*
> [X] Sync attributes released by the IDP
> [X] Confirm license and attribution
> "As the code is ASL2 and does not require a notice or anything else, we don't
> need to mention in. But I think its usually good style to do so and have a
> single sentence in our NOTICE that we include (modified) code from ... which
> has ASL2 as the license"
>
> *TODO After Initial*
> [ ] Get confirmation the project builds and operates as expected
> [X] Ensure that the NOTICE file is the correct one
> [ ] Testing setup ( documentation, local SAML provider, etc )
> [ ] Clarify whether we can depend on artifacts not deployed on Maven Central
> [ ] Review Web Browser SSO Profile Specification 4.1 and confirm all aspects
> * [https://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf]
> [ ] Consider whether use of {{SAML2ConfigService}} and
> {{SAML2ConfigServiceImpl}} is a good design or not.
> [ ] Get feedback whether README instructions are too much, too little,
> unclear, etc
> [ ] Decide whether to make signing and encryption optional. Currently it is
> required
> [ ] Find and fix any bugs
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-9397) SAML2 Authentication Handler [initial submission]
[
https://issues.apache.org/jira/browse/SLING-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-9397:
---
Description:
Here is a pull request which adds an authentication handler for a SAML2 Service
Provider via the embedded OpenSAML V3 dependencies
[https://github.com/apache/sling-whiteboard/pull/51]
*TODO Before Initial*
[X] Sync attributes released by the IDP
[X] Confirm license and attribution
"As the code is ASL2 and does not require a notice or anything else, we don't
need to mention in. But I think its usually good style to do so and have a
single sentence in our NOTICE that we include (modified) code from ... which
has ASL2 as the license"
*TODO After Initial*
[ ] Get confirmation the project builds and operates as expected
[X] Ensure that the NOTICE file is the correct one
[ ] Testing setup ( documentation, local SAML provider, etc )
[ ] Clarify whether we can depend on artifacts not deployed on Maven Central
[ ] Review Web Browser SSO Profile Specification 4.1 and confirm all aspects
* [https://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf]
[ ] Consider whether use of {{SAML2ConfigService}} and
{{SAML2ConfigServiceImpl}} is a good design or not.
[ ] Get feedback whether README instructions are too much, too little, unclear,
etc
[ ] Decide whether to make signing and encryption optional. Currently it is
required
[ ] Find and fix any bugs
was:
Here is a pull request which adds an authentication handler for a SAML2 Service
Provider via the embedded OpenSAML V3 dependencies
[https://github.com/apache/sling-whiteboard/pull/51]
*TODO Before Initial*
[X] Sync attributes released by the IDP
[X] Confirm license and attribution
"As the code is ASL2 and does not require a notice or anything else, we don't
need to mention in. But I think its usually good style to do so and have a
single sentence in our NOTICE that we include (modified) code from ... which
has ASL2 as the license"
*TODO After Initial*
[ ] Get confirmation the project builds and operates as expected
[X] Ensure that the NOTICE file is the correct one
[ ] Clarify whether we can depend on artifacts not deployed on Maven Central
[ ] Review Web Browser SSO Profile Specification 4.1 and confirm all aspects
* [https://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf]
[ ] Consider whether use of {{SAML2ConfigService}} and
{{SAML2ConfigServiceImpl}} is a good design or not.
[ ] Get feedback whether README instructions are too much, too little, unclear,
etc
[ ] Decide whether to make signing and encryption optional. Currently it is
required
[ ] Find and fix any bugs
> SAML2 Authentication Handler [initial submission]
> -
>
> Key: SLING-9397
> URL: https://issues.apache.org/jira/browse/SLING-9397
> Project: Sling
> Issue Type: New Feature
> Components: Authentication
> Environment: localhost
>Reporter: Cris Rockwell
>Priority: Major
> Labels: SAML, authentification, security, user_management
> Original Estimate: 168h
> Time Spent: 1h
> Remaining Estimate: 167h
>
> Here is a pull request which adds an authentication handler for a SAML2
> Service Provider via the embedded OpenSAML V3 dependencies
> [https://github.com/apache/sling-whiteboard/pull/51]
>
> *TODO Before Initial*
> [X] Sync attributes released by the IDP
> [X] Confirm license and attribution
> "As the code is ASL2 and does not require a notice or anything else, we don't
> need to mention in. But I think its usually good style to do so and have a
> single sentence in our NOTICE that we include (modified) code from ... which
> has ASL2 as the license"
>
> *TODO After Initial*
> [ ] Get confirmation the project builds and operates as expected
> [X] Ensure that the NOTICE file is the correct one
> [ ] Testing setup ( documentation, local SAML provider, etc )
> [ ] Clarify whether we can depend on artifacts not deployed on Maven Central
> [ ] Review Web Browser SSO Profile Specification 4.1 and confirm all aspects
> * [https://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf]
> [ ] Consider whether use of {{SAML2ConfigService}} and
> {{SAML2ConfigServiceImpl}} is a good design or not.
> [ ] Get feedback whether README instructions are too much, too little,
> unclear, etc
> [ ] Decide whether to make signing and encryption optional. Currently it is
> required
> [ ] Find and fix any bugs
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-9321) Update to declarative services 1.4
[ https://issues.apache.org/jira/browse/SLING-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-9321: -- Fix Version/s: (was: Content Distribution Journal Core 0.1.14) Content Distribution Journal Core 0.1.16 > Update to declarative services 1.4 > -- > > Key: SLING-9321 > URL: https://issues.apache.org/jira/browse/SLING-9321 > Project: Sling > Issue Type: Bug > Components: Content Distribution >Affects Versions: Content Distribution Journal Core 0.1.10 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.1.16 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #812 is BROKEN
[INFO]
[INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @
org.apache.sling.launchpad.testing ---
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.codehaus.groovy.reflection.CachedConstructor
(file:/home/jenkins/.m2/repository/org/codehaus/groovy/groovy-all-minimal/1.5.6/groovy-all-minimal-1.5.6.jar)
to constructor java.io.File(java.lang.String,java.io.File)
WARNING: Please consider reporting this to the maintainers of
org.codehaus.groovy.reflection.CachedConstructor
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
[INFO] Checking legal files in:
org.apache.sling.launchpad.testing-12-SNAPSHOT.jar
[INFO] Checking legal files in:
org.apache.sling.launchpad.testing-12-SNAPSHOT-sources.jar
[INFO]
[INFO] --- apache-rat-plugin:0.11:check (default) @
org.apache.sling.launchpad.testing ---
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: DEPENDENCIES
[INFO] Exclude: src/main/appended-resources/META-INF/*
[INFO] Exclude: velocity.log
[INFO] Exclude: target/*
[INFO] Exclude: README.md
[INFO] Exclude: maven-eclipse.xml
[INFO] Exclude: .*
[INFO] Exclude: .*/**
[INFO] Exclude: **/*.json
[INFO] Exclude: DEPENDENCIES
[INFO] Exclude: **/*.rej
[INFO] Exclude: hs_err_*.log
[INFO] Exclude: **/repository/index/*/index-details.txt
[INFO] Exclude: bnd.bnd
[INFO] 7 resources included (use -debug for more details)
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 6 licence.
[INFO]
[INFO] --- maven-failsafe-plugin:2.21.0:verify (default) @
org.apache.sling.launchpad.testing ---
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 05:59 min
[INFO] Finished at: 2020-05-26T13:35:14Z
[INFO]
[INFO] [jenkins-event-spy] Generated
/home/jenkins/jenkins-slave/workspace/e-sling-launchpad-testing_master@tmp/withMavenac99577b/maven-spy-20200526-132914-4267351362377615089812.log
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-failsafe-plugin:2.21.0:verify (default) on
project org.apache.sling.launchpad.testing: There are test failures.
[ERROR]
[ERROR] Please refer to
/home/jenkins/jenkins-slave/workspace/e-sling-launchpad-testing_master/target/failsafe-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[Pipeline] }
[withMaven] Publishers: Pipeline Graph Publisher: 7 ms, JGiven Publisher: 2 ms
[Pipeline] // withMaven
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] stage
[Pipeline] { (Notifications)
[Pipeline] echo
Status change is BROKEN, notifications will be sent.
[Pipeline] emailext
Re: [VOTE] Release Apache Sling Installer Factory Feature 0.4.0
+1 Carsten On 25.05.2020 12:30, Carsten Ziegeler wrote: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING-9470 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2268 You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2268 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org -- -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Updated] (SLING-9403) Filter status messages by subscriber agent
[ https://issues.apache.org/jira/browse/SLING-9403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-9403: -- Fix Version/s: (was: Content Distribution Journal Core 0.1.12) Content Distribution Journal Core 0.1.16 > Filter status messages by subscriber agent > -- > > Key: SLING-9403 > URL: https://issues.apache.org/jira/browse/SLING-9403 > Project: Sling > Issue Type: Bug > Components: Content Distribution >Reporter: Timothee Maret >Assignee: Timothee Maret >Priority: Major > Fix For: Content Distribution Journal Core 0.1.16 > > > Status messages are emit by editable subscriber agents. Multiple editable > agents may exist at the same time, e.g. when replacing services using a > rolling update strategy. Different editable agents may evolve differently and > thus the status messages are not interchangeable. > This issue tracks > 1. Identifying the subscriber agent producing the status messages > 2. Extending the staging precondition to filter by subscriber agent -- This message was sent by Atlassian Jira (v8.3.4#803005)
