The deployment was prepared for Octopus 3.15. I change deployment script to
using System;
using System.Collections.Generic;
using System.Diagnostics;
using System.IO;
using System.Text;
string OctoVariable(string Name, string DefaultValue)
{
return Octopus.Parameters.ContainsKey(Name) ? Octopus.Parameters[Name] : DefaultValue;
}
void Deploy ()
{
try
{
var someVar = OctoVariable("Test","DefaultValue");
Console.WriteLine(someVar);
}
catch(Exception e)
{
Console.WriteLine($"Exception in deploy: {e.Message}\n{e.ToString()}");
throw e;
}
}
Deploy();
And now My errors are:
(3,12): error CS0103: The name `Octopus' does not exist in the current context
(3,51): error CS0103: The name `Octopus' does not exist in the current context
(1,2): error CS0103: The name `Octopus' does not exist in the current context
I think that is bug calamari. Will try remove new 4.X and run script on old 3.X
I’ve run the attached script on different versions of Octopus in the versions of 3.15.x, 4.x and 2018.2.1 without any issues.
So, could you please send through some more information for me please.
What version was the script originally running on? (You mentioned 3.15, but what’s the full version)
What version did you upgrade to? (Looking at the log, it looks like you must’ve updated to at least2018.2.1 as that’s when we introduced the new package cache naming, i.e. <packageid>@S<versionnumber>@<guid>.<ext>)
What OS is your Linux target running, and what version of mono is installed?
Sorry for low detailed issue. Current Octopus Version is 2018.3.3
we trying deploy to Centos
>uname -a
3.10.0-514.21.1.el7.x86_64 #1 SMP Thu May 25 17:04:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)
We found that problem in mono update, previos success deployment was to mono 5.8.0.108, but We updated it to the latest available in the repo (5.10.0.160) and it brokes octopus deployment.
