-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
-
pipeline-model-definition 1.6.0
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:
- mvn hpi:run
- Load http://localhost:8080/jenkins/pluginManager/available
- Select Pipeline
- Click Download now and install after restart
- Restart the mvn hpi:run command
- Load http://localhost:8080/jenkins/view/all/newJob
- Fill in item name
- Click Pipeline
- Click OK
- Click the Pipeline tab
- Click try sample Pipeline...
- Click Hello World
- Click Save
- Click Build Now
- 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 |
- is caused by
-
JENKINS-51865 Stage locks are created for skipped stages in declarative pipeline
- Resolved
- relates to
-
JENKINS-41827 JenkinsRule mode to use realistic class loading
- Resolved
-
JENKINS-62988 ModelInterpreter.groovy unable to resolve class javax.annotation.Nonnull with Jenkins v2.235.1
- Closed
- links to