• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Component/s: msbuild-plugin
• Labels:

  None
• Environment:

  Jenkins V1.580, Windows 7 64bit.
  MSBuild V 4.0.30319.18408
  .Net Framework V4.0.30319.18444

[JENKINS-24753] MSBuild fails with error "fatal error C1090: PDB API call failed, error code '23'"

Sanketh PB created issue - 2014-09-18 03:56

Sanketh PB made changes - 2014-09-18 04:45

Description

Original: VS2010 C++, C# build fails with error fatal error C1090: PDB API call failed, error code '23' when run using MSBuild plugin. The build passes if run using command line (Windows Batch Command)

New: VS2010 C++, C# build fails with error fatal error C1090: PDB API call failed, error code '23' when run using MSBuild plugin. Parameters: /m /p:Configuration=Release /p:Platform=win32 The build passes if run using command line (Windows Batch Command)

Collapse comment: Daniel Beck added a comment - 2014-09-18 16:56

Daniel Beck added a comment - 2014-09-18 16:56

Does this occur every time when building in Jenkins? Are you building multiple VS projects in parallel when this occurs? Try not doing that.

Expand comment: Daniel Beck added a comment - 2014-09-18 16:56

Daniel Beck added a comment - 2014-09-18 16:56 Does this occur every time when building in Jenkins? Are you building multiple VS projects in parallel when this occurs? Try not doing that.

Collapse comment: Sanketh PB added a comment - 2014-09-18 17:55

Sanketh PB added a comment - 2014-09-18 17:55

This happens atleast twice in 8 builds. We build many projects in parallel.
Our intention of using msbuild is to improve the speed and reduce build time by parallelization. I am not sure why this issue occurs.

Expand comment: Sanketh PB added a comment - 2014-09-18 17:55

Sanketh PB added a comment - 2014-09-18 17:55 This happens atleast twice in 8 builds. We build many projects in parallel. Our intention of using msbuild is to improve the speed and reduce build time by parallelization. I am not sure why this issue occurs.

Collapse comment: Daniel Beck added a comment - 2014-09-18 18:38

Daniel Beck added a comment - 2014-09-18 18:38

Duplicates JENKINS-9104.

Expand comment: Daniel Beck added a comment - 2014-09-18 18:38

Daniel Beck added a comment - 2014-09-18 18:38 Duplicates JENKINS-9104 .

Daniel Beck made changes - 2014-09-18 18:38

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Daniel Beck made changes - 2014-09-18 18:39

Link

New: This issue duplicates JENKINS-9104 [ JENKINS-9104 ]

R. Tyler Croy made changes - 2016-07-25 23:56

Workflow

Original: JNJira [ 157790 ]

New: JNJira + In-Review [ 195828 ]

Collapse comment: David Aldrich added a comment - 2018-04-25 17:10

David Aldrich added a comment - 2018-04-25 17:10

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?

Expand comment: David Aldrich added a comment - 2018-04-25 17:10

David Aldrich added a comment - 2018-04-25 17:10 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?