On Wed, 17 Feb 2021 at 07:33, Jaroslav Tulach <[email protected]> wrote: > Shall I change something in the job configuration? Or shall we modify the > "pattern matching" to match `origin/release123`?
The latter might be useful to look at at a later date, but not an option now. I guess this might be triggered by a difference in environment variables between that job and the multibranch main job, looking at https://ci-builds.apache.org/env-vars.html/ Given that this is hopefully the last release with this built separately to the other artefacts, it's hopefully good enough to change the ant calls in the job configuration now - eg. ant build -Ddo.build.windows.launchers=true -Dmetabuild.branch=release123 Eric might be able to explain more how this is being picked up in the Jenkins build. Incidentally, looking back at earlier conversations, particularly between Eric and I, in the original merging of all this, we were looking for ways to make tags work (locally). Somehow we need to relate the tag back to the branch it's on. At the moment the branch and hash fallback parses the raw git files - eg. https://github.com/apache/netbeans/blob/master/nbbuild/antsrc/org/netbeans/nbbuild/GitBranchHash.java That was forked from an earlier HgID task to not rely on git. It's only meant as a fallback for local building really though - CI build scripts should be able to use git directly to set up the right env vars. 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
