You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. This message was sent by Atlassian JIRA (v7.1.7#71011- sha1:2526d7c) I added an API token and when I tried to add a Dropbox location I received the following error: Failed to connect or change directory : Failed to change to remote directory / When I put the path field blank - I receive a success message, but another error: Remote directory must be an absolute path. Here is how/where I am getting Jenkins 2.33 currently via :
Jenkins dropbox plugin error install#
I am able to install other plugins using this same CLI command without issue.Īm I using a high enough version of Jenkins? This is the line that errors either via playbook or via command line: I have attached the Ansible playbook so you can see the exact build steps. remote call to Chunked connection to Method)Īt (Channel.java:1537)Īt (Request.java:172)Īt (Channel.java:821)Īt (RemoteInvocationHandler.java:256)Īt .$Prox圓.main(Unknown Source)Ĭaused by: java.io.IOException: Unexpected termination of the channel
: java.io.IOException: Unexpected termination of the channelĪt (Request.java:307)Īt (Channel.java:888)Īt $n(SynchronousCommandTransport.java:92)Īt. SEVERE: I/O error in channel Chunked connection to java.io.IOException: Unexpected termination of the channelĪt $n(SynchronousCommandTransport.java:73)Īt java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)Īt java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)Īt java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)Īt java.io.ObjectInputStream.(ObjectInputStream.java:301)Īt .(ObjectInputStreamEx.java:48)Īt 圜ommandTransport.read(AbstractSynchronousByteArra圜ommandTransport.java:34)Īt $n(SynchronousCommandTransport.java:59) fastlane is MIT licensed, its good to have plugins use MIT too: readmescore: 50: How well is the README of the document written: age: 31: Project that have been around for longer tend to be more stable: majorrelease: 0: Post 1.0 releases are great: githubissues-8: Lots of open issues are not a good sign usually, unless the project is really. usr/bin/java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -s install-plugin blueocean -restart -username admin -password blahblahblah Repeatable steps on a clean system to reproduce:
The blueocean plugin install errors at the CLI on a clean / new system (no other plugin on my standard list fail like this, for example, these install just fine: github-oauth and build-pipeline-plugin) Blue Ocean plugin error when installing via CLIīlueocean_jenkins_centos7_ansible-playbook.yml, bug1.png
0 kommentar(er)
