Skip builds on appveyor still use like 1:40
See original GitHub issueIf a recipe skip some builds (python 2 only for example), appveyor is still running 4 containers that take around 2 minutes each.
This seems like a huge waste of time and computing resources. A check could be made early on on the build by simple checking for a line that looks like skip: True # [py3k]
or similar… no need to even parse with yaml.
Thoughts @jakirkham ?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Setting up commits filtering - AppVeyor
AppVeyor supports “standard” directives to skip a build of particular commit. Add [skip ci] or [ci skip] to commit message title and build...
Read more >Continuous Integration Travis & Appveyor - GitHub
If you have [skip ci] in the first line of your commit message then neither Appveyor nor Travis will build it. You can...
Read more >Why does AppVeyor use VS2010 tools for VS2015 image?
For example, below is for the Visual Studio 2015 build image. It dies when the toolset version is set to v140 , which...
Read more >conda-build Documentation
Some users want to use the latest Anaconda packages but do not yet want to use the Anaconda compilers. To enable.
Read more >conda-forge/conda-forge.github.io - Gitter
conda build . is usually a pretty good proxy for what happens on appveyor or the ... Needs the conda_build_config.yaml file from conda-forge-pinning...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So I think there are two problems that I would like to tease out. They are both problems, but they are different problems.
There have been many discussion about both of these at different times. I can try dredging the issue trackers for references if you are curious. Though in both cases I think there is one main solution that is being pursed, which should help many builds regardless of the which builds are involved.
The most pertinent discussion for 1 is actually issue ( https://github.com/conda-forge/conda-forge-webservices/issues/79 ). While I would probably accept small hacky improvements on CIs, I think they will likely get removed in the end once we have a reasonable webservice that does the same thing more cleanly. So the webservice may just be time better spent.
As for 2, the general consensus has been to make a conda-forge installer. The reason being a lot of time is spent upgrading
root
fromdefaults
toconda-forge
. Starting with an installer that includesconda-forge
packages from the outset should speed this up dramatically. This work is all happening at this repo. Would definitely appreciate any thoughts and/or help on the various issues open there.Only 1 job now