When a build fails provide by default a build environment artifact.
Often my build fails because I've done something stupid but I can't find out what it is because I can't look at the build environment at the point it failed.
If I have the whole build environment to download as an archive afterwards I can do forensics to figure out what is wrong. At the moment I am a bit blind. I am sure I should have a folder available at the end of the build but the artifact builder finds nothing so I am not sure where the problem is.
Another possibility is a local version of appveyor for testing the build process before committing.
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 28 Apr, 2014 04:44 PM
Maybe you can use "on build error script" to do environment variables dump or "dir" to see what's there?
There is an idea to provide PowerShell interactive console for failed builds, for some time, but it's still an idea :)
2 Posted by bradphelan on 28 Apr, 2014 05:56 PM
Yeah I'd love shell access to the vm in event of failure to poke around.
3 Posted by Rifat Erdem Sah... on 26 Nov, 2014 03:42 PM
Maybe you can use "on build error script" to do environment variables dump or "dir" to see what's there?
>>> could you give an example
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:50 AM.