Home → Questions →

How to debug appveyor.yml?

• Edit

Violet Giraffe

26 Jul, 2016 10:55 AM

Hello,

Is there a better way of debugging my configuration than spamming the repo with appveyor.yml commits?

P. S. Odd behavior: got a "Project file "xxx.smproj" is not a valid MSBuild project file which must be an XML." build error. .smproj is a project file for SourceMonitor (C++ code metrics software). Why is MSBuild trying to build it?.. Because it ends with *proj? Could it be a mistake in the script that searches for projects/solutions to use MSBuild on?
I can work around this using project: xxx.sln, but it's weird that I have to.

1. 1 Posted by Ilya Finkelshte... on 27 Jul, 2016 12:07 AM

   

   Hi Alex,

   I think that in addition to updating appveyor.yml you can insert blocking RDP statement at needed stage of the build https://www.appveyor.com/docs/how-to/rdp-to-build-worker. This may be useful if you need to explore build worker file system, or try some specific command on the build worker, and you don’t want to start new build for every flavor of command to try. Please note that RDP session does not have the same set of environment variable as a build process.

   What about .smproj I believe it is a bug and filed it here: https://github.com/appveyor/ci/issues/949. Thanks for catch!

   --Ilya.

   • Edit

2. 2 Posted by Violet Giraffe on 27 Jul, 2016 07:41 AM

   

   Thank you!
   A great service you've created here :)

   • Edit

3. 3 Posted by dragon788 on 07 Dec, 2016 07:23 PM

   

   Violet, you can also temporarily host the appveyor.yml in a Gist or on an http/s server during development and only check it into the repository once you are happy with the results. This would allow revision tracking (via Gist) plus it makes for an easy way to share the same config across multiple jobs.

   https://github.com/appveyor/ci/issues/1089#issuecomment-265544933

   • Edit

4. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:09 AM.