Continuos Integration for AzioMQ about azmq HOT 19 CLOSED

At some point I plan on investigating TravisCI (probably won't work for
Windows, but I admit I haven't checked). Until then (and perhaps even
then), this is as good anything else I could offer, so configure away
please.

On Tue, Nov 25, 2014 at 12:07 PM, Andrey Upadyshev <[email protected]

wrote:

I have Linux and Windows servers with TeamCity
https://www.jetbrains.com/teamcity/ CI deployed. Are you OK if I'll
setup a build/test jobs for AsioMQ on this servers? There is a problem that
I can't give anybody access to servers itself, only to TeamCity web UI
where the build status can be monitored. But may be this is better than
nothing. If you are OK, I'll proceed with configuring the CI.

—
Reply to this email directly or view it on GitHub
#18.

from azmq.

Travis definitely doesn't support Windows. That's the reason I've decided to setup my own CI.

from azmq.

By the way, I set up https://libzmq.cloudapp.net/ a while a go that builds libzmq, it's integrated with github and in theory marks the pull requests as failed, though the travis CI usually comes along afterwards and writes over the build status.

Your welcome to use that as well if you want, its a machine running on azure, dedicated to zmq.

from azmq.

It appears the current TravisCI tooling environment is insufficient for building :-/

Current compilers are GCC4.6 and Clang3.4, neither of which are sufficiently C++11 conforming, also no CMake.

from azmq.

So I added a azmq build to https://libzmq.cloudapp.net.

Currently it should build when new changes are merged, but I can get it to build each pull request if you are OK with that.

from azmq.

@ricnewton thank you! But I still proceed with my TeamCity environment - I want to setup CI for Win/Linux/OSX platforms and with wide set of compiler versions.

from azmq.

Fair enough, I wont set up the pull request integration then if you prefer to do it on yours.

from azmq.

I will, just not sure it will be finished soon.

from azmq.

I've configured TeamCity to build and run tests for AZMQ: https://78.46.71.115/project.html?projectId=Azmq Right now it's build on the following platforms:

• gcc 4.9.1 on Ubuntu 14.10 (x64)
• MSVS 2013 U4 on Windows Server 2008 R2 (x86)

Both platforms have Boost 1.55 and zmq 4.0.5.

I'm currently finishing to setup an OS X machine but it's going to be outdated OS X 10.8 because I failed to install OS X 10.10 under KVM and failed to find OS X 10.9 distributive to try it. Because of OS X 10.8 the latest Xcode can't be installed so there will be Xcode 5. Hope it can compile AZMQ. I would appreciate if somebody can help me with advice about installing 10.10 or with 10.9 distributive.

Right now the build performed on each change in master branch and for each pull request. If we need to publish pull request status back to GitHub, please provide me with a username and password of a user having push access rights (https://developer.github.com/v3/repos/statuses/#create-a-status).

from azmq.

First thanks for setting this up.

With respect to OSX builds, I am happy to treat it as a bit of a snowflake,
precisely because Apple makes it so difficult set up VMs for this kind of
thing.

A more robust CI solution may be to just say what version of Clang's
upstream is supported and put together a VM that runs (free/open) BSD with
that version of Clang. There would be a pretty high likelihood that it
would then also work on the version of Xcode that bundled that version of
Clang, and we could add BSD to the list of supported build targets.

On Sunday, December 7, 2014, Andrey Upadyshev [email protected]
wrote:

I've configured TeamCity to build and run tests for AZMQ:
https://78.46.71.115/project.html?projectId=Azmq Right now it's build on
the following platforms:

• gcc 4.9.1 on Ubuntu 14.10 (x64)
• MSVS 2013 U4 on Windows Server 2008 R2 (x86) Both platforms has
  Boost 1.55 and zmq 4.0.5.

I'm currently finishing to setup an OS X machine but it's going to be
outdated OS X 10.8 because I failed to install OS X 10.10 under KVM and
failed to find OS X 10.9 distributive to try it. Because of OS X 10.8 the
latest Xcode can't be installed so there will be Xcode 5. Hope it can
compile AZMQ. If anybody could help me with advice about installing OS X
10.10 or with 10.9 distributive I would appreciate.

Right now the build performed on each change in master branch and for each
pull request (not testsed yet). If we need to publish pull request status
back to GitHub, please provide me with a username and password of user
having push access rights (
https://developer.github.com/v3/repos/statuses/#create-a-status).

—
Reply to this email directly or view it on GitHub
#18 (comment).

from azmq.

Good idea. First I'll try to build AZMQ with Xcode 5 on OS X 10.8 (it's deployed already so cost nothing to try). If it will fail then I'll setup FreeBSD machine. Regardless this, I can setup FreeBSD machine later to get more platforms coverage.

There is still a question regarding pull requests integration. TeamCity fetches pull request, build it and run tests. Then TeamCity set the pull request status on GitHub, like is it good to merge or not. If we want to use pull request status for AZMQ, I should have push access rights to the repo then I'll setup TeamCity to report status with my credentials. Of course I promise to don't push any changes directly.

from azmq.

I've rechecked the documentation and found the more secure way to publish statuses. Repo owner should generate Personal Access Token with the permissions repo:status and public_repo or repo depending on the repository type and pass the token to me.

from azmq.

I will look into setting this up

On Mon, Dec 8, 2014 at 3:26 PM, Andrey Upadyshev [email protected]
wrote:

I've rechecked the documentation and found the more secure way to publish
statuses. Repo owner should generate Personal Access Token with the
permissions repo:status and public_repo or repo depending on the
repository type and pass the token to me.

—
Reply to this email directly or view it on GitHub
#18 (comment).

from azmq.

It appears that these tokens apply 'per user' not 'per repo' so it doesn't seem quite right

from azmq.

Looks like GitHub has no per repo granularity for external applications.
I've setup the token you sent. Let's wait the next pull request :)
Btw, TeamCity can publish pull request status only from one platform build. I'm gonna publish it as a result of Linux build. Is it OK?

from azmq.

Linux status is fine

On Monday, December 8, 2014, Andrey Upadyshev [email protected]
wrote:

Looks like GitHub has no per repo granularity for external applications.
I've setup the token you sent. Let's wait the next pull request :)
Btw, TeamCity can publish pull request status only from one platform
build. I'm gonna publish it as a result of Linux build. Is it OK?

—
Reply to this email directly or view it on GitHub
#18 (comment).

from azmq.

Eh. It's changed again :) TeamCity can publish from all platforms but only the last one will be a pull request's final status. You can check at #41.
I can leave it as it is, so there will be comments about build start and build finish for both platforms or I can leave the only one platform (which is not that safe imho). If there are too many comments, I can remove comments about build start.

from azmq.

Agree, it is fine for now. Thanks!

On Mon, Dec 8, 2014 at 5:02 PM, Andrey Upadyshev [email protected]
wrote:

Eh. It's cnanged again :) TeamCity can publish from all platforms but only
the last one will be a pull request's final status. You can check at #41
#41.
I can leave it as it is, so there will be comments about build start and
build finish for both platforms or I can leave the only one (which is not
that safe imho). If there are too many comments, I can remove comments
about build start.

—
Reply to this email directly or view it on GitHub
#18 (comment).

from azmq.

Finished with CI.
Finally there are three configurations:

• gcc 4.9.1 on Ubuntu 14.10 (x64)
• MSVS 2013 U4 on Windows Server 2008 R2 (x86)
• Xcode 5.1 (Apple Clang 5.1) on OS X 10.8

There is still issues with Windows tests but they are not related to CI but to the product.

from azmq.