Travis CI提示Could not parse .travis.yml，请求排查CI配置问题

Hey there! Let's figure out why Travis CI is throwing that "Could not parse .travis.yml" error—even without detailed messages, there are a few common spots to check first.

First: Validate Your .travis.yml Syntax #

YAML is super picky about indentation, spacing, and special characters. Even a missing space after a colon or inconsistent indentation can break parsing. Here’s how to rule this out:

• Double-check that every key-value pair has a space after the colon (e.g., language: csharp is correct, language:csharp is not).
• Ensure consistent indentation (use 2 spaces per level—tabs or mixed spaces/tabs will cause issues). Your current .travis.yml looks structurally correct, but run it through a YAML linter (you can use a local tool like yamllint or an offline validator) to catch hidden syntax issues like invisible full-width spaces.

Second: Fix Script File Issues (Even If They’re Not the Direct Parse Error) #

While the parse error points to .travis.yml, broken scripts can sometimes cause unexpected downstream behavior. Let’s tweak your shell scripts to avoid future problems:

1. Add shebangs to all script files
   Every bash script should start with #!/bin/bash to tell Travis which interpreter to use. Without this, some environments might fail to execute the scripts properly.

   Updated dotnet-build.sh:

   #!/bin/bash
   dotnet restore
   dotnet build
   

   Note: I removed the leading space before dotnet restore—extra spaces at the start of commands won’t break parsing, but they’re unnecessary and can cause confusion.

   Updated dotnet-publish.sh:

   #!/bin/bash
   dotnet publish ./BookMeMobi2 -c Release -o ./bin/Docker
   

2. Fix AWS CLI path in docker-publish-travis.sh
   When installing awscli with --user, it gets placed in ~/.local/bin, which might not be in Travis’s default PATH. Add an export line to ensure the aws command is found:

   #!/bin/bash
   pip install --user awscli
   export PATH=$PATH:$HOME/.local/bin
   eval $(aws ecr get-login --no-include-email --region eu-central-1)
   docker build -t bookmemobi2 .
   docker ps
   docker tag bookmemobi2:latest 601510060817.dkr.ecr.eu-central-1.amazonaws.com/bookmemobi2:latest
   docker push 601510060817.dkr.ecr.eu-central-1.amazonaws.com/bookmemobi2:latest
   

Third: Rule Out Travis CI Environment Quirks #

• The dist: trusty image is quite old (Ubuntu 14.04). While this shouldn’t cause a parse error, consider upgrading to dist: xenial or a newer image if you run into other issues later.
• Ensure the dotnet: 2.0.0 version is supported by the trusty distro. Travis’s docs confirm it is, but it’s worth double-checking if you still have issues after fixing syntax.

Start with validating the YAML syntax first—this is the most likely cause of the "Could not parse" error. Once that’s confirmed, apply the script fixes to smooth out the rest of your pipeline.

内容的提问来源于stack exchange，提问作者Michał Ściborski