Re: [HEADS UP] getTestResultAction removed in 1.577

2014-08-26 Thread Jesse Glick
On Tue, Aug 26, 2014 at 6:51 PM, 'Bruno P. Kinoshita' via Jenkins
Developers  wrote:
> IIRC the tap-plugin also utilizes these methods.

I do not think so—it calls TestObject.getTestResultAction, but that is
fine. Only the methods on AbstractBuild are affected.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [HEADS UP] getTestResultAction removed in 1.577

2014-08-26 Thread 'Bruno P. Kinoshita' via Jenkins Developers
Thanks for the heads up Jesse. IIRC the tap-plugin also utilizes these methods. 
I'll take a look this weekend and will update it.

Bruno

>
> From: Jesse Glick 
>To: Jenkins Dev  
>Sent: Tuesday, August 26, 2014 4:24 PM
>Subject: [HEADS UP] getTestResultAction removed in 1.577
> 
>
>For proper stratification I needed to deprecate
>AbstractBuild.getTestResultAction (and .getAggregatedTestResultAction)
>in Jenkins core 1.577, allowing the JUnit test result publisher and
>associated APIs to be split into junit-plugin. Plugins calling these
>methods will generally not work in 1.577+. The replacement is trivial
>and does not require a newer core dependency: just call
>.getAction(DesiredActionClass.class).
>
>For the economy of scale I committed this fix to the master branch of
>all plugins in https://github.com/jenkinsci/ a month ago, but did not
>release it except for a handful of bundled plugins. The following
>plugins still have this change unreleased as of this writing:
>
>ci-game-plugin
>email-ext-plugin
>extra-columns-plugin
>graphite-plugin
>integrity-plugin
>ivy-plugin
>JiraTestResultReporter-plugin
>lotus-connections-plugin
>meliora-testlab-plugin
>parallel-test-executor-plugin
>regression-report-plugin
>tikal-multijob-plugin
>violation-columns-plugin
>
>If you maintain one of these plugins, please consider cutting a
>release from trunk to support users of weekly builds. If there are
>other unreleased and unreleasable trunk changes, the fixing commits
>ought to be easy to backport to a special branch release, but reply
>here or to me privately if you need any help with that.
>
>-- 
>You received this message because you are subscribed to the Google Groups 
>"Jenkins Developers" group.
>To unsubscribe from this group and stop receiving emails from it, send an 
>email to jenkinsci-dev+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[HEADS UP] getTestResultAction removed in 1.577

2014-08-26 Thread Jesse Glick
For proper stratification I needed to deprecate
AbstractBuild.getTestResultAction (and .getAggregatedTestResultAction)
in Jenkins core 1.577, allowing the JUnit test result publisher and
associated APIs to be split into junit-plugin. Plugins calling these
methods will generally not work in 1.577+. The replacement is trivial
and does not require a newer core dependency: just call
.getAction(DesiredActionClass.class).

For the economy of scale I committed this fix to the master branch of
all plugins in https://github.com/jenkinsci/ a month ago, but did not
release it except for a handful of bundled plugins. The following
plugins still have this change unreleased as of this writing:

ci-game-plugin
email-ext-plugin
extra-columns-plugin
graphite-plugin
integrity-plugin
ivy-plugin
JiraTestResultReporter-plugin
lotus-connections-plugin
meliora-testlab-plugin
parallel-test-executor-plugin
regression-report-plugin
tikal-multijob-plugin
violation-columns-plugin

If you maintain one of these plugins, please consider cutting a
release from trunk to support users of weekly builds. If there are
other unreleased and unreleasable trunk changes, the fixing commits
ought to be easy to backport to a special branch release, but reply
here or to me privately if you need any help with that.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.