The githubbranchhash may set the branch also it prune ***/ from git branch but 
there is too many fallback and no verbosity that its impossible to check the 
path

Yep to ponder after 12.3 

Regards
Eric 


-----Message d'origine-----
De : Neil C Smith <[email protected]> 
Envoyé : mercredi 17 février 2021 14:48
À : dev <[email protected]>
Objet : Re: Branch 'origin/release123' is not having good pattern defaulting to 
'master'

On Wed, 17 Feb 2021 at 13:31, Eric Barboni <[email protected]> wrote:
>  In the ASF  multi branch build we use BRANCH_NAME not BRANCH. I'm not sure 
> there is a pattern detection it's more "is my branchname in the list of json 
> release keys". The jobs itself filter also to have release*** and master 
> branch only.

Thanks, Eric.  In the docs at
https://ci-builds.apache.org/env-vars.html/ it suggests that's only set for 
multibranch builds.

Is the BRANCH_NAME value actually passed to Ant?  I saw it in use in the 
Jenkins script, but couldn't see it passed to the build.

The section at 
https://github.com/apache/netbeans/blob/master/nbbuild/build.xml#L153
reads env.GIT_BRANCH.  Is that then what's picked up?  The docs has GIT_BRANCH 
- The remote branch name, if any. GIT_LOCAL_BRANCH - The local branch name 
being checked out, if applicable.  I wonder if that's what's causing the 
difference here?

Anyway, something to ponder after 12.3!  Let's not change anything right now.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Reply via email to