Note that there are some explanatory texts on larger screens.

plurals
  1. POMake Python version depending on env var (using travis-ci)
    primarykey
    data
    text
    <p>Is there a way to configure travis-ci to make the Python versions dependent on a certain env var?</p> <p>Please consider the following <code>travis.yml</code> config:</p> <pre><code>language: python python: - "2.5" - "2.6" - "2.7" env: - DJANGO=1.3.4 - DJANGO=1.4.2 - DJANGO=https://github.com/django/django/zipball/master install: - pip install -q Django==$DJANGO --use-mirrors - pip install -e . --use-mirrors script: - python src/runtests.py </code></pre> <p>Among Django 1.3 (<code>DJANGO=1.3.4</code>) and 1.4 (<code>DJANGO=1.4.2</code>) i also want to test against the latest development version of Django (<code>DJANGO=https://github.com/django/django/zipball/master</code>), which is basically Django 1.5.</p> <p>The problem i see is that travis-ci will automatically run the integration against <strong>all</strong> specified Python versions. Django 1.5 however doesn't support Python 2.5 anymore. Is it possible to omit it for the Django development version so that i get integrations like this only:</p> <ul> <li>DJANGO=1.3.4 --> python "2.5", "2.6", "2.7"</li> <li>DJANGO=1.4.2 --> python "2.5", "2.6", "2.7"</li> <li>DJANGO=<a href="https://github.com/django/django/zipball/master" rel="noreferrer">https://github.com/django/django/zipball/master</a> --> python "2.6", "2.7"</li> </ul> <p><strong>UPDATE:</strong></p> <p>Here's a link to a live example based on Odi's answer which i've been using successfully for a few months: <a href="https://github.com/deschler/django-modeltranslation/blob/master/.travis.yml" rel="noreferrer">https://github.com/deschler/django-modeltranslation/blob/master/.travis.yml</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload