-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added appveyor config #339
Added appveyor config #339
Conversation
-filesystem pkg repo uses this to create tmp '.buildingXXX' files during install/release -these tagfiles tell the system it needs to check for valid package.py files for these packages -this avoids breaking resolves when partial pkg installs don't yet have package.py written
Interesting. AFAIK Appveyor is also free for open source projects. Can we have something there that is accessible for everyone? (We do use AppVeyor here in product dev, but i am not involved with that and don't really know the service) |
Yeah, it's free for open source projects. Haven't used it extensively either, don't know if you can see the test reports but you can at least use the icon in the readme to show if the project is passing all the tests right now. I think it would help everyone in being more confident about the latest changes. |
Continuous testing is a great addition, thanks Sebastian. Will have this A On Tue, Aug 16, 2016 at 6:41 AM, Sebastian Kral notifications@github.com
|
Yes, it's free for open source and it shows you test reports similar to Travis. Here's an example of what that looks like for one of my projects.
Including the Travis equivalent for completeness. Any questions about using it, I'd be happy to help. |
…replacing the file
…ts are properly unwrapped
# Conflicts: # src/rez/utils/_version.py # src/rezplugins/package_repository/filesystem.py
…l plugins to use the alternate library on windows to enable git and command hook support on windows.
… support interactive environment creation in subshells.
…when running in non-interactive command mode.
…ly do it if install was provided
-ported to wrapper
…_and_default_shell'
…e-3 which may be causing test fails
-just add new attrib 'build_command=False' to package.py instead if you need this
…config-paths' into config_updates
-works for package config overrides also
-means PRs can also include doc updates
Closed as we're now using GitHub Actions: #750 |
In the wake of the open source initiative I think a appveyor config might help.
Initial config which runs all the tests. Unfortunately one test fails right now. Didn't look into why.