# Trigger CI build when new version of Python is released
**URL:** https://discourse.itk.org/t/trigger-ci-build-when-new-version-of-python-is-released/1548
**Category:** Engineering
**Tags:** python, wrapping
**Created:** [January 25, 2019, 2:04pm UTC](https://discourse.itk.org/t/trigger-ci-build-when-new-version-of-python-is-released/1548 "2019-01-25T14:04:13Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@T4mmi](https://discourse.itk.org/u/T4mmi)
#### Post date: [January 25, 2019, 2:04pm UTC](https://discourse.itk.org/t/trigger-ci-build-when-new-version-of-python-is-released/1548/1 "2019-01-25T14:04:13Z")
Hi,
Quick question regarding ITK “remote” modules [wrapped for python](https://itkpythonpackage.readthedocs.io/en/latest/Build_ITK_Module_Python_packages.html).
**Travis / Circle / Appveyor provide great help to build the modules !**
_even if I somehow struggle with the automatic PyPI upload, but that’s not the point_
The only _\*problem\*_ I see here is that new versions of python arrives pretty fast and the manual re-build & upload of wheels seems like something that could be automated to catch up with python releases.
my question is therefore:
> **Is there a way to trigger a new build when a new version of python is released ?**
---
### Author:  [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [January 25, 2019, 2:18pm UTC](https://discourse.itk.org/t/trigger-ci-build-when-new-version-of-python-is-released/1548/2 "2019-01-25T14:18:18Z")
Hi Thomas,
Currently you need to go into each of the Travis / Circle / Appveyor web administrative panels and retrigger a build.
In the future, we should move to Azure Pipelines builds, which will allow a unifiied interface, avoid timeouts, and resources to store build artifacts (Python packages), and possibly even deploy them to PyPI.
Matt
---
### Author:  [@T4mmi](https://discourse.itk.org/u/T4mmi)
#### Post date: [January 25, 2019, 2:26pm UTC](https://discourse.itk.org/t/trigger-ci-build-when-new-version-of-python-is-released/1548/3 "2019-01-25T14:26:46Z")
> [@matt.mccormick](#):
>
> Currently you need to go into each of the Travis / Circle / Appveyor web administrative panels and retrigger a build.
That’s what I thought…
> [@matt.mccormick](#):
>
> In the future, we should move to Azure Pipelines builds, which will allow a unifiied interface, avoid timeouts, and resources to store build artifacts (Python packages), and possibly even deploy them to PyPI.
Seems really promising !
Thanks a lot @matt.mccormick for your answers