Skip to content
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

[CI] Integrate AppVeyor Support #13690

Closed
mbabker opened this issue Jan 22, 2017 · 3 comments
Closed

[CI] Integrate AppVeyor Support #13690

mbabker opened this issue Jan 22, 2017 · 3 comments

Comments

@mbabker
Copy link
Contributor

mbabker commented Jan 22, 2017

This is mainly a placeholder for discussion before opening an actual PR.

AppVeyor support should be added to this repository. AppVeyor is another continuous integration platform which offers testing support for GitHub repositories, except this platform specializes in supporting the Windows environment. This would enable the test suite to be ran on a Windows environment and include test coverage for the Microsoft SQL Server database driver. Even though SQL Server support will be phased out of the CMS in 4.0, it would still be beneficial to consistently run the test suite on the Windows platform and hopefully better be able to support it and address Windows specific items.

This is currently being integrated into the Framework's Database package, see joomla-framework/database#72 for the current progress.

@Bakual
Copy link
Contributor

Bakual commented Jan 22, 2017

Given the issues we get repeatedly on Windows systems, it sure makes sense to use that service

@mbabker
Copy link
Contributor Author

mbabker commented Jan 25, 2017

After some trial and error we've finally got the database package's environment provisioned and executing properly - https://ci.appveyor.com/project/joomla/database/build/1.0.77

There are two issues to address now, both of which at first appearance seem to be more environmental/configuration related than code issues:

If anyone can help with solutions there that'll be helpful here too as most likely the same problems will need to be addressed.

@mbabker
Copy link
Contributor Author

mbabker commented Jan 28, 2017

PR opened.

@mbabker mbabker closed this as completed Jan 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants