You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Herbert Duerr <hd...@apache.org> on 2012/07/09 13:37:24 UTC
Testing of SVN Bugzilla Robot enabled (was: [Bug 25920] test issue)
Testing is enabled now for the robot [1] that watches out for commits
into our SVN-tree and updates then updates the corresponding bugzilla
entry if an issue was referenced in the commit summary.
[1] https://issues.apache.org/jira/browse/INFRA-5004
At the beginning of the commit summary classic issue references such as
#i123456# are recognized. Some committers demanded that issue reference
such as #123456# (without the 'i') are also accepted, so they are
recognized too. Should we ever switch to another tracker like JIRA this
will have to be revisited, though.
If the test is successful there is a good chance that the automatism
will be deployed in the apache infrastructure.
Currently the robot adds a one-line comment to an issue, e.g.
"hdu" committed SVN revision 1234567: #i25920# a test commit
Would it be helpful if the comment was more or less verbose? E.g. it
could mention whether trunk or a branch was updated, which sub-projects
(e.g. sw, sc) were touched, whether a commit into the release branch had
a matching release-blocker flag, etc.
Herbert
Re: Testing of SVN Bugzilla Robot enabled
Posted by Herbert Duerr <hd...@apache.org>.
Armin Le Grand wrote:
> Herbert Duerr <hd...@apache.org> wrote:
>> Currently the robot adds a one-line comment to an issue, e.g.
>> "hdu" committed SVN revision 1234567: #i25920# a test commit
>> Would it be helpful if the comment was more or less verbose? E.g. it
>> could mention whether trunk or a branch was updated, which sub-projects
>> (e.g. sw, sc) were touched, whether a commit into the release branch had
>> a matching release-blocker flag, etc.
>
> Nice Idea! But why not simply take all the comment instead of trying to
> 'guess' the first line?
Currently I have the practical problem that the script listens to the
svnpubsub service to get the commit details and the functionality there
"optimizes linefeeds" away, so that the full description would be
somehow mangled. Once this is solved (or replaced by asking svn
directly) we can do this.
> I often try to provide a brief description for the
> commit on the command line and a longer one on the task (including the
> shorter from the commit plus extra infos). With your change I could simply
> add a single, more extensive description when comitting.
A good change description would be good regardless of the svnbot.
> Maybe the 'Patch
> by:', etc. fields should be filtered out though (by identifyingb them using
> the ':' or 'by*:'. Just my 2 cent...
That's a good idea. Otherwise the bugzilla comment would look too
automatic and noisy.
Other than that I changed the machine the test svnbot is running on not
to fall into sleep when there was no key/mouse/net interaction for a
while. Due to that problem some commits last night didn't result in
automatic bugzilla updates. Sorry about that.
Herbert
Re: Testing of SVN Bugzilla Robot enabled (was: [Bug 25920] test issue)
Posted by Armin Le Grand <Ar...@me.com>.
Hi Herbert,
Herbert Duerr <hd...@apache.org> wrote:
> Testing is enabled now for the robot [1] that watches out for commits
> into our SVN-tree and updates then updates the corresponding bugzilla
> entry if an issue was referenced in the commit summary.
>
> [1] https://issues.apache.org/jira/browse/INFRA-5004
>
> At the beginning of the commit summary classic issue references such as
> #i123456# are recognized. Some committers demanded that issue reference
> such as #123456# (without the 'i') are also accepted, so they are
> recognized too. Should we ever switch to another tracker like JIRA this
> will have to be revisited, though.
>
> If the test is successful there is a good chance that the automatism will
> be deployed in the apache infrastructure.
>
> Currently the robot adds a one-line comment to an issue, e.g.
> "hdu" committed SVN revision 1234567: #i25920# a test commit
> Would it be helpful if the comment was more or less verbose? E.g. it
> could mention whether trunk or a branch was updated, which sub-projects
> (e.g. sw, sc) were touched, whether a commit into the release branch had
> a matching release-blocker flag, etc.
Nice Idea! But why not simply take all the comment instead of trying to
'guess' the first line? I often try to provide a brief description for the
commit on the command line and a longer one on the task (including the
shorter from the commit plus extra infos). With your change I could simply
add a single, more extensive description when comitting. Maybe the 'Patch
by:', etc. fields should be filtered out though (by identifyingb them using
the ':' or 'by*:'. Just my 2 cent...
>
> Herbert
--
ALG
Re: Testing of SVN Bugzilla Robot enabled (was: [Bug 25920] test issue)
Posted by Kay Schenk <ka...@gmail.com>.
On Mon, Jul 9, 2012 at 4:37 AM, Herbert Duerr <hd...@apache.org> wrote:
> Testing is enabled now for the robot [1] that watches out for commits into
> our SVN-tree and updates then updates the corresponding bugzilla entry if
> an issue was referenced in the commit summary.
>
> [1] https://issues.apache.org/**jira/browse/INFRA-5004<https://issues.apache.org/jira/browse/INFRA-5004>
>
> At the beginning of the commit summary classic issue references such as
> #i123456# are recognized. Some committers demanded that issue reference
> such as #123456# (without the 'i') are also accepted, so they are
> recognized too. Should we ever switch to another tracker like JIRA this
> will have to be revisited, though.
>
> If the test is successful there is a good chance that the automatism will
> be deployed in the apache infrastructure.
>
> Currently the robot adds a one-line comment to an issue, e.g.
> "hdu" committed SVN revision 1234567: #i25920# a test commit
> Would it be helpful if the comment was more or less verbose? E.g. it could
> mention whether trunk or a branch was updated, which sub-projects (e.g. sw,
> sc) were touched, whether a commit into the release branch had a matching
> release-blocker flag, etc.
>
> Herbert
>
This would be super! Thanks for getting this started!
--
----------------------------------------------------------------------------------------
MzK
"I would rather have a donkey that takes me there
than a horse that will not fare."
-- Portuguese proverb
Re: Testing of SVN Bugzilla Robot enabled
Posted by Herbert Duerr <hd...@apache.org>.
On 09.07.2012 20:54, Dave Fisher wrote:
> On Jul 9, 2012, at 4:37 AM, Herbert Duerr wrote:
>> Testing is enabled now for the robot [1] that watches out for commits into our SVN-tree and updates then updates the corresponding bugzilla entry if an issue was referenced in the commit summary.
>> [...]
>> Currently the robot adds a one-line comment to an issue, e.g.
>> "hdu" committed SVN revision 1234567: #i25920# a test commit
>> Would it be helpful if the comment was more or less verbose? E.g. it could mention whether trunk or a branch was updated, which sub-projects (e.g. sw, sc) were touched, whether a commit into the release branch had a matching release-blocker flag, etc.
>
> You could add the url:
>
> http://svn.apache.org/viewvc?view=revision&revision=1234567
>
> That link can followed to show the whole commit.
Bugzilla already recognizes the keyword "revision" followed by a number
and then automatically links into viewvc. Please see e.g.
https://issues.apache.org/ooo/show_bug.cgi?id=120234#c2
where the full details of the commit are only a click away.
Herbert
Re: Testing of SVN Bugzilla Robot enabled
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 07/09/2012 08:54 PM, schrieb Dave Fisher:
>
> On Jul 9, 2012, at 4:37 AM, Herbert Duerr wrote:
>
>> Testing is enabled now for the robot [1] that watches out for commits into our SVN-tree and updates then updates the corresponding bugzilla entry if an issue was referenced in the commit summary.
that's great. Thanks for this nice feature, Herbert.
>> [1] https://issues.apache.org/jira/browse/INFRA-5004
>>
>> At the beginning of the commit summary classic issue references such as #i123456# are recognized. Some committers demanded that issue reference such as #123456# (without the 'i') are also accepted, so they are recognized too. Should we ever switch to another tracker like JIRA this will have to be revisited, though.
>>
>> If the test is successful there is a good chance that the automatism will be deployed in the apache infrastructure.
>>
>> Currently the robot adds a one-line comment to an issue, e.g.
>> "hdu" committed SVN revision 1234567: #i25920# a test commit
>> Would it be helpful if the comment was more or less verbose? E.g. it could mention whether trunk or a branch was updated, which sub-projects (e.g. sw, sc) were touched, whether a commit into the release branch had a matching release-blocker flag, etc.
I'm not a coder on the Office code ;-) but a hint on which branch the
commit was done would be helpful for everyone to get the overview.
> You could add the url:
>
> http://svn.apache.org/viewvc?view=revision&revision=1234567
>
> That link can followed to show the whole commit.
+1
Marcus
Re: Testing of SVN Bugzilla Robot enabled (was: [Bug 25920] test issue)
Posted by Dave Fisher <da...@comcast.net>.
On Jul 9, 2012, at 4:37 AM, Herbert Duerr wrote:
> Testing is enabled now for the robot [1] that watches out for commits into our SVN-tree and updates then updates the corresponding bugzilla entry if an issue was referenced in the commit summary.
>
> [1] https://issues.apache.org/jira/browse/INFRA-5004
>
> At the beginning of the commit summary classic issue references such as #i123456# are recognized. Some committers demanded that issue reference such as #123456# (without the 'i') are also accepted, so they are recognized too. Should we ever switch to another tracker like JIRA this will have to be revisited, though.
>
> If the test is successful there is a good chance that the automatism will be deployed in the apache infrastructure.
>
> Currently the robot adds a one-line comment to an issue, e.g.
> "hdu" committed SVN revision 1234567: #i25920# a test commit
> Would it be helpful if the comment was more or less verbose? E.g. it could mention whether trunk or a branch was updated, which sub-projects (e.g. sw, sc) were touched, whether a commit into the release branch had a matching release-blocker flag, etc.
You could add the url:
http://svn.apache.org/viewvc?view=revision&revision=1234567
That link can followed to show the whole commit.
Regards,
Dave
>
> Herbert