Versioned Settings: "Pending UI changes detected" - what does it mean
In our TeamCity setup, we use Versioned Settings for all configuration for a number of reasons:
- we can revert changes if needed
- we can re-run old builds with the old settings if needed
- and... we can make changes to the configurations by committing our own configuration to the same VCS (Git in our case).
But... today we have seen a problem where the Versioned Settings page have the following status:
Current Status:
[15:38:28]: Pending UI changes detected, skip updating settings to revision 302956347a6eaba584e087c8e6215ee294ef8556
And it just stays in this state for a very long time. We cannot see any outstanding changes made via the UI that have not already been committed to the VCS (the persist queue is empty). Earlier today this also happened, but suddenly TC snapped out of it come and continued without any issues. (And that just happened again, while I was writing the above)
What can we do?
Please sign in to leave a comment.
You can check the teamcity-versioned-settings.log file in the logs folder for a bit of extra information.
This usually means that TeamCity has detected modifications on the UI and they haven't been committed, and it's trying to make sense of the differences, but it shouldn't take such a very long time. What version of TeamCity are you using?
If it takes way too long in that state please consider opening an issue in our tracker: https://youtrack.jetbrains.com/issues/TW
When it happens it takes forever... I have not yet found a way out of this state. We can still make changes to TeamCity via the UI, but the changes made via VCS (in our case Git), are never applied.
This is happening to me right now. Changes made in the UI don't make it to VCS, and changes made in VCS don't get observed by the UI any more. TeamCity Enterprise 2020.2.4 (build 86063)