Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Using travis-ci for GitHub Pull request builds

Hi All,

Will Embedded MQTT C Client library will work for Windows CE 6.0?If yes then please tell the procedure.

 

Is MQTT Communication is possible on Windows CE 6.0 &.Net Compact Framework 2.0 excluding M2MQTT for .Net Compact Framework 3.5?

 

Regards,

Himanshu

 

 

From: paho-dev-bounces@xxxxxxxxxxx [mailto:paho-dev-bounces@xxxxxxxxxxx] On Behalf Of Ian Craggs
Sent: Monday, March 14, 2016 3:20 PM
To: paho-dev@xxxxxxxxxxx
Subject: Re: [paho-dev] Using travis-ci for GitHub Pull request builds

 

Hi James,

sounds good to me.  The only negative thought I had was if it impacts the other work we have to do for the upcoming releases, but it sounds like it should only help.

Ian

On 11/03/16 12:41, James Sutton1 wrote:

Whilst at EclipseCon NA I've had some very useful conversations with a few people. One of which was about getting Pull Request Builds going with our GitHub Repositories. Apparently there isn't really any issue with using Travis-CI and the Eclipse HIPP infrastructure in combination. This is great news because currently there is no easy way (that I've been able to find) to get Hudson to trigger correctly upon Pull Requests in GitHub, whereas Travis-ci is very commonly used for this. Here's my idea for how we could split the builds in the Java and Android projects: - New Pull Requests / Updates to commits in existing Pull Requests: Triggered Travis Build - Commits into the Master or Develop Branch: Triggered Travis Build - Nightly builds that generate artifacts: Eclipse Hudson instance (We need to do the artifact builds on the Eclipse Hudson so that we can sign the JAR files and push them to the Nexus & Maven central) Additionally, at least for the Java components, we are running builds every night regardless of whether there have been any changes to the repository. I'm wondering if it would be better to only trigger a hudson nightly build if there has actually been any changes to the branch? I've set up a travis build as a test on my fork of this project and have got travis builds working as can be seen here: https://travis-ci.org/jpwsutton/paho.mqtt.java/builds/115184050 Does this sound like a good change? And could it be useful for the other clients as well as Java and Android? - James Sent from IBM Verse

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU




_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev

 

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.

Back to the top