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 current
version, then there would be a "<plugin-name>.bak" file in the /plugins/
subdirectory of the Jenkins home directory.  For example, I recently
upgraded the docker-commons plugin and there is now a "docker-commons.bak"
file (previous docker-commons plugin version) and a "docker-commons.jpi"
file (currentl version of the docker-commons plugin).

Plugins which have not been upgraded (at least on my installation) appear
as "<plugin-name>.jpi" without a matching "<plugin-name>.bak".

If you want to replace an existing plugin at the file system level with a
different version, it may be enough to stop Jenkins, perform a backup, then
repalce the "<plugin-name>.jpi" (or "<plugin-name>.hpi" if it exists
instead) with the replacement version.

You might also read the Jenkins log file to see if there are hints in the
log file that might give an indication why the plugin is unable to start.

Mark Waite


>
> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>>
>> 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 version.
>>
>> On Sun, May 20, 2018 at 1:50 PM Kernel Panic <[email protected]> wrote:
>>
>>> 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:
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>> <st:include> Type org.eclipse.jgit.transport.RemoteConfig not present
>>>
>>> If I scroll down to Source Management I do not see the git option, only
>>> None, CVS, and CVS Project set.
>>> If I got to Manage Jenkins / Configure System I get the same java error.
>>>
>>> The git plugin version is 3.9.0 and I do no see an option to downgrade,
>>> so Im lost in here, any  idea how can I troubleshoot this issue?
>>> The servert is Debian 8.2
>>>
>>> Thanks in advance
>>> Regards
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHLxKv5xvNq2mHVvv0PPcfe4N0uZThrpACM19zAQPn7CQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to