Examine individual changes

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to:navigation Jump to:search

This page allows you to examine the variables generated by the Abuse Filter for an individual change, and test it against filters.

Variables generated for this change

VariableValue
Edit count of the user (user_editcount)
304
Name of the user account (user_name)
'Sam'
Age of the user account (user_age)
110672819
Page ID (page_id)
226076
Page namespace (page_namespace)
510
Page title (without namespace) (page_title)
'Build Service'
Full page title (page_prefixedtitle)
'Project:Build Service'
Action (action)
'edit'
Edit summary/reason (summary)
'Retire mudler'
Old content model (old_content_model)
'wikitext'
New content model (new_content_model)
'wikitext'
Old page wikitext, before the edit (old_wikitext)
'{{Project |Name=Gentoo Build Service |Description=Deploy privately a build service for building and testing Gentoo packages. |IRC=#gentoo-buildservice |ParentProject=Project:Gentoo |PropagatesMembers=No |Members={{Project Member |Developer=User:Mudler |Role=Lead |IsLead=Yes }}{{Project Member |Developer=User:Amynka |IsLead=No }}{{Project Member |Developer=User:MGorny |IsLead=No }} }} The Gentoo Build Service project will have as aim to provide a software and relative ebuilds that would offer a way to deploy privately a build service: A web interface that exposes API to control remote workers (a cluster of builder nodes) that can build packages as a set of repo with specifications that indicates the packages, the steps, and the desired customizations (useflags, keywords, local ebuilds override, ecc..). Workers will build packages on top of a container or a VM - with support (at least) for Docker. In such way, the webui can be hooked also to Github repositories, and build-test against Pull requests or changes of an overlay, and even the Gentoo tree, with the option to publish the generated artefacts thru the web server. '''The project is still in early stage, so consider this page under construction yet.''' == Project status == Code is still '''alpha''', usage is encouraged in a local environment still. Documentation (in construction) can be found [https://mottainaici.github.io/docs/ here]. If you are experimenting it - do it locally or do not expose the service outside your network. It is composed already of a server (master), a CLI and an agent executable for bringing up nodes to the cluster. Configurations can also be managed with etcd. A web interface is available to display tasks overview and starting new builds, it's also possible to see the build live from the webui. It currently allows remote building: nodes are executing the steps inside a Docker container or a Vagrant environment, the content originated from it is managed and can be published. Nodes are communicating with a broker which can be MongoDB, AMQP (e.g RabbitMQ), Redis, AWS SQS, memcache, Dynamodb. The repositories containing the tools are currently [https://github.com/MottainaiCI here] and in the [https://github.com/gentoo-build-service Build Service Project] organization on GitHub. == User contributors == {| class="table table-striped table-condensed" |- ! User !! Name !! Role |- | [[User:geaaru|geaaru]] || Daniele Rondina || Developer |} == Development plan / TODO == * Implement syncing of artefacts [Done] * Handle Namespaces (tag, publish) [Done] * Handle GitHub webhooks [Done] * Implement Users/Groups and login system [Done] * Nail down security aspects * Documentation * Release'
New page wikitext, after the edit (new_wikitext)
'{{Project |Name=Gentoo Build Service |Description=Deploy privately a build service for building and testing Gentoo packages. |IRC=#gentoo-buildservice |ParentProject=Project:Gentoo |PropagatesMembers=No |Members={{Project Member |Developer=User:Amynka |IsLead=No }}{{Project Member |Developer=User:MGorny |IsLead=No }} }} The Gentoo Build Service project will have as aim to provide a software and relative ebuilds that would offer a way to deploy privately a build service: A web interface that exposes API to control remote workers (a cluster of builder nodes) that can build packages as a set of repo with specifications that indicates the packages, the steps, and the desired customizations (useflags, keywords, local ebuilds override, ecc..). Workers will build packages on top of a container or a VM - with support (at least) for Docker. In such way, the webui can be hooked also to Github repositories, and build-test against Pull requests or changes of an overlay, and even the Gentoo tree, with the option to publish the generated artefacts thru the web server. '''The project is still in early stage, so consider this page under construction yet.''' == Project status == Code is still '''alpha''', usage is encouraged in a local environment still. Documentation (in construction) can be found [https://mottainaici.github.io/docs/ here]. If you are experimenting it - do it locally or do not expose the service outside your network. It is composed already of a server (master), a CLI and an agent executable for bringing up nodes to the cluster. Configurations can also be managed with etcd. A web interface is available to display tasks overview and starting new builds, it's also possible to see the build live from the webui. It currently allows remote building: nodes are executing the steps inside a Docker container or a Vagrant environment, the content originated from it is managed and can be published. Nodes are communicating with a broker which can be MongoDB, AMQP (e.g RabbitMQ), Redis, AWS SQS, memcache, Dynamodb. The repositories containing the tools are currently [https://github.com/MottainaiCI here] and in the [https://github.com/gentoo-build-service Build Service Project] organization on GitHub. == User contributors == {| class="table table-striped table-condensed" |- ! User !! Name !! Role |- | [[User:geaaru|geaaru]] || Daniele Rondina || Developer |} == Development plan / TODO == * Implement syncing of artefacts [Done] * Handle Namespaces (tag, publish) [Done] * Handle GitHub webhooks [Done] * Implement Users/Groups and login system [Done] * Nail down security aspects * Documentation * Release'
Unified diff of changes made by edit (edit_diff)
'@@ -6,8 +6,4 @@ |PropagatesMembers=No |Members={{Project Member -|Developer=User:Mudler -|Role=Lead -|IsLead=Yes -}}{{Project Member |Developer=User:Amynka |IsLead=No '
Old page size (old_size)
2713
Lines added in edit (added_lines)
[]
Lines removed in edit (removed_lines)
[ 0 => '|Developer=User:Mudler', 1 => '|Role=Lead', 2 => '|IsLead=Yes', 3 => '}}{{Project Member' ]
New page text, stripped of any markup (new_text)
' Gentoo Build Service Description Deploy privately a build service for building and testing Gentoo packages. Project email IRC channel #gentoo-buildservice Lead(s) Ettore Di Giacinto (mudler)Lead No lead election date set Member(s) Amy Liffey (amynka)Michał Górny (mgorny) Subproject(s)(and inherited member(s)) (none) Parent Project Gentoo Project listing The Gentoo Build Service project will have as aim to provide a software and relative ebuilds that would offer a way to deploy privately a build service: A web interface that exposes API to control remote workers (a cluster of builder nodes) that can build packages as a set of repo with specifications that indicates the packages, the steps, and the desired customizations (useflags, keywords, local ebuilds override, ecc..). Workers will build packages on top of a container or a VM - with support (at least) for Docker. In such way, the webui can be hooked also to Github repositories, and build-test against Pull requests or changes of an overlay, and even the Gentoo tree, with the option to publish the generated artefacts thru the web server. The project is still in early stage, so consider this page under construction yet. Project status[edit | edit source] Code is still alpha, usage is encouraged in a local environment still. Documentation (in construction) can be found here. If you are experimenting it - do it locally or do not expose the service outside your network. It is composed already of a server (master), a CLI and an agent executable for bringing up nodes to the cluster. Configurations can also be managed with etcd. A web interface is available to display tasks overview and starting new builds, it's also possible to see the build live from the webui. It currently allows remote building: nodes are executing the steps inside a Docker container or a Vagrant environment, the content originated from it is managed and can be published. Nodes are communicating with a broker which can be MongoDB, AMQP (e.g RabbitMQ), Redis, AWS SQS, memcache, Dynamodb. The repositories containing the tools are currently here and in the Build Service Project organization on GitHub. User contributors[edit | edit source] User Name Role geaaru Daniele Rondina Developer Development plan / TODO[edit | edit source] Implement syncing of artefacts [Done] Handle Namespaces (tag, publish) [Done] Handle GitHub webhooks [Done] Implement Users/Groups and login system [Done] Nail down security aspects Documentation Release'
Parsed HTML source of the new revision (new_html)
'<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;"> <tbody><tr> <th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>Gentoo Build Service</big> </th></tr> <tr valign="top"> <th>Description </th> <td style="text-align: justify;">Deploy privately a build service for building and testing Gentoo packages. </td></tr> <tr> <th><span title="Mails to member(s) listed below.">Project email</span> </th> <td> </td></tr> <tr> <th><span title="The link opens a webchat to this project&#39;s Freenode IRC channel.">IRC channel</span> </th> <td><a rel="nofollow" class="external text" href="https://webchat.freenode.net/?channels=gentoo-buildservice">#gentoo-buildservice</a> </td></tr> <tr valign="top"> <th>Lead(s) </th> <td><ul><li><a href="/wiki/User:Mudler" title="User:Mudler">Ettore Di Giacinto</a> (mudler)<br /><i>Lead</i></li></ul> <br />No lead election date set </td></tr> <tr valign="top"> <th>Member(s) </th> <td><ul><li><a href="/wiki/User:Amynka" title="User:Amynka">Amy Liffey</a> (amynka)</li><li><a href="/wiki/User:MGorny" title="User:MGorny">Michał Górny</a> (mgorny)</li></ul> </td></tr> <tr valign="top"> <th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small> </th> <td>(none) </td></tr> <tr> <th>Parent Project </th> <td><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Gentoo</a> </td></tr> <tr> <td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a> </td></tr></tbody></table> <p>The Gentoo Build Service project will have as aim to provide a software and relative ebuilds that would offer a way to deploy privately a build service: </p><p>A web interface that exposes API to control remote workers (a cluster of builder nodes) that can build packages as a set of repo with specifications that indicates the packages, the steps, and the desired customizations (useflags, keywords, local ebuilds override, ecc..). Workers will build packages on top of a container or a VM - with support (at least) for Docker. </p><p>In such way, the webui can be hooked also to Github repositories, and build-test against Pull requests or changes of an overlay, and even the Gentoo tree, with the option to publish the generated artefacts thru the web server. </p><p><b>The project is still in early stage, so consider this page under construction yet.</b> </p> <h2><span class="mw-headline" id="Project_status">Project status</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Build_Service&amp;veaction=edit&amp;section=1" class="mw-editsection-visualeditor" title="Edit section: Project status">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Build_Service&amp;action=edit&amp;section=1" title="Edit section: Project status">edit source</a><span class="mw-editsection-bracket">]</span></span></h2> <p>Code is still <b>alpha</b>, usage is encouraged in a local environment still. Documentation (in construction) can be found <a rel="nofollow" class="external text" href="https://mottainaici.github.io/docs/">here</a>. </p><p>If you are experimenting it - do it locally or do not expose the service outside your network. It is composed already of a server (master), a CLI and an agent executable for bringing up nodes to the cluster. Configurations can also be managed with etcd. </p><p>A web interface is available to display tasks overview and starting new builds, it's also possible to see the build live from the webui. It currently allows remote building: nodes are executing the steps inside a Docker container or a Vagrant environment, the content originated from it is managed and can be published. Nodes are communicating with a broker which can be MongoDB, AMQP (e.g RabbitMQ), Redis, AWS SQS, memcache, Dynamodb. </p><p>The repositories containing the tools are currently <a rel="nofollow" class="external text" href="https://github.com/MottainaiCI">here</a> and in the <a rel="nofollow" class="external text" href="https://github.com/gentoo-build-service">Build Service Project</a> organization on GitHub. </p> <h2><span class="mw-headline" id="User_contributors">User contributors</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Build_Service&amp;veaction=edit&amp;section=2" class="mw-editsection-visualeditor" title="Edit section: User contributors">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Build_Service&amp;action=edit&amp;section=2" title="Edit section: User contributors">edit source</a><span class="mw-editsection-bracket">]</span></span></h2> <table class="table table-striped table-condensed"> <tbody><tr> <th>User</th> <th>Name</th> <th>Role </th></tr> <tr> <td><a href="/index.php?title=User:Geaaru&amp;action=edit&amp;redlink=1" class="new" title="User:Geaaru (page does not exist)">geaaru</a></td> <td>Daniele Rondina</td> <td>Developer </td></tr></tbody></table> <h2><span id="Development_plan_/_TODO"></span><span class="mw-headline" id="Development_plan_.2F_TODO">Development plan / TODO</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Build_Service&amp;veaction=edit&amp;section=3" class="mw-editsection-visualeditor" title="Edit section: Development plan / TODO">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Build_Service&amp;action=edit&amp;section=3" title="Edit section: Development plan / TODO">edit source</a><span class="mw-editsection-bracket">]</span></span></h2> <ul><li>Implement syncing of artefacts [Done]</li> <li>Handle Namespaces (tag, publish) [Done]</li> <li>Handle GitHub webhooks [Done]</li> <li>Implement Users/Groups and login system [Done]</li> <li>Nail down security aspects</li> <li>Documentation</li> <li>Release</li></ul> '
Unix timestamp of change (timestamp)
1612196542