A modern programming language that makes developers happier.

kotlinlang

Hi. Testing the waters here to see if anyone is still active here :grimacing:

I'm working on an internal DSL to make interfacing with TeamCity easier for our developers. It seems to run well enough when running the mvn:generate action on an actual pipeline, but writing test-code has proven to be quite the challenge. Even with this block
```    fun generate() {
        project {
            internalBuildTypes.forEach {
                buildType(it)
            }
        }
    }```
I get an error `Project builder is not provided` which I cannot get to the bottom off. Anyone have some pointer? Be happy to provide more code if needed!

You had a blog-post were you wrote some basic test-code for teamcity DSLs <@U0B99GN30>, maybe you have some pointers?

ahhh, TeamCity DSL.. long time no see :sweat_smile:

I doubt I can suggest the right thing from the top of my head. I’d need to allocate some time to recall the subject. But it’s best to ask someone from TeamCity devs about it. Let me ping someone in the team

Looking at <https://blog.jetbrains.com/teamcity/2019/05/configuration-as-code-part-6-testing-configuration-scripts/>


What if you configure this with an `object X: Project`, instead of `project {}` ?

the pipelines dsl did not exist at the time when I wrote the tutorial so I haven’t experimented with that in the tests

Thanks :pray:

Yeah, definitely found some quirks, but also found a workaround now. Rather than having an internal `private val project: Project` variable in my `PipelineBuilder` and appending the buildTypes onto that, I opted to use the same setup as the TeamCity dsl uses internally, by storing the buildTypes in the `PipelineBuilder` and then providing the projectbuilder directly in the `ProjectBuilder#generate` method above
```    fun generate(): Project {
        return Project {
            parameters.forEach { params.add(it) }
            this@PipelineBuilder.buildTypes.forEach(::buildType)
        }
    }```
This seems to work so I'll leave it at that for now, but if some of the devs stumble upon this I'll be happy to provide more :sweat_smile:

Thanks for some pointers <@U0B99GN30> :tada: Gotta say that having the option to build an internal DSL for teamcity stuff is pretty cool though :sweat_smile:

Just confirmed with devs - yeah, `project {}` cannot be used in tests because of the required builder. Makes sense to document it though.

Gotcha! Then it's even weirder that I got it to work I guess, but I'm happy for now :sweat_smile:

maybe there's an internal difference between the `Project {}` and the `project {}` builders :zany_face:

Right, then the solution makes sense at least :slightly_smiling_face: But yeh, having a sentence about that in the docs would be :100: