Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Declarative pipeline seems to be broken as some plugin dependencies are broken #139

Open
v1v opened this issue Jun 17, 2019 · 2 comments
Open

Comments

@v1v
Copy link
Member

v1v commented Jun 17, 2019

Some plugin dependencies are broken

What error do I get?

 make run
docker run --rm -v maven-repo:/root/.m2 \
	    -v /Users/vmartinez/work/src/github.com/v1v/ci.jenkins.io-runner/demo/simple/:/workspace/ \
	    jenkins4eval/ci.jenkins.io-runner:local-test 
   3.806 [id=29]	SEVERE	jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Docker Commons Plugin v1.15 (docker-commons)
java.io.IOException: Docker Commons Plugin version 1.15 failed to load.
 - Pipeline: Declarative Extension Points API version 1.3.2 is older than required. To fix, install version 1.3.8 or later.
	...
java.io.IOException: Docker Pipeline version 1.14 failed to load.
 - Docker Commons Plugin version 1.15 failed to load. Fix this plugin first.
	...
java.io.IOException: Pipeline: Declarative version 1.3.2 failed to load.
 - Docker Pipeline version 1.14 failed to load. Fix this plugin first.
	...
java.io.IOException: Pipeline version 2.6 failed to load.
 - Pipeline: Declarative version 1.3.2 failed to load. Fix this plugin first.
	...
java.io.IOException: Yet Another Docker Plugin version 0.1.0-rc52 failed to load.
 - Docker Commons Plugin version 1.15 failed to load. Fix this plugin first.
	...
== Configuring the Jenkins Pipeline library
===== Using the Pipeline library from https://github.com/oleg-nenashev/pipeline-library 
...
java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps 

#127
#127 # How to reproduce?

make docker
make clean build

Edit demo/simple/Jenkinsfile with the below snippet:

#!/usr/bin/env groovy
pipeline {
    agent {
        label "java"
    }
    tools {
        maven 'mvn'
        jdk 'jdk8'
    }
    options {
        timestamps()
    }
    stages {
        stage('Checkout') {
            steps {
                deleteDir()
                git url: 'https://github.com/v1v/pipeline-library', branch: 'master'                    
            }
        }
        stage('Test') {
            steps {
                sh 'mvn clean test'
            }
            post {
                always {
                    junit(keepLongStdio: true, testResults: "target/surefire-reports/junit-*.xml,target/surefire-reports/TEST-*.xml")
                }
            }
        }
    }
}

Then make run

I was able to get the above issue using my fork repo: https://github.com/v1v/ci.jenkins.io-runner
which it's up to date with the commit f43c078

Please let me know if you need further details.

@oleg-nenashev
Copy link
Member

Likely it is a glitch after Dependabot bumps.
Better CI is definitely needed in this repo, and it would be great to integrate https://github.com/jenkinsci/jenkinsfile-runner-test-framework from @varyvol and @fcojfernandez

@oleg-nenashev
Copy link
Member

Once jenkinsci/custom-war-packager#104 is landed, we should have more options to test Custom WAR packager-based flows without massive overheads

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants