PaulStovell

Typical Tentacle home directory (C:\Octopus on a web server, for example):

│   DeploymentJournal.xml
│   Tentacle-ApiTest-B.config
│
├───Applications
│   └───UAT
│       └───Acme.Web
│           ├───3.2.3
│           │       Default.aspx

PaulStovell

CREATE TABLE [Account] (
  [K] INTEGER IDENTITY(1,1) NOT NULL CONSTRAINT [IX_Account_K] UNIQUE CLUSTERED, 
  [Id] VARCHAR(50) NOT NULL CONSTRAINT [PK_Account_Id] PRIMARY KEY NONCLUSTERED, 
  [AccountType] VARCHAR(50) NOT NULL, 
  [Name] NVARCHAR(100) NOT NULL, 
  [EnvironmentIds] NVARCHAR(MAX) NOT NULL, 
  [JSON] NVARCHAR(MAX) NOT NULL
)
ALTER TABLE [Account] ADD CONSTRAINT [UQ_AccountUniqueName] UNIQUE([Name])

PaulStovell

scriptcs.exe hello.csx -loglevel trace -output scriptcs.log

PaulStovell

Communications between the Octopus Deploy server and Tentacles are secured using X.509 certificates. When Octopus is installed, a new self-signed certificate is generated. When Tentacles are installed, they also generate a new, self-signed certificate. In this post I'd like to discuss why we use self-signed certificates - after all, isn't that bad?

Background

When the Tentacle is registered in Octopus, the thumbprints (which identify the public key of the certificates) are exchanged - that is, you manually paste the Octopus thumbprint into the Tentacle setup wizard, and you manually verify the Tentacle's thumbprint in the Octopus UI. This screenshot is from Octopus 1.0 but the same concept exists in 2.6:

When Octopus connects to a Tentacle, it verifies that the Tentacle presents a certificate with the thumbprint it expects. Likewise, when Tentacle hand

PaulStovell

On the Octopus server

Octopus.Server.exe service --stop
Octopus.Server.exe configure --commsListenPort=10945
Octopus.Server.exe service --start

On Tentacle, find the Tentacle.config file, then find the Tentacle.Communication.TrustedOctopusServers section. You can change the address to use the port you want.

PaulStovell

http://www.abc.net.au/news/2014-11-24/mark-scott-announces-abc-job-cuts/5913082#abbott

First paragraph:

More than 400 ABC staff could lose their jobs as the public broadcaster moves to implement the $254 million the Federal Government will cut over the next five years.

In other words: 400 people being sacked because of the government.

Later in the same article:

PaulStovell

The SQL database table has 90,000 records.

Tested using:

ab.exe -c 1000 -n 1000 http://localhost:1234/
ab.exe -c 1000 -n 1000 http://localhost:1234/a

Output for synchronous version:

PaulStovell

# Create arguments as an array
$args = @("create-release", "--project", "My Project")

# Dynamically add arguments
$environments = @("My Environment", "Production")
foreach ($environment in $environments) 
{
    $args += "--environment"
    $args += $environment.Trim()
}

PaulStovell

using System;
using System.IO;
using System.Threading;

namespace PackagingDeadlock
{
    static class Program
    {
        // Set this to 100, and it works fine - all threads finish and exit
        // Set it to 10000, however, and it deadlocks, as per: http://support.microsoft.com/kb/951731

PaulStovell

Configuration SampleConfig
{
    param ($ApiKey, $OctopusServerUrl, $Environments, $Roles, $ListenPort)

    Import-DscResource -Module OctopusDSC

    Node "localhost"
    {
        cTentacleAgent OctopusTentacle 
        {