Category: Uncategorized

Here is a PowerShell build script for creating NuGet packages on a Jenkins server. It restores and builds a .NET solution, packs the project with dotnet pack, and pushes the package to your NuGet server.

I recently had to rewrite my build scripts when moving Jenkins from one server to another, and this time I went all out with variables. The script reads the Jenkins WORKSPACE and JOB_NAME environment variables plus VERSION and SLN_NAME job parameters. Replace the NuGet path, server URL and API key placeholders with your own. See also multi-project build scripts for Jenkins.

Write-Host "This Script is for Compiling Nuget Packages"

# Print environment details
Write-Host "VERSION                : $env:VERSION"
Write-Host "WORK SPACE PATH        : $ENV:WORKSPACE"
$version = "$env:VERSION"

# Define solutionName, solutionDir, projectDir, and projectName
$solutionName = $env:SLN_NAME
Write-Host "SOLUTION NAME          : $solutionName"
$solutionDir = $ENV:WORKSPACE
Write-Host "SOLUTION DIRECTORY     : $solutionDir"
$projectDir = "$ENV:WORKSPACE\$ENV:JOB_NAME"
Write-Host "PROJECT DIRECTORY      : $projectDir"
$projectName = $ENV:JOB_NAME
Write-Host "PROJECT NAME           : $ENV:JOB_NAME"

# Define flags for nuget operations (not currently utilized properly except for display)
$nugetPack = $true
Write-Host "NUGET PACK             : $nugetPack"
$nugetDeploy = $true
Write-Host "NUGET DEPLOY           : $nugetDeploy"

# Target framework (only utilized for display)
$framework = "net8.0"
Write-Host "TARGET FRAMEWORK       : $framework"

# Change to the $ENV:Workspace (ensure that we are in the workspace directory)
cd $ENV:Workspace
Write-Host "CURRENT DIRECTORY           : $ENV:Workspace"

# Define NUGET paths, csproject name and directory, and NUGET Server URL and API Key
$nugetEXE = D:\build_tools\"your nuget location"\nuget.exe
$csprojectPath = "$projectDir\$ENV:JOB_NAME.csproj"
Write-Host "PROJECT PATH           : $csprojectPath"
$nugetPackageDir = "$solutionDir\nupkgs"
Write-Host "NUGET PACKAGE DIRECTORY: $nugetPackageDir"
$nugetPublishDir = "$solutionDir\publish"
Write-Host "NUGET PUBLISH DIRECTORY: $nugetPublishDir"
$NugetServer = "https://"your nuget package server"/nuget"
Write-Host "NUGET SERVER URL       : $NugetServer"
$NugetServerKey = "your nuget server key"
Write-Host "NUGET SERVER KEY       : $NugetServerKey"

# Clean and Create necessary directories
if (Test-Path $nugetPackageDir) {
    Write-Host "DOTNET BUILD: Delete Directory $nugetPackageDir"
    Remove-Item -Path $nugetPackageDir -Recurse -Force
}

Write-Host "DOTNET BUILD: Create Directory $nugetPackageDir"
New-Item -ItemType Directory -Force -Path $nugetPackageDir

if (Test-Path $nugetPublishDir) {
    Write-Host "DOTNET BUILD: Delete Directory $nugetPublishDir"
    Remove-Item -Path $nugetPublishDir -Recurse -Force
}

Write-Host "DOTNET BUILD: Create Directory $nugetPublishDir"
New-Item -ItemType Directory -Force -Path $nugetPublishDir

# Define the Solution location
$slnPath = "$solutionDir\$solutionName.sln"
Write-Host "Solution Path         : $slnPath"
# Run dotnet restore
Write-Host "DOTNET BUILD: dotnet restore $slnPath"
dotnet restore $slnPath -v q

# Run dotnet build
Write-Host "DOTNET BUILD: dotnet build $csprojectPath -c Release --version-suffix $version --verbosity quiet"
dotnet build $csprojectPath -c Release --version-suffix $version --verbosity quiet

# Change to the $projectDir (ensure that we are in the project directory)
cd $projectDir
Write-Host "CURRENT DIRECTORY           : $projectDir"

# Run nuget pack
Write-Host "DOTNET BUILD: dotnet pack -c Release --no-restore -o $nugetPackageDir --version-suffix $version --verbosity quiet"
dotnet pack -c Release --no-restore -o $nugetPackageDir --version-suffix $version --verbosity quiet

# Display completed tasks
Write-Host "DOTNET BUILD: Completed Tasks"

# Define the NuGet Package Name
$NugetPackageName = "$ENV:JOB_NAME.$version.nupkg"
Write-Host "NUGET: Nuget Package Name: $NugetPackageName"

#Change to the $nugetPackageDir (ensure that we are in the NUPKG directory)
cd $nugetPackageDir
Write-Host "CURRENT PATH           : $nugetPackageDir"
  
# Push the package to the NuGet server
Write-Host "NUGET: Push "$NugetPackageName" -k $NugetServerKey -s $NugetServer"
dotnet nuget push "$NugetPackageName" -k $NugetServerKey -s $NugetServer


# Display completed tasks
Write-Host "NUGET: Completed Tasks"

Here are the simple steps to install the Check_MK agent on a Red Hat (or CentOS) 6.x Linux server. Replace %checkmkurl% with the address of your Check_MK server.

1. Install xinetd and Add the Agent Service

Save the Check_MK xinetd config file as /tmp/xinetd.conf, then:

yum -y install xinetd
cd /tmp
cp xinetd.conf /etc/xinetd.d/check_mk

2. Download and Install the Agent

wget http://%checkmkurl%/check_mk/agents/check_mk_agent.linux
cp check_mk_agent.linux check_mk_agent
chmod 776 check_mk_agent
cp /tmp/check_mk_agent /usr/bin/check_mk_agent

3. Add the Inventory Plugin

mkdir /usr/lib/check_mk_agent
mkdir /usr/lib/check_mk_agent/plugins
cd /usr/lib/check_mk_agent/plugins
wget http://%checkmkurl%/check_mk/agents/plugins/mk_inventory.linux
cp mk_inventory.linux mk_inventory.sh
chmod 776 mk_inventory.sh

4. Restart xinetd

/etc/init.d/xinetd restart

Running Debian? See installing the Check_MK agent on Debian Linux.

This is the xinetd configuration for the Check_MK Linux agent. Save it as /etc/xinetd.d/check_mk. It runs the agent on TCP port 6556 whenever your monitoring server connects. Before you use it, replace %YOUR IP ADDRESSES HERE!!!% on the only_from line with the IP address(es) of your monitoring server, so no one else can query the agent.

For the full install steps, see installing the Check_MK agent on Red Hat Linux.

# This file is part of Check_MK (GNU General Public License v2).
# Copyright Mathias Kettner 2014. The official homepage is at http://mathias-kettner.de/check_mk.

service check_mk
{
type = UNLISTED
port = 6556
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/bin/check_mk_agent

# If you use fully redundant monitoring and poll the client
# from more then one monitoring servers in parallel you might
# want to use the agent cache wrapper:
#server = /usr/bin/check_mk_caching_agent

# configure the IP address(es) of your Nagios server here:
only_from = 127.0.0.1 %YOUR IP ADDRESSES HERE!!!%

# Don't be too verbose. Don't log every check. This might be
# commented out for debugging. If this option is commented out
# the default options will be used for this service.
log_on_success =

disable = no
}

SSL 3.0 is insecure and should be turned off on any IIS web server. Here’s how to disable it through the registry on Windows Server 2008 R2 or 2012. For background, see the SSL 3.0 information disclosure vulnerability.

Step-by-Step

1. Open the Registry Editor as administrator: on the Start screen type regedit.exe, right-click it, and click Run as administrator.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols.
   
3. Right-click Protocols and click New > Key. Name the key SSL 3.0.
   
4. Right-click the new SSL 3.0 key, click New > Key, and name it Client.
   
5. Right-click SSL 3.0 again, click New > Key, and name it Server.
   
6. Under SSL 3.0, right-click Client, click New > DWORD (32-bit) Value, and name it DisabledByDefault.
   
7. Double-click DisabledByDefault, set Value data to 1, and click OK.
   
8. Under SSL 3.0, right-click Server, click New > DWORD (32-bit) Value, and name it Enabled.
   
9. Double-click Enabled, leave Value data at 0, and click OK.
   
10. Restart the server.

SSL 3.0 is now disabled. To confirm it, see this quick way to test for SSLv3.

If you’ve forgotten the password for the super admin account on an RSA SecurID Authentication Manager appliance, you can recover by creating a temporary super admin account (for example, tempAdmin) from the command line, then using it to reset the original account’s password.

Create a Temporary Super Admin

Run the super admin restoration utility from the CLI or a serial console:

1. Log in with the emcsrv account and enter its password when prompted.
2. Switch to root, entering the password when prompted.
3. Change to the directory that holds the restoration utility and create the temporary account.

% sudo su
% cd /usr/opt/rsa/am/utils
% ./rsautil restore-admin -u [tempadmin_name] -p [password]

Enter Master Password: **********
A temporary admin will be created with the user ID 'tempAdmin'.
Are you sure you want to continue (Y/N): Y
Admin created successfully.

• [tempadmin_name] is the temporary super admin account to create.
• [password] is the password for that temporary account.

Reset the Original Password

4. Log into the Security Console with the temporary account.
5. Go to Identity > Users > Manage Existing and search for the super admin account whose password needs resetting.
6. From the context menu, select Edit and scroll to the Password section.
7. Enter the new password for the super admin account and click Save.

Note: The temporary super admin account expires after 24 hours.

Oh yeah, I got it working! I installed the Jetpack plugin on my WordPress site to connect it with Facebook, and with Google+ too, so new posts are shared to both automatically.