Travis CI的.yml配置问题与构建时长优化咨询

Let's tackle your two Travis CI issues one by one—here's what you need to know:

1. Troubleshooting FTP Upload Failures in Your .travis.yml #

First off, the fact that your config passed Travis's validation tool means the YAML syntax is correct, so the problem lies in either the FTP command itself or permissions/setup. Let's break down the likely culprits:

• Double-check your target file: Your curl command uses uploadfilename—that's a placeholder, right? You need to replace this with the actual path to the file you want to upload (e.g., dist/main.html if you're uploading a built file from a dist folder). To confirm the file exists in Travis's working directory, add a quick ls -la command before the curl call (like in before_script) to verify the file is there.
• FTP permissions don't require sudo: Your FTP_USER doesn't need to be a sudo user—what matters is that this account has write access to the /var/www/test directory on your server. Try manually logging in with this FTP account and uploading a file to that directory; if that fails, Travis will too. Fix the server-side permissions first if this is the case.
• Add passive mode to your curl command: Many FTP servers require passive mode to accept uploads, and curl uses active mode by default. Update your curl command to include --ftp-pasv:

  curl --ftp-create-dirs --ftp-pasv -T [actual-file-path] -u $FTP_USER:$FTP_PASSWORD ftp://$FTP_ADDRESS/var/www/test
  

• Verify your encrypted environment variables: Even though you've encrypted FTP_USER, FTP_PASSWORD, and FTP_ADDRESS, it's worth confirming they're being decrypted correctly during builds. Add a safe debug line like echo $FTP_ADDRESS (never echo the password!) to your script to check if the variable resolves to the correct server address.
• Ensure the after_success stage runs: The after_success stage only executes if the script stage completes successfully. Since language: generic has no default script step, Travis marks the build as successful, but sometimes edge cases can cause the stage to skip. Try moving the curl command to the script stage instead, or add a dummy script: echo "Build complete" to ensure the pipeline flows correctly.

2. Optimizing Build Duration for Your Small Project #

A 1-2 minute build for a 9MB HTML/CSS/PHP project is definitely longer than necessary—here's how to speed it up:

• language: generic is slow by design: Generic environments spin up a bare-bones virtual machine with no pre-installed tools, which takes extra time to initialize. In contrast, language: php uses Travis's pre-configured PHP environments, which are pre-built and optimized to start quickly.
• Switch to language: php for faster builds: Since your project includes PHP, switching to this language tag is the easiest win. Travis will skip the generic environment's lengthy setup and use a tailored PHP environment, cutting down on initialization time significantly. If you use Composer for PHP dependencies, you can also enable caching to avoid re-downloading packages every build:

  cache:
    directories:
      - vendor
      - ~/.composer
  

• Dig into your build logs for extra gains: Open your Travis build logs and look for the slowest steps—maybe it's the virtual machine boot time, or an unnecessary step in the generic environment. Once you identify the bottleneck, you can eliminate redundant steps or tweak your config further.

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