StartBuildPrecondition
I'm trying to use the groovy plug for setting a precondition to a build configuration, but it doesn't seem to work.
How can I tell if the plugin is even installed and if a build configuration is using a lock?
Is it supposed to create a .BuildServer/_groovyPlug_ folder, because I have none.
TeamCity 4.5.5 (build 9103).
Please sign in to leave a comment.
The question perhaps no longer relevant. If it's not please leave a comment or create a separate thread.
Kind regards,
Marina
Hi Marina.
Incidentally, I have the same issue. I'm unable to use this groovy plug.
I did exactly what it says in the instructions.
The groovy folder is created, and I added the "lock.writelock.<lockname>" and "lock.readlock.<lockname>" locks on the required build configurations.
The problem is that the locks do not prohibit the build from occurring.
Thanks!
Could you please atttach screenshots of the build conffiguration settings (props & environment step)?
Sure, I'm attaching 2 files - write.png holding the build configuration properties o
f the writing build, and read.png - that of the reading build.
For some weird reason, I also can't seem to remove system system properties (there are 3 properties, I tried to remove two of them but even though it wrote "removed successfully" they are still there).
Thanks!
Attachment(s):
write.png
read.png
According to this configuration there can be several Deploy CS builds running simultaneously unless there is a build running from the configuration with write lock. Build with write lock can only be one at a time. So how it is working in your case?
As for properties removing: are there any exceptions in the server log?
The deploys can happen simultaneously, and so we gave them a readlock. I have no idea why the readlock builds are still running with the writelock build. From what you can see, is it defined properly?
About the logs, I can't find any mention of a deletion of a property. I also edited one of them and it created a new one instead of replacing the old one. For some reason I did manage to remove this new property.
It looks like a bug. I would recommend to submit a bug report to our tracker and watch/vote for it.
http://youtrack.jetbrains.net/issue/TW-12934