yetus-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject yetus git commit: YETUS-64, YETUS-77
Date Thu, 29 Oct 2015 15:04:55 GMT
Repository: yetus
Updated Branches:
  refs/heads/asf-site c2e4f8618 -> f7e1368c8



Branch: refs/heads/asf-site
Commit: f7e1368c8e2d00f38433a8f43933cb6db1b691ff
Parents: c2e4f86
Author: Allen Wittenauer <>
Authored: Thu Oct 29 08:04:48 2015 -0700
Committer: Allen Wittenauer <>
Committed: Thu Oct 29 08:04:48 2015 -0700

 doap_yetus.rdf                                  | 54 ++++++++++++++++++++
 .../latest/precommit-bugsystems/index.html      | 35 +++++++++++++
 2 files changed, 89 insertions(+)
diff --git a/doap_yetus.rdf b/doap_yetus.rdf
new file mode 100644
index 0000000..b57a982
--- /dev/null
+++ b/doap_yetus.rdf
@@ -0,0 +1,54 @@
+<?xml version="1.0"?>
+<?xml-stylesheet type="text/xsl"?>
+<rdf:RDF xml:lang="en"
+         xmlns=""
+         xmlns:rdf=""
+         xmlns:asfext=""
+         xmlns:foaf="">
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+  <Project rdf:about="">
+    <created>2015-09-16</created>
+    <license rdf:resource="" />
+    <name>Apache Yetus</name>
+    <homepage rdf:resource="" />
+    <asfext:pmc rdf:resource="" />
+    <shortdesc>A collection of libraries and tools that enable contribution and release
processes for software projects.</shortdesc>
+    <description>A collection of libraries and tools that enable contribution and release
processes for software projects.</description>
+    <bug-database rdf:resource="" />
+    <mailing-list rdf:resource="" />
+    <download-page rdf:resource="" />
+    <programming-language>Bash</programming-language>
+    <programming-language>Java</programming-language>
+    <programming-language>Python</programming-language>
+    <category rdf:resource="" />
+    <category rdf:resource="" />
+    <category rdf:resource="" />
+    <repository>
+      <GitRepository>
+        <location rdf:resource=""/>
+        <browse rdf:resource=""/>
+      </GitRepository>
+    </repository>
+    <maintainer>
+      <foaf:Person>
+        <foaf:name>Allen Wittenauer</foaf:name>
+          <foaf:mbox rdf:resource=""/>
+      </foaf:Person>
+    </maintainer>
+  </Project>
diff --git a/documentation/latest/precommit-bugsystems/index.html b/documentation/latest/precommit-bugsystems/index.html
index 8131cb3..77a2aba 100644
--- a/documentation/latest/precommit-bugsystems/index.html
+++ b/documentation/latest/precommit-bugsystems/index.html
@@ -151,6 +151,41 @@
+<h1 id="bugzilla-specific">Bugzilla Specific</h1>
+<p>Currently, Bugzilla support is read-only.  To use it, the Bug ID must be preferenced
with &lsquo;BZ:&rsquo;.  For example:</p>
+<pre class="highlight shell"><code><span class="gp">$ </span><span
class="nb">test</span> <span class="o">(</span>other options<span
class="o">)</span> BZ:4
+<p>&hellip; will pull down Bugzilla ID #4.</p>
+<p>Using the <code>--bugzilla-base-url</code> on the command line or BUGZILLA_BASE_URL
in a project&rsquo;s personality will define the location of the Bugzilla instance.  By
default, it is <a href=""></a>
+<h1 id="github-specific">GitHub Specific</h1>
+<p>GitHub supports the full range of functionality, including putting comments on individual
lines.  Be aware, however, that will require that GitHub PRs be fully rebased
(i.e., a single commit) in many circumstances.</p>
+<p>By default, the GitHub plug-in assumes that <a href=""></a>
is the base URL for GitHub.  Enterprise users may override this with the <code>--github-base-url</code>
for the normal web user interface and <code>--github-api-url</code> for the API
URL.  Personalities may use GITHUB_API_URL and GITHUB_BASE_URL.</p>
+<p>The specific repository on GitHub is defined with either <code>--github-repo</code>
on the command line or GITHUB_REPO in a personality.  It should take the form of &ldquo;user/repo&rdquo;.</p>
+<p>In order to comment on issues or, depending upon the security setup of the repo,
authentication credentials.  The GitHub plug-in supports two types:</p>
+<li><p>Token-based:  <code>--github-token</code> or GITHUB_TOKEN</p></li>
+<li><p>Username/password: <code>--github-user</code>/ GITHUB_USER
, <code>--github-password</code> / GITHUB_PASSWD</p></li>
+<p>Pull requests that are made off of a specific branch will switch the test repo to
that branch, if permitted.  If the pull request references a JIRA issue that matches the given
JIRA issue regexp in the Subject, the JIRA plug-in will also be invoked as needed.</p>
+<h1 id="jira-specific">JIRA Specific</h1>
+<p>JIRA support allows both patch downloads and summary writes.  It also supports branch
detection-based upon the name of the attached patch file.</p>
+<p>JIRA issues are invoked by matching the command line option to a specific regular
expression as given by the <code>--jira-issue-re</code> option or via the JIRA_ISSUE_RE
personality variable.  By default, the plug-in uses <a href=""></a>
as the JIRA instance to use.  However that may be overwritten via the <code>--jira-base-url</code>
option or personalities may define via JIRA_URL.</p>
+<p>In order to write information on the issue, JIRA requires username and password
authentication using the <code>--jira-user</code>/<code>--jira-password</code>
options or the JIRA_USER and JIRA_PASSWORD variables in a personality.</p>
       <div class="container">

View raw message