Re: Execute a function from post actions in Jenkinsfile
Hello
Yes, that's what I want to do
Thank you so much.
El domingo, 20 de diciembre de 2020 a las 14:51:45 UTC-3, Gianluca escribió:
> Hi,
>
> I'm not sure I understood your issue on calling functions. Maybe there is
> only a bit of confusion about the Jenkins pipeline syntax.
>
> From what you said, you are already calling functions into the post
> sections: "cleanWs()" is a function, "emailext body: ... " is a function.
>
> So, maybe you are confused by the fact Jenkins syntax in post doesn't
> allow something like:
>
> post {
>
> aFunction()
>
> }
>
> So, nope, the above doesn't work. Because the "post" syntax are blocks
> based on the result of the pipeline and you actually listed all possible
> options:
>
> "always, changed, fixed, regression, aborted, success, unsuccessful,
> unstable, failure, notBuilt, cleanup"
>
> And if I understood, you want to call a function that does different
> things depending on the pipeline result ... then, you need to used "always":
>
> post {
>
>always {
>
>aFunction(BUILD_RESULT)
>
>}
>
> }
>
> And then the function will do different things depending of the
> BUILD_RESULT value:
>
> if (BUILD_RESULT == "SUCCESS") {
>
>message = "Pipeline failed"
>
> } else {
>
>message = "Pipeline ... whatever"
>
> }
>
> I hope that helps.
>
> Cheers,
>
> Gianluca.
>
>
> On 20/12/2020 17:35, Kernel Panic wrote:
>
>
> Hello there.
>
> I looking for an elagant way to execute code from the post {} section,
> I want to write a clean Jenkinsfile and execute code from shared libraries
> as
> posible.
>
> In the post section I have the tipical clean working directory like this:
>
> always {
> cleanWs()
> }
>
> I also send notification based on pipeline completion, I mean, aobrted ,
> failed,
> changed and so on, but I want to call a function to do that, I want to
> remove the
> email code I have something like this:
>
> emailext body: 'Check console output at $BUILD_URL to view the results.
> \n\n ${CHANGES} \n\n - \n${BUILD_LOG,
> maxLines=50, escapeHtml=false}',
> to: "${EMAIL_ADDRESSES}",
> subject: 'Pipeline Execution Failed: $PROJECT_NAME -
> #$BUILD_NUMBER'
>
> The problem seems that from the post you only can call an expected
> function of
> type: always, changed, fixed, regression, aborted, success, unsuccessful,
> unstable, failure, notBuilt, cleanup.
>
> Is there another way to accomplish this to write a more clean Post section?
>
>
> Thanks
> 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 jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/ea74e553-88a7-4925-ade2-27462aaceab1n%40googlegroups.com
>
> <https://groups.google.com/d/msgid/jenkinsci-users/ea74e553-88a7-4925-ade2-27462aaceab1n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/c45f0c38-08e9-4b23-bb21-ed4b47179090n%40googlegroups.com.
Execute a function from post actions in Jenkinsfile
Hello there.
I looking for an elagant way to execute code from the post {} section,
I want to write a clean Jenkinsfile and execute code from shared libraries
as
posible.
In the post section I have the tipical clean working directory like this:
always {
cleanWs()
}
I also send notification based on pipeline completion, I mean, aobrted ,
failed,
changed and so on, but I want to call a function to do that, I want to
remove the
email code I have something like this:
emailext body: 'Check console output at $BUILD_URL to view the results.
\n\n ${CHANGES} \n\n - \n${BUILD_LOG,
maxLines=50, escapeHtml=false}',
to: "${EMAIL_ADDRESSES}",
subject: 'Pipeline Execution Failed: $PROJECT_NAME -
#$BUILD_NUMBER'
The problem seems that from the post you only can call an expected function
of
type: always, changed, fixed, regression, aborted, success, unsuccessful,
unstable, failure, notBuilt, cleanup.
Is there another way to accomplish this to write a more clean Post section?
Thanks
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/ea74e553-88a7-4925-ade2-27462aaceab1n%40googlegroups.com.
Re: Jenkinsfile Accessing variables from shared libraries
Hello
Is there a way to access those variables from as sh command from the script
section?
for example this works:
script {
echo GlobalVariables.MyVariable
}
but the same with sh does not, that just echos GlobalVariables.MyVariable
and not the variable content.
script {
sh ' echo GlobalVariables.MyVariable'
}
Thanks
Regards
El jueves, 17 de diciembre de 2020 a las 5:45:11 UTC-3, venh...@gmail.com
escribió:
> In my case, I do the following. I have a GlobalVars.groovy file with below
> content.
>
> #!/usr/bin/env groovypackage com..;public class
> GlobalVars { static String myVar = ""}
>
> Then in my Shared Library class, I use it like below.
>
> GlobalVars.myVar = ""
>
> Try it like this and check. Here, I have declared the class as Public and the
> variable as static. That's the only difference.
>
>
> Regards,
> Venkatesh
>
>
> On Thu, Dec 17, 2020 at 12:56 PM Adrian Wyssmann
> wrote:
>
>> I see several problem
>>
>>1. using ' will not expand the parameters is your call should be sh
>>"echo ${CustomMessage}"
>>2. CustomMessage is declared within the class Vars(), so you cannot
>>access it
>>
>> You could implement a getter an then do something like this "echo
>> ${globalVars.getCustomMessage()}"
>>
>> Maybe others have better ideas...?
>> On Thursday, December 17, 2020 at 12:10:19 AM UTC+1 netwar...@gmail.com
>> wrote:
>>
>>> Hello there
>>> Maybe this is a very basic question, but am not being able to access a
>>> global variable
>>> from a shared library from a Jenkinsfile
>>>
>>> under vars I defined something like this
>>>
>>> globalVars.groovy
>>> class Vars () {
>>>
>>> def CustomMessage = "This is a new deployment"
>>>
>>> }
>>>
>>> from my Jenkinsfile
>>>
>>> library identifier: 'globalVars@master', \
>>> retriever: modernSCM([$class: 'GitSCMSource', \
>>> credentialsId: 'tfsservice', \
>>> remote: 'http://myrepo.com', \
>>> traits: [gitBranchDiscovery()]])
>>>
>>>
>>> pipeline {
>>>
>>> stages {
>>> stage('Do Some Stuff') {
>>> steps {
>>> script {
>>>
>>>sh 'echo ${CustomMessage}'
>>>
>>> }
>>> }
>>> }
>>> }
>>>
>>> }
>>>
>>> But the above returns nothing, what am I doing wrong?
>>> Thanks
>>> 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 jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/099e3aee-dffc-459d-8eb5-d64204effb58n%40googlegroups.com
>>
>>
>> .
>>
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/9db63ce0-9c9d-4683-b58d-a5cd1a4f8355n%40googlegroups.com.
Re: Jenkinsfile Accessing variables from shared libraries
Hello
Defining a global class worked for me, at least did what I wanted to do,
Thanks you very much for your time and support
Regards
El jueves, 17 de diciembre de 2020 a las 5:45:11 UTC-3, venh...@gmail.com
escribió:
> In my case, I do the following. I have a GlobalVars.groovy file with below
> content.
>
> #!/usr/bin/env groovypackage com..;public class
> GlobalVars { static String myVar = ""}
>
> Then in my Shared Library class, I use it like below.
>
> GlobalVars.myVar = ""
>
> Try it like this and check. Here, I have declared the class as Public and the
> variable as static. That's the only difference.
>
>
> Regards,
> Venkatesh
>
>
> On Thu, Dec 17, 2020 at 12:56 PM Adrian Wyssmann
> wrote:
>
>> I see several problem
>>
>>1. using ' will not expand the parameters is your call should be sh
>>"echo ${CustomMessage}"
>>2. CustomMessage is declared within the class Vars(), so you cannot
>>access it
>>
>> You could implement a getter an then do something like this "echo
>> ${globalVars.getCustomMessage()}"
>>
>> Maybe others have better ideas...?
>> On Thursday, December 17, 2020 at 12:10:19 AM UTC+1 netwar...@gmail.com
>> wrote:
>>
>>> Hello there
>>> Maybe this is a very basic question, but am not being able to access a
>>> global variable
>>> from a shared library from a Jenkinsfile
>>>
>>> under vars I defined something like this
>>>
>>> globalVars.groovy
>>> class Vars () {
>>>
>>> def CustomMessage = "This is a new deployment"
>>>
>>> }
>>>
>>> from my Jenkinsfile
>>>
>>> library identifier: 'globalVars@master', \
>>> retriever: modernSCM([$class: 'GitSCMSource', \
>>> credentialsId: 'tfsservice', \
>>> remote: 'http://myrepo.com', \
>>> traits: [gitBranchDiscovery()]])
>>>
>>>
>>> pipeline {
>>>
>>> stages {
>>> stage('Do Some Stuff') {
>>> steps {
>>> script {
>>>
>>>sh 'echo ${CustomMessage}'
>>>
>>> }
>>> }
>>> }
>>> }
>>>
>>> }
>>>
>>> But the above returns nothing, what am I doing wrong?
>>> Thanks
>>> 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 jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/099e3aee-dffc-459d-8eb5-d64204effb58n%40googlegroups.com
>>
>>
>> .
>>
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/eea95ea1-71e8-4fb3-9d7e-a6035f0ee0e8n%40googlegroups.com.
Jenkinsfile Accessing variables from shared libraries
Hello there
Maybe this is a very basic question, but am not being able to access a
global variable
from a shared library from a Jenkinsfile
under vars I defined something like this
globalVars.groovy
class Vars () {
def CustomMessage = "This is a new deployment"
}
from my Jenkinsfile
library identifier: 'globalVars@master', \
retriever: modernSCM([$class: 'GitSCMSource', \
credentialsId: 'tfsservice', \
remote: 'http://myrepo.com', \
traits: [gitBranchDiscovery()]])
pipeline {
stages {
stage('Do Some Stuff') {
steps {
script {
sh 'echo ${CustomMessage}'
}
}
}
}
}
But the above returns nothing, what am I doing wrong?
Thanks
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/9cea34b1-38b7-41fb-9e1f-fd6af0db38d3n%40googlegroups.com.
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 any other error? I cannot find which is the dependency error or how to fix it, maybe a previous version works fine. Thanks Regards El domingo, 20 de mayo de 2018, 21:45:25 (UTC-3), Mark Waite escribió: > > 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 <netwar...@gmail.com > > wrote: > >> 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 Panic <netwar...@gmail.com> >>> 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 resolve >>>> that >>>> dependency 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: >>>> >>>> Type org.eclipse.jgit.transport.RemoteConfig not present >>>> >>>> >>> I think that error means that the git client plugin failed to initailize >>> and all git operations after the git client plugin failure to initailize >>> will be suspect. The git client plugin initalization failure is likely >>> much earlier in the log file. >>> >>> Mark Waite >>> >>> >>> >>>> Thanks >>>> Regards >>>> >>>> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió: >>>> >>>>> 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 >>>>> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins >>>>> for >>>>> the list of plugins that I use. I had assumed (possibly incorrectly) >>>>> that >>>>> hpi files were originally associated with the Hudson project, and jpi >>>>> files >>>>> are associated with the Jenkins project. >>>>> >>>>> If you have both hpi and jpi files, that may be a source of confusion >>>>> for Jenkins. You might try an experiment to assure that only one or the >>>>> other are available. >>>>> >>>>> Mark Waite >>>>> >>>>> >>>>> >>>>> On Sun, May 20, 2018 at 5:07 PM Kernel Panic <netwar...@gmail.com> >>>>> wrote: >>>>> >>>> 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 >>>>>> replace with with .bak version? >>>>>> >>>>>> >>>>>> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30 2015 github.bak >>>>>> >>>>>> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi >>>>>> >>>>>> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi >>>>>> >>>>>> >>>>>> >>>>>> Thanks you very much for your help >>>>>> Regards >>>>>> >>
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 Panic <netwar...@gmail.com > > 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 resolve >> that >> dependency 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: >> >> Type org.eclipse.jgit.transport.RemoteConfig not present >> >> > I think that error means that the git client plugin failed to initailize > and all git operations after the git client plugin failure to initailize > will be suspect. The git client plugin initalization failure is likely > much earlier in the log file. > > Mark Waite > > > >> Thanks >> Regards >> >> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió: >> >>> 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 >>> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins >>> for >>> the list of plugins that I use. I had assumed (possibly incorrectly) that >>> hpi files were originally associated with the Hudson project, and jpi files >>> are associated with the Jenkins project. >>> >>> If you have both hpi and jpi files, that may be a source of confusion >>> for Jenkins. You might try an experiment to assure that only one or the >>> other are available. >>> >>> Mark Waite >>> >>> >>> >>> On Sun, May 20, 2018 at 5:07 PM Kernel Panic <netwar...@gmail.com> >>> wrote: >>> >> 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 replace >>>> with with .bak version? >>>> >>>> >>>> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30 2015 github.bak >>>> >>>> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi >>>> >>>> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi >>>> >>>> >>>> >>>> Thanks you very much for your help >>>> Regards >>>> >>>> >>>> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió: >>>> >>>>> 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 <netwar...@gmail.com> >>>>> wrote: >>>>> >>>> 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 >>>>>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) >>>>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) >>>>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >>>>>> at >>>>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) >>>>>> at >>>>>> org.apache.commons.jel
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: 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 Thanks Regards El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió: > > 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 > https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins > for > the list of plugins that I use. I had assumed (possibly incorrectly) that > hpi files were originally associated with the Hudson project, and jpi files > are associated with the Jenkins project. > > If you have both hpi and jpi files, that may be a source of confusion for > Jenkins. You might try an experiment to assure that only one or the other > are available. > > Mark Waite > > > > On Sun, May 20, 2018 at 5:07 PM Kernel Panic <netwar...@gmail.com > > wrote: > >> 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 replace >> with with .bak version? >> >> >> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30 2015 github.bak >> >> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi >> >> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi >> >> >> >> Thanks you very much for your help >> Regards >> >> >> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió: >> >>> 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 <netwar...@gmail.com> >>> wrote: >>> >> 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 >>>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) >>>>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) >>>>at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >>>>at >>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) >>>>at >>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) >>>>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >>>>at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >>>>at >>>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) >>>>at >>>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) >>>>at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >>>>at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) >>>>at >>>> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) >>>>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >>>>at >>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) >>>>at >>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) >>>>at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >>>>at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >>>>at >>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript
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 replace with with .bak version? -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30 2015 github.bak -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi Thanks you very much for your help Regards El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió: > > 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 <netwar...@gmail.com > > wrote: > >> 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 >> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) >> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) >> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >> at >> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) >> at >> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) >> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >> at >> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) >> at >> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) >> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) >> at >> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) >> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >> at >> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) >> at >> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) >> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >> at >> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) >> at >> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) >> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) >> at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) >> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) >> at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) >> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) >> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >> at >> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) >> at >> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) >> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >> at >> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) >> at >> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) >> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) >> at >> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) >> at >> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) >> at >> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) >> at >> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) >> at >> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) >> at org.apache
Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present
(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:190) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:188) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1253) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:168) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:166) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1155) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:564) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:317) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124) at org.eclipse.jetty.util.thread.Invocable.invokePreferred(Invocable.java:128) at org.eclipse.jetty.util.thread.Invocable$InvocableExecutor.invoke(Invocable.java:222) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:294) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:199) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) El domingo, 20 de mayo de 2018, 19:36:46 (UTC-3), Mark Waite escribió: > > 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 <netwar...@gmail.com > > wrote: > >> 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 >> org.jenkinsci.plugins.github.config.GitHubPluginConfig.getHookUrl(GitHubPluginConfig.java:116) >> >> ... 341 more >> >> >> May 20, 2018 9:00:55 PM hudson.ExpressionFactory2$JexlExpression evaluate >> >> WARNING: Caught exception evaluating: descriptor.helpFile in >> /job/project-name/configure. Reason: >> java.lang.reflect.InvocationTargetException >> >> java.lang.reflect.InvocationTargetException >> at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)Caused >> by: java.lang.NoClassDefFoundError: org/eclipse/jgit/transport/RemoteConfig >> >> at java.lang.Class.getDeclaredMethods0(Native Method) >> >> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) >> >> at java.lang.Class.getDeclaredMethods(Class.java:1975) >> >> at >> org.kohsuke.stapler.ClassDescriptor.findMethods(ClassDescriptor.java:149) >> >> at org.kohsuke.stapler.ClassDescriptor.(ClassDescriptor.java:85) >> >&g
Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present
Caused by: java.lang.ClassNotFoundException: org.eclipse.jgit.transport.RemoteConfig at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 182 more May 20, 2018 10:43:47 PM hudson.model.Run execute INFO: project-name #320 main build action completed: FAILURE May 20, 2018 10:43:47 PM jenkins.plugins.slack.ActiveNotifier completed WARNING: Project project-name has no Slack configuration. El domingo, 20 de mayo de 2018, 19:36:46 (UTC-3), Mark Waite escribió: > > 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 <netwar...@gmail.com > > wrote: > >> 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 >> org.jenkinsci.plugins.github.config.GitHubPluginConfig.getHookUrl(GitHubPluginConfig.java:116) >> >> ... 341 more >> >> >> May 20, 2018 9:00:55 PM hudson.ExpressionFactory2$JexlExpression evaluate >> >> WARNING: Caught exception evaluating: descriptor.helpFile in >> /job/project-name/configure. Reason: >> java.lang.reflect.InvocationTargetException >> >> java.lang.reflect.InvocationTargetException >> at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)Caused >> by: java.lang.NoClassDefFoundError: org/eclipse/jgit/transport/RemoteConfig >> >> at java.lang.Class.getDeclaredMethods0(Native Method) >> >> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) >> >> at java.lang.Class.getDeclaredMethods(Class.java:1975) >> >> at >> org.kohsuke.stapler.ClassDescriptor.findMethods(ClassDescriptor.java:149) >> >> at org.kohsuke.stapler.ClassDescriptor.(ClassDescriptor.java:85) >> >> at >> org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:216) >> >> at >> org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:141) >> >> at org.kohsuke.stapler.lang.Klass.getFunctions(Klass.java:98) >> >> at org.kohsuke.stapler.KlassDescriptor.(KlassDescriptor.java:27) >> >> at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:105) >> >> at org.kohsuke.stapler.MetaClass.(MetaClass.java:93) >> >> at org.kohsuke.stapler.WebApp.getMetaClass(WebApp.java:204) >> >> at >> org.kohsuke.stapler.jelly.groovy.GroovyFacet.createRequestDispatcher(GroovyFacet.java:109) >> >> at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:257) >> >> at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:252) >> >> at hudson.model.Descriptor.getHelpFile(Descriptor.java:750) >> >> at hudson.model.Descriptor.getHelpFile(Descriptor.java:732) >> >> at hudson.model.Descriptor.getHelpFile(Descriptor.java:721) >> >> ... 160 more >> >> Caused by: java.lang.ClassNotFoundException: >> org.eclipse.jgit.transport.RemoteConfig >> >> at >> jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) >> >> at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) >> >> at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) >> >> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) >> El domingo, 20 de mayo de 2018, 19:00:03 (UTC-3), Mark Waite escribió: >> >>> 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 ".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 "dock
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 org.jenkinsci.plugins.github.config.GitHubPluginConfig.getHookUrl(GitHubPluginConfig.java:116) ... 341 more May 20, 2018 9:00:55 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: descriptor.helpFile in /job/project-name/configure. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)Caused by: java.lang.NoClassDefFoundError: org/eclipse/jgit/transport/RemoteConfig at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.getDeclaredMethods(Class.java:1975) at org.kohsuke.stapler.ClassDescriptor.findMethods(ClassDescriptor.java:149) at org.kohsuke.stapler.ClassDescriptor.(ClassDescriptor.java:85) at org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:216) at org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:141) at org.kohsuke.stapler.lang.Klass.getFunctions(Klass.java:98) at org.kohsuke.stapler.KlassDescriptor.(KlassDescriptor.java:27) at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:105) at org.kohsuke.stapler.MetaClass.(MetaClass.java:93) at org.kohsuke.stapler.WebApp.getMetaClass(WebApp.java:204) at org.kohsuke.stapler.jelly.groovy.GroovyFacet.createRequestDispatcher(GroovyFacet.java:109) at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:257) at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:252) at hudson.model.Descriptor.getHelpFile(Descriptor.java:750) at hudson.model.Descriptor.getHelpFile(Descriptor.java:732) at hudson.model.Descriptor.getHelpFile(Descriptor.java:721) ... 160 more Caused by: java.lang.ClassNotFoundException: org.eclipse.jgit.transport.RemoteConfig at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) El domingo, 20 de mayo de 2018, 19:00:03 (UTC-3), Mark Waite escribió: > > > > 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 ".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 ".jpi" without a matching ".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 ".jpi" (or ".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 <netwar...@gmail.com> >>> 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: >>>> >>>> Type org.eclipse.jgit
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 "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 <netwar...@gmail.com > > 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: >> >> 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 jenkinsci-use...@googlegroups.com . >> 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_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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
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 /var/lib/jenkins/jobs) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). Build step 'Execute shell' marked build as failure Skipped archiving because build is not successful Finished: FAILURE 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 <netwar...@gmail.com > > 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: >> >> 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 jenkinsci-use...@googlegroups.com . >> 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_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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f3a61d48-a4ce-4547-89d3-eb8cb321b05d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
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 <https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin>GitHub access tokens stored in in build.xml <https://jenkins.io/security/advisory/2018-03-26/#SECURITY-261>Environment Injector Plugin 2.1.5 <https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin>Exposure of sensitive build variables stored by EnvInject 1.90 and earlier <https://jenkins.io/security/advisory/2018-02-26/#SECURITY-248> And when I got to configure system A problem occurred while processing the request. Please check our bug tracker <https://jenkins.io/redirect/issue-tracker> to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list <https://jenkins.io/redirect/users-mailing-list> might be also useful in understanding what has happened. Stack trace org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/jenkins/model/Jenkins/configure.jelly:59:84: Type org.eclipse.jgit.transport.RemoteConfig not present Thanks for your time and support Regards 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 <netwar...@gmail.com > > 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: >> >> 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 jenkinsci-use...@googlegroups.com . >> 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_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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/022d0dc1-d6a2-4cb3-a2e5-e2fe6bfad468%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
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 like it boils down to: > > Caused by: java.lang.ClassNotFoundException: > org.eclipse.jgit.transport.RemoteConfig > > > > Any ideas on how to fix this? > > Thanks > > > javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: > jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.626.jar!/lib/hudson/project/config-scm.jelly:36:63: > org/eclipse/jgit/transport/RemoteConfig > at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) > at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) > at org.kohsuke.stapler.Stapler.service(Stapler.java:238) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) > at > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) > at > hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) > at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) > at > hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) > at > hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) > at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) > at > org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) > at > hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) > at > org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) > at >
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: 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 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
