Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to run custom builds on TeamCity 2018.1.2 #14

Open
Chhed13 opened this issue Sep 18, 2018 · 3 comments
Open

Fail to run custom builds on TeamCity 2018.1.2 #14

Chhed13 opened this issue Sep 18, 2018 · 3 comments

Comments

@Chhed13
Copy link

Chhed13 commented Sep 18, 2018

We just upgraded to TC 2018.1.2 and found that Matrix tab is broken.
I found unreleased fix, compile and apply new version, after that matrix tab is fixed, BUT any custom build (3 dots new run button) that contains Matrix throw an exception with huge stack trace.
Further more, if and matrix build was added in the queue, you can't open tab with queue
Log is here: TC-custom-build-exception.log
image
Is it possible to hot fix it? Rollback of a whole server is not what we want

@Chhed13
Copy link
Author

Chhed13 commented Sep 21, 2018

Hi, it looks we found the solution.
This exception was caused due to simultaneous upgrade of Matrix plugin from 1.0.0 to 1.0.2 (unreleased).
In version 1.0.1 parameter Const build parameters become mandatory, but we already had a lot of matrix configurations that didn't have it. After we fill this field everything becomes normal, but of course we had to suppress this exception and recompile plugin, before we had a chance to see what is going on.
The issue is solved

@presidentio
Copy link
Owner

@Chhed13 I'm sorry I don't have a time to work on this plugin. If you have time to prepare PR, I will be glad to review it and merge

Chhed13 added a commit to Chhed13/teamcity-matrix-build-plugin that referenced this issue Oct 17, 2018
This `catch` help to identify root cause of behavior from presidentio#14 preventing UI from showing long stack trace and show not settled pamas instead
@Chhed13
Copy link
Author

Chhed13 commented Oct 17, 2018

@presidentio that's ok. I made small PR that helped us to find the root cause and fix changed params

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants