This repository has been archived by the owner on Apr 6, 2022. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
[FIXED JENKINS-13397] Added help for pattern fields.
- Loading branch information
Showing
14 changed files
with
653 additions
and
47 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,8 @@ | ||
rm -rf $HUDSON_HOME/plugins/tasks* | ||
rm -rf $HUDSON_HOME/plugins/warnings* | ||
|
||
mvn install || { echo "Build failed"; exit 1; } | ||
|
||
cp -f target/*.hpi $HUDSON_HOME/plugins/ | ||
|
||
cd $HUDSON_HOME | ||
java -jar jenkins.war | ||
./debug.sh |
9 changes: 1 addition & 8 deletions
9
src/main/resources/hudson/plugins/tasks/TasksPublisher/config.jelly
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
158 changes: 158 additions & 0 deletions
158
src/main/resources/hudson/plugins/tasks/TasksPublisher/help-excludePattern.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,158 @@ | ||
<div> | ||
<p>Patterns look very much like the patterns used in DOS and | ||
UNIX:</p> | ||
<p>'*' matches zero or more characters, '?' matches one character.</p> | ||
|
||
<p> | ||
In general, patterns are considered relative paths, relative to the | ||
Jenkins workspace. Only files found below that base directory are | ||
considered. So while a pattern like | ||
<code>../foo.java</code> | ||
is possible, it will not match anything when applied since the base | ||
directory's parent is never scanned for files. | ||
</p> | ||
|
||
<p> | ||
<b>Examples:</b> | ||
</p> | ||
<p> | ||
<code>*.java</code> | ||
matches | ||
<code>.java</code> | ||
, | ||
<code>x.java</code> | ||
and | ||
<code>FooBar.java</code> | ||
, but not | ||
<code>FooBar.xml</code> | ||
(does not end with | ||
<code>.java</code> | ||
). | ||
</p> | ||
<p> | ||
<code>?.java</code> | ||
matches | ||
<code>x.java</code> | ||
, | ||
<code>A.java</code> | ||
, but not | ||
<code>.java</code> | ||
or | ||
<code>xyz.java</code> | ||
(both don't have one character before | ||
<code>.java</code> | ||
). | ||
</p> | ||
<p> | ||
Combinations of | ||
<code>*</code> | ||
's and | ||
<code>?</code> | ||
's are allowed. | ||
</p> | ||
<p> | ||
Matching is done per-directory. This means that first the first | ||
directory in the pattern is matched against the first directory in | ||
the path to match. Then the second directory is matched, and so on. | ||
For example, when we have the pattern | ||
<code>/?abc/*/*.java</code> | ||
and the path | ||
<code>/xabc/foobar/test.java</code> | ||
, the first | ||
<code>?abc</code> | ||
is matched with | ||
<code>xabc</code> | ||
, then | ||
<code>*</code> | ||
is matched with | ||
<code>foobar</code> | ||
, and finally | ||
<code>*.java</code> | ||
is matched with | ||
<code>test.java</code> | ||
. They all match, so the path matches the pattern. | ||
</p> | ||
<p> | ||
To make things a bit more flexible, we add one extra feature, which | ||
makes it possible to match multiple directory levels. This can be | ||
used to match a complete directory tree, or a file anywhere in the | ||
directory tree. To do this, | ||
<code>**</code> | ||
must be used as the name of a directory. When | ||
<code>**</code> | ||
is used as the name of a directory in the pattern, it matches zero | ||
or more directories. For example: | ||
<code>/test/**</code> | ||
matches all files/directories under | ||
<code>/test/</code> | ||
, such as | ||
<code>/test/x.java</code> | ||
, or | ||
<code>/test/foo/bar/xyz.html</code> | ||
, but not | ||
<code>/xyz.xml</code> | ||
. | ||
</p> | ||
<p> | ||
There is one "shorthand": if a pattern ends with | ||
<code>/</code> | ||
or | ||
<code>\</code> | ||
, then | ||
<code>**</code> | ||
is appended. For example, | ||
<code>mypackage/test/</code> | ||
is interpreted as if it were | ||
<code>mypackage/test/**</code> | ||
. | ||
</p> | ||
<p> | ||
<b>Example patterns:</b> | ||
</p> | ||
<table border="1" cellpadding="2" cellspacing="0"> | ||
<tr> | ||
<td valign="top"><code>**/CVS/*</code></td> | ||
<td valign="top">Matches all files in <code>CVS</code> | ||
directories that can be located anywhere in the directory tree.<br> | ||
Matches: <pre> | ||
CVS/Repository | ||
org/apache/CVS/Entries | ||
org/apache/jakarta/tools/ant/CVS/Entries | ||
</pre> But not: <pre> | ||
org/apache/CVS/foo/bar/Entries (<code>foo/bar/</code> | ||
part does not match) | ||
</pre> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td valign="top"><code>org/apache/jakarta/**</code></td> | ||
<td valign="top">Matches all files in the <code>org/apache/jakarta</code> | ||
directory tree.<br> Matches: <pre> | ||
org/apache/jakarta/tools/ant/docs/index.html | ||
org/apache/jakarta/test.xml | ||
</pre> But not: <pre> | ||
org/apache/xyz.java | ||
</pre> (<code>jakarta/</code> part is missing). | ||
</td> | ||
</tr> | ||
<tr> | ||
<td valign="top"><code>org/apache/**/CVS/*</code></td> | ||
<td valign="top">Matches all files in <code>CVS</code> | ||
directories that are located anywhere in the directory tree | ||
under <code>org/apache</code>.<br> Matches: <pre> | ||
org/apache/CVS/Entries | ||
org/apache/jakarta/tools/ant/CVS/Entries | ||
</pre> But not: <pre> | ||
org/apache/CVS/foo/bar/Entries | ||
</pre> (<code>foo/bar/</code> part does not match) | ||
</td> | ||
</tr> | ||
<tr> | ||
<td valign="top"><code>**/test/**</code></td> | ||
<td valign="top">Matches all files that have a <code>test</code> | ||
element in their path, including <code>test</code> as a | ||
filename. | ||
</td> | ||
</tr> | ||
</table> | ||
</div> |
158 changes: 158 additions & 0 deletions
158
src/main/resources/hudson/plugins/tasks/TasksPublisher/help-pattern.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,158 @@ | ||
<div> | ||
<p>Patterns look very much like the patterns used in DOS and | ||
UNIX:</p> | ||
<p>'*' matches zero or more characters, '?' matches one character.</p> | ||
|
||
<p> | ||
In general, patterns are considered relative paths, relative to the | ||
Jenkins workspace. Only files found below that base directory are | ||
considered. So while a pattern like | ||
<code>../foo.java</code> | ||
is possible, it will not match anything when applied since the base | ||
directory's parent is never scanned for files. | ||
</p> | ||
|
||
<p> | ||
<b>Examples:</b> | ||
</p> | ||
<p> | ||
<code>*.java</code> | ||
matches | ||
<code>.java</code> | ||
, | ||
<code>x.java</code> | ||
and | ||
<code>FooBar.java</code> | ||
, but not | ||
<code>FooBar.xml</code> | ||
(does not end with | ||
<code>.java</code> | ||
). | ||
</p> | ||
<p> | ||
<code>?.java</code> | ||
matches | ||
<code>x.java</code> | ||
, | ||
<code>A.java</code> | ||
, but not | ||
<code>.java</code> | ||
or | ||
<code>xyz.java</code> | ||
(both don't have one character before | ||
<code>.java</code> | ||
). | ||
</p> | ||
<p> | ||
Combinations of | ||
<code>*</code> | ||
's and | ||
<code>?</code> | ||
's are allowed. | ||
</p> | ||
<p> | ||
Matching is done per-directory. This means that first the first | ||
directory in the pattern is matched against the first directory in | ||
the path to match. Then the second directory is matched, and so on. | ||
For example, when we have the pattern | ||
<code>/?abc/*/*.java</code> | ||
and the path | ||
<code>/xabc/foobar/test.java</code> | ||
, the first | ||
<code>?abc</code> | ||
is matched with | ||
<code>xabc</code> | ||
, then | ||
<code>*</code> | ||
is matched with | ||
<code>foobar</code> | ||
, and finally | ||
<code>*.java</code> | ||
is matched with | ||
<code>test.java</code> | ||
. They all match, so the path matches the pattern. | ||
</p> | ||
<p> | ||
To make things a bit more flexible, we add one extra feature, which | ||
makes it possible to match multiple directory levels. This can be | ||
used to match a complete directory tree, or a file anywhere in the | ||
directory tree. To do this, | ||
<code>**</code> | ||
must be used as the name of a directory. When | ||
<code>**</code> | ||
is used as the name of a directory in the pattern, it matches zero | ||
or more directories. For example: | ||
<code>/test/**</code> | ||
matches all files/directories under | ||
<code>/test/</code> | ||
, such as | ||
<code>/test/x.java</code> | ||
, or | ||
<code>/test/foo/bar/xyz.html</code> | ||
, but not | ||
<code>/xyz.xml</code> | ||
. | ||
</p> | ||
<p> | ||
There is one "shorthand": if a pattern ends with | ||
<code>/</code> | ||
or | ||
<code>\</code> | ||
, then | ||
<code>**</code> | ||
is appended. For example, | ||
<code>mypackage/test/</code> | ||
is interpreted as if it were | ||
<code>mypackage/test/**</code> | ||
. | ||
</p> | ||
<p> | ||
<b>Example patterns:</b> | ||
</p> | ||
<table border="1" cellpadding="2" cellspacing="0"> | ||
<tr> | ||
<td valign="top"><code>**/CVS/*</code></td> | ||
<td valign="top">Matches all files in <code>CVS</code> | ||
directories that can be located anywhere in the directory tree.<br> | ||
Matches: <pre> | ||
CVS/Repository | ||
org/apache/CVS/Entries | ||
org/apache/jakarta/tools/ant/CVS/Entries | ||
</pre> But not: <pre> | ||
org/apache/CVS/foo/bar/Entries (<code>foo/bar/</code> | ||
part does not match) | ||
</pre> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td valign="top"><code>org/apache/jakarta/**</code></td> | ||
<td valign="top">Matches all files in the <code>org/apache/jakarta</code> | ||
directory tree.<br> Matches: <pre> | ||
org/apache/jakarta/tools/ant/docs/index.html | ||
org/apache/jakarta/test.xml | ||
</pre> But not: <pre> | ||
org/apache/xyz.java | ||
</pre> (<code>jakarta/</code> part is missing). | ||
</td> | ||
</tr> | ||
<tr> | ||
<td valign="top"><code>org/apache/**/CVS/*</code></td> | ||
<td valign="top">Matches all files in <code>CVS</code> | ||
directories that are located anywhere in the directory tree | ||
under <code>org/apache</code>.<br> Matches: <pre> | ||
org/apache/CVS/Entries | ||
org/apache/jakarta/tools/ant/CVS/Entries | ||
</pre> But not: <pre> | ||
org/apache/CVS/foo/bar/Entries | ||
</pre> (<code>foo/bar/</code> part does not match) | ||
</td> | ||
</tr> | ||
<tr> | ||
<td valign="top"><code>**/test/**</code></td> | ||
<td valign="top">Matches all files that have a <code>test</code> | ||
element in their path, including <code>test</code> as a | ||
filename. | ||
</td> | ||
</tr> | ||
</table> | ||
</div> |
9 changes: 1 addition & 8 deletions
9
src/main/resources/hudson/plugins/tasks/TasksReporter/config.jelly
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 changes: 0 additions & 5 deletions
5
src/main/resources/hudson/plugins/tasks/TasksReporter/config.properties
This file was deleted.
Oops, something went wrong.
11 changes: 0 additions & 11 deletions
11
src/main/resources/hudson/plugins/tasks/TasksReporter/config_de.properties
This file was deleted.
Oops, something went wrong.
12 changes: 0 additions & 12 deletions
12
src/main/resources/hudson/plugins/tasks/TasksReporter/config_ja.properties
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.