[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Roman Pickl edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
I used [~ext3h]'s solution:https://issues.jenkins-ci.org/browse/JENKINS-9104?focusedCommentId=360603&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360603 we solved it like this in a jenkins github multi-branch setup with jenkinsfiles: {code:java} bat """ mkdir tmp set _MSPDBSRV_ENDPOINT_= ${BUILD_TAG} set TMP=${Workspace}\\tmp set TEMP=${Workspace}\\tmp set TMPDIR=${Workspace}\\tmp build.bat """ {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.139260.1300499644000.14795.1587468902158%40Atlassian.JIRA.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Roman Pickl commented on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
I used Andreas Ringlstetter's solution: https://issues.jenkins-ci.org/browse/JENKINS-9104?focusedCommentId=360603&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360603 we solved it like this in a jenkins github multi-branch setup with jenkinsfiles: bat """ mkdir tmp set MSPDBSRV_ENDPOINT= ${BUILD_TAG} set TMP=${Workspace}tmp set TEMP=${Workspace}tmp set TMPDIR=${Workspace}tmp build.bat """
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.139260.1300499644000.14702.1587468841800%40Atlassian.JIRA.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Andreas Ringlstetter edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Solution is still the same, before invoking `msbuild`, set the following environment variables to something unique:{code:java}_MSPDBSRV_ENDPOINT_=TMP=TEMP=$TMPTMPDIR=$TMP{code}Once you have done that, you can launch as many parallel MSBuild instances as you like, even mixing different msbuild versions or whatever. They will not interfere in any way. Doing that on a regular base with mixed MSVC12, MSVC14 and MSVC15 toolchains on the same machine, and didn't have any issues since. The "official" fix for this problem (trying not to kill the job scheduler) is plain wrong, and causes massive issues. Mostly because MSBuild itself isn't exactly stable either when using the same job server for multiple parallel builds. And if the builds are using different toolchains, a crash is ensured.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Andreas Ringlstetter edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Solution is still the same, before invoking `msbuild`, set the following environment variables to something unique:{code:java}_MSPDBSRV_ENDPOINT_=TMP=TEMP=$TMPTMPDIR=$TMP{code}Once you have done that, you can launch as many parallel MSBuild instances as you like, even mixing different msbuild versions or whatever. They will not interfere in any way. Dong Doing that on a regular base with mixed MSVC12, MSVC14 and MSVC15 toolchains on the same machine, and didn't have any issues since.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Andreas Ringlstetter commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Solution is still the same, before invoking `msbuild`, set the following environment variables to something unique: _MSPDBSRV_ENDPOINT_= TMP= TEMP=$TMP TMPDIR=$TMP Once you have done that, you can launch as many parallel MSBuild instances as you like, even mixing different msbuild versions or whatever. They will not interfere in any way. Dong that on a regular base with mixed MSVC12, MSVC14 and MSVC15 toolchains on the same machine, and didn't have any issues since. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Bill Hoo commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed John Doe, totaly the same, we have many different jobs which use MSVC14 as toolchain, but now we can only perform one build at a time, its a huge waste of mashine resources ;( Hope it can be truly solved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title John Doe commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Bill Hoo, thanks for the tip! I was running VS 2017 (v141 toolset), but there were indeed two simultaneous jobs! So the workaround is to limit this agent to one job at a time. Pity, as it's a pretty powerful multicore server, but it's better than flaky builds. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Bill Hoo commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Same error with latest Jenkins ver. 2.150.3 The error is aways occured when running two jobs concurrently on the same agent with VS2015: fatal error C1090: PDB API Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title John Doe commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed I'm occasionally getting this error with the latest versions of Jenkins and all the plugins. It started in the recent months, haven't been a problem for a year before that. The problem seems to have NOT been resolved, or possibly re-emerged. What can I do, is there a workaround? Sporadic build failures for no reason are super annoying. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Daniel Beck resolved as Fixed Jenkins 2.120 contains a fix for the previous problem of the ProcessKillingVeto extension point not working on agents. Jenkins / JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Change By: Daniel Beck Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, s
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/ProcessTree.java test/src/test/java/hudson/util/ProcessTreeKillerTest.java http://jenkins-ci.org/commit/jenkins/3465da4764c322baf4fb5b90651ef6b9bcd409fb Log: Merge pull request #3419 from dwnusbaum/JENKINS-9104-test-fix Fix test failure by cleaning up static state after tests Compare: https://github.com/jenkinsci/jenkins/compare/ddbc4bbce7d3...3465da4764c3 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Code changed in jenkins User: Daniel Beck Path: content/_data/changelogs/weekly.yml http://jenkins-ci.org/commit/jenkins.io/62409d42a5769cac66337cbd4b5df5754f0e2384 Log: Merge pull request #1522 from daniel-beck/changelog-2.119-amended Remove JENKINS-9104 fix from release to unblock it Compare: https://github.com/jenkins-infra/jenkins.io/compare/58f029c79331...62409d42a576 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Code changed in jenkins User: Daniel Beck Path: content/_data/changelogs/weekly.yml http://jenkins-ci.org/commit/jenkins.io/0391fcb9b4c957e9e41fde03409de330a3de571d Log: Remove JENKINS-9104 fix from release to unblock it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
David Aldrich commented on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Please can anyone advise me how to set _MSPDBSRV_ENDPOINT_ with value BUILD_TAG in a pipeline declarative script? I don’t really understand the difference between defining and injecting an environment variable. I could do:
stage('build_VisualStudio') {
environment { _MSPDBSRV_ENDPOINT_=$BUILD_TAG }
etc.
Would that be sufficient or must environment variable injection be done in a different way?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Stefan Walter commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Hi Mark Grills, thanks a lot for your suggestion. It seems that this solved our issues. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Mark Grills commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Hi Stefan, refer my comments above. This fixed it for us. Cheers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Stefan Walter commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Is there any workaround to this issue, because it completely breaks our usage of Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Andy Neebel commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed I spent some more time chasing code and I have a suspicion as to the cause of the issue. In ProcessTree.java, there are two different functions that appear to need information from the master and yet operate in different manners getVeto() is how the whitelist extension is accessed to block the killing of the process. This function just gets the list as it exists, no attempt to go ask the master for any information. getKillers() is used to access the list of ProcessKillers if there are any classes implementing that extension point. This function gets the channel back to the master so it can ask for the master's list of classes implementing this extension. I think that getVeto() needs to have part of it implemented more like getKillers(), so that it will go to the master for the list. It may be also that the accessor belongs in ProcessTree instead, so that it caches the data and doesn't go back to the master quite as much. Then, I think the veto logic should work properly on both a master and a slave. Unfortuntely, this means a change to Jenkins core and upgrading the full instance to fix the issue instead of just a fix to the plugin itself. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Andy Neebel commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed We recently re-encountered this on our build network and I did some investigation, here's what I found: On the master node, the veto from MSBuild plugin works properly, I was able to confirm the log message show it. On a slave node, I do not see the log message from the veto. Instead I see a message that my process is being killed recursively (I was watching the process list to get the id during the build). It appears that the veto logic doesn't execute on the slave nodes. Is there something special that has to be done in order for it to be detected and executed there? I don't understand enough about how the remoting logic in Jenkins operates to know the answer to this. Most of the other work-arounds for this are ones that we cannot easily deploy in our environment. If this is truly the issue, does anyone have an idea what it would take to fix it and how long that would take to carry out? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/op
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Mark Grills edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
[~mwinter69], thanks for the pointer.We couldn't get it working with $JENKINS_COOKIE but managed to correct it by adding the following property via EnvInject prior to kicking off the build{noformat}_MSPDBSRV_ENDPOINT_=$BUILD_TAG{noformat}This resulted in a separate process being initiated for each build and no conflicts/error. Edit: Correction due to formatting . Refer below
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Mark Grills edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
[~mwinter69], thanks for the pointer.We couldn't get it working with $JENKINS_COOKIE but managed to correct it by adding the following property via EnvInject prior to kicking off the build {noformat} _MSPDBSRV_ENDPOINT_ {noformat} =$BUILD_TAGThis resulted in a separate process being initiated for each build and no conflicts/error.Edit: Correction. Refer below
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Mark Grills edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
[~mwinter69], thanks for the pointer.We couldn't get it working with $JENKINS_COOKIE but managed to correct it by adding the following property via EnvInject prior to kicking off the build{noformat}_MSPDBSRV_ENDPOINT_ {noformat} =$BUILD_TAG {noformat} This resulted in a separate process being initiated for each build and no conflicts/error. Edit: Correction. Refer below
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Mark Grills commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Apologies, yes an underscore at each end. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Daniel Fischer edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Is it It is {noformat} _MSPDBSRV_ENDPOINT_ {noformat} (with underlines) or is it not MSPDBSRV_ENDPOINT ? .Just realized it myself that it's a formatting issue. If you enclose the word in underlines it will get italicised and the underlines disappear. ;)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Daniel Fischer commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Is it MSPDBSRV_ENDPOINT (with underlines) or is it MSPDBSRV_ENDPOINT ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Mark Grills commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Markus Winter, thanks for the pointer. We couldn't get it working with $JENKINS_COOKIE but managed to correct it by adding the following property via EnvInject prior to kicking off the build MSPDBSRV_ENDPOINT=$BUILD_TAG This resulted in a separate process being initiated for each build and no conflicts/error. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Markus Winter edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
set the environment variable{{__MSPDBSRV_ENDPOINT__=$JENKINS_COOKIE}} (The variable starts and ends with a single '_') This will lead to separate instance of mspdbsrv being started.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Markus Winter edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
set the environment variable{{ _MSPDBSRV_ENDPOINT_ __MSPDBSRV_ENDPOINT__ =$JENKINS_COOKIE}}This will lead to separate instance of mspdbsrv being started.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Markus Winter edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
set the environment variable {{ _MSPDBSRV_ENDPOINT_=$JENKINS_COOKIE }} This will lead to separate instance of mspdbsrv being started.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Markus Winter commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed set the environment variable MSPDBSRV_ENDPOINT=$JENKINS_COOKIE This will lead to separate instance of mspdbsrv being started. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Daniel Beck commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Then install it. MSBuild will veto all mspdbsrv killing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Michael Brock commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Updating the msbuild plugin won't work in our situation. We run into this issue, but we don't have the plugin installed. Rather the issue comes for us in the Final Builder scripts we run via Jenkins that call msbuild. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Johannes Schmieder commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed As a workaround I have created a Jenkins Job that executes a Windows batch command on the jenkins node where Visual Studio is installed. The jenkins job triggers the batch command once a day and works in my environment for several years now. The batch command looks like this: set MSPDBSRV_EXE=mspdbsrv.exe set MSPDBSRV_PATH=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE set PATH=%MSPDBSRV_PATH%;%PATH% set ORIG_BUILD_ID=%BUILD_ID% set BUILD_ID=DoNotKillMe echo stop mspdbsrv.exe %MSPDBSRV_EXE% -stop echo wait 7 sec %windir%\system32\ping.exe -n 7 localhost> nul echo restart mspdbsrv.exe with a shutdowntime of 25 hours start /b %MSPDBSRV_EXE% -start -spawn -shutdowntime 9 set BUILD_ID=%ORIG_BUILD_ID% set ORIG_BUILD_ID= exit 0 What the batch command does is: stop the mspdbsrv.exe to free up resources start mspdbsrv.exe with BUILD_ID=DoNotKillMe and a shutdowntime of 25 hours, that leaks the mspdbsrv process without getting killed and it runs for 25 hours so that other build jobs can use the already running process What you maybe have to do is to change the Path to mspdbsrv -> set MSPDBSRV_PATH=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title James Telfer commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Daniel Beck no need to apologise, I appreciate you looking at it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Daniel Beck commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed *sigh* 1.26 is tagged in GitHub but no artifacts are uploaded. Looks like a failed release. Sorry about that. Note that MSBuild Plugin is almost certainly not currently maintained, as Gregory stopped working on his plugins, so if someone here wants to take over (Daniel Weber perhaps?) that should be possible. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title James Telfer commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed IMO, as soon as 1.26 is released. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Daniel Beck commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed msbuild-1.26 should contain the fix. Can we finally resolve this, or is something missing? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
James Telfer commented on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
FWIW, we implemented a workaround to this issue that doesn't involve wiping out the BUILD_ID variable (as we need to use it). Having a release with the Veto would be better, but this avoids random crashes in the meantime. Instead of allowing the MSBuild process to start the daemon itself, you cause the daemon to start using an environment that you choose. MSBuild then just uses the instance you started rather than starting its own. The Powershell we use is as follows. Use the Powershell plugin to run this as a step before the MSBuild plugin step (could be translated to Windows batch too if you like).
# https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller
var originalBuildID = $Env:BUILD_ID
$Env:BUILD_ID = "DoNotKillMe"
try
{
start mspdbsrv -argumentlist '-start','-spawn' -NoNewWindow
}
catch {}
$Env:BUILD_ID = originalBuildID
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://grou
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Lars Rosenboom commented on JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Still happening with Visual Studio 2010 (under Windows 7), BTW. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Pete W commented on JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Seconded Yimin Li's comment... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Yimin Li commented on JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Is it possible to add the workaround to the next Jenkins release and solve the problem later? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
[
https://issues.jenkins-ci.org/browse/JENKINS-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162171#comment-162171
]
Christoph Vogtländer commented on JENKINS-9104:
---
I would not recommend setting the shutdown time to such a high value.
mspdbsrv.exe tends to hang after some time because of handle leaks (at least
the version shipped with Visual Studio 2005) causing the compiler to exit with
error when trying to access pdb files. mspdbsrv process must be killed
manually, then.
> Visual studio builds started by Jenkins fail with "Fatal error C1090" because
> mspdbsrv.exe gets killed
> --
>
> Key: JENKINS-9104
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9104
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Windows XP, using MSBuild or devenv.exe to build MS
> Visual Studio Projects
>Reporter: Christoph Vogtländer
>Priority: Minor
>
> I run into errors when using a customized build system which uses Visual
> Studio's devenv.exe under the hood to compile VisualStudio 2005 projects
> (with VC++ compiler). When starting two parallel builds with Jenkins (on
> different code base) the second job will always fail with "Fatal error C1090:
> PDB API call failed, error code '23' : '(" in exactly the same second the
> first job finishes processing. Running both jobs outside Jenkins does not
> produce the error.
> This has also been reported for builds executed by MSBuild on the Jenkins
> user mailing list [1].
> I analysed this issue thoroughly and can track the problem down to the usage
> of mspdbsrv.exe. This program is automatically spawned when building a
> VisualStudio project. All Visual Studio instances normally share one common
> pdb-server which shutdown itself after a idle period (standard is 10
> minutes). "It ensures access to .pdb files is properly serialized in parallel
> builds when multiple instances of the compiler try to access the same .pdb
> file" [2].
> I assume that Jenkins does a clean up of its build environment when a
> automatically started job finishes (like as described at
> http://wiki.jenkins-ci.org/display/JENKINS/Aborting+a+build). I checked
> mspbsrv.exe with ProcessExplorer and the process indeed has a variable
> JENKINS_COOKIE/HUDSON_COOKIE set in its environment if started through
> Jenkins. Killing mspdbsrv.exe while projects are still connected will break
> compilation.
> Jenkins mustn't kill mspdbsrv.exe to be able to build more than one Visual
> Studio project at the same time.
> --
> [1]
> http://jenkins.361315.n4.nabble.com/MSBuild-fatal-errors-when-build-triggered-by-timer-td385181.html
> [2]
> http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/b1d1bceb-06b6-47ef-a0ea-23ea752e0c4f/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
[
https://issues.jenkins-ci.org/browse/JENKINS-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162154#comment-162154
]
Daniel Weber commented on JENKINS-9104:
---
We adopted Neil's workaround, but found a small issue. The problem is that
checking if
mspdbsrv is running does not reset its timeout. Consider this scenario where
the compiler
is first used 5 min after build start:
00:00 job A starts -> mspdbsrv not yet running -> mspdbsrv is started with
the changed BUILD_ID
01:00 job A finishes (mspdbsrv default timeout of 10 min starts here)
01:07 job B starts -> mspdbsrv still running -> mspdbsrv is not restarted
01:10 mspdbsrv timeout elapses, shuts down
01:12 job B tries to use mspdbsrv for the first time. As mspdbsrv is not
running, it starts a new
instance with unchanged BUILD_ID, which is what we wanted to avoid in
the first place.
I suggest to change the build script as follows
start mspdbsrv -start -spawn -shutdowntime 2147483647
This sets the shutdown time to the max value of 2^31-1. This timeout (~68
years) should be long enough :)
> Visual studio builds started by Jenkins fail with "Fatal error C1090" because
> mspdbsrv.exe gets killed
> --
>
> Key: JENKINS-9104
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9104
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Windows XP, using MSBuild or devenv.exe to build MS
> Visual Studio Projects
>Reporter: Christoph Vogtländer
>Priority: Minor
>
> I run into errors when using a customized build system which uses Visual
> Studio's devenv.exe under the hood to compile VisualStudio 2005 projects
> (with VC++ compiler). When starting two parallel builds with Jenkins (on
> different code base) the second job will always fail with "Fatal error C1090:
> PDB API call failed, error code '23' : '(" in exactly the same second the
> first job finishes processing. Running both jobs outside Jenkins does not
> produce the error.
> This has also been reported for builds executed by MSBuild on the Jenkins
> user mailing list [1].
> I analysed this issue thoroughly and can track the problem down to the usage
> of mspdbsrv.exe. This program is automatically spawned when building a
> VisualStudio project. All Visual Studio instances normally share one common
> pdb-server which shutdown itself after a idle period (standard is 10
> minutes). "It ensures access to .pdb files is properly serialized in parallel
> builds when multiple instances of the compiler try to access the same .pdb
> file" [2].
> I assume that Jenkins does a clean up of its build environment when a
> automatically started job finishes (like as described at
> http://wiki.jenkins-ci.org/display/JENKINS/Aborting+a+build). I checked
> mspbsrv.exe with ProcessExplorer and the process indeed has a variable
> JENKINS_COOKIE/HUDSON_COOKIE set in its environment if started through
> Jenkins. Killing mspdbsrv.exe while projects are still connected will break
> compilation.
> Jenkins mustn't kill mspdbsrv.exe to be able to build more than one Visual
> Studio project at the same time.
> --
> [1]
> http://jenkins.361315.n4.nabble.com/MSBuild-fatal-errors-when-build-triggered-by-timer-td385181.html
> [2]
> http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/b1d1bceb-06b6-47ef-a0ea-23ea752e0c4f/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
[
https://issues.jenkins-ci.org/browse/JENKINS-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161729#comment-161729
]
Neil Bird commented on JENKINS-9104:
Visual Studio is so ubiquitous that I personally think this could warrant a
special case built into Jenkins, but anyway this is what we have just started
doing (before calling devenv but after the MSC setup.bat has been called) to
work around this (for all Windows builds):
{quote}
:: PITA to keep MSPDBSRV alive
set ORIG_BUILD_ID=%BUILD_ID%
set BUILD_ID=DoNotKillMe
start mspdbsrv -start -spawn
set BUILD_ID=%ORIG_BUILD_ID%
set ORIG_BUILD_ID=
{quote}
It seems, from reading around, that the Jenkins process “tree” killer rummages
through the *whole* process tree looking for processes with the environment
variable BUILD_ID set to what Jenkins originally set it to, and killing any it
finds. The above temporarily changes that to something else (anything, you
could even just blank it), launches mspdbsrv manually (so it has the altered
env. var.) and then puts it back (to restore the usual no-resource-leak fix).
When you run mspdbsrv, it seems to immediately exit if there's already an
appropriate version running, so it doesn't matter having multiple jobs trying
to kick it off.
> Visual studio builds started by Jenkins fail with "Fatal error C1090" because
> mspdbsrv.exe gets killed
> --
>
> Key: JENKINS-9104
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9104
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Windows XP, using MSBuild or devenv.exe to build MS
> Visual Studio Projects
>Reporter: Christoph Vogtländer
>Priority: Minor
>
> I run into errors when using a customized build system which uses Visual
> Studio's devenv.exe under the hood to compile VisualStudio 2005 projects
> (with VC++ compiler). When starting two parallel builds with Jenkins (on
> different code base) the second job will always fail with "Fatal error C1090:
> PDB API call failed, error code '23' : '(" in exactly the same second the
> first job finishes processing. Running both jobs outside Jenkins does not
> produce the error.
> This has also been reported for builds executed by MSBuild on the Jenkins
> user mailing list [1].
> I analysed this issue thoroughly and can track the problem down to the usage
> of mspdbsrv.exe. This program is automatically spawned when building a
> VisualStudio project. All Visual Studio instances normally share one common
> pdb-server which shutdown itself after a idle period (standard is 10
> minutes). "It ensures access to .pdb files is properly serialized in parallel
> builds when multiple instances of the compiler try to access the same .pdb
> file" [2].
> I assume that Jenkins does a clean up of its build environment when a
> automatically started job finishes (like as described at
> http://wiki.jenkins-ci.org/display/JENKINS/Aborting+a+build). I checked
> mspbsrv.exe with ProcessExplorer and the process indeed has a variable
> JENKINS_COOKIE/HUDSON_COOKIE set in its environment if started through
> Jenkins. Killing mspdbsrv.exe while projects are still connected will break
> compilation.
> Jenkins mustn't kill mspdbsrv.exe to be able to build more than one Visual
> Studio project at the same time.
> --
> [1]
> http://jenkins.361315.n4.nabble.com/MSBuild-fatal-errors-when-build-triggered-by-timer-td385181.html
> [2]
> http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/b1d1bceb-06b6-47ef-a0ea-23ea752e0c4f/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
[
https://issues.jenkins-ci.org/browse/JENKINS-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161412#comment-161412
]
Daniel Weber commented on JENKINS-9104:
---
How about adding a configurable list of process names which shall not be killed
by the "process tree killer"?
The workaround described above leaves mspdbsrv.exe running, but also any other
"dangling" processes a build
might have left behind. I'd still like to use the process tree killer in
general, it should just not kill
mspdbsrv.exe.
> Visual studio builds started by Jenkins fail with "Fatal error C1090" because
> mspdbsrv.exe gets killed
> --
>
> Key: JENKINS-9104
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9104
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Windows XP, using MSBuild or devenv.exe to build MS
> Visual Studio Projects
>Reporter: Christoph Vogtländer
>Priority: Minor
>
> I run into errors when using a customized build system which uses Visual
> Studio's devenv.exe under the hood to compile VisualStudio 2005 projects
> (with VC++ compiler). When starting two parallel builds with Jenkins (on
> different code base) the second job will always fail with "Fatal error C1090:
> PDB API call failed, error code '23' : '(" in exactly the same second the
> first job finishes processing. Running both jobs outside Jenkins does not
> produce the error.
> This has also been reported for builds executed by MSBuild on the Jenkins
> user mailing list [1].
> I analysed this issue thoroughly and can track the problem down to the usage
> of mspdbsrv.exe. This program is automatically spawned when building a
> VisualStudio project. All Visual Studio instances normally share one common
> pdb-server which shutdown itself after a idle period (standard is 10
> minutes). "It ensures access to .pdb files is properly serialized in parallel
> builds when multiple instances of the compiler try to access the same .pdb
> file" [2].
> I assume that Jenkins does a clean up of its build environment when a
> automatically started job finishes (like as described at
> http://wiki.jenkins-ci.org/display/JENKINS/Aborting+a+build). I checked
> mspbsrv.exe with ProcessExplorer and the process indeed has a variable
> JENKINS_COOKIE/HUDSON_COOKIE set in its environment if started through
> Jenkins. Killing mspdbsrv.exe while projects are still connected will break
> compilation.
> Jenkins mustn't kill mspdbsrv.exe to be able to build more than one Visual
> Studio project at the same time.
> --
> [1]
> http://jenkins.361315.n4.nabble.com/MSBuild-fatal-errors-when-build-triggered-by-timer-td385181.html
> [2]
> http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/b1d1bceb-06b6-47ef-a0ea-23ea752e0c4f/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
[
https://issues.jenkins-ci.org/browse/JENKINS-9104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159695#comment-159695
]
chanti vlad commented on JENKINS-9104:
--
"Jenkins mustn't kill mspdbsrv.exe to be able to build more than one Visual
Studio project at the same time."
Although i will try the indicated workaround, i think this would be good to
have it as a feature somewhere, maybe in the node configuration?
> Visual studio builds started by Jenkins fail with "Fatal error C1090" because
> mspdbsrv.exe gets killed
> --
>
> Key: JENKINS-9104
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9104
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Windows XP, using MSBuild or devenv.exe to build MS
> Visual Studio Projects
>Reporter: Christoph Vogtländer
>Priority: Minor
>
> I run into errors when using a customized build system which uses Visual
> Studio's devenv.exe under the hood to compile VisualStudio 2005 projects
> (with VC++ compiler). When starting two parallel builds with Jenkins (on
> different code base) the second job will always fail with "Fatal error C1090:
> PDB API call failed, error code '23' : '(" in exactly the same second the
> first job finishes processing. Running both jobs outside Jenkins does not
> produce the error.
> This has also been reported for builds executed by MSBuild on the Jenkins
> user mailing list [1].
> I analysed this issue thoroughly and can track the problem down to the usage
> of mspdbsrv.exe. This program is automatically spawned when building a
> VisualStudio project. All Visual Studio instances normally share one common
> pdb-server which shutdown itself after a idle period (standard is 10
> minutes). "It ensures access to .pdb files is properly serialized in parallel
> builds when multiple instances of the compiler try to access the same .pdb
> file" [2].
> I assume that Jenkins does a clean up of its build environment when a
> automatically started job finishes (like as described at
> http://wiki.jenkins-ci.org/display/JENKINS/Aborting+a+build). I checked
> mspbsrv.exe with ProcessExplorer and the process indeed has a variable
> JENKINS_COOKIE/HUDSON_COOKIE set in its environment if started through
> Jenkins. Killing mspdbsrv.exe while projects are still connected will break
> compilation.
> Jenkins mustn't kill mspdbsrv.exe to be able to build more than one Visual
> Studio project at the same time.
> --
> [1]
> http://jenkins.361315.n4.nabble.com/MSBuild-fatal-errors-when-build-triggered-by-timer-td385181.html
> [2]
> http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/b1d1bceb-06b6-47ef-a0ea-23ea752e0c4f/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
