amending #269 FTR

Probably fine so far as it goes but I suspect what you really wanted was

diff --git src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubAppCredentials.java src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubAppCredentials.java
index c4f45cf..f062de5 100644
--- src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubAppCredentials.java
+++ src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubAppCredentials.java
@@ -323,6 +323,11 @@ public class GitHubAppCredentials extends BaseStandardCredentials implements Sta
         return appID;
     }
 
+    @Override
+    public boolean isUsernameSecret() {
+        return false;
+    }
+
     @NonNull
     public synchronized GitHubAppCredentials withOwner(@NonNull String owner) {
         if (this.owner != null) {

Care to test & file ^^^?

I suspect what you really wanted was

+    @Override
+    public boolean isUsernameSecret() {
+        return false;
+    }

I'm new to Jenkins code, but if I interpret this correctly, this is absolutely what we want: https://issues.jenkins.io/browse/JENKINS-66675

Care to test & file ^^^?

@jglick Tested ✔️

Being you the author of the fix, it'd be more appropriate if you file the PR yourself. There is the already mentioned issue https://issues.jenkins.io/browse/JENKINS-66675 reporting on this. I have edited it to reflect that the component github-branch-source-plugin is also affected.

@jglick is there any update on this? this is messing up a few of our build logs

@schiasileon do you have some one-character passwords?

…is it x?

@schiasileon do you have some one-character passwords?

…is it x?

This mostly concerns us as we use a custom implementation that allows for multiline secrets from vault where we have some troubles with single character lines or empty lines being treated as separate secrets. Not a huge issue, but a fix would be nice.
Also on some instances we have empty secrets due to our CasC setup that cause this issue

a custom implementation

Of what?

multiline secrets from vault where we have some troubles with single character lines or empty lines being treated as separate secrets

Secret masking does not support multiline secrets. You have to use a secret file type. Perhaps this plugin should be improved to at least print a warning if a secret includes a line terminator, since at least its raw form cannot possibly match. (An input with a newline could still be masked in its Base64 form, but you are still in danger of accidentally printing it without Base64 encoding.)

we have empty secrets due to our CasC setup

AFAICT empty “secrets” are already ignored

@jglick, all output inside withCredentials is masked. This is hugely inconvenient to debug. Could someone please take a look at this?