Warning Plugin 5.0 Release - Beta Testing

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Warning Plugin 5.0 Release - Beta Testing

Ulli Hafner
A new major release of the static analysis suite is about to come. Since there are a lot of changes (see [1]) I decided to start with a public beta. I.e., the new release is currently only available at the experimental update center.

Important changes at a glance:
- All plug-ins have been merged into the Warning Plug-in, i.e. there is only a single entry point for all static analysis tools now. That means that the plugins android-lint, ccm, checkstyle, dry, pmd, findbugs, analysis-core, analysis-collector, task-scanner are at end-of-life. You do not need them anymore after a (manual) migration of your existing jobs.
- New UI using modern frameworks (charts, tables, etc.). See documentation [1] for some screenshots and details about the user experience.
- New API for pipelines to combine and filter reports.

Since the wiki is not reliable in the moment I published the new documentation directly in GitHub [1].

HOW CAN YOU HELP?
- Convert some of your jobs to the new API and test the new (and old) features (based on your requirements).
- Read all labels carefully, I’m not a native speaker so some descriptions might be misleading or incorrect.
- Check the new URLs and names of the parsers, see list of supported formats [2].

If you find a problem, incorrect phrase, typo, etc. please report a bug in Jira (or even better: file a PR in GitHub).

[1] https://github.com/jenkinsci/warnings-plugin/blob/master/doc/Documentation.md
[2] https://github.com/jenkinsci/warnings-plugin/blob/master/SUPPORTED-FORMATS.md 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CE2AE646-04C8-44F4-930D-A493A2FF3359%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Warning Plugin 5.0 Release - Beta Testing

Ulli Hafner
The next beta release is available for download!

In order to simplify the upgrade process I moved all new reporters and steps to a completely new plugin: Warnings Next Generation Plugin (warnings-ng).
That means the old plugins (warnings, checkstyle, findbugs, analysis-core etc.) are not required anymore if you have converted your jobs.

You need to install the following plugins (from the experimental update center):
        • analysis-model-api: 1.0.0-beta9
        • warnings-ng (Warnings Next Generation Plugin): 1.0.0-beta1


> Am 10.09.2018 um 10:05 schrieb Ullrich Hafner <[hidden email]>:
>
> A new major release of the static analysis suite is about to come. Since there are a lot of changes (see [1]) I decided to start with a public beta. I.e., the new release is currently only available at the experimental update center.
>
> Important changes at a glance:
> - All plug-ins have been merged into the Warning Plug-in, i.e. there is only a single entry point for all static analysis tools now. That means that the plugins android-lint, ccm, checkstyle, dry, pmd, findbugs, analysis-core, analysis-collector, task-scanner are at end-of-life. You do not need them anymore after a (manual) migration of your existing jobs.
> - New UI using modern frameworks (charts, tables, etc.). See documentation [1] for some screenshots and details about the user experience.
> - New API for pipelines to combine and filter reports.
>
> Since the wiki is not reliable in the moment I published the new documentation directly in GitHub [1].
>
> HOW CAN YOU HELP?
> - Convert some of your jobs to the new API and test the new (and old) features (based on your requirements).
> - Read all labels carefully, I’m not a native speaker so some descriptions might be misleading or incorrect.
> - Check the new URLs and names of the parsers, see list of supported formats [2].
>
> If you find a problem, incorrect phrase, typo, etc. please report a bug in Jira (or even better: file a PR in GitHub).
>
> [1] https://github.com/jenkinsci/warnings-plugin/blob/master/doc/Documentation.md
> [2] https://github.com/jenkinsci/warnings-plugin/blob/master/SUPPORTED-FORMATS.md
>
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9141891F-F88A-43C7-8FA0-EFDDB3F2424E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (540 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Is there a way to force reconnect / redeploy of nodes after a Java update?

Adam von Nieda

   Hi folks,

   My situation is that I have to keep OpenJDK up to date on all of my Redhat 7 Linux boxes, and updating Java does not necessarily mean a system boot. Is there a way that I can tell the agents on a number of machines (preferably by label) to redeploy / restart, so that they will pick up the new Java? What happens is I update the JDK, and then jobs start failing because libraries no longer exist for the previous version of java, which is still running “remoting.jar”. 

   Thanks very much for the advice,

      -Adam 

--
Adam vonNieda


--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/168289C0-76F3-4C7D-9605-C34EB4DEF986%40vonnieda.org.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Is there a way to force reconnect / redeploy of nodes after a Java update?

Jan Monterrubio
Yeah, you can access the agents via Jenkins.getNodes()

Then in a loop do something like:

agent.setOffline() 
agent.reconnect()

Here’s some references that might help. 


On Thu, Nov 1, 2018 at 08:05 Adam von Nieda <[hidden email]> wrote:

   Hi folks,

   My situation is that I have to keep OpenJDK up to date on all of my Redhat 7 Linux boxes, and updating Java does not necessarily mean a system boot. Is there a way that I can tell the agents on a number of machines (preferably by label) to redeploy / restart, so that they will pick up the new Java? What happens is I update the JDK, and then jobs start failing because libraries no longer exist for the previous version of java, which is still running “remoting.jar”. 

   Thanks very much for the advice,

      -Adam 

--
Adam vonNieda


--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/168289C0-76F3-4C7D-9605-C34EB4DEF986%40vonnieda.org.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9Lxp-KfwJBrF--wSEg-w8MLbZOCWnBo47fNaYdwbQGtrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Is there a way to force reconnect / redeploy of nodes after a Java update?

Adam von Nieda

  Thanks very much Jan, that’s very helpful, and I appreciate the response :) 

      -Adam 

--
Adam vonNieda




On Nov 1, 2018, at 6:14 PM, Jan Monterrubio <[hidden email]> wrote:

Yeah, you can access the agents via Jenkins.getNodes()

Then in a loop do something like:

agent.setOffline() 
agent.reconnect()

Here’s some references that might help. 


On Thu, Nov 1, 2018 at 08:05 Adam von Nieda <[hidden email]> wrote:

   Hi folks,

   My situation is that I have to keep OpenJDK up to date on all of my Redhat 7 Linux boxes, and updating Java does not necessarily mean a system boot. Is there a way that I can tell the agents on a number of machines (preferably by label) to redeploy / restart, so that they will pick up the new Java? What happens is I update the JDK, and then jobs start failing because libraries no longer exist for the previous version of java, which is still running “remoting.jar”. 

   Thanks very much for the advice,

      -Adam 

--
Adam vonNieda



--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/168289C0-76F3-4C7D-9605-C34EB4DEF986%40vonnieda.org.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9Lxp-KfwJBrF--wSEg-w8MLbZOCWnBo47fNaYdwbQGtrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/C1FC8183-1A80-4412-99EB-716E1A90EC22%40vonnieda.org.
For more options, visit https://groups.google.com/d/optout.