2019.1 - 'New' UI vs. 'Classic' UI's 'Run' button issue

I have an issue with the 'New' vs. 'Classic' UI and how it displays the 'Run' button.

Classic UI's Run button 

In the 'Classic' UI, we always see the 'Run' button along with the three dots (...) next to it.  Pressing the 'Run' button vs. the three dots displays different dialog windows.  Our build process depends on the behavior of just the 'Run' button dialog as we have several 'prompt' parameters setup that display in that dialog.  If you press the three dots (...) instead of 'Run' you get a different dialog listing ALL the parameters.  (Which can be confusing).

In the 'New' UI, on SOME of our TeamCity servers, we do NOT see both of these options.  It displays a 'Run...' button without the 2nd three dot option.

New UI's Run button (Missing three dots)

If the 'Run...' button is pressed, we get the behavior of the Classic UI's dialog with all the parameters, instead of just the parameters setup as 'prompt'.

On another one of our servers (all of them running build 2019.1), the 'New' UI's 'Run' button is different.

New UI's Run button (Including three dots)

I can't find what is controlling this behavior.  Does anybody know why this would be different, or what setting is causing it to hide this option vs. showing it?  On both servers my account is setup as a System Administrator, so it should have all the permissions.  I need to figure this out as if there is going to be a transition to the 'New' UI we would want to continue to use the 'prompt' parameter behavior.

Thanks in advance for the help.

Jim

0
14 comments

Hi Jim!

 

This is a bug in the experimental UI. We'll address it in the next bugfix release. You can check updates for the related issue in our YouTrack.

0

Thank you Nadia.  Would you happen to know why, on one of our three servers, this button does display correctly in the Experimental UI?  It's showing up this way on our 'longest running' server.  On our two newest servers we only have the one 'Run' option, instead of two.

Thanks again,

Jim

0

Jim, are the build configurations the same on all servers? The first one is always shown for me if there are any prompt parameters in a build configuration, the second one for all other cases. 

0

On the 'newer' servers, all the build projects contain 'Prompt' parameters, but only the 'Run...' button is shown on the 'New' UI.  On the older server, we have a ton of projects, none of which have a 'prompt' parameter, but they show the 'Run | ...' button on the 'New' UI.

I just wasn't sure what was causing the two servers to behave differently.

Thanks,

Jim

0

It's because the Run button was reworked in 2019.1 version in the experimental UI to support prompt parameter (what was actually the cause of the mentioned bug).

0

I think I may have confused the issue by referring to our servers as 'newer' and 'older'.

All three of our TeamCity servers are running build 2019.1.  Using the 'New experimental UI' on all of them, two of the servers have the wrong 'Run' button, but one of them actually has the correct one.  It seems like something on one of our servers, a setting, or a database value, is causing the button to work properly.  I was wondering if you knew what that might be?

I understand you found a bug here, which will be fixed in the next update.  That will solve our problem as we depend on that 'prompt' functionality.  If there was something I could change on the two servers that might make it function in the meantime I would do that, but it's not critical since we can still switch over to the 'Classic UI'.

Thanks again, sorry if I've confused the issue.

Jim

0

Hi Jim

Could you please execute "{URL}/app/rest/ui/buildTypes/id:{ID}/parameters?fields=property(type(rawValue))" for build configurations with different buttons but exactly the same configuration and attach here results? It will help us with further investigation. 

0

The configurations aren't 'exactly' the same for the two build configurations.  One of our servers shows the proper 'Run' button with the 'New' UI, for ALL of its build configurations, and another server shows the incorrect 'Run' button with the 'New' UI for ALL of its configurations.  They are both running the same build of TeamCity (2019.1) so it seems like there is something that's controlling that.  I did run this URL command on two different projects, one from each server.  That information is included below.

Project on Server that DOES show the 'Run | ...' button

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<properties>
<property/>
<property/>
<property/>
<property/>
<property/>
<property>
<type rawValue="checkbox uncheckedValue='%system.Platform.Configuration.Release%' display='normal' checkedValue='%system.Platform.Configuration.Retail%' description='Produces a retail build of the platform when checked' label='Retail Build'"/>
</property>
<property/>
<property>
<type rawValue="text display='normal' description='The SVN tag that will be used if tag build is true' label='Tag Build Label' validationMode='any'"/>
</property>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property>
<type rawValue="select data_6='Manitoba' data_5='Illinois' data_8='Oregon' data_7='Nevada' data_9='Quebec' display='normal' description='Sets the jurisdiction for a build' label='Jurisdiction' data_1='' label_1='All' data_4='Atlantic Lottery Corporation' data_3='Alberta'"/>
</property>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property>
<type rawValue="checkbox description='Create an SVN tag from the checked out source' label='Tag Build' uncheckedValue='false' display='normal' checkedValue='true'"/>
</property>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property>
<type rawValue="password display='hidden' description='The user account used to sync SVN and build the platform.' label='VLT Team Platform Build User'"/>
</property>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
</properties>
 
 
Project on server that does NOT show the 'Run | ...' button
 
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<properties>
<property/>
<property>
<type rawValue="text description='The subversion path to be used for the Monaco Platform build.' label='Monaco Subversion Path' validationMode='regex' display='prompt' validationMessage='The subversion path to be used for the Monaco Platform should be the part of the tag following |'https://svn.ali.global/PlatformArchitecture/Monaco/|'. Place ONLY that part in this field.'"/>
</property>
<property/>
<property/>
<property/>
<property/>
<property/>
<property>
<type rawValue="text regexp='(\d+\.)(\d+\.)(\d+\.)(\d+)' display='prompt' validationMessage='The version must be exactly 4 numbers, each one separate by a period |'.|' character. Example: 1.0.0.1' description='The Monaco build version number. Each part should be separated by a period (.). Example: 1.0.0.1' label='Product Version (Major.Minor.Revision.Build)' validationMode='regex'"/>
</property>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property/>
<property>
<type rawValue="text description='The path of the GDK to be used for the Runtime build.' label='GDK Subversion Path' validationMode='regex' display='prompt' validationMessage='The subversion path to be used for the GDK should be the part of the tag following |'https://svn.ali.global/nAble/|'. Place ONLY that part in this field.'"/>
</property>
<property/>
<property/>
<property/>
<property/>
</properties>
 
Thanks.  Let me know if this is helpful.
 
Jim
0

Hi Jim! 

 

I don't see any prompt parameters in the first build configuration. Could you please re-check, that this configuration has any? If yes could you please describe what is special about this configuration? Maybe, a parameter is set not in the configuration or this configuration is inherited from a template? 

0

The first one does not have any of those, only the 2nd.  On our main build server, which has 54 build configurations, none of them use the 'prompt' parameters.  We do that on our other two servers.

Is that the difference?  If the configurations use the 'prompt' parameters then the 'Run' button will be broken?

Jim

0

Yes, the difference is in prompt parameters. This new button is supposed to indicate that you cannot run a build without specifying some of the required parameters.  

0

I see.  And the bug is that instead of the limited UI with ONLY the 'prompt' parameters, it's instead showing the full list of parameters.  Is that correct?

0

I've noticed the Run button also doesn't display for projects in the new UI, I've had to redo some permissions for it to show up. Is this related?

0

Hi James, yes you're right. The bug was that we started to show all parameters instead of only prompt ones. 

Hi Daniel, this is another problem that was already fixed and will be released next week in 2019.1.1 version. Please, watch\vote for https://youtrack.jetbrains.com/issue/TW-60556.

0

Please sign in to leave a comment.