[JIRA] (JENKINS-50558) Valgrind plugin results error
Title: Message Title Marshall Galbraith commented on JENKINS-50558 Re: Valgrind plugin results error I've yet to hear anything... I've noticed that if I look at an individual build that has finished as part of a matrix project it works, but as soon as the matrix finishes I get the error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50558) Valgrind plugin results error
Title: Message Title
Marshall Galbraith updated an issue
Jenkins / JENKINS-50558
Valgrind plugin results error
Change By:
Marshall Galbraith
Valgrind report pages have stopped working as of today. I recently installed the latest pipeline plugin upgrads, but I don't know if that is related. The valgrind xml files appear to be processes without warnings or errors in the console log.I get the following "Ooops" page when trying to view results: {code:java} org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/valgrind/WEB-INF/lib/valgrind.jar!/org/jenkinsci/plugins/valgrind/ValgrindResult/index.jelly:13:57: No page found 'sidepanel.jelly' for class org.jenkinsci.plugins.valgrind.ValgrindResult at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) 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.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:140) at org.kohsuke.stapler.IndexViewDispatcher.dispatch(IndexViewDispatcher.java:30) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at
[JIRA] (JENKINS-50558) Valgrind plugin results error
Title: Message Title Marshall Galbraith commented on JENKINS-50558 Re: Valgrind plugin results error It's good to know I'm not the only one with the problem. I would look into fixing it my self, but I don't have any skills with Java... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50558) Valgrind plugin results error
Title: Message Title Marshall Galbraith commented on JENKINS-50558 Re: Valgrind plugin results error Knut, do you have to delete the actual job or just all the builds from the job? I actually observed a matrix configuration where one of the configurations finished, and the results were properly displayed for that conflagration. However, later that same configuration stopped working. I did not reboot in between, but I can't recall if a different configuration finished during that same time period. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29963) MatrixProject builds previous revision in pull request
Title: Message Title Marshall Galbraith closed an issue as Fixed Jenkins / JENKINS-29963 MatrixProject builds previous revision in pull request Change By: Marshall Galbraith Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50558) Valgrind plugin results error
Title: Message Title Marshall Galbraith created an issue Jenkins / JENKINS-50558 Valgrind plugin results error Issue Type: Bug Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 2018-04-04 03:34 Environment: jenkins 2.107.1 valgrind-plugin 0.28 Priority: Blocker Reporter: Marshall Galbraith Valgrind report pages have stopped working as of today. I recently installed the latest pipeline plugin upgrads, but I don't know if that is related. The valgrind xml files appear to be processes without warnings or errors in the console log. I get the following "Ooops" page when trying to view results: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/valgrind/WEB-INF/lib/valgrind.jar!/org/jenkinsci/plugins/valgrind/ValgrindResult/index.jelly:13:57: No page found 'sidepanel.jelly' for class org.jenkinsci.plugins.valgrind.ValgrindResult at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) 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.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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
[JIRA] [ghprb-plugin] (JENKINS-29963) MatrixProject builds previous revision in pull request
Title: Message Title Marshall Galbraith commented on JENKINS-29963 Re: MatrixProject builds previous revision in pull request I added this as an issue on github as well. I was not sure where the preferred places was for adding this. I have not been able to find a workaround. I'm willing to help find and fix the bug, but I'm a bit of a Java novice (much more experience with C++ and python). I wanted to first create a unit tests that reproduces the problem, but I have not had the time to sort out the unit testing framework. I'm confident that once I have a unit test I should be able to at least hone in on the real cause of the error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-pullrequest-plugin] (JENKINS-29963) MatrixProject builds previous revision in pull request
Title: Message Title Marshall Galbraith created an issue Jenkins / JENKINS-29963 MatrixProject builds previous revision in pull request Issue Type: Bug Assignee: Kanstantsin Shautsou Components: github-pullrequest-plugin Created: 14/Aug/15 10:39 PM Environment: Jenkins 1.624, GitHub Pull Request Builder 1.26.2 Priority: Major Reporter: Marshall Galbraith First I just want to say this is a really amazing plugin and aside from this one problem our group is really happy with it. We currently have a matrix project to test on multiple systems. Unfortunately we have a problem when new commits are pushed to a pull request. The main build of the matrix project will always get the correct revision, but the matrix builds end up building the the previous revision. The matrix builds are consistently one revision behind. I suspect it has something to do with the interaction between this line of code in GhprbTrigger.java // add the previous pr BuildData as an action so that the correct change log is generated by the GitSCM plugin // note that this will be removed from the Actions list after the job is completed so that the old (and incorrect) // one isn't there return this.job.scheduleBuild2(job.getQuietPeriod(), cause, new ParametersAction(values), findPreviousBuildForPullId(pullIdPv));
[JIRA] [ghprb-plugin] (JENKINS-29963) MatrixProject builds previous revision in pull request
Title: Message Title Marshall Galbraith assigned an issue to Honza Brzdil Jenkins / JENKINS-29963 MatrixProject builds previous revision in pull request Change By: Marshall Galbraith Component/s: ghprb-plugin Component/s: github-pullrequest-plugin Assignee: KanstantsinShautsou HonzaBrzdil Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23179) git pre-merge fails with matrix project
Marshall Galbraith updated JENKINS-23179 git pre-merge fails with matrix project Change By: Marshall Galbraith (18/Jul/14 2:38 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23179) git pre-merge fails with matrix project
Marshall Galbraith edited a comment on JENKINS-23179 git pre-merge fails with matrix project I created a unit test that reproduces the problem, and created a fix. Both are available with this pull request: https://github.com/jenkinsci/git-plugin/pull/235 The fix does not modify the behavior for regular projects, or matrix projects that do not use the git pre-merge feature. The current implementation always uses the decorated revision for the matrix axes. However, the decorated revision only exists in the workspace of the cloned parent build, and does not exist in the cloned workspace for the axes. This fix causes the axes to use the marked revision, rather than the decorated one. The axis then subsequently decorate the marked revision. The only other way that I could think of fixing this problem would require the axes to pull the decorated revision from the parent workspace. However, this would cause all kinds of headaches in particular if working with multiple distributed slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23179) git pre-merge fails with matrix project
Marshall Galbraith edited a comment on JENKINS-23179 git pre-merge fails with matrix project I created a unit test that reproduces the problem, and created a fix. Both are available with this pull request: https://github.com/jenkinsci/git-plugin/pull/235 The fix does not modify the behavior for regular projects, or matrix projects that do not use the git pre-merge feature. The current implementation always uses the decorated revision for the matrix axes. However, the decorated revision only exists in the workspace of the cloned parent build, and does not exist in the cloned workspace for the axes. This fix causes the axes to use the marked revision, rather than the decorated one. The axes then subsequently decorate the marked revision. The only other way that I could think of fixing this problem would require the axes to pull the decorated revision from the parent workspace. However, this would cause all kinds of headaches in particular if working with multiple distributed slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuildscript] (JENKINS-23394) Build Results for each Script
Marshall Galbraith created JENKINS-23394 Build Results for each Script Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: postbuildscript Created: 11/Jun/14 2:55 AM Description: Right now we have global toggles to run all scripts on either build success, failure, or both. I would like to be able to execute some scripts on success, and other scripts on failure. I'm willing to spend some time on this if you want me to. I have looked at the source and I can implement this for the script files. I'm not sure how to do it though for the build tasks. Project: Jenkins Priority: Major Reporter: Marshall Galbraith This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23179) git pre-merge fails with matrix project
Marshall Galbraith commented on JENKINS-23179 git pre-merge fails with matrix project I created a unit test that reproduces the problem, and created a fix. Both are available with this pull request: https://github.com/jenkinsci/git-plugin/pull/235 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23179) git Pre-merge fails with matrix project
Marshall Galbraith
created JENKINS-23179
git Pre-merge fails with matrix project
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
25/May/14 4:06 AM
Description:
For a matrix project, the pre-merge occurs on the parent build, and the resulting merged revision number is passed to the slaves for their builds. However, the slaves are not able to checkout the merged revision because it only exists in the temporary parent clone. In the example below the build is triggered for revision d4c5faa85 on the feature branch xxx/xxx/develop. This feature branch is merged into xxx/master. This is the log for the parent build
Fetching changes from the remote Git repository
git config remote.xxx.url ssh://repoURLremoved
Pruning obsolete local branches
Fetching upstream changes from ssh://repoURLremoved
git --version
git fetch --tags --progress ssh://repoURLremoved +refs/heads/:refs/remotes/xxx/ --prune
git rev-parse xxx/xxx/develop^{commit}
Merging Revision d4c5faa8537180c26350fdecebe2d0b3d05c04c5 (xxx/xxx/develop) onto xxx/master using default strategy
git rev-parse xxx/master^{commit}
git config core.sparsecheckout
git checkout -f xxx/master
git merge d4c5faa8537180c26350fdecebe2d0b3d05c04c5
git rev-parse HEAD^{commit}
Seen branch in repository xxx/xxx/develop
Seen branch in repository xxx/master
Seen 4 remote branches
Checking out Revision 3ead3e08dc58524349b8c629a8a0a5775a3edf74 ()
git config core.sparsecheckout
git checkout -f 3ead3e08dc58524349b8c629a8a0a5775a3edf74
Here is the log for one of the slaves
Fetching changes from the remote Git repository
git config remote.xxx.url ssh://repoURLremoved
Pruning obsolete local branches
Fetching upstream changes from ssh://repoURLremoved
git --version
git fetch --tags --progress ssh://repoURLremoved +refs/heads/:refs/remotes/xxx/ --prune
Checking out Revision 3ead3e08dc58524349b8c629a8a0a5775a3edf74 ()
git config core.sparsecheckout
git checkout -f 3ead3e08dc58524349b8c629a8a0a5775a3edf74
FATAL: Could not checkout null with start point 3ead3e08dc58524349b8c629a8a0a5775a3edf74
So the slave tries to checkout the temporary commit 3ead3e08d that only exists in the clone for the parent build.
I've looked at the source and I think the problem is in the function determineRevisionToBuild in GitSCM.java. I am willing to spend some time on this, and I think I know how to solve the problem. However, I could use some guidance on testing to ensure I don't introduce a different bug in the process.
Project:
Jenkins
Labels:
git
jenkins
matrix
Priority:
Blocker
Reporter:
Marshall Galbraith
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23179) git pre-merge fails with matrix project
Marshall Galbraith updated JENKINS-23179 git pre-merge fails with matrix project Change By: Marshall Galbraith (25/May/14 4:08 AM) Summary: git Pre pre -mergefailswithmatrixproject This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-22312) email-ext add argument showMessage to token FAILED_TESTS
Marshall Galbraith created JENKINS-22312 email-ext add argument showMessage to token FAILED_TESTS Issue Type: New Feature Assignee: Alex Earl Components: email-ext Created: 22/Mar/14 4:14 AM Description: I would appreciate if an option could be added to the token FAILED_TESTS to suppress error messages similar to how showStack can be used to suppress the error stack. I am willing to help add this option. Project: Jenkins Priority: Minor Reporter: Marshall Galbraith This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
