Artifact Migration Tool

Hi Blush,

Since those are Java properties, you can either use forward slashes or escape backward slashes. I.e.:

teamcity.storage.migration.artifact.directories=C:/TeamCity/Data/system/artifacts

or

teamcity.storage.migration.artifact.directories=C:\\TeamCity\\Data\\system\\artifacts

Let me know if that helps.

Hi Mikhail, yes that resolved one of the two issues (and helps me understand how it works!). My only remaining issue is with the token being rejected, but I can use it to call the Rest API with 200 status. I have an open support ticket. I'll post the resolution in this thread.

PS C:\Users\..\Downloads\artifacts-migration-tool\teamcity-artifacts-migration-tool-2022.10\bin> .\migrate -p MY_SPECIAL_PROJECT

Exception in thread "main" java.lang.IllegalArgumentException: Authentication token not found. Please provide a valid Te
amCity authentication token
        at jetbrains.buildServer.artifacts.migration.rest.TeamCityRestClient.<init>(TeamCityRestClient.kt:27)
        at jetbrains.buildServer.artifacts.migration.Main.run(Main.kt:102)
        at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:198)
        at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:18)
        at com.github.ajalt.clikt.core.CliktCommand.parse(CliktCommand.kt:395)
        at com.github.ajalt.clikt.core.CliktCommand.parse$default(CliktCommand.kt:392)
        at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:410)
        at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:435)
        at jetbrains.buildServer.artifacts.migration.MainKt.main(Main.kt:337)
PS C:\Users\..\Downloads\artifacts-migration-tool\teamcity-artifacts-migration-tool-2022.10\bin> Invoke-WebRequest
 -Headers @{"Authorization"="Bearer $tokenValue"} -Uri http://localhost/app/rest/builds


StatusCode        : 200
StatusDescription :
Content           : <?xml version="1.0" encoding="UTF-8" standalone="yes"?><builds count="100" href="/app/rest/builds"
                    nextHref="/app/rest/builds?locator=count:100,start:100"><build id="1011111"
                    buildTypeId="ApiGateway_A...
RawContent        : HTTP/1.1 200
                    TeamCity-Node-Id: MAIN_SERVER
                    Transfer-Encoding: chunked
                    Keep-Alive: timeout=60
                    Connection: keep-alive
                    Cache-Control: no-store
                    Content-Type: application/xml
                    Date: Wed, 22 Mar 2023...
Forms             : {}
Headers           : {[TeamCity-Node-Id, MAIN_SERVER], [Transfer-Encoding, chunked], [Keep-Alive, timeout=60],
                    [Connection, keep-alive]...}
Images            : {}
InputFields       : {}
Links             : {}
ParsedHtml        : System.__ComObject
RawContentLength  : 40400

Found that there was an invisible character pasted in with my token :( that fixed the auth issue.

I noticed an other issue. You can get an error that is hard to understand when running the migration tool:

Current target storage in project 'foo' is the same as the source storage

This is unclear since I clearly state in the application.properties I want the destination to be S3 bucket. What you need to do is update the TeamCity Project's Target Artifact Storage "Active" before you run the migration command. It makes sense but this is not documented.

Hi Mikhail,

There was definitely an invisible character when pasting from Mac to Windows. This usually happens when I create a file from Powershell and forget to encode with UTF-8 but this time I just when 100% UI based. Still after deleting the line and pasting again it worked. Same token value same parameter value (I searched and compared and the original and new matched equally). So it must have been an invisible character like ^m or similar.