Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Provides a post build action for submitting artifacts to PaaSLane for scanning.

Plugin Information

View PaaSLane Estimate on the plugin site for more information.

Goal

The PaaSLane Estimate plugin for Jenkins provides a secure submission capability for users of PaaSLane. a static code analysis platform, and Jenkins. PaaSLane is a static code analyzer for modernizing and optimizing applications. When modernizing existing code, PaaSLane can help to make your application be more performant, more secure, and easier to maintain. When developing new cloud applications, PaaSLane helps ensure optimal performance and scalability in the most popular public and private cloud platforms. PaaSLane automatically spots hundreds of potential issues and optimizations in your source code, giving you detailed examples and suggesting remediations to enhance developer productivity. For a free trial click here .

The PaaSLane Estimate plugin is implemented as a Post Build Action and is intended to sweep a directory structure looking for files that match the specified patterns and securely upload them to PaaSLane for verification. Once the files are uploaded, they are profiled and then an estimation report is generated. This report will include overall conformance with the rules defined, a list of instances of the violations with their recomended remediation, as well as an estimate for the remediation.

Getting started

Install the plugin using the Plugin Manager via the Available tab, and restart Jenkins

Job Setup

The PaaSLane Estimate plugin is implemented as a Post Build Action as shown below

Options:

  • url - The "PaaSLane URL" field specifies the root url, including the host, port and context that define the location of the PaaSLane profiling environment to use. For most SaaS customers, this will be https://app.paaslane.com/paaslaneagentserver. However, customers utilizing distributed profiling, will want to get their URL from their administrator.
  • token - The "Authentication Token" field contains the PaaSLane token associated with a specific user in a specific tenant. This token can be gotten by logging into PaaSLane, clicking the username dropdown and selecting to "Get Token". Once you have this option you should be presented with the time sensitive token.
  • exclude-regex - The "Exclude Regular Expressions" field contains a comma separated list of regular expression patterns that will be applied to every matched artifact. If any of the patterns match the path of the artifact being reviewed, then artifact will not be sent to PaaSLane. Examples of these regular expressions can be found here.(http://ocpsoft.org/opensource/guide-to-regular-expressions-in-java-part-1/)
  • name - The name field is used to specify the PaaSLane application that the artifacts mapped later will be associated with. For example, if the name of this field is "My Application" and you match 3 artifacts, there will be an application "My Application" with 3 modules that get profiled.
  • language - The "Language" selection specifies which language rules should be applied to the artifacts that are uploaded and profiled.
  • path - This required value specifies where to start looking for artifacts to include in the application. This, paired with "Regular Expression for Selecting Modules" and "Exclude Regular Expressions" help to specify included artifacts.
  • testOnly - The "Test, but don't send files" field, when checked, will only display the files that would have been sent, based on the parameters. Use this field to get the parameters correct.
  • No labels