[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it

161 views
Skip to first unread message

jsoref+jenkins@gmail.com (JIRA)

unread,
Feb 6, 2020, 6:46:05 PM2/6/20
to jenkinsc...@googlegroups.com
Josh Soref created an issue
 
Jenkins / Bug JENKINS-61007
pipeline-model-definition is using findbugs without providing / depending on it
Issue Type: Bug Bug
Assignee: Andrew Bayer
Components: pipeline-model-definition-plugin
Created: 2020-02-06 23:45
Priority: Minor Minor
Reporter: Josh Soref

I'm using hpi:run from the workflow-basic-steps-plugin.

I bumped the <jenkins.version>2.150.3</jenkins.version> because the Credentials Plugin objects to 2.150.1.

Expected results: I should be able to test a pipeline.
Actual results:

Started by user Admin
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] End of Pipeline
hudson.remoting.ProxyException: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
jar:file:~/code/jenkinsci/workflow-basic-steps-plugin/work/plugins/pipeline-model-definition/WEB-INF/lib/pipeline-model-definition.jar!/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy: 29: unable to resolve class edu.umd.cs.findbugs.annotations.SuppressFBWarnings
 @ line 29, column 1.
   import edu.umd.cs.findbugs.annotations.SuppressFBWarnings
   ^

Steps:

  1. mvn hpi:run
  2. Load http://localhost:8080/jenkins/pluginManager/available
  3. Select Pipeline
  4. Click Download now and install after restart
  5. Restart the mvn hpi:run command
  6. Load http://localhost:8080/jenkins/view/all/newJob
  7. Fill in item name
  8. Click Pipeline
  9. Click OK
  10. Click the Pipeline tab
  11. Click try sample Pipeline...
  12. Click Hello World
  13. Click Save
  14. Click Build Now
  15. Click the ball next to the run to get to the console log.

 

I installed Pipeline and upgraded.

Name ↓ Version
[Credentials Binding Plugin
Allows credentials to be bound to environment variables for use from miscellaneous build steps.
1.2  
[Credentials Plugin
This plugin allows you to store credentials in Jenkins.
2.3.1  
[Docker Pipeline
Build and use Docker containers from pipelines.
1.21 
[Git client plugin
Utility plugin for Git support in Jenkins
3.1.1 
[Mailer Plugin
This plugin allows you to configure email notifications for build results
1.3
Pipeline
A suite of plugins that lets you orchestrate automation, simple or complex. See Pipeline as Code with Jenkins for more details.
2.6 
[Pipeline: API
Plugin that defines Pipeline API.
2.39
[Pipeline: Basic Steps
Commonly used steps for Pipelines.
2.20-SNAPSHOT (private-02/06/2020 17:00-jsoref)
[Pipeline: Declarative
An opinionated, declarative Pipeline.
1.5.1
[Pipeline: Declarative Agent API
Replaced by Pipeline: Declarative Extension Points API plugin.
1.1.1
[Pipeline: Declarative Extension Points API
APIs for extension points used in Declarative Pipelines.
1.5.1
[Pipeline: Groovy
Pipeline execution engine based on continuation passing style transformation of Groovy scripts.
2.78
[Pipeline: Input Step
Adds the Pipeline step input to wait for human input or approval.
2.11
[Pipeline: Model API
Model API for Declarative Pipeline.
1.5.1
[Pipeline: Multibranch
Enhances Pipeline plugin to handle branches better by automatically grouping builds from different branches.
2.21
[Pipeline: Nodes and Processes
Pipeline steps locking agents and workspaces, and running external processes that may survive a Jenkins restart or slave reconnection.
2.31
[Pipeline: SCM Step
Adds a Pipeline step to check out or update working sources from various SCMs (version control).
2.1
[Pipeline: Shared Groovy Libraries
Shared libraries for Pipeline scripts.
2.15
[Pipeline: Stage Step
Adds the Pipeline step stage to delineate portions of a build.
2.3
[Pipeline: Stage Tags Metadata
Library plugin for Pipeline stage tag metadata.
1.5.1
[Pipeline: Supporting APIs
Common utility implementations to build Pipeline Plugin
3.4
[SCM API Plugin
This plugin provides a new enhanced API for interacting with SCM systems.
2.6.3
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

wfollonier@cloudbees.com (JIRA)

unread,
Feb 24, 2020, 7:31:07 AM2/24/20
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Mar 9, 2020, 12:45:03 PM3/9/20
to jenkinsc...@googlegroups.com

Able to reproduce simply by

  • Running 2.224 on a new home dir.
  • Selecting just Pipeline from setup wizard.
  • Creating a Pipeline job using the hello world sample.
  • Running it.
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

jglick@cloudbees.com (JIRA)

unread,
Mar 9, 2020, 12:50:03 PM3/9/20
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Mar 9, 2020, 12:50:03 PM3/9/20
to jenkinsc...@googlegroups.com
Jesse Glick started work on Bug JENKINS-61007
 
Change By: Jesse Glick
Status: Open In Progress

jglick@cloudbees.com (JIRA)

unread,
Mar 9, 2020, 12:50:04 PM3/9/20
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Mar 9, 2020, 1:02:02 PM3/9/20
to jenkinsc...@googlegroups.com
 
Re: pipeline-model-definition is using findbugs without providing / depending on it

Filed a fix. BTW I came across this because it was mentioned twice in the 2.224 changelog, though I see no reason to believe that it is specific to a given version of core.

jglick@cloudbees.com (JIRA)

unread,
Mar 9, 2020, 1:02:02 PM3/9/20
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Mar 9, 2020, 1:10:02 PM3/9/20
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Mar 10, 2020, 8:47:03 AM3/10/20
to jenkinsc...@googlegroups.com
Change By: Jesse Glick
Status: In Review Resolved
Resolution: Fixed
Released As: pipeline-model-definition 1.6.0

rameshm78@gmail.com (JIRA)

unread,
Mar 11, 2020, 9:29:02 PM3/11/20
to jenkinsc...@googlegroups.com

dbeck@cloudbees.com (JIRA)

unread,
Mar 13, 2020, 3:44:02 PM3/13/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages