Minor issues with Teamcity Plugin

Legacy Uncategorised
1

I ran into one minor thing with the new TeamCity Plugin (version: 1.3.5.14)

If you create a release, but don’t want to deploy it anywhere (so don’t enter an environment) on the initial create of the step and click save the step will never persist. You can work around this though by creating the step with an environment and then going back and editing it, then it saves correctly.

EDIT: Nevermind on the API key I mentioned, that was from when I was using octo.exe directly, sorry :slight_smile:

UPDATE: Actually if you remove the deploy environment it can’t start the build. It throws the following error:

java.lang.NullPointerException at octopus.teamcity.agent.OctopusCommandBuilder.splitCommaSeparatedValues(OctopusCommandBuilder.java:40) at octopus.teamcity.agent.OctopusCreateReleaseBuildProcess$1.buildCommand(OctopusCreateReleaseBuildProcess.java:63) at octopus.teamcity.agent.OctopusCommandBuilder.buildMaskedCommand(OctopusCommandBuilder.java:28) at octopus.teamcity.agent.OctopusBuildProcess.startOcto(OctopusBuildProcess.java:77) at octopus.teamcity.agent.OctopusBuildProcess.start(OctopusBuildProcess.java:47) at jetbrains.buildServer.agent.impl.buildStages.runnerStages.start.CallRunnerStage.doBuildStage(CallRunnerStage.java:58) at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor$1.callStage(RunnerStagesExecutor.java:25) at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor$1.callStage(RunnerStagesExecutor.java:18) at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.callRunStage(StagesExecutor.java:78) at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.doStages(StagesExecutor.java:37) at jetbrains.buildServer.agent.impl.buildStages.RunnerStagesExecutor.doStages(RunnerStagesExecutor.java:18) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.RunnerContextExecutor.callRunnerStages(RunnerContextExecutor.java:43) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.StepExecutor.doProcessNextStep(StepExecutor.java:89) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.StepExecutor.processNextStep(StepExecutor.java:44) at jetbrains.buildServer.agent.impl.buildStages.startStages.steps.ForEachBuildRunnerStage.doBuildStage(ForEachBuildRunnerStage.java:77) at jetbrains.buildServer.agent.impl.buildStages.BuildStagesExecutor$1.callStage(BuildStagesExecutor.java:31) at jetbrains.buildServer.agent.impl.buildStages.BuildStagesExecutor$1.callStage(BuildStagesExecutor.java:24) at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.callRunStage(StagesExecutor.java:78) at jetbrains.buildServer.agent.impl.buildStages.StagesExecutor.doStages(StagesExecutor.java:37) at jetbrains.buildServer.agent.impl.buildStages.BuildStagesExecutor.doStages(BuildStagesExecutor.java:24) at jetbrains.buildServer.agent.impl.BuildRunAction.doStages(BuildRunAction.java:70) at jetbrains.buildServer.agent.impl.BuildRunAction.runBuild(BuildRunAction.java:50) at jetbrains.buildServer.agent.impl.BuildAgentImpl.doActualBuild(BuildAgentImpl.java:247) at jetbrains.buildServer.agent.impl.BuildAgentImpl.access$100(BuildAgentImpl.java:48) at jetbrains.buildServer.agent.impl.BuildAgentImpl$1.run(BuildAgentImpl.java:220) at java.lang.Thread.run(Unknown Source)

Thanks!

-Dan

2

Just wanted to confirm that we are experiencing the same issue. It works perfectly if an environment is defined for automatic deployment, but we get the same error as Dan when no environment is specified.

Cheers!

3

Thanks Dan, Brad, I’ve added this bug to the backlog. I’ll try to fix it soon.

https://trello.com/card/teamcity-plugin-should-allow-empty-deployment-environment/4e907de70880ba000079b75c/255

Paul

4

Hi Paul,

Same experience for us, we got the same error when the “Deploy to:” field does not have a value. It say’s in the field caption field that: **“Leave empty to create a release without deploying it.”

Thanks.

5

Thanks all, this bug is now fixed and the new TeamCity plugin can be downloaded from:

Paul

6

Awesome Paul, thanks very much for the incredibly quick response on this!