Sent from my iPhone
> On Nov 27, 2014, at 10:54 PM, Alex <[email protected]> wrote: > > Hi guys, > > first of all thank you Moon for helping with Jenkins access! > > I'v been working on getting CI server for the project AKA MRQL-35 and here's > current status: > - build of master works https://builds.apache.org/job/mrql-master-snapshot > - it polls repository for changes every 5min and build in case of any or it > can be triggered manually from web ui above (I guess only for logged-in users) > - it run tests, published a reports like this one > - it is configured according to Apache wiki Jenkins guideline > - it tries to comment on a relevant JIRA issue with the build status > - it emails to [email protected] on the build\test failure > (to finish this setup moderator needs to send en email to > dev-allow-subscribe-jenkins=builds.apache....@mrql.incubator.apache.org > according to > http://wiki.apache.org/general/Jenkins#How_do_I_allow_Jenkins_to_mail_to_my_project) > > Please check it out and do not hesitate to provide a feedback! > > > I was wondering if you would be interested in adding more of the quality > assurance automation to the project? > > Some examples that I could also give a hand with are: > - add a test coverage report > - add a project coding conventions checks (if one exists documented) > > > Another suggestion could be - create a "release build" job, which takes the > desired version number and does the magic by changing version > number\building\tagging\deploying to Maven repository\uploading somewhere. > > > -- > Kind regards, > Alexander. >
