Update to support auth token format in 2018.1 #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Example of new format: Super user authentication token: 8888888888888881 (use empty username with the token as the password to access the server)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I attempted to install TC "2018.1" using these settings:
teamcity_server_version: "2018.1"
teamcity_server_sha256: "d16ec0a4693cf4203d5e201cedf00e7a1559efaec98f54d018e67a3a17ad893d"
The role was failing when on the "Create Admin User" step and I traced it to not having the proper auth token. From the logs I could see that the auth token in 2018.1 does not have double-quotes around it so the grep and cut were not working. I updated the auth token extraction step to support the new format. I have not tried this on an earlier TC build but I did locally test adding double-quotes on both sides of the token.