The title is the short version. Unless I’m missing something, overriding phases with
skip prevented the deployment from happening. (Not sure which category is best to post here, but since my problem came about because of config imports, I’m putting under that.)
Context: I’m developing a tool to implement a complex Python release cycle based on Travis stages. I’ve been copying parts of this into projects ever since stages were released; the release of config imports allows me to keep all the fancy Travis stages is a single, unified location (yay! thanks!)
As I’ve been migrating my projects over to this, I recently made it so my imported config jobs skip everything except the phases are used in that stage. But when I did this, the deploy phase didn’t run.
The recycle cycle also includes a test deployment job (directly using twine in the script phase), so I know the credentials are working. It’s the final deployment job, which uses dpl, that didn’t work. And it didn’t even seem to download the stuff for dpl.
Here’s the relevant build: https://travis-ci.org/openpathsampling/openpathsampling/builds/624268394, particularly the
deploy pypi job.
The possibilities I’ve thought of are:
- doing nothing looks like a job failure to deploy (but reports passing!)
- skipping something else (maybe
after_script?) causes deploy to be skipped
- I found a bug
Maybe I’m missing something else? If it isn’t a bug, it would be really helpful if the docs at https://docs.travis-ci.com/user/job-lifecycle/ could be updated.