Arianne Development Meeting 2016-01-06: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Hendrik Brummermann No edit summary |
imported>Hendrik Brummermann No edit summary |
||
| Line 3: | Line 3: | ||
== Sourceforge, Github, Travis == |
== Sourceforge, Github, Travis == |
||
| ⚫ | |||
* A quick update from Hendrik about the recent infrastructure changes |
|||
* ... |
|||
| ⚫ | Since then we have improved the situation significantly: The mirroring is now done in both directions, and it is done almost instantaneously. This means it does not matter anymore whether commits are done to Sourceforge or Github. So we can use Github features such as pull request. And we can make use of Travis for running the JUnit test. [[Two way git mirror]] explains the details. |
||
| ⚫ | |||
All JUnit tests for Marauroa [https://travis-ci.org/arianne/marauroa] and Stendhal [https://travis-ci.org/arianne/stendhal] are passing. So before we do a new release, we can just check there. In addition, Travis will execute the test suite for each pull request and post the result directly to the pull request page. Unfortunetelly there is nice output of failed tests. So in case of failures, we have to look at the console log or execute the tests locally. |
|||
Failed tests are reported to IRC again. |
|||
<!-- |
<!-- |
||
| ⚫ | |||
20:06hendrik1. Recent infrastructure changes: Sourceforge, Github, Travis |
|||
| ⚫ | |||
20:07hendrikBack than the mirroring was only from Sourceforge to github, and it was done by the testserver build script once a night. |
|||
20:07hendrikSince then we have improved the situation significantly: |
|||
20:08hendrikThe mirroring is now done in both directions, and it is done almost instantaniously. |
|||
| ⚫ | |||
20:09hendrikhttps://stendhalgame.org/wiki/Two_way_git_mirror explains the details. |
|||
| ⚫ | |||
20:10hendrikAll junit tests for Marauroa https://travis-ci.org/arianne/marauroa and Stendhal https://travis-ci.org/arianne/stendhal are passing. |
|||
20:11alberthjavierhi |
|||
20:11hendrikSo before we do a new release, we can just check there. In addition, Travis will execute the test suite for each pull request and post the result directly to the pull request page. |
|||
20:12hendrikUnfortunetelly there is nice output of failed tests. So in case of failures, we have to look at the console log or execute the tests locally. |
|||
20:12hendrikSo far a quick infrastructure updates. Any comments or questions? |
|||
20:12kiherucan it notify about failure to irc like the old jenkins setup? |
|||
20:13hendrikAccording to https://docs.travis-ci.com/user/notifications/#IRC-notification that is supposed to work. I tried to configure it, but it does not work. |
|||
20:14hendrikhttps://github.com/arianne/stendhal/blob/master/.travis.yml |
|||
20:14kiheruaw :-( |
|||
20:14markusFirst of all I like travis and the new possibilities of github, esp. pull requests. This brings up a thing we could consider: pointing new contributors to creating pull requests instead of patches? |
|||
20:15hendrikI am not sure, if I made a mistake or whether it does not work anymore. In the second case, that's a task for postman. |
|||
20:15hendrikmarkus, yes, that may be a good idea. |
|||
20:16markusThe question would be: Do we think it is easier for them to create a patch or create a pull request from a fork |
|||
20:17markushendrik: didn't you tell me about uploading the testresults somewhere? |
|||
20:17hendrikYes, but that only works partly. |
|||
| ⚫ | |||
20:18hendrikBut it would be the place to invoke postman from. |
20:18hendrikBut it would be the place to invoke postman from. |
||
20:18balaurI also like the idea of pull requests more, but for a patch you don't need an account |
20:18balaurI also like the idea of pull requests more, but for a patch you don't need an account |
||
| Line 60: | Line 45: | ||
20:30hendrikOn the website it's basically advertisment that we are doing good work[tm]. |
20:30hendrikOn the website it's basically advertisment that we are doing good work[tm]. |
||
20:31hendrikOn IRC is were we will need it for practical reasons. |
20:31hendrikOn IRC is were we will need it for practical reasons. |
||
20:31markusexactly. :) |
|||
20:32kiheruagreed. hopefully the irc notification is something that can be fixed |
|||
20:33kiheruhey |
|||
20:33hendrikIt might be a good idea, if someone else looks at my configuration, to check that I did not mess it up. |
|||
20:33kiheruthre travis docs have "irc:" under section "notifications:" |
|||
20:34kiheruwhereas on the .travis.yml it is top level, if I read it right |
|||
20:35kiheru(I have been trying to find the problem during the discussion. that's the best idea yet) |
|||
20:35postmanarianne_rpg: nhnb * rc4c927c49d7c stendhal/.travis.yml: fixed travis irc configuration |
|||
20:35hendrikOops. |
|||
20:35kiheruI hope it worked |
|||
20:35balaurok now let's break a test :p |
|||
20:36hendrikShall we move to the next topic? |
|||
20:37travis-ciarianne/stendhal#102 (master - c4c927c : Hendrik Brummermann): The build passed. |
|||
20:37travis-ciChange view : https://github.com/arianne/stendhal/compare/a0d70ed2e3f1...c4c927c49d7c |
|||
20:37travis-ciBuild details : https://travis-ci.org/arianne/stendhal/builds/100660289 |
|||
20:37kiheruwoo! |
|||
20:37markusyay! |
|||
20:37hendrikkiheru, yay!!! |
|||
20:38postmanarianne_rpg: nhnb * r98affef72de0 stendhal/.classpath: report only test status changes |
|||
20:38*hendrik closes Eclipse. |
|||
--> |
--> |
||
| Line 237: | Line 202: | ||
22:03hendrikWe can do that in (rather large) chunks by converting all the code that goes to the wiki-database, game-database, website-date. |
22:03hendrikWe can do that in (rather large) chunks by converting all the code that goes to the wiki-database, game-database, website-date. |
||
--> |
--> |
||
== Other topics == |
|||
* ... |
|||
Note: We may want to postpone topics regarding Stendhal features to a follow up meeting. But it is okay to list them here. This will help with preparing an agenda for the next meeting. |
|||
Revision as of 14:46, 10 January 2016
We will meet in #arianne on irc.freenode.net, https://webchat.freenode.net/?channels=arianne on Wednesday, 6th January, 2016 at 20.00 server time (19.00 GMT)
Sourceforge, Github, Travis
In August after an extended downtime of Sourceforge, we created the Arianne organisation on Github and mirrored the Stendhal git repository. Back than the mirroring was only from Sourceforge to github, and it was done by the testserver build script once a night.
Since then we have improved the situation significantly: The mirroring is now done in both directions, and it is done almost instantaneously. This means it does not matter anymore whether commits are done to Sourceforge or Github. So we can use Github features such as pull request. And we can make use of Travis for running the JUnit test. Two way git mirror explains the details.
In addition to Stendhal, Marauroa is now on github, too.
All JUnit tests for Marauroa [1] and Stendhal [2] are passing. So before we do a new release, we can just check there. In addition, Travis will execute the test suite for each pull request and post the result directly to the pull request page. Unfortunetelly there is nice output of failed tests. So in case of failures, we have to look at the console log or execute the tests locally.
Failed tests are reported to IRC again.
Prepaing release of Marauroa 4.0
- After years of development, perception_json was merged into master.
- Release bockers are tagged with MARAUROA_03_99
- ...
Doing Sendhal releases
- At the moment I am the only person who can do a Stendhal release. If I am not available and there is an active contributor, lots of changes pill up. This is hard to review, and I assume it may be frustrating for contributors. Creating a release, however, is both complicated and time consuming.
- ...
PostgreSQL support
- ...