only_commits.files not honored
It feels like the appveyor.yaml only_commit.files rule doesn't always run.
We use a monorepo with tons of different projects. But the only_commit rule doesn't seem to be always honored. For instance this build was triggered when absolutely no files under {root}/backend/dashboard/
was changed.
See what files were changed by this commit here
What can we do to fix this? This causes our CI to get clogged with builds of the wrong projects and it's super annoying.
version: $(major).$(minor).$(patch).{build}
assembly_info:
patch: true
file: '**\AssemblyInfo.*'
assembly_version: '{version}'
assembly_file_version: '{version}'
assembly_informational_version: '{version}'
branches:
only:
- master
- staging
- production
skip_tags: true
image: Visual Studio 2017
configuration: Release
environment:
major: 1
minor: 0
patch: 127
cache:
- backend/dashboard/packages
only_commits:
files:
- backend/dashboard/
before_build:
- cmd: >-
cd backend/dashboard
nuget restore
build:
project: backend\dashboard\Ueat.Dashboard.Api\Ueat.Dashboard.Api.csproj
publish_wap: true
verbosity: minimal
deploy:
- provider: Environment
name: myenv
on:
branch: production
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by mperron on Mar 20, 2019 @ 08:02 PM
(updated the above post)
Support Staff 2 Posted by Owen McDonnell on Mar 21, 2019 @ 04:06 AM
Can you link to a specific build that this occured on?
3 Posted by mperron on Mar 21, 2019 @ 03:21 PM
Yes I can, this one for instance: https://ci.appveyor.com/project/Cyprex/ueat-6s2du/builds/23255703.
It looks like the AppVeyor build failed to read the
appveyor.yaml
file, even if it's definitely there.4 Posted by mperron on Mar 21, 2019 @ 03:23 PM
Here is another example: https://ci.appveyor.com/project/Cyprex/ueat-59s6o/builds/23255210.
This time we don't have the
appveyor.yaml
not found error, it's theSpecify which project or solution file to use because the folder contains more than one project or solution file.
variant.5 Posted by mperron on Mar 21, 2019 @ 04:26 PM
(deleted)
6 Posted by Ilya Finkelshte... on Mar 21, 2019 @ 05:44 PM
Can you please open https://ci.appveyor.com/account/Cyprex/authorizations, and check Bitbucket authorization? Revoke and authorize Bitbucket again if needed (this will not break any settings).
7 Posted by mperron on Mar 21, 2019 @ 08:34 PM
Thansk Ilya, we're trying this now.
8 Posted by mperron on Mar 29, 2019 @ 05:07 PM
Hey Ilya, this seems to have fixed all of our issues. Thanks!
9 Posted by Ilya Finkelshte... on Mar 29, 2019 @ 05:11 PM
Great, thanks for the update!
Ilya Finkelshteyn closed this discussion on Mar 29, 2019 @ 05:11 PM.