Travis无法将带标签的提交部署至PyPI问题求助

Hey there, let's break down this Travis-PyPI deployment issue you're hitting with the ffn project, especially since you've already got it working for the bt project—we can use that as a reference!

First, let's zero in on the key error clues #

The logs show two critical hints:

Not currently on any branch
PyPI upload failed

This tells us Travis is running in a detached HEAD state during deployment, which is likely breaking your deployment workflow (whether it's version generation, git-based checks, or PyPI upload logic).

Let's walk through actionable fixes, using your bt project as a reference point #

Here are the most likely culprits and how to address them:

1. Check your .travis.yml branch/triggers vs. bt's configuration

   • Compare the deploy section in both projects. Does ffn's config restrict deployment to a specific branch (like master) but Travis is triggering on a tag or PR (which puts it in detached HEAD)?
   • For example, if you're deploying on tags, make sure your config explicitly handles this:

     deploy:
       provider: pypi
       on:
         tags: true
         branch: master # If you want to limit to tags pushed to master
     

   • Check if bt uses a before_deploy step to switch to a valid branch—add this to ffn if missing:

     before_deploy:
       - git checkout master # Or your main branch name
     

2. Debug the git state during builds

   • Add debug commands to ffn's .travis.yml to see exactly what's happening with git before deployment:

     before_deploy:
       - git branch
       - git status
       - git tag
     

   • This will show you if Travis is checking out a tag (detached HEAD) or a branch, and whether there's any unexpected state that's throwing off your deployment.

3. Fix version generation if you're using git-based tools

   • If ffn uses tools like setuptools_scm to generate versions from git tags/branches, a detached HEAD state can break version detection.
   • Compare how bt handles versioning: does it hardcode versions, use an environment variable, or configure setuptools_scm to work in detached HEAD mode?
   • For setuptools_scm, you can pass a fallback version via environment variable:

     before_deploy:
       - export SETUPTOOLS_SCM_PRETEND_VERSION=$(git describe --tags)
     

4. Dig into the actual PyPI upload error

   • The log just says "PyPI upload failed"—look deeper in the Travis job logs for the full error from twine or setup.py. Common issues here include:
     • A duplicate version number already on PyPI
     • Invalid PyPI credentials (though this is less likely since bt works)
     • Malformed package metadata caused by the detached HEAD state

Final step: Mirror bt's working workflow #

Since you know bt's deployment works, copy its .travis.yml deployment section verbatim into ffn's config (adjusting branch names or project-specific details), then test a deployment. This will quickly tell you if the issue is in the config differences between the two projects.

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