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. 
   
   If you are expecting to see Build Scans from this build, unfortunately you 
will not, because @jprinet is creating this PR from a fork. Forks will not have 
access to the GE_ACCESS_TOKEN secret since they are not part of the ASF 
organization. In fact, what you might instead see is a warning about failing to 
publish a build scan.
   
   I would remove that most recent commit. If you would like to verify the 
publication of the build scan, you may push @jprinet's branch to the 
`apache/logging-log4j2` and run it from there.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to