Closed dshemetov closed 2 months ago
@melange396: Added the context to the OP. I did the readability improvement you suggested, but it turns out that we have at least one indicator that doesn't have a setup.py (backfill_corrections) and the more direct phrasing causes it to return with an exit code of 1 and stop the rest of the Jenkins build. So I had to get more verbose. @minhkhul: This should be it, the rest of #2014 should be fine.
Description
Our Jenkins build script previously looked in every indicator folder and if it finds
setup.py
it installs the indicator. I changed this check topyproject.toml
, in anticipation of #2016, but that is premature. This adds thesetup.py
check in, but also future proofs by adding a check forpyproject.toml
as well.Changelog
Maintaining previous behavior and future-proofing
Jenkins/build-indicators.sh
.Associated Issue(s)