Read text file in Kotlin DSL from repo root

Avatar
Paetz89
Created

Hi,

I want to read a version text file into my Kotlin DSL configuration and use it for some other step.

Here is my project structure:

repo_root
| - version.txt
| - .teamcity
  | - settings.kts

The following Kotlin code

import java.io.File
...
steps {
  script {
    val version = File("../version.txt").readlines().joinToString(".")
    ...
  }
}

gives me the an access error: 

java.security.AccessControlException: access denied ("java.io.FilePermission" "../version.txt" "read")

while file permission is

-rw-rw-r--

So how can I read a text file that is located outside the .teamcity directory?

Thanks

Votes

0

Share

5 comments
Avatar
Fedor Rumyantsev
Created
Hello!

Unfortunately, anything outside of the `.teamcity` directory is inaccessible by the compiler for security reasons. Is it feasible to move the file into `.teamcity` directory?
0
Avatar
Paetz89
Created

Ok, got it.

if moving the version file to .teamcity directory is not possible, I can show some workaround via bash script in a script-step:

val buildCount = "%build.number%"
scriptContent = """
                    #!/bin/bash
                    version=<bash_magic> # Retrieve version from version file via bash processing
                    echo "##teamcity[buildNumber '${'$'}version_$buildCount']"
                """.trimIndent()

Take care of correct escaping of reserved bash characters $ and % since both are key characters in Kotlin and Teamcity, respectively:

- Escaping single $ becomes ${'$'}

- Escaping single % becomes %%%%

Say "123.456" is assigned to `version` in the bash script (retrieved from version file) and TeamCity's `build.number` is "1000", this last line of the bash script assigns "123.456_1000" to TeamCity's `build.number` environment variable that may then be used in another step as %build.number% for archiving, e.g.

0
Avatar
Fedor Rumyantsev
Created
Hello,

Yes, this would work just fine - thanks for sharing the example!
0
Avatar
Michael Hammond
Created

@...,

I have a similar scenario where I am trying to populate options for select parameters based on deployment configurations in my source code. The goal was to avoid having to maintain and synchronize the list in two places or force a user to type the value in manually.

Thanks,

Michael

0
Avatar
Fedor Rumyantsev
Created

Hello Michael,

Thank you for sharing your use case! I have just realized there is one more option present; if you have a teamcity.default.properties file in your VCS root, TeamCity will read the parameters from there and pass them into any build that is using this VCS root. This way, you could keep the version in this file and reference it in your build version parameter. Please refer to this article for more details on the usage of this logic.

0

Please sign in to leave a comment.