So I hate to be that guy who doesn't know the simple things, but what is Jenkins? The server has come up in discussion a few times since I joined this mailing list about a month ago.
Actually if there is a Wiki page where these sorts of things are documented. that would be fantastic.
Thank you,
Derric Atzrott
Computer Specialist
Alizee Pathology
On Thu, Jun 28, 2012 at 12:06 AM, Derric Atzrott datzrott@alizeepathology.com wrote:
So I hate to be that guy who doesn't know the simple things, but what is Jenkins? The server has come up in discussion a few times since I joined this mailing list about a month ago.
It is a form of dark magic which automatically runs all test suites for all revisions pushed into our revision control.
See https://www.mediawiki.org/wiki/CI and https://integration.mediawiki.org/ci/
—Victor.
On Jun 27, 2012, at 10:08 PM, Victor Vasiliev wrote:
On Thu, Jun 28, 2012 at 12:06 AM, Derric Atzrott datzrott@alizeepathology.com wrote:
So I hate to be that guy who doesn't know the simple things, but what is Jenkins? The server has come up in discussion a few times since I joined this mailing list about a month ago.
It is a form of dark magic which automatically runs all test suites for all revisions pushed into our revision control.
See https://www.mediawiki.org/wiki/CI and https://integration.mediawiki.org/ci/
—Victor.
.. and it doesn't just run the tests. It also reports back to Gerrit (our code review tool) with a comment linking to the test results and a flag "PASSED" or "FAILED".
For example: https://gerrit.wikimedia.org/r/#/c/13037/ (jenkins-bot)
-- Krinkle
2012/6/27 Derric Atzrott:
So I hate to be that guy who doesn't know the simple things
It's a cliche, but it's important: there are no stupid questions. Ask more.
2012/6/27 Victor Vasiliev:
It is a form of dark magic which automatically runs all test suites for all revisions pushed into our revision control.
... But only for core, not for extensions. Should be done for extensions, too, in some point in the future.
See https://www.mediawiki.org/wiki/CI and https://integration.mediawiki.org/ci/
That, and also https://www.mediawiki.org/wiki/Testing_portal
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
On 27/06/12 22:34, Amir E. Aharoni wrote:
2012/6/27 Derric Atzrott:
So I hate to be that guy who doesn't know the simple things
It's a cliche, but it's important: there are no stupid questions. Ask more.
You're welcome to ask, Derric. I thought the topic was going to be compeltely different :) Jenkins is a service which automatically runs the tests with each patchset, to ensure we get no regressions inadvertently.
2012/6/27 Victor Vasiliev:
It is a form of dark magic which automatically runs all test suites for all revisions pushed into our revision control.
... But only for core, not for extensions. Should be done for extensions, too, in some point in the future.
Tracked by bug 34617
On Wed, Jun 27, 2012 at 2:06 PM, Derric Atzrott < datzrott@alizeepathology.com> wrote:
So I hate to be that guy who doesn't know the simple things, but what is Jenkins? The server has come up in discussion a few times since I joined this mailing list about a month ago.
And since no one has mentioned it yet, you might want to read http://en.wikipedia.org/wiki/Continuous_integration.
Jenkins is an open source system for doing CI. It used to be called Hudson. (Those are both names of butlers, which has always been the mascot of the project.) Over time, Jenkins has become a very powerful hub for automated testing and deployment, and most serious software projects integrate with Jenkins via "plugins". (Although some of those projects don't do it very well, Fitnesse for example.) -C
This is linked from their but just to make it easier to find http://en.wikipedia.org/wiki/Jenkins_(software). Jenkins is actually very cool and also helps run (and keep track of) the consumers for our donation service for example.
James
On Wed, Jun 27, 2012 at 2:16 PM, Chris McMahon cmcmahon@wikimedia.orgwrote:
On Wed, Jun 27, 2012 at 2:06 PM, Derric Atzrott < datzrott@alizeepathology.com> wrote:
So I hate to be that guy who doesn't know the simple things, but what is Jenkins? The server has come up in discussion a few times since I joined this mailing list about a month ago.
And since no one has mentioned it yet, you might want to read http://en.wikipedia.org/wiki/Continuous_integration.
Jenkins is an open source system for doing CI. It used to be called Hudson. (Those are both names of butlers, which has always been the mascot of the project.) Over time, Jenkins has become a very powerful hub for automated testing and deployment, and most serious software projects integrate with Jenkins via "plugins". (Although some of those projects don't do it very well, Fitnesse for example.) -C _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Le 27/06/12 22:06, Derric Atzrott a écrit :
So I hate to be that guy who doesn't know the simple things, but what is Jenkins? The server has come up in discussion a few times since I joined this mailing list about a month ago.
Actually if there is a Wiki page where these sorts of things are documented. that would be fantastic.
There was not wiki page until someone asked for one :-] I have wrote a very quick description on:
https://www.mediawiki.org/wiki/Continuous_integration/Jenkins
Basically, Jenkins is a tool to automatically run tasks and report its status. The typical example is to build packages or execute a test suite.
wikitech-l@lists.wikimedia.org