Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

On Sun, May 20, 2018 at 6:52 PM Kernel Panic wrote: > Ok, I'll try to install a previous version manually , I have no option to > Downgrade it from the UI, do you know which is the previous stable version > to 3.9.0 ? or which one should I try with Jenkins 2.107.3 ? >

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Ok, I'll try to install a previous version manually , I have no option to Downgrade it from the UI, do you know which is the previous stable version to 3.9.0 ? or which one should I try with Jenkins 2.107.3 ? Is there a way to run the plugin manually like "java something" to see if I can see

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Yes, it means that the git client plugin did not initialize correctly. The git client plugin includes JGit. That class (and the RemoteConfig class) are classes from JGit which is included in the git client plugin. On Sun, May 20, 2018 at 6:24 PM Kernel Panic wrote: >

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Hi Mark Under Manage Old Data I found this, does it mean something to you? hudson.model.FreeStyleBuild project-name #82 NoClassDefFoundError: org/eclipse/jgit/lib/AnyObjectId El domingo, 20 de mayo de 2018, 20:36:48 (UTC-3), Mark Waite escribió: > > > > On Sun, May 20, 2018 at 5:32 PM Kernel

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

On Sun, May 20, 2018 at 5:32 PM Kernel Panic wrote: > Ok, I'll play a bit with it, and what do you think about this error? does > it mean anything? what happens if I remove or clean /var/cache/jenkins > directory? I can bet this is the root of cause, but no idea how to

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Ok, I'll play a bit with it, and what do you think about this error? does it mean anything? what happens if I remove or clean /var/cache/jenkins directory? I can bet this is the root of cause, but no idea how to resolve that dependency error. org.apache.commons.jelly.JellyTagException:

Re: I would like to downgrade the version of Python that Jenkins is using.

Check out the global config in jenkins to find what version of python is used? If there is no python listed, check the default python that the instance on which the build is executed On Mon, May 14, 2018 at 11:41 AM Patricia Sandt wrote: > The Ubuntu 16.04 version

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

I don't know how the Jenkins loader decides between an hpi and a jpi file. I would assume it will choose jpi if it exists, and choose hpi if the jpi does not exist. However, that assumption could be completely wrong. The docker image that I use contains only jpi files. See

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Hi Mark, Yes, that's the output from /var/log/jenkins/jenkins.log not of the plugin, and I get that error on every job I want to configure by the way, is not related to a particular job, are all of them with the same error. Byt the way, I have both jpi and hpi files, which one should I

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

When I say "the jenkins log", I mean the log file written by Jenkins as it is running. I don't mean the log from individual jobs. On my Debian machine, the Jenkins logs are written in /var/log/jenkins/ Mark Waite On Sun, May 20, 2018 at 4:51 PM Kernel Panic wrote: >

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

And this is the full log when I go to project / configure. org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91: Type org.eclipse.jgit.transport.RemoteConfig not present at

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Hi Mark, really appreciated your help! this is the full log May 20, 2018 10:41:27 PM hudson.model.Run execute INFO: project-name #319 main build action completed: FAILURE May 20, 2018 10:41:27 PM jenkins.plugins.slack.ActiveNotifier completed WARNING: Project project-name has no Slack

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

I suspect the last thing in the Jenkins log is much less helpful for diagnosis than the early contents of the Jenkins log. Somewhere in the early portions of the Jenkins log I would expect to find a good hint that something is unable to start. On Sun, May 20, 2018 at 4:24 PM Kernel Panic

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Thank you very much for the explanation, I will try to restore the old plugin version, and by the way this is the last thing on jenkins log Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.github.config.GitHubPluginConfig.constructDefaultUrl(GitHubPluginConfig.java:228) at

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

On Sun, May 20, 2018 at 2:32 PM Kernel Panic wrote: > If there was a manual update, ( I can see some some git-client git and git > hub hpi/jpi files under plugin directory ) how can I revert it back? > > Thanks you very much! > > If one or more plugins were upgraded from a prior version to the

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

On Sun, May 20, 2018 at 2:30 PM Kernel Panic wrote: > And this is the error I get when building the project > > Building on master in workspace /var/lib/jenkins/jobs/project-name/workspace > [workspace] $ /bin/sh -xe /tmp/jenkins1514082732430590998.sh > > That message

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

If there was a manual update, ( I can see some some git-client git and git hub hpi/jpi files under plugin directory ) how can I revert it back? Thanks you very much! El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió: > > Have you checked in the "Plugin Manager" section of

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

And this is the error I get when building the project Building on master in workspace /var/lib/jenkins/jobs/project-name/workspace [workspace] $ /bin/sh -xe /tmp/jenkins1514082732430590998.sh + git checkout master fatal: Not a git repository (or any parent up to mount point

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Hi, this what I get when I go to Manage Jenkins Warnings have been published for the following currently installed components.GitHub Pull Request Builder 1.40.0 GitHub access tokens stored in in build.xml

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Have you checked in the "Plugin Manager" section of "Manage Jenkins" to confirm that there are no warnings about unsatisfied dependencies? I think that type of message might appear if a new git plugin were manually uploaded to a system that hadn't yet updated the git client plugin to the latest

Re: jenkins UI crashes after git plugin update

Im getting the same error but after upgrade to jenkins 2, any idea how to troubleshoot this issue? Thanks Regards El viernes, 27 de mayo de 2016, 1:46:32 (UTC-3), Paul C escribió: > > Currently using jenkins 1.626. Upgraded git-plugin to 2.4.4, git-client > to 1.19.6 > > The error looks

jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

Hello I inherited a server with git 2.107.3 installed, it seems the previous admin upgraded it, now when I got to project config I get this error: org.apache.commons.jelly.JellyTagException:

Nexus Artifact Resolver unable to download large artifacts

Hi, I'm using Nexus Repository connector and Artifact Resolver to download a specific version of a .zip artifact which is around 3.3 GB. I usually download and copy to staging environment. But since the file is large, the Artifact resolver is not able to download it fully. It downloads 2GB

Re: Jenkins Setup Wizard Fail with 'An error occurred during installation: No such plugin: cloudbees-folder'

Hi, I found a workaround. $ diff /etc/init.d/jenkins.org /etc/init.d/jenkins 80c80,81 < JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR" --- > JAVA_CMD="$JENKINS_JAVA_CMD -Dhudson.model.DownloadService.noSignatureCheck=true $JENKINS_JAVA_OPTIONS