Gitlab CI变量未生效：部署成功但数据库连接字符串为空

It looks like your app isn't picking up the CONNECTION_STRING variable from GitLab CI, leading to that ArgumentNullException when EF Core tries to connect to MySQL. Let's break down the possible issues and fix them step by step:

1. Fix the Environment Variable Syntax #

You're using %CONNECTION_STRING% which is Windows CMD syntax, but most GitLab CI runners run on Linux (using bash). Switch to bash's variable syntax instead:

# Update your before_script command in .gitlab-ci.yml
dotnet user-secrets set "ConnectionString" "$CONNECTION_STRING"

If you're explicitly using a Windows runner, keep %CONNECTION_STRING%—but double-check your runner's OS first.

2. Verify the CI Variable Is Actually Being Passed #

First, confirm that GitLab is injecting the variable correctly into your job. Add a debug line to your before_script to check:

echo "Checking CONNECTION_STRING variable..."
# If the variable is masked (recommended for secrets), this will show *** instead of the actual value
echo "$CONNECTION_STRING"

If the output is empty, head to your GitLab project's Settings > CI/CD > Variables:

• Make sure the variable isn't marked as Protected unless your deployment branch is also protected.
• Check the Environment scope—if you set it to a specific environment, ensure your deployment job targets that environment.
• Confirm the variable name matches exactly (CONNECTION_STRING—case matters in bash).

3. Ditch User-Secrets for CI (More Reliable Approach) #

dotnet user-secrets is designed for local development, not CI/CD environments. It stores secrets in a user-specific directory, which can be unpredictable in shared CI runners. A better approach is to use .NET's built-in support for environment variables directly:

Step A: Remove User-Secrets Commands #

Delete the dotnet user-secrets set line from your .gitlab-ci.yml—GitLab will automatically make the CONNECTION_STRING variable available to your job's environment.

Step B: Ensure Configuration Reads Environment Variables #

.NET's IConfiguration already reads environment variables by default, but you can explicitly confirm this in your setup to be safe:

• For .NET 5 and earlier (Startup.cs):

public Startup(IHostEnvironment env)
{
    var builder = new ConfigurationBuilder()
        .SetBasePath(env.ContentRootPath)
        .AddJsonFile("appsettings.json", optional: true)
        .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true)
        // Explicitly add environment variables as a configuration source
        .AddEnvironmentVariables();
    SecretConfiguration = builder.Build();
}

• For .NET 6+ (Program.cs):

var builder = WebApplication.CreateBuilder(args);
// Environment variables are included by default, but this line makes it explicit
builder.Configuration.AddEnvironmentVariables();

Step C: Read the Variable as Usual #

Your existing code SecretConfiguration["ConnectionString"] will work here—.NET maps environment variables to configuration keys automatically. Note that for nested keys (like ConnectionStrings:Default), you'd use ConnectionStrings__Default as the environment variable name (double underscores replace colons), but since your key is top-level, CONNECTION_STRING works perfectly.

4. If You Must Use User-Secrets in CI #

If you want to stick with user-secrets, make sure your project has a UserSecretsId set in the .csproj file:

<PropertyGroup>
  <UserSecretsId>your-unique-secrets-guid</UserSecretsId>
</PropertyGroup>

This ID links your project to the correct secrets store. If it's missing, add this line, and run dotnet user-secrets init in your before_script before setting the secret:

dotnet user-secrets init
dotnet user-secrets set "ConnectionString" "$CONNECTION_STRING"

Quick Debugging Tip #

To confirm the connection string is loaded correctly, add a temporary log line in your ConfigureServices method (remove this after debugging):

public void ConfigureServices(IServiceCollection services)
{
    var connString = SecretConfiguration["ConnectionString"];
    // Log the first 10 characters to avoid exposing the full secret
    Console.WriteLine($"Loaded connection string: {connString?.Substring(0, 10)}...");
    
    services.AddCors();
    services.AddDbContext<StudentRepository>(options => options.UseMySQL(connString));
    services.AddMvc();
}

内容的提问来源于stack exchange，提问作者Weeedooo