Personal build Can not calculate a status for patch error

Answered

Hi, 

 

I'm running Teamcity server 2019.2.1 (build 71758) and have an issue with personal builds.

 

I've created a patch (.diff) file with my local changes. I can apply that patch to a personal build using the new workflow as long as these changes only involve code. However, my project includes other types of files (it's a Unity game project and I'm talking specificially about the .prefab files, which are essentially yaml files hidden under this extension). 

 

When I trigger a personal build with a .diff file that includes code and .prefab file changes, the build fails at step 'Updating sources: personal build patch'

Error while applying patch: Can not calculate a status for patch for {myfile}.prefab.


I don't get any more information than that and thus I'm not sure how to fix this issue (if it's even possible).

 

I would appreciate any input on this. I would love to get rid of our old, clunky solution of monitoring multiple streams for changes and creating kind of 'personal builds' that way. 

 

Cheers

3 comments
Comment actions Permalink

Hi Adrian,

 

sorry for the delay. How do you create this personal builds? Do you use the command line tool, or do you send them through a plugin on some specific IDE? Each method has to handle some of this actions on their own way due to their nature so having specific information is important in tracing where the issue resides.

 

I'm not particularly aware of any limitation to types of files so knowing that would be useful to at least try to replicate it locally.

0
Comment actions Permalink

Hi Denis,

 

I create the personal builds using the web frontend running in a Docker container on our local network. I follow the new personal builds workflow, and it works as long as my changes are code only.

0
Comment actions Permalink

Hi Adrian,

 

Thanks for the clarification. If you check our docs on that specific functionality (https://www.jetbrains.com/help/teamcity/2019.2/personal-build.html#PersonalBuild-DirectPatchUpload) you will see that there are some limitations to the formats we can support for it, so it would be helpful if you could be more descriptive about the exact issue. How do you exactly generate the patch, at which exact point it fails, etc.

 

It's likely that if you check the logs (build log, teamcity-vcs.log from either agent or server depending on where it actually fails to be processed) you will find a full stacktrace, and having some more context about the error (not just the line with the error message, but some of the previous log lines as well) might give us a better chance at identifying what the exact cause of the issue is.

0

Please sign in to leave a comment.