[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title John Elion edited a comment on JENKINS-50711 Re: plugin doesn't work with ssh link to git repo Discovered by accident: If I create a copy of a job that has this bug, the copy does not seem to! (Click "New Item" in a folder, give the new item a name and choose "Copy" down at the bottom, and enter the name of the job that is breaking like this.) Save, run the job once (the first time it has been working for everybody), run it again - and the second time seems to be working. Even after doing this, the original job still has the error described by this bug.I looked at the two config.xml files - they seem identical except for a GUID. So I'm not sure why this happens, but it might provide a sort of workaround to those who are frustrated by this behavior.My jobs are all FreeStyle jobs. I have seen this on multiple jobs (I had to essentially rename a bunch of jobs because their common suffix was part of an exclusion pattern in a test config.). I am confident that, because it is still happening on the original jobs, it is not related to any sort of plugin upgrades (I have upgraded plugins, though the Git plugins I noted above are still at those same versions.) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189802.1523350889000.22855.1559841360330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title John Elion commented on JENKINS-50711 Re: plugin doesn't work with ssh link to git repo Discovered by accident: If I create a copy of a job that has this bug, the copy does not seem to! (Click "New Item" in a folder, give the new item a name and choose "Copy" down at the bottom, and enter the name of the job that is breaking like this.) Save, run the job once (the first time it has been working for everybody), run it again - and the second time seems to be working. Even after doing this, the original job still has the error described by this bug. I looked at the two config.xml files - they seem identical except for a GUID. So I'm not sure why this happens, but it might provide a sort of workaround to those who are frustrated by this behavior. My jobs are all FreeStyle jobs. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189802.1523350889000.22848.1559841240216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title John Elion reopened an issue I understand that a fix has been made, but I am seeing the exact behavior described here right down to the stack trace (with different line numbers) in Jenkins 2.164.2 running on Centos 7 Linux with Git Parameter 0.9.10, Git plugin 3.10.0 and Git Client Plugin 2.7.7. The referenced Wiki page describes a similar error and states that the SSH command is not available. However, in my installation I have confirmed that it is available from an interactive terminal session both on the Jenkins master and the Jenkins slave, from the Jenkins Groovy Console a groovy script that executes an arbitrary command prints the ssh help when "ssh" is the arbitrary command, and when "SSH" is entered as the only command in a "Execute windows batch script" build step in a Freestyle test job running on our Windows Jenkins slave. (It's not clear to me whether this command is being attempted on the master, or on the slave where the job's workspace has already been created.) I mean no disrespect by re-opening this bug, but I believe it is still occurring. Could I ask that this be given a second look? If there is any output or missing information I can provide I will be happy to try to find it. [ Resurgence/jke_vulcan_playground ] Unexpected error! hudson.plugins.git.GitException: Command "git ls-remote -h ssh://vdn-bitbucket.pa10lab.gd-ms.us:7999/resurg/vulcan.git" returned status code 128: stdout: stderr: /tmp/ssh2051896551955727069.sh: line 6: ssh: command not found fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1666) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1657) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteReferences(CliGitAPIImpl.java:2877) Jenkins / JENKINS-50711 plugin doesn't work with ssh link to git repo Change By: John Elion Resolution: Fixed Status: Resolved Reopened
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
John Elion edited a comment on JENKINS-38268
Re: Parallel step and closure scope
I've been hit by the same issue. I've noticed that certain kinds of scoping passes through ok, but some kinds do not. def say1(s) \{ println('say1: ' + s) } def say2 = \{ s -> println('say2: ' + s) } def setup = \{ def map = [:] def say3 = \{ s -> println('say3: ' + s) } for (def i = 0; i < 3; i++) \{ def x = I map[x] = \{ println x; say1( x ); say2( x ); say3( x ) } } return map } def jobs = setup() parallel(jobs)The "println" , and "say1" , and work but "say2" work but and "say3" does not (and the def say4( x ) \{ are wrong, println( x ) } form isn't allowed inside setup's block) and in a different ways . Stripping all the "noise", I get the following: [0] 0 [1] 1 [2] 2 [0] say1: 0 [1] say1: 1 [2] say1: 2 [0] say2: 2 [1] say2: 0 [2] say2: 1 [0] say3: 2 [1] say3: 2 [2] say3: 2 Hoping this helps say2 is not printing the x value associated with a workaround the parallel branch. say3 is always printing the x value from branch "2". (I don't have mine yet had originally commented that say2 was working, but it is not. The branch name in brackets should always match the number at the end of each line. ) Spotting these differences helped me work around the issue and also understanding what the scope resolution issue might be...
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
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
John Elion edited a comment on JENKINS-38268
Re: Parallel step and closure scope
I've been hit by the same issue. I've noticed that certain kinds of scoping passes through ok, but some kinds do not. def say1(s) \{ println('say1: ' + s) } def say2 = \{ s -> println('say2: ' + s) } def setup = \{ def map = [:] def say3 = \{ s -> println('say3: ' + s) } for (def i = 0; i < 3; i++) \{ def x = I map[x] = \{ println x; say1(x); say2(x); say3(x) } } return map } def jobs = setup() parallel(jobs)The "println", "say1", and "say2" work but "say3" does not (and the def say4(x) \{ println(x) } form isn't allowed inside setup's block). Stripping all the "noise", I get the following: [0] 0 [1] 1 [2] 2 [0] say1: 0 [1] say1: 1 [2] say1: 2 [0] say2: 2 [1] say2: 0 [2] say2: 1 [0] say3: 2 [1] say3: 2 [2] say3: 2Hoping this helps with a workaround (I don't have mine yet) and also understanding what the scope resolution issue might be...
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-38268) Parallel step and closure scope
Title: Message Title
John Elion commented on JENKINS-38268
Re: Parallel step and closure scope
I've been hit by the same issue. I've noticed that certain kinds of scoping passes through ok, but some kinds do not. def say1(s) { println('say1: ' + s) } def say2 = { s -> println('say2: ' + s) } def setup = { def map = [:] def say3 = { s -> println('say3: ' + s) } for (def i = 0; i < 3; i++) { def x = I map[x] = { println x; say1; say2; say3 } } return map } def jobs = setup() parallel(jobs) The "println", "say1", and "say2" work but "say3" does not (and the def say4 { println } form isn't allowed inside setup's block). Stripping all the "noise", I get the following: [0] 0 [1] 1 [2] 2 [0] say1: 0 [1] say1: 1 [2] say1: 2 [0] say2: 2 [1] say2: 0 [2] say2: 1 [0] say3: 2 [1] say3: 2 [2] say3: 2 Hoping this helps with a workaround (I don't have mine yet) and also understanding what the scope resolution issue might be...
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-40633) Log parser should emit string in log indicating it found a problem.
Title: Message Title John Elion created an issue Jenkins / JENKINS-40633 Log parser should emit string in log indicating it found a problem. Issue Type: Improvement Assignee: Manuel Recena Soto Components: log-parser-plugin Created: 2016/Dec/22 1:16 PM Environment: Jenkins 2.19.4, log-parser 2.0 Priority: Minor Reporter: John Elion I suggest that the console log parser ought to emit a message in the build log when it finds one or more errors that fails the build. I concede that I am guessing: I had what appeared to be a successful build, except that the build failure analyzer detected "Build step 'Use publishers from another project' changed build result to FAILURE". However, none of the publisher build steps showed any signs of failure. After some study, It dawned on me to check the parsed console log where I discovered a single error had been reported that had no other consequences (i.e., despite the error Ant reported BUILD SUCCESSFUL and a usable artifact was produced.) I am guessing that by detecting an error, the console log parser failed the build. It would have been helpful if when it ran, it reported that it had detected an error in the console log and failed the build - I would have got to the parsed console output a lot sooner. Very nice plugin. By writing up these details I in no way mean to imply the utility is bad; rather, I took the time to write this up because I think it is a great tool and this is something that I hope will be easy to implement and when done, it will help more readily guide the user to the source of problems.
[JIRA] [findbugs-plugin] (JENKINS-28650) Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports
Title: Message Title John Elion commented on JENKINS-28650 Re: Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports I did try to create a freestyle project, and with it I did get the Findbugs link. Still saw the org.log4j messages, not sure if they are significant - they do seem to be related. I'm not sure if we'll be able to use freestyle projects or not - I did notice we lost some other things (the Maven variant seems to know the downstream project build sequence, for example, and automatically populates the build's project web site to the project page.) Thank you for your suggestions. 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] [findbugs-plugin] (JENKINS-28650) Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports
Title: Message Title John Elion commented on JENKINS-28650 Re: Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports Both. When Publish Findbugs... is checked, the Maven generated website link stops appearing (and the related log messages appear) and when it is unchecked, the link comes back. And, I have never seen anything on the project or build page related to Findbugs results. I went back and added findbugs:findbugs to the Maven goals - that is, the goals were changed to site findbugs:findbugs install. I did not remove findbugs from reporting (it comes from a corporate master pom) I understand that means Findbugs is executed twice right now. I saw neither the web site nor the findbugs report in my project page, and my build status page did not show Findbugs results. My log showed this: 00:02:36.009 [INFO] Generating CPD report — maven-pmd-plugin:3.4:cpd 00:02:36.040 [INFO] Generating PMD report — maven-pmd-plugin:3.4:pmd 00:02:36.539 log4j:WARN No appenders could be found for logger (org.apache.commons.digester3.Digester.sax). 00:02:36.539 log4j:WARN Please initialize the log4j system properly. 00:02:37.725 [WARNING] Using default org.dom4j.DocumentFactory 00:02:37.756 [WARNING] Using default org.dom4j.DocumentFactory 00:02:37.819 [WARNING] Using default org.dom4j.DocumentFactory 00:02:37.819 [WARNING] Using default org.dom4j.DocumentFactory 00:02:38.162 [WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: null 00:02:38.162 [INFO] 00:02:38.162 [INFO] — findbugs-maven-plugin:3.0.1:findbugs (default-cli) @ viz-common — 00:02:39.004 [INFO] Fork Value is true 00:02:56.383 [java] Warnings generated: 114 00:02:56.492 [INFO] Done FindBugs Analysis 00:02:57.179 [WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: Could not initialize class edu.umd.cs.findbugs.SortedBugCollection 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
[JIRA] [findbugs-plugin] (JENKINS-28650) Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports
Title: Message Title John Elion edited a comment on JENKINS-28650 Re: Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports First,thankyouyourcommentandsuggestion. Both.WhenPublishFindbugs...ischecked,theMavengeneratedwebsitelinkstopsappearing(andtherelatedlogmessagesappear)andwhenitisunchecked,thelinkcomesback.And,IhaveneverseenanythingontheprojectorbuildpagerelatedtoFindbugsresults.Iwentbackandaddedfindbugs:findbugstotheMavengoals-thatis,thegoalswerechangedtositefindbugs:findbugsinstall.Ididnotremovefindbugsfromreporting(itcomesfromacorporatemasterpom)IunderstandthatmeansFindbugsisexecutedtwicerightnow.Isawneitherthewebsitenorthefindbugsreportinmyprojectpage,andmybuildstatuspagedidnotshowFindbugsresults.Mylogshowedthis:00:02:36.009[INFO]GeneratingCPDreport---maven-pmd-plugin:3.4:cpd00:02:36.040[INFO]GeneratingPMDreport---maven-pmd-plugin:3.4:pmd00:02:36.539log4j:WARNNoappenderscouldbefoundforlogger(org.apache.commons.digester3.Digester.sax).00:02:36.539log4j:WARNPleaseinitializethelog4jsystemproperly.00:02:37.725[WARNING]Usingdefaultorg.dom4j.DocumentFactory00:02:37.756[WARNING]Usingdefaultorg.dom4j.DocumentFactory00:02:37.819[WARNING]Usingdefaultorg.dom4j.DocumentFactory00:02:37.819[WARNING]Usingdefaultorg.dom4j.DocumentFactory00:02:38.162[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:null00:02:38.162[INFO]00:02:38.162[INFO]---findbugs-maven-plugin:3.0.1:findbugs(default-cli)@viz-common---00:02:39.004[INFO]ForkValueistrue00:02:56.383[java]Warningsgenerated:11400:02:56.492[INFO]DoneFindBugsAnalysis00:02:57.179[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:Couldnotinitializeclassedu.umd.cs.findbugs.SortedBugCollection 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] [findbugs-plugin] (JENKINS-28650) Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports
Title: Message Title John Elion updated an issue Jenkins / JENKINS-28650 Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports Change By: John Elion AftergettingasmallMavendemonstrationprojectworkingwithinJenkins,Iattemptedtoaddthestaticanalysisreports,installingtheStaticAnalysisUtilitiesandCollectorandtheFindbugsPlugin.ItriedseveralsettingsbutwasneverabletoseeaFindBugsreportontheJenkinsbuildstatuspage,andeventuallynoticedthatthe'Maven-generatedsite'linkdisappearedfromtheleft-handsideofmyprojectlinks.UltimatelyItracedthisdownto:IfPublishFindbugsanalysisresultsischeckedintheBuildSettingsareabelowAddpost-buildstep,nolinkisgenerated;ifitisunchecked,theMavenwebsitelinkappears.Thelogfilesareinstructive:neartheendofasuccessfulbuildIseethefollowing,whichseemstoshowthewebsitetreecopytowhereJenkinsstoresthewebsite:00:01:02.137[INFO]CoberturaReportgenerationwassuccessful.00:01:02.137[INFO]GeneratingCPDreport---maven-pmd-plugin:3.4:cpd00:01:02.168[INFO]GeneratingPMDreport---maven-pmd-plugin:3.4:pmd00:01:02.324[JENKINS]ArchivingsitefromC:\ProgramFiles(x86)\Jenkins\workspace\VizCommon\target\sitetoC:\ProgramFiles(x86)\Jenkins\jobs\VizCommon\siteNeartheendofafailedbuildIseethisinstead00:01:04.536[INFO]GeneratingCPDreport---maven-pmd-plugin:3.4:cpd00:01:04.581[INFO]GeneratingPMDreport---maven-pmd-plugin:3.4:pmd00:01:05.345log4j:WARNNoappenderscouldbefoundforlogger(org.apache.commons.digester3.Digester.sax).00:01:05.345log4j:WARNPleaseinitializethelog4jsystemproperly.00:01:06.534[WARNING]Usingdefaultorg.dom4j.DocumentFactory00:01:06.553[WARNING]Usingdefaultorg.dom4j.DocumentFactory00:01:06.595[WARNING]Usingdefaultorg.dom4j.DocumentFactory00:01:06.596[WARNING]Usingdefaultorg.dom4j.DocumentFactory00:01:06.885[WARNING]Failedtonotifyspyhudson.maven.Maven3Builder$JenkinsEventSpy:null00:01:06.885[INFO]00:01:06.885[INFO]---maven-resources-plugin:2.6:resources(default-resources)@viz-common---NotethatIonlyenabledFindbugsreporting,eventhoughMavensuccessfullygeneratesthePMDandCoberturareports(IhadinstalledtheCoberturapluginbutfirstdisabled,thenuninstalledit.IsuspecttheproblemiswithFindbugs(seePMDtestbelow).IthoughtthismightberelatedtoJENKINS- 24743 26923 ,whichsuggestedaproblemwithcommon-io(althoughIbelievemyversionoftheSAtoolincludesthatbug'sfix);soIstoppedJenkins,renamedcommons-io-2.2.jarandrestarted;butre-runningaPublishFindbugsbuildstillpresentedthelog4janddom4jwarningsandnowebsite.Isuspect(orhope)theseerrorsarenotonlycausingtheMavenwebsitetonotbepublished,butmaybewhyIneversawalinktoFindbugsreports.IdidalsotrythecasewherePublishPMDanalysisresultsischecked(only,withtheFindbugsboxunchecked).InthatcaseIsawthelog4jwarnings,butnotthedom4jwarnings;thewebsitedidpublish-andIalsogotaPMDlink.
[JIRA] [findbugs-plugin] (JENKINS-28650) Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports
Title: Message Title John Elion created an issue Jenkins / JENKINS-28650 Publish Findbugs stops Maven web site publishing, not publishing Findbugs reports Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 30/May/15 4:23 AM Environment: Jenkins 1.615 running on Windows 7 Enterprise SP1 on X64 Findbugs Plugin 4.6.0 PMD Plugin 3.41 Static Analysis Collector Plugin 1.43 Static Analysis Utilities 1.71 Maven 3.3.3 Findbugs 3.0.1 Priority: Major Reporter: John Elion After getting a small Maven demonstration project working within Jenkins, I attempted to add the static analysis reports, installing the Static Analysis Utilities and Collector and the Findbugs Plugin. I tried several settings but was never able to see a FindBugs report on the Jenkins build status page, and eventually noticed that the 'Maven-generated site' link disappeared from the left-hand side of my project links. Ultimately I traced this down to: If Publish Findbugs analysis results is checked in the Build Settings area below Add post-build step, no link is generated; if it is unchecked, the Maven web site link appears. The log files are instructive: near the end of a successful build I see the following, which seems to show the web site tree copy to where Jenkins stores the web site: 00:01:02.137 [INFO]
