question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Commit messages made by maestro can be so long they break the build

See original GitHub issue

Example:

The generated commit message listed the complete history of the PR. This was so long, it caused MSBuild.exe to crash.

##[warning]Environment variable 'BUILD_SOURCEVERSIONMESSAGE' exceeds the maximum supported length. Environment variable length: 33743 , Maximum supported length: 32766

Downloading vswhere
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\msbuild.exe /nologo /bl:F:\workspace\_work\1\s\artifacts\log\Debug\ToolsetRestore.binlog /clp:Summary /clp:ErrorsOnly;NoSummary /m /nr:False /p:ContinuousIntegrationBuild=True /p:TreatWarningsAsErrors=true /p:__ToolsetLocationOutputFile=F:\workspace\_work\1\s\artifacts\toolset\1.0.0-beta.19225.5.txt /t:__WriteToolsetLocation /v:minimal /warnaserror F:\workspace\_work\1\s\artifacts\toolset\restore.proj
##[error]Unhandled Exception: Microsoft.Build.Shared.InternalErrorException: MSB0001: Internal MSBuild Error: Environment variable name or value is too long.
=============
System.ArgumentException: Environment variable name or value is too long.
   at System.Environment.SetEnvironmentVariable(String variable, String value)
   at Microsoft.Build.BackEnd.InProcNode.HandleShutdown(Exception& exception)

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
natemcmastercommented, May 6, 2019

Another build failure caused by the bot. https://dnceng.visualstudio.com/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=179049

cc @markwilkie for triage - the bot is making commits which are unbuildable in Azure Pipelines because the commit message is too long.

0reactions
markwilkiecommented, May 9, 2019
Read more comments on GitHub >

github_iconTop Results From Across the Web

Is there any way to incrementally build commit messages in ...
Make a code change; Update my commit message to describe change; Repeat 3 and 4 until commit is ready. Is there any mechanism...
Read more >
Git commit message convention that you can follow!
This post is a good intro to conventional commits, but I guess I don't agree that this is a "standard" -- it's popular,...
Read more >
Write joyous git commit messages - Joshua Tauberer - Medium
I have been known to write very long git commit messages. What follows is a guide to writing good commit messages in a...
Read more >
Git Commit Messages: Options and Approaches
Limitations: These commit messages can get long. That has two drawbacks. First, Github or your IDE may cut off the message. You may...
Read more >
When is a version control commit too large? [closed]
In a multi-person project, a greater chance that your commits will cause conflicts for other developers to resolve. It is harder to accurately ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found