Appear to be building a project which is excluded via release configuration?
Hi,
We have a strange issue whereby we are having build errors on a project.
The build itself is being requested to package artefacts ready to be deploy via Web Deploy and we build the main bulk of the project fine (the actual bit we appear to only require!). Once this is built, the job moves onto trying to build another section which is actually excluded from being necessary in our release configuration. Upon trying to build this artefact, the job fails.
Is there any information that I can offer to clear the water on this and move towards a solution? This is the tail-end of the log (I can upload the whole file if needed?) and reprinted below.
... 8015 Discovering tests...Done
8016 Packaging artifacts...Done
8017 Uploading artifact adazzleMediaAppWeb.zip (63.7 MB)...Done
8018 Could not find file
'C:\Users\appveyor\AppData\Local\Temp\fscw1c6yuc\ThirtyTwoBit.zip'.
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
Support Staff 1 Posted by Feodor Fitsner on 17 Jun, 2014 05:01 PM
Hi Adam,
So, as I correctly understand you've set "Package web application" flag to automatically build packages. Then for release configuration that Web app project in the solution is excluded from build thus package is not generated, but AppVeyor is still trying to collect that non-existing artifact, correct?
2 Posted by Adam on 18 Jun, 2014 08:14 AM
Exactly that.
We're seeing everything build correctly in VS locally and TeamCity handles the builds for us as expected. AppVeyor, on the other hand, seems to believe that this project needs to be built, is trying to build it and then failing. While this wouldn't be a problem in itself, as the project is unneeded, this then fails the build on AppVeyor and means we cannot use that build in a deployment scenario.
Support Staff 3 Posted by Feodor Fitsner on 18 Jun, 2014 05:16 PM
OK, I see. I will add an issue to fix that. In the meantime I'd recommend you to disable automatic packaging and do that with your own msbuild command depending on current configuration.
Support Staff 4 Posted by Feodor Fitsner on 18 Jun, 2014 05:20 PM
This article could help: http://vishaljoshi.blogspot.ca/2009/02/web-packaging-creating-web-p...
5 Posted by Adam on 19 Jun, 2014 10:32 AM
Thanks Feodor.
In the mean time, we have removed the troublesome project from the build and that completed successfully (looks like we were failing on the very last step!). I'd appreciate an update once the issue has been resolved.
Support Staff 6 Posted by Feodor Fitsner on 19 Jun, 2014 02:34 PM
Sure, I'll let you know when it's fixed.
- Feodor
Support Staff 7 Posted by Feodor Fitsner on 27 Jul, 2014 09:41 AM
Hi Adam,
It's been fixed and update deployed. You can give it another try.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:46 AM.