github-actions[bot] merged PR #2637:
URL: https://github.com/apache/logging-log4j2/pull/2637
--
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: notificatio
ppkarwasz commented on PR #2637:
URL: https://github.com/apache/logging-log4j2/pull/2637#issuecomment-2148890242
@dependabot rebase
--
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 co
ppkarwasz commented on PR #2637:
URL: https://github.com/apache/logging-log4j2/pull/2637#issuecomment-2148862012
@dependabot rebase
--
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 co
ppkarwasz commented on PR #2641:
URL: https://github.com/apache/logging-log4j2/pull/2641#issuecomment-2148440553
@clayburn,
Thanks, I fixed it in efb4a0e93b732710a30c9d0dcb643fad96fc6b8d.
We'll test the "Predictive Test Selection" feature for a couple of weeks and
then we'll st
clayburn commented on PR #2641:
URL: https://github.com/apache/logging-log4j2/pull/2641#issuecomment-2148408013
The reusable workflow may change what needs to happen here:
https://docs.github.com/en/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow
ppkarwasz merged PR #2641:
URL: https://github.com/apache/logging-log4j2/pull/2641
--
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: notifications-unsubsc
ppkarwasz commented on PR #2641:
URL: https://github.com/apache/logging-log4j2/pull/2641#issuecomment-2148396826
@clayburn,
Thanks for the information.
We use reusable builds in our workflow, I am not entirely sure that the
reusable workflow will have access to the environment
clayburn commented on PR #2641:
URL: https://github.com/apache/logging-log4j2/pull/2641#issuecomment-2147956532
@ppkarwasz - I see your last commit to always publish from CI. This
shouldn't be necessary. Your CI builds will be authenticated by accessing the
`DEVELOCITY_ACCESS_KEY` env var.
jprinet opened a new pull request, #2641:
URL: https://github.com/apache/logging-log4j2/pull/2641
This PR will enable you to publish Build Scans to
[ge.apache.org](https://ge.apache.org/) as discussed with @ppkarwasz
## Description
This PR publishes a build scan for CI builds from
github-actions[bot] merged PR #129:
URL: https://github.com/apache/logging-log4j-tools/pull/129
--
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: notifica
Yavor16 opened a new issue, #2640:
URL: https://github.com/apache/logging-log4j2/issues/2640
## Description
We are using file logging because we have many steps and after every step
the logs are persisted in the database and the files are deleted. While our
application was running on
11 matches
Mail list logo
