Split Azure Pipelines configuration into multiple files - #1481
Conversation
Split the different stages that are run in Azure Pipelines into multiple files.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1481 +/- ##
==========================================
- Coverage 86.19% 86.18% -0.01%
==========================================
Files 394 394
Lines 50299 50299
Branches 5309 5309
==========================================
- Hits 43353 43351 -2
- Misses 5493 5494 +1
- Partials 1453 1454 +1 ☔ View full report in Codecov by Sentry. |
We would need to make sure the token works for making the push. Currently it fails to authenticate.
…o split-deploy-docs-pypi
Leave line commented out for now.
Just to test the download and upload of artifacts
Comment out condition so we can test if the push works.
Azure didn't like having variables in the template file.
Also, replace `setup.py` for `pyproject.toml` when updating the `local_scheme` configuration for `setuptools_scm`.
Update docs.yml so now it makes use of the setup scripts in `.ci`.
Also bump minimum versions for setuptools and setuptools_scm, according to the ones used in pyproject.toml.
Install only build and twine for building simpeg, since the build requirements will be installed in an isolated environment. By removing the `--skip-isolation` option we solve the issue of not getting the proper version in the built package.
This reverts commit aadcc33.
|
@jcapriot, I think this is ready to be merged. Would you take a second look at it? |
| displayName: "Configure local_scheme (except on release)" | ||
|
|
||
| - bash: | | ||
| python -m build --sdist . |
There was a problem hiding this comment.
The biggest change I made after updating this branch once the pyproject.toml was merged was to change how we build the sdist. Instead of installing the build dependencies (and pin the versions here in the yml), I just install build and let it install the required build dependencies in isolation. This also solved an issue I saw when trying to push to TestPyPI, where the sdist didn't have the right simpeg version. I think it was related to incompatible versions of setuptools and setuptools_scm.
jcapriot
left a comment
There was a problem hiding this comment.
Just a little bit more cleanup.
| - bash: .ci/azure/setup_env.sh | ||
| displayName: Setup SimPEG environment | ||
|
|
||
| - script: | |
There was a problem hiding this comment.
Should remove this step since it uploads to pypi in the other file.
There was a problem hiding this comment.
Right! I forgot to update the new version of the old-docs.yml as well 🤦🏼♂️
Split the stages from
azure-pipelines.ymlinto multiple files under the.ci/azuredirectory. Strip deployment to PyPI from the deployment of the docs into different stages. Add new job to upload each version merged tomainto TestPyPI. Configure thesetuptools_scmlocal version scheme so we can modify it before building the wheels for TestPyPI. Refactor the new docs pipeline: have a single build job and two jobs for deploying the docs tosimpeg-doctest, one after a release and one for nightly builds. While building the sdist (before pushing to PyPI), rely onbuildto install build dependencies listed inpyproject.tomlin isolation.