Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Update on GitHub move, Build Infrastructure updates.

Hi James,

in several projects I use Travis as CI environment. It works quite fine with GitHub and analizes PR feasibility very well. Perhaps it could be of interest.

I've an additional question. Is the "issue feature" of GitHub going to be used to report bugs, comments...? Or are you maintaining the "old" way of managing issues in eclipse?

Thanks.

2016-01-21 11:24 GMT+01:00 James Sutton1 <james.sutton@xxxxxxxxxx>:
Hi All,
 
Just a quick update on the work I've been doing on the general infrastructure around some of the Paho Repositories & Builds.
 
Now that Ian's started the move to GitHub, I've been updating the Java Repository to have some new contribution guidelines that will hopefully make it easy for others to contribute code to the project.
 
Because repositories in GitHub will no longer use Gerrit and will now be using Pull Requests to assist with merging contributions, the Java builds will have to change as well. Previously we had a Gerrit build that would build and test incoming changes and then comment on the Gerrit Review as to whether the code could be compiled / tested. This was a great way of ensuring a basic level of quality of the changes before properly reviewing and merging them. 
 
Fortunately GitHub Pull requests will allow for a similar build to take place, however this requires the Jenkins GitHub Pull Request Build plugin which is not compatible with the existing Hudson instances we use. Whilst investigating, I noticed that the Eclipse Community team are looking at moving away from Hudson in favour of Jenkins anyway (https://bugs.eclipse.org/bugs/show_bug.cgi?id=336262), I've volunteered the java builds to be some of the first moved over so that we can start doing Pull request builds as soon as possible. Assuming that our experiences moving to Jenkins go well then I will make sure the process is well documented so that we can implement PR builds for the other repositories as well in the future.
 
In a previous thread, Roger suggested expanding our existing branch model (Currently Master and Develop) to include a fixes branch (something like this: http://nvie.com/posts/a-successful-git-branching-model/). I think this is definitely worth trying on the Java client at least as there have been a number of queries on the forums and mailing list recently where users have encountered bugs already fixed in develop but have not made it to the release because of our schedule. Once we've got PR builds working, I would like to experiment and implement the fixes branch which would allow us to get fixes to a release much faster than we normally would, thus reducing any confusion for users or forcing people to include snapshot releases in their project just to get a fix.
Kind regards,
 
James Sutton
Software Engineer - IoT Foundation - MQTT Open Source Projects
Technical Trojan - Wimbledon Project

Phone: 01962 815438 | Extension: x372454
E-mail: james.sutton@xxxxxxxxxx
Personal Website: www.jsutton.co.uk
Find me on:      
IBM

Hursley Park
HursleySO212JN
United Kingdom
 
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
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



--
---
Manuel Domínguez Dorado
ingeniero ARROBA ManoloDominguez PUNTO com
http://www.ManoloDominguez.com

Back to the top