Re: [VOTE] Release Apache Sling Engine 2.13.0
+1 Carsten Am 29.11.2022 um 07:25 schrieb Carsten Ziegeler: Hi, We solved 1 issue in this release https://issues.apache.org/jira/projects/SLING/versions/12352598 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2698 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 2698 /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 cziege...@apache.org
Re: [VOTE] Release Apache Sling Servlets Resolver 2.9.10
+1 regards, Karl On Wed, Nov 30, 2022 at 8:33 PM Eric Norman wrote: > +1 > > On Mon, Nov 28, 2022 at 10:26 PM Carsten Ziegeler > wrote: > > > Hi, > > > > We solved 1 issue in this release > > https://issues.apache.org/jira/projects/SLING/versions/12352599 > > > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2699 > > > > 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 2699 /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 > > cziege...@apache.org > > > -- Karl Pauls karlpa...@gmail.com
Re: [VOTE] Release Apache Sling Engine 2.13.0
+1 regards, Karl On Wed, Nov 30, 2022 at 8:32 PM Eric Norman wrote: > Hi Carsten, > > Thanks for the follow up. I'm satisfied with the explanation and > solutions. The tests are all working now for me. > > +1 for me. > > Regards, > Eric > > On Wed, Nov 30, 2022 at 3:57 AM Carsten Ziegeler > wrote: > > > Thanks Eric, > > > > the errors are caused by two things: > > a) wrongly written error handlers as part of the tests. As we document > > an error handler needs to set the status code (if different from 200). > > The test ones didn't do that. I fixed the error handlers. > > b) the other failing tests are actually testing what is now fixed in the > > engine. when a response can't be reset, an error handler must not output > > anything. However, some tests are checking this. Increasing the response > > buffer (which I did in the starter now for the tests), fixes that > problem. > > > > So I think, there is no problem with the new engine release. > > > > Regards > > Carsten > > > > Am 29.11.2022 um 20:12 schrieb Eric Norman: > > > -1 for me. > > > > > > Switching to this artifact introduces 7 new failures in the starter > > > integration tests that need to be remedied or explained. > > > > > > Most of the failures appear to be related to the wrong status code > > arriving > > > with the error pages. > > > > > > Regards, > > > Eric > > > > > > On Mon, Nov 28, 2022 at 10:25 PM Carsten Ziegeler < > cziege...@apache.org> > > > wrote: > > > > > >> Hi, > > >> > > >> We solved 1 issue in this release > > >> https://issues.apache.org/jira/projects/SLING/versions/12352598 > > >> > > >> > > >> Staging repository: > > >> > https://repository.apache.org/content/repositories/orgapachesling-2698 > > >> > > >> 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 2698 /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 > > >> cziege...@apache.org > > >> > > > > > > > -- > > Carsten Ziegeler > > Adobe > > cziege...@apache.org > > > -- Karl Pauls karlpa...@gmail.com
[GitHub] [sling-org-apache-sling-testing-rules] enapps-enorman commented on pull request #2: SLING-11679: Add rule for defining a custom user-agent
enapps-enorman commented on PR #2: URL: https://github.com/apache/sling-org-apache-sling-testing-rules/pull/2#issuecomment-1332657972 > junit5 migration would be a larger topic on its own FYI: I opened the SLING-11708 ticket for tracking junit5 compatibility separately. -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SLING-11708) Provide a junit5 compatible variation of the org-apache-sling-testing-rules project
[ https://issues.apache.org/jira/browse/SLING-11708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman updated SLING-11708: Summary: Provide a junit5 compatible variation of the org-apache-sling-testing-rules project (was: org-apache-sling-testing-rules) > Provide a junit5 compatible variation of the org-apache-sling-testing-rules > project > --- > > Key: SLING-11708 > URL: https://issues.apache.org/jira/browse/SLING-11708 > Project: Sling > Issue Type: New Feature >Reporter: Eric Norman >Priority: Major > Fix For: Apache Sling Testing Rules 2.0.2 > > > The sling specific rules in org-apache-sling-testing-rules would be only for > consumers who are still using junit4. > For those that have migrated to junit5, a > [BeforeEachCallback|https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/BeforeEachCallback.html] > extension would be needed instead of these rules. > Expected: > A junit5 compatible fork of the project should be provided, sharing as much > code as possible with the junit4 variation. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-11708) org-apache-sling-testing-rules
Eric Norman created SLING-11708: --- Summary: org-apache-sling-testing-rules Key: SLING-11708 URL: https://issues.apache.org/jira/browse/SLING-11708 Project: Sling Issue Type: New Feature Reporter: Eric Norman Fix For: Apache Sling Testing Rules 2.0.2 The sling specific rules in org-apache-sling-testing-rules would be only for consumers who are still using junit4. For those that have migrated to junit5, a [BeforeEachCallback|https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/BeforeEachCallback.html] extension would be needed instead of these rules. Expected: A junit5 compatible fork of the project should be provided, sharing as much code as possible with the junit4 variation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-11701) Starter CI builds are sometimes failing with an error about a conflict with the docker container name
[
https://issues.apache.org/jira/browse/SLING-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641517#comment-17641517
]
Eric Norman commented on SLING-11701:
-
[~rombert] Thanks. It looks like the last 2 ci builds look worked without any
errors.
> Starter CI builds are sometimes failing with an error about a conflict with
> the docker container name
> -
>
> Key: SLING-11701
> URL: https://issues.apache.org/jira/browse/SLING-11701
> Project: Sling
> Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The CI builds are sometimes failing with an error about a conflict with the
> docker container name
> *
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/]
> This error is logged:
> {noformat}
> [ERROR] DOCKER> I/O Error [Unable to create container for
> [apache/sling:snapshot] : {"message":"Conflict. The container name
> \"/sling-1\" is already in use by container
> \"561df86f937afdecddc271bf24a537c182c98bc266337e5eee0b679423710689\". You
> have to remove (or rename) that container to be able to reuse that name."}
> (Conflict: 409)]
> {noformat}
> The docker-maven-plugin documentation indicates that the containerNamePattern
> configuration is what determines the container name being launched.
> * [https://dmp.fabric8.io/#container-name]
> The documentation states that the default containerNamePattern value is
> "%n-%i". The "%i" segment of the pattern is supposed to be an index which is
> incremented if a container has already been created. But this doesn't seem
> to be working for us, so maybe a different value would work more reliably?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [VOTE] Release Apache Sling Servlets Resolver 2.9.10
+1 On Mon, Nov 28, 2022 at 10:26 PM Carsten Ziegeler wrote: > Hi, > > We solved 1 issue in this release > https://issues.apache.org/jira/projects/SLING/versions/12352599 > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2699 > > 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 2699 /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 > cziege...@apache.org >
Re: [VOTE] Release Apache Sling Engine 2.13.0
Hi Carsten, Thanks for the follow up. I'm satisfied with the explanation and solutions. The tests are all working now for me. +1 for me. Regards, Eric On Wed, Nov 30, 2022 at 3:57 AM Carsten Ziegeler wrote: > Thanks Eric, > > the errors are caused by two things: > a) wrongly written error handlers as part of the tests. As we document > an error handler needs to set the status code (if different from 200). > The test ones didn't do that. I fixed the error handlers. > b) the other failing tests are actually testing what is now fixed in the > engine. when a response can't be reset, an error handler must not output > anything. However, some tests are checking this. Increasing the response > buffer (which I did in the starter now for the tests), fixes that problem. > > So I think, there is no problem with the new engine release. > > Regards > Carsten > > Am 29.11.2022 um 20:12 schrieb Eric Norman: > > -1 for me. > > > > Switching to this artifact introduces 7 new failures in the starter > > integration tests that need to be remedied or explained. > > > > Most of the failures appear to be related to the wrong status code > arriving > > with the error pages. > > > > Regards, > > Eric > > > > On Mon, Nov 28, 2022 at 10:25 PM Carsten Ziegeler > > wrote: > > > >> Hi, > >> > >> We solved 1 issue in this release > >> https://issues.apache.org/jira/projects/SLING/versions/12352598 > >> > >> > >> Staging repository: > >> https://repository.apache.org/content/repositories/orgapachesling-2698 > >> > >> 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 2698 /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 > >> cziege...@apache.org > >> > > > > -- > Carsten Ziegeler > Adobe > cziege...@apache.org >
[jira] [Commented] (SLING-11707) Update Bnd to 6.4.0
[ https://issues.apache.org/jira/browse/SLING-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641488#comment-17641488 ] Konrad Windszus commented on SLING-11707: - Unfortunately hasn't hit Maven Central yet: [https://github.com/bndtools/bnd/issues/5442.] Hopefully should appear in the next few hours. > Update Bnd to 6.4.0 > --- > > Key: SLING-11707 > URL: https://issues.apache.org/jira/browse/SLING-11707 > Project: Sling > Issue Type: Improvement >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 50 > > > https://github.com/bndtools/bnd/releases/tag/6.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11707) Update Bnd to 6.4.0
[ https://issues.apache.org/jira/browse/SLING-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-11707. - Assignee: Konrad Windszus Resolution: Fixed Fixed in https://github.com/apache/sling-parent/commit/71c514c31db9d201e238aa6fb77d873a3c5ce0d9. > Update Bnd to 6.4.0 > --- > > Key: SLING-11707 > URL: https://issues.apache.org/jira/browse/SLING-11707 > Project: Sling > Issue Type: Improvement >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 50 > > > https://github.com/bndtools/bnd/releases/tag/6.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-11707) Update Bnd to 6.4.0
Konrad Windszus created SLING-11707: --- Summary: Update Bnd to 6.4.0 Key: SLING-11707 URL: https://issues.apache.org/jira/browse/SLING-11707 Project: Sling Issue Type: Improvement Reporter: Konrad Windszus Fix For: Parent 50 https://github.com/bndtools/bnd/releases/tag/6.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-11707) Update Bnd to 6.4.0
[ https://issues.apache.org/jira/browse/SLING-11707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-11707: Fix Version/s: Bundle Parent 50 (was: Parent 50) > Update Bnd to 6.4.0 > --- > > Key: SLING-11707 > URL: https://issues.apache.org/jira/browse/SLING-11707 > Project: Sling > Issue Type: Improvement >Reporter: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 50 > > > https://github.com/bndtools/bnd/releases/tag/6.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #543 is FIXED
Please see https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/543/ for details. No further emails will be sent until the status of the build is changed.
Re: [VOTE] Release Apache Sling Engine 2.13.0
Thanks Eric, the errors are caused by two things: a) wrongly written error handlers as part of the tests. As we document an error handler needs to set the status code (if different from 200). The test ones didn't do that. I fixed the error handlers. b) the other failing tests are actually testing what is now fixed in the engine. when a response can't be reset, an error handler must not output anything. However, some tests are checking this. Increasing the response buffer (which I did in the starter now for the tests), fixes that problem. So I think, there is no problem with the new engine release. Regards Carsten Am 29.11.2022 um 20:12 schrieb Eric Norman: -1 for me. Switching to this artifact introduces 7 new failures in the starter integration tests that need to be remedied or explained. Most of the failures appear to be related to the wrong status code arriving with the error pages. Regards, Eric On Mon, Nov 28, 2022 at 10:25 PM Carsten Ziegeler wrote: Hi, We solved 1 issue in this release https://issues.apache.org/jira/projects/SLING/versions/12352598 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2698 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 2698 /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 cziege...@apache.org -- Carsten Ziegeler Adobe cziege...@apache.org
Re: [VOTE] Release Apache Sling Servlets Resolver 2.9.10
+1 Carsten Am 29.11.2022 um 07:26 schrieb Carsten Ziegeler: Hi, We solved 1 issue in this release https://issues.apache.org/jira/projects/SLING/versions/12352599 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2699 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 2699 /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 cziege...@apache.org
Re: [Vote] Release Sling Testing Clients 3.0.18
+1 Andrei On Wed, 30 Nov 2022 at 10:58, Jörg Hoh wrote: > +1 > > > Am Mi., 30. Nov. 2022 um 10:57 Uhr schrieb Jörg Hoh < > jhoh...@googlemail.com > >: > > > We solved 1 issue in this release: > https://issues.apache.org/jira/projects/SLING/versions/12352343 > > > > > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2700/ > > > > 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 2700 /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. > > > > > > > > -- > > Cheers, > > Jörg Hoh, > > > > https://cqdump.joerghoh.de > > Twitter: @joerghoh > > > > > -- > Cheers, > Jörg Hoh, > > https://cqdump.joerghoh.de > Twitter: @joerghoh >
Re: [Vote] Release Sling Testing Clients 3.0.18
+1 Am Mi., 30. Nov. 2022 um 10:57 Uhr schrieb Jörg Hoh : > We solved 1 issue in this > release:https://issues.apache.org/jira/projects/SLING/versions/12352343 > > > Staging > repository:https://repository.apache.org/content/repositories/orgapachesling-2700/ > > 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 2700 /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. > > > > -- > Cheers, > Jörg Hoh, > > https://cqdump.joerghoh.de > Twitter: @joerghoh > -- Cheers, Jörg Hoh, https://cqdump.joerghoh.de Twitter: @joerghoh
[Vote] Release Sling Testing Clients 3.0.18
We solved 1 issue in this release:https://issues.apache.org/jira/projects/SLING/versions/12352343 Staging repository:https://repository.apache.org/content/repositories/orgapachesling-2700/ 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 2700 /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. -- Cheers, Jörg Hoh, https://cqdump.joerghoh.de Twitter: @joerghoh
[jira] [Comment Edited] (SLING-11701) Starter CI builds are sometimes failing with an error about a conflict with the docker container name
[
https://issues.apache.org/jira/browse/SLING-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641157#comment-17641157
]
Robert Munteanu edited comment on SLING-11701 at 11/30/22 8:43 AM:
---
This should have been fixed with [PR
#81|https://github.com/apache/sling-org-apache-sling-starter/pull/81] .
[~enorman] - please reopen if you still see the problem.
was (Author: rombert):
This should have been fixed with [PR
#81|https://github.com/apache/sling-org-apache-sling-starter/pull/81] .
[~enorman] - please reopen if you still se the problem/
> Starter CI builds are sometimes failing with an error about a conflict with
> the docker container name
> -
>
> Key: SLING-11701
> URL: https://issues.apache.org/jira/browse/SLING-11701
> Project: Sling
> Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The CI builds are sometimes failing with an error about a conflict with the
> docker container name
> *
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/]
> This error is logged:
> {noformat}
> [ERROR] DOCKER> I/O Error [Unable to create container for
> [apache/sling:snapshot] : {"message":"Conflict. The container name
> \"/sling-1\" is already in use by container
> \"561df86f937afdecddc271bf24a537c182c98bc266337e5eee0b679423710689\". You
> have to remove (or rename) that container to be able to reuse that name."}
> (Conflict: 409)]
> {noformat}
> The docker-maven-plugin documentation indicates that the containerNamePattern
> configuration is what determines the container name being launched.
> * [https://dmp.fabric8.io/#container-name]
> The documentation states that the default containerNamePattern value is
> "%n-%i". The "%i" segment of the pattern is supposed to be an index which is
> incremented if a container has already been created. But this doesn't seem
> to be working for us, so maybe a different value would work more reliably?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-11701) Starter CI builds are sometimes failing with an error about a conflict with the docker container name
[
https://issues.apache.org/jira/browse/SLING-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-11701.
-
Resolution: Fixed
This should have been fixed with [PR
#81|https://github.com/apache/sling-org-apache-sling-starter/pull/81] .
[~enorman] - please reopen if you still se the problem/
> Starter CI builds are sometimes failing with an error about a conflict with
> the docker container name
> -
>
> Key: SLING-11701
> URL: https://issues.apache.org/jira/browse/SLING-11701
> Project: Sling
> Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The CI builds are sometimes failing with an error about a conflict with the
> docker container name
> *
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/]
> This error is logged:
> {noformat}
> [ERROR] DOCKER> I/O Error [Unable to create container for
> [apache/sling:snapshot] : {"message":"Conflict. The container name
> \"/sling-1\" is already in use by container
> \"561df86f937afdecddc271bf24a537c182c98bc266337e5eee0b679423710689\". You
> have to remove (or rename) that container to be able to reuse that name."}
> (Conflict: 409)]
> {noformat}
> The docker-maven-plugin documentation indicates that the containerNamePattern
> configuration is what determines the container name being launched.
> * [https://dmp.fabric8.io/#container-name]
> The documentation states that the default containerNamePattern value is
> "%n-%i". The "%i" segment of the pattern is supposed to be an index which is
> incremented if a container has already been created. But this doesn't seem
> to be working for us, so maybe a different value would work more reliably?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [sling-org-apache-sling-starter] rombert merged pull request #81: SLING-11701 - Starter CI builds are sometimes failing with an error about a conflict with the docker container name
rombert merged PR #81: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/81 -- 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. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
