Describe the bug
When adding a new Blazor UI project,the generated BuildAndPublish.yml is not triggered as expected.
The root cause is the use of a variables in the 'paths' part of the trigger.
By design, variables cannot be used in that context because they are evaluated AFTER the build is triggered.
In the sample below, the use of $(servicename) does not work - sadly. Instead, use the hard-coded path (under FE) encoded when adding the blazor project.
trigger:
branches:
include:
main
release/*
develop/*
paths:
include:
FE/$(servicename)/*
Shared/*
BE/Yarp/Sdks/*
Other issue (see extract below): the same variable is used further is this yaml file but is not declared (so, the build will fail).
Please declare the variable or use the hard-coded value.
Describe the bug When adding a new Blazor UI project,the generated BuildAndPublish.yml is not triggered as expected.
The root cause is the use of a variables in the 'paths' part of the trigger. By design, variables cannot be used in that context because they are evaluated AFTER the build is triggered.
In the sample below, the use of $(servicename) does not work - sadly. Instead, use the hard-coded path (under FE) encoded when adding the blazor project.
trigger: branches: include:
Other issue (see extract below): the same variable is used further is this yaml file but is not declared (so, the build will fail). Please declare the variable or use the hard-coded value.
stages:
To Reproduce When a PR related to the FE part is merged in the develop/1.0 branch (for example), the build is not triggered.
Expected behavior The filter in the build trigger should work when part of the code under FE/ is updated.
Desktop: