[
https://issues.apache.org/jira/browse/XERCESC-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh updated XERCESC-2098:
---------------------------------
Description:
The project does not currently have any continuous integration in place. I've
spent the last few days getting a working solution to consider. The attached
patch files add support for two commonly used services,
[Travis|https://travis-ci.org/] (Unix) and [AppVeyor|https://www.appveyor.com]
(Windows).
See this [GitHub
branch|https://github.com/rleigh-codelibre/xerces-c/commits/ci]. The last
commit has a green tick mark, which is the CI status. This links through to
the build results:
- [Travis|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/241140155]
-
[AppVeyor|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.87]
How to use this? Go to the Travis or AppVeyor websites and log in with
GitHub/BitBucket/GitLab credentials, or use you own public git repo. Enable
the service for your xerces-c git repo. Now any branch you push to your git
repo will be automatically built in several configuration combinations for
Linux (Autotools, CMake), MacOS X (Autotools, CMake) and Windows (CMake with
Cygwin, MingGW64 and MSVC 2015). The exact combinations tested are viewable
with the above build links, or in the attached patch files. The set of test
combinations can be adjusted as desired. The initial set of combinations
exercise all configurable options, debug and release builds.
This could additionally be enabled for the Apache GitHub mirror or the Apache
git repo itself, which would trigger builds for all subversion commits to do
post-commit testing.
Would there be any objection to committing these changes?
was:
The project does not currently have any continuous integration in place. I've
spent the last few days getting a working solution to consider. The attached
patch files add support for two commonly used services,
[Travis|https://travis-ci.org/] (Unix) and [AppVeyor|https://www.appveyor.com]
(Windows).
See this [GitHub
branch|https://github.com/rleigh-codelibre/xerces-c/commits/ci]. The last
commit has a green tick mark, which is the CI status. This links through to
the build results:
-
[Travis|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/240825536?utm_source=github_status&utm_medium=notification]
-
[AppVeyor|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.76]
How to use this? Go to the Travis or AppVeyor websites and log in with
GitHub/BitBucket|GitLab credentials, or use you own public git repo. Enable
the service for your xerces-c git repo. Now any branch you push to your git
repo will be automatically built in several configuration combinations for
Linux (Autotools, CMake) and Windows (CMake with Cygwin, MingGW64 and MSVC
2015). The exact combinations tested are viewable with the above build links,
or in the attached patch files. The set of test combinations can be adjusted
as desired.
This could additionally be enabled for the Apache GitHub mirror or the Apache
git repo itself, which would trigger builds for all subversion commits to do
post-commit testing.
Would there be any objection to committing these changes?
> Add support for external continuous integration services
> --------------------------------------------------------
>
> Key: XERCESC-2098
> URL: https://issues.apache.org/jira/browse/XERCESC-2098
> Project: Xerces-C++
> Issue Type: Test
> Components: Miscellaneous
> Affects Versions: 3.2.0
> Environment: Unix/Linux
> Windows (MSVC, Cygwin, MinGW)
> Reporter: Roger Leigh
> Labels: appveyor, continuous_integration, travis-ci
> Attachments:
> 0001-ci-Add-appveyor-support-for-Cygwin-MinGW64-and-MSVC1.patch,
> 0002-ci-Add-travis-support-for-Linux-and-MacOS-X.patch
>
>
> The project does not currently have any continuous integration in place.
> I've spent the last few days getting a working solution to consider. The
> attached patch files add support for two commonly used services,
> [Travis|https://travis-ci.org/] (Unix) and
> [AppVeyor|https://www.appveyor.com] (Windows).
> See this [GitHub
> branch|https://github.com/rleigh-codelibre/xerces-c/commits/ci]. The last
> commit has a green tick mark, which is the CI status. This links through to
> the build results:
> - [Travis|https://travis-ci.org/rleigh-codelibre/xerces-c/builds/241140155]
> -
> [AppVeyor|https://ci.appveyor.com/project/rleigh-codelibre/xerces-c/build/1.0.87]
> How to use this? Go to the Travis or AppVeyor websites and log in with
> GitHub/BitBucket/GitLab credentials, or use you own public git repo. Enable
> the service for your xerces-c git repo. Now any branch you push to your git
> repo will be automatically built in several configuration combinations for
> Linux (Autotools, CMake), MacOS X (Autotools, CMake) and Windows (CMake with
> Cygwin, MingGW64 and MSVC 2015). The exact combinations tested are viewable
> with the above build links, or in the attached patch files. The set of test
> combinations can be adjusted as desired. The initial set of combinations
> exercise all configurable options, debug and release builds.
> This could additionally be enabled for the Apache GitHub mirror or the Apache
> git repo itself, which would trigger builds for all subversion commits to do
> post-commit testing.
> Would there be any objection to committing these changes?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
