[JIRA] [rich-text-publisher-plugin] (JENKINS-26533) get You must use POST method to trigger builds when adding link to jenkins job via Rich Text Publisher
Rick Patterson closed JENKINS-26533 as Not A Defect get You must use POST method to trigger builds when adding link to jenkins job via Rich Text Publisher I guess I will close this item. I am thinking I need a POST method, I didn't know enough about URL's to know that they apparently do GET methods, and can't do POSTs. What I am trying to do is create a link on one Jenkins job's build results page to second Jenkins job that will pass parameters about the build, and invoke the second Jenkins job. I need a link, since the first job does not always require the second job, the need for the second job might be determined days or even weeks later. Change By: Rick Patterson (22/Jan/15 2:02 PM) Status: Open Closed Resolution: NotADefect 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli edited a comment on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Sorry Daniel if you felt offended (although I am not sure whether you are reading this one) but I was just pointing out the fact that probably using a DB would fix many problems we have been experiencing (especially on Windows!). In fact, lets say you have a big project with 10.000 builds (yes it is easy to collect so many of them if you work for a company that has at least 15 developers) do you really want to have your Jenkins parse 10.000 XML files? Also considering the fact that in case of errors the system will try parsing them forever producing large error log files till the service crashes? Yes I do value the time you have been spending on this project but allow me to say we probably could improve the system. The log format has changed many times so far causing many issues. In some cases you can fix the problem by discarding the offending builds (generally the old ones) which of course fails the main principle of any software pipeline. Also using all of those symlinks on Windows... You can back-up and restore all projects no problem but if you try restoring log files then you might run into problems https://issues.jenkins-ci.org/browse/JENKINS-18924 That said... my two cents... I was just trying to help 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] [prioritysorter-plugin] (JENKINS-24618) Absolute priority not working
Markus commented on JENKINS-24618 Absolute priority not working Hi Pedro, I am not the expert on this plugin. But for us, some jobs are in multiple views. It seems that the Job Priorities (advanced-build-queue) starts at the top and when a job matches a criteria, it gets that priority. It does not matter if the jobs is in other views further down in the list. We use regular expressions for the views, but some priorities are set using the Job Priorities criteria. Such as manually started jobs. We don't have any priorities set up for individual jobs, those are all removed. I do not know if that is required. We have also disabled "allow priorities directly on Jobs". I do not know if that is required. 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Daniel Beck commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Not sure what I've done to deserve condescending answers such as that one. I'm volunteering to do a bit of work for the Jenkins project in my free time. I've warned on the jenkinsci-users mailing list about installing it, I've provided an explanation and workarounds to the disk-usage plugin problem on JENKINS-26496, I've pointed Jesse (the migration code author) to the Windows migration issue JENKINS-26519 and increased its priority, and I've even asked other project members for more public announcements mentioning possible side effects of this change prior to release (which didn't happen, unfortunately). I'm unsubscribing from this issue, as it appears to serve no constructive purpose. You're clearly not interested in this leading to any kind of improvement. This should have been a post on your blog. 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] [template-project-plugin] (JENKINS-26548) Jenkins scheduled build jobs fails randomly with java.lang.NullPointerException
Daniel Beck updated JENKINS-26548 Jenkins scheduled build jobs fails randomly with java.lang.NullPointerException Looks more like a Template Project Plugin issue. Change By: Daniel Beck (22/Jan/15 11:55 AM) Component/s: template-project-plugin Component/s: parameterized-trigger-plugin Component/s: schedule-build-plugin 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Sorry Daniel if you felt offended (although I am not sure whether you are reading this one) but I was just pointing out the fact that probably using a DB would fix many problems we have been experiencing (especially on Windows!). In fact, lets say you have a big project with 10.000 builds (yes it is easy to collect so many of them if you work for a company that has at least 15 developers) do you really want to have your Jenkins parse 10.000 XML files? Also considering the fact that in case of errors the system will try parsing them forever till the system crashes? Yes I do value the time you have been spending on this project but allow me to say we probably could improve the system. The log format has changed many times so far causing many issues. In some cases you can fix the problem by discarding the offending builds (generally the old ones) which of course fails the main principle of any software pipeline. Also using all of those symlinks on Windows... You can back-up and restore all projects no problem but if you try restoring log files then you might run into problems https://issues.jenkins-ci.org/browse/JENKINS-18924 That said... my two cents... I was just trying to help 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] [virtualbox-plugin] (JENKINS-16231) Stop slave options should list all possible options, not just save and poweroff
Henri Gomez commented on JENKINS-16231 Stop slave options should list all possible options, not just save and poweroff What about PR, so I could review it and apply. Side note, I'm not using VB Plugin anymore. 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli edited a comment on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Sorry Daniel if you felt offended (although I am not sure whether you are reading this one) but I was just pointing out the fact that probably using a DB would fix many problems we have been experiencing (especially on Windows!). In fact, lets say you have a big project with 10.000 builds (yes it is easy to collect so many of them if you work for a company that has at least 15 developers) do you really want to have your Jenkins parse 10.000 XML files? Also considering the fact that in case of errors the system will try parsing them forever producing large error log files till the service crashes? Yes I do value the time you have been spending on this project but allow me to say we probably could improve the system. The build log format has changed many times so far causing many issues. In some cases you can fix the problem by discarding the offending builds (generally the old ones) which of course fails the main principle of any software pipeline. Also using all of those symlinks on Windows... You can back-up and restore all projects no problem but if you try restoring log files then you might run into problems https://issues.jenkins-ci.org/browse/JENKINS-18924 That said... my two cents... I was just trying to help 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] [parameterized-trigger-plugin] (JENKINS-26548) Jenkins scheduled build jobs fails randomly with java.lang.NullPointerException
Ramakrishna Bejawar created JENKINS-26548 Jenkins scheduled build jobs fails randomly with java.lang.NullPointerException Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin, schedule-build-plugin Created: 22/Jan/15 11:50 AM Description: FATAL: null java.lang.NullPointerException at hudson.plugins.templateproject.ProxySCM.getBrowser(ProxySCM.java:102) at hudson.scm.AutoBrowserHolder.infer(AutoBrowserHolder.java:79) at hudson.scm.AutoBrowserHolder.get(AutoBrowserHolder.java:64) at hudson.scm.SCM.getEffectiveBrowser(SCM.java:136) at hudson.scm.ChangeLogSet.browserFromBuild(ChangeLogSet.java:82) at hudson.scm.ChangeLogSet.init(ChangeLogSet.java:76) at hudson.scm.SubversionChangeLogSet.init(SubversionChangeLogSet.java:63) at hudson.scm.SubversionChangeLogParser.parse(SubversionChangeLogParser.java:74) at hudson.scm.SubversionChangeLogParser.parse(SubversionChangeLogParser.java:43) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:896) at hudson.model.AbstractBuild.access$600(AbstractBuild.java:106) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:636) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530) at hudson.model.Run.execute(Run.java:1732) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Environment: Jenkins Version 1.570 Project: Jenkins Labels: jenkins NullPointerException Proxy Priority: Major Reporter: Ramakrishna Bejawar 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli edited a comment on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Sorry Daniel if you felt offended (although I am not sure whether you are reading this one) but I was just pointing out the fact that probably using a DB would fix many problems we have been experiencing (especially on Windows!). In fact, lets say you have a big project with 10.000 builds (yes it is easy to collect so many of them if you work for a company that has at least 15 developers) do you really want to have your Jenkins parse 10.000 XML files? Also considering the fact that in case of errors the system will try parsing them forever till the it crashes? Yes I do value the time you have been spending on this project but allow me to say we probably could improve the system. The log format has changed many times so far causing many issues. In some cases you can fix the problem by discarding the offending builds (generally the old ones) which of course fails the main principle of any software pipeline. Also using all of those symlinks on Windows... You can back-up and restore all projects no problem but if you try restoring log files then you might run into problems https://issues.jenkins-ci.org/browse/JENKINS-18924 That said... my two cents... I was just trying to help 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-plugin] (JENKINS-26549) build.testResultAction was not set and it is always empty
Purna kumar created JENKINS-26549 build.testResultAction was not set and it is always empty Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 22/Jan/15 2:23 PM Description: I have configured my Build.xml as mentioned below to run test cases for Dotnet assemblies, PropertyGroupTestResultsPath$(JENKINS_HOME)\jobs\$(JOB_NAME)\builds\$(BUILD_NUMBER)\TestResults.xml/TestResultsPath /PropertyGroup Target Name="RunUnitTests" Exec Command='"$(NUnitConsole)" "$(UnitTestsDLL_Service)" "$(UnitTestsDLL_Business)" /result="$(TestResultsPath)" /framework=4.0' / /Target Where $(UnitTestsDLL_Business), $(UnitTestsDLL_Service) are dll absolute paths. I tried by changes "TestResultsPath" to local folder.But nothing is working.But i could the test summary in the build log.Could you please help me in resolving the issue? Environment: plugin : Email-ext OS : Windows Server 2008 R2 Browser : Any (Not applicable) Jenkins version : Jenkins ver. 1.560 Project: Jenkins Labels: Hudson Priority: Major Reporter: Purna kumar 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] [maven-plugin] (JENKINS-26057) Workflow build step for Maven
Jesse Glick updated JENKINS-26057 Workflow build step for Maven Change By: Jesse Glick (22/Jan/15 1:31 PM) Description: Reallybelongsinadifferentpluginasdescribedin https://trello.com/c/ImfSSGkj/4 JENKINS - classic-maven-builder-into-maven-builder-plugin 26462 butfilinghereforthemoment.AwaytorunMavenfromaworkflowusingconfiguredMaveninstallationsandwithsupportforotherfeaturessuchassettingsfilesandconsolehighlighting. 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] [core] (JENKINS-26539) Build descriptions in sidebar ignores HTML breaks (br)
Daniel Beck resolved JENKINS-26539 as Duplicate Build descriptions in sidebar ignores HTML breaks (br) Duplicates JENKINS-26406. Change By: Daniel Beck (22/Jan/15 8:05 AM) Status: Open Resolved Resolution: Duplicate 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Daniel Beck resolved JENKINS-26545 as Wont Fix Persist build(s) log(s) in MySQL (or similar) A major architectural change like this needs to be discussed on the dev list. FWIW a more exhaustive description of failure modes in the current system is needed right now it's not clear at all what the problem is, or how use of a database would help. Change By: Daniel Beck (22/Jan/15 8:12 AM) Status: Open Resolved Assignee: PraqmaSupport Resolution: WontFix 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli reopened JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Ok... first of all... how to correctly back that stuff up? On Windows copying all those links is a problem, some back up systems run into issues trying to copying those links. Then what if a code change breaks build logs? You will end up with a completely broken system. And this is happening on Windows... Change By: Libero Scarcelli (22/Jan/15 8:21 AM) Resolution: WontFix Status: Resolved Reopened 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] [envinject-plugin] (JENKINS-26547) Should be able to pick a password from the credenials
andreasmandel created JENKINS-26547 Should be able to pick a password from the credenials Issue Type: Improvement Assignee: Gregory Boissinot Components: envinject-plugin Created: 22/Jan/15 8:02 AM Description: Passwords stored as credentials in Jenkins should be a valid source for the environment variable value. If I get it right, this would partly replace the Credentials Binding Plugin but I think this plugin is the more natural place for this functionality!? Project: Jenkins Priority: Minor Reporter: andreasmandel 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Mads Nielsen commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Why did you put this under the logging-plugin component? The logging-plugin has nothing to do with this core change? 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] [rich-text-publisher-plugin] (JENKINS-26533) get You must use POST method to trigger builds when adding link to jenkins job via Rich Text Publisher
Daniel Beck commented on JENKINS-26533 get You must use POST method to trigger builds when adding link to jenkins job via Rich Text Publisher What exactly is the bug here? Note that If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. does not apply, as you wrote the link yourself. 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Ok... first of all... how to correctly back that stuff up? On Windows copying all those links is a problem, some back up systems run into issues trying to copying those links. Then what if a code change breaks build logs? You will end up with a completely broken system. And this is happening on Windows... 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] [subversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
JM D commented on JENKINS-26318 Subversion Plug in 2.5 causes sporadic problems Thanks for the tip Łukasz, unfortunately it doesn't work on my side, I still get the a similar stack: FATAL: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState java.lang.ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1265) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Daniel Beck commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) You're still incredibly vague, with no actionable information as to what the problems you're observing are (unreadable data is different from OOM situations, and for both, more information is needed to investigate further see https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue and https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump). Responding with a variant of "You don't know what you're talking about" when I try to redirect your responses to something constructive isn't helpful. Note that I've never written that you discard old builds (for one thing, I still don't know what the problems are). This report contains no substance, and the justification for requesting a major architectural change is questionable at best. So, could you please explain, in detail, what the problems are that you're facing? 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] [docker-plugin] (JENKINS-23301) Cannot connect to Docker using unix protocol
Guilhem Lettron commented on JENKINS-23301 Cannot connect to Docker using unix protocol Docker-java now support unix and tls! https://github.com/docker-java/docker-java/blob/master/CHANGELOG.md#docker-java-0105 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] [docker-plugin] (JENKINS-23301) Cannot connect to Docker using unix protocol
Guilhem Lettron edited a comment on JENKINS-23301 Cannot connect to Docker using unix protocol Docker-java now support unix and tls! https://github.com/docker-java/docker-java/blob/master/CHANGELOG.md#docker-java-0105 Oops didn't see your comment Jesse Glick 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Daniel... does the number "1.597" ring any bell to you? 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli edited a comment on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Because after modifying the Core you might want to modify the logging-plugin as well in order to extend it using new functionality... But yes... it's not necessary 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] [disk-usage-plugin] (JENKINS-26496) Trying to get the DateFormat as build ID
Andrey Regentov commented on JENKINS-26496 Trying to get the DateFormat as build ID By the way, 0.25-snapshot does not show disk usage for builds that are built prior to jenkins update 1.596-1.597. Disk usage for newer builds is shown, but for older there is just "-". 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] [other] (JENKINS-13249) workspace cleanup runs on offline nodes
Oliver Gondža resolved JENKINS-13249 as Fixed workspace cleanup runs on offline nodes Change By: Oliver Gondža (22/Jan/15 9:10 AM) Status: Open Resolved Resolution: Fixed 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] [other] (JENKINS-13249) workspace cleanup runs on offline nodes
Oliver Gondža commented on JENKINS-13249 workspace cleanup runs on offline nodes Seems fixed since 1.427. Note that putting node temporarily offline means no further builds will be scheduled on that node. There is no guarantee that Jenkins will not interact with the slave in any other way. Also, creating random content in node workspace (Jenkins can not get rid off) should generally be discouraged. 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Also... it's not just about not being able to access old builds but this leads to have a system crash when Jenkins starts logging continuously because it is not able to reach previous builds information 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Because after modifying the Core you might want modify the logging-plugin as well in order to extend it using new functionality... But yes... it's not necessary 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] [core] (JENKINS-25869) Jenkins is getting crashed and shutting down once in a while
Vamsi Hari commented on JENKINS-25869 Jenkins is getting crashed and shutting down once in a while Thanks Daniel for your help, We will keep posted if we find any solution for this java bug. Cheers, Vamsi Hari 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Daniel Beck commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) On Windows copying all those links is a problem, some back up systems run into issues trying to copying those links. In other words, you want Jenkins to not use OS features because your crap software doesn't support them. Well, if you prohibit creation of symbolic links on Windows through Group Policy, Jenkins will not create them. Then what if a code change breaks build logs? You're still incredibly vague. Please note that build logs in Jenkins are simple text files. They cannot break (unless moving to a completely different architecture like IBM's servers, I suppose). Please mind your terminology, otherwise communication will be incredibly difficult. As to code changes making parts of build logs unloadable (including disabling plugins that store data in configuration or build records), that's handled by Old Data Monitor. You can discard these plugins' data. For deliberate code changes, plugin authors can write backward compatibility code to transform old data into a new format. So what exactly is the problem you're trying to solve, and how is a database supposed to solve it? 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Daniel Beck edited a comment on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) On Windows copying all those links is a problem, some back up systems run into issues trying to copying those links. In other words, you want Jenkins to not use OS features because your crap software doesn't support them. Well, if you prohibit creation of symbolic links on Windows through Group Policy, Jenkins will not create them. Then what if a code change breaks build logs? You're still incredibly vague. Please note that build logs in Jenkins are simple text files. They cannot break (unless moving to a completely different architecture like IBM's servers, I suppose). Please mind your terminology, otherwise communication will be incredibly difficult. As to code changes making parts of build records unloadable (including disabling plugins that store data in configuration or build records), that's handled by Old Data Monitor. You can discard these plugins' data. For deliberate code changes, plugin authors can write backward compatibility code to transform old data into a new format. So what exactly is the problem you're trying to solve, and how is a database supposed to solve it? 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Daniel Beck commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) This looks a lot like a situation similar to the XY problem. You observe some behavior and propose a solution that you think would help. But you're not telling us what the exact behavior you're seeing is. It would help if you did that. 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] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Libero Scarcelli commented on JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Daniel you probably have never used Jenkins on Windows extensively. Why should I discard old builds? So what's the point in having a build pipeline? For "broken" logs I mean logs that are made unreadable which once again may lead to crash (out of memory, CPU starvation, etc...) 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] [disk-usage-plugin] (JENKINS-26508) Upgrade to 1.597 breaks Job page
apgray commented on JENKINS-26508 Upgrade to 1.597 breaks Job page Downgrading is where we want to be going forward. So are we waiting for another Disk Usage plugin release or another core release? 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-client-plugin] (JENKINS-23091) Git. Problem with encoding in the list changes
hayarobi Park commented on JENKINS-23091 Git. Problem with encoding in the list changes I found some blog posting that seems to be related to this issue. https://rkeithhill.wordpress.com/2010/05/26/handling-native-exe-output-encoding-in-utf8-with-no-bom/ 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] [maven-plugin] (JENKINS-26557) Unable to run the build step in Jenkins slave job but works as a pre build step when i invoke top level Maven targets
Sushma Kaniganti updated JENKINS-26557 Unable to run the build step in Jenkins slave job but works as a pre build step when i invoke top level Maven targets Change By: Sushma Kaniganti (22/Jan/15 6:52 PM) Summary: Unabletorunthebuildstep inJenkinsslavejob butworksasaprebuildstepwheniinvoketoplevelMaventargets 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] [swarm-plugin] (JENKINS-26558) createSlave Node name collision avoidance creates dead nodes
Kyle C created JENKINS-26558 createSlave Node name collision avoidance creates dead nodes Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 22/Jan/15 6:58 PM Description: In the swarm server-side slave creation logic, when a node of the provided name already exists, '-$IP' is appended to the end in an effort to end with a unique name (see https://github.com/jenkinsci/swarm-plugin/blob/master/plugin/src/main/java/hudson/plugins/swarm/PluginImpl.java#L59) However, as far as I can tell, that new name is never provided to the slave, so it doesn't seem like it'd be possible for the slave to connect with that name, and in my experience I've seen hundreds of collision-avoidance nodes in this setup, and have never once seen one online or connected in any way. These dead "hyphen nodes" don't hurt running builds, but they are visual noise and false positives in our offline slave metrics, so it'd be nice if they could be avoided. Environment: Jenkins 1.590 on Linux with Swarm Plugin 1.21 Project: Jenkins Priority: Minor Reporter: Kyle C 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] [google-play-android-publisher-plugin] (JENKINS-26542) Cannot change Google Service Account
Christopher Orr commented on JENKINS-26542 Cannot change Google Service Account So you mean you can change the service account, and running the job uses the new account, but the wrong one appears in the job config? Do the two accounts have the same name? I'll check it out; I need to improve how credentials are configured anyway! 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] [core] (JENKINS-25234) Improve readability of the 'schedule build' tooltip
Peter Marcoen started work on JENKINS-25234 Improve readability of the schedule build tooltip Change By: Peter Marcoen (22/Jan/15 1:08 PM) Status: Open InProgress 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] [ownership-plugin] (JENKINS-23926) Job Ownership not available if VCS fails
Hubert Grzeskowiak commented on JENKINS-23926 Job Ownership not available if VCS fails Big thanks for this, Oleg. I'll try to test this next week. 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] [ownership-plugin] (JENKINS-23947) Make ownership injection default
Hubert Grzeskowiak commented on JENKINS-23947 Make ownership injection default Big thanks for this, Oleg. I'll try to test this next week. 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] [envinject-plugin] (JENKINS-20334) envInject leaves in backslash for #, !, =, :
Thomas Froehlich commented on JENKINS-20334 envInject leaves in backslash for #, !, =, : Hi, this is definitely a bug. We are having exactly the same problem. Although this issue is old it would be nice to know if there is an "official workaround". 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] [copy-to-slave-plugin] (JENKINS-26353) Copy to slave fails and getting error message Pipe is already closed
Markus Heiden commented on JENKINS-26353 Copy to slave fails and getting error message Pipe is already closed I got the same problem. The problem is that the plugin im my case copies the file with read-only privileges (444) into the destination directory. So if the file is already there, the plugin fails to overwrite it. I checked the directory privileges where the file resides and they are ok (755). I checked the umask of the user used to execute the job and it is ok (0022). If I delete the file or change its privileges to 644 the plugin succeeds to copy the file. But it uses 444 again, so I have to do this after each job run. 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] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Thierry-Dimitri Roy commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I was able to further analyze the problem. I saw the emulator running on port 5763 with the deamon running on the port 5764. But when I ran the command: adb -P 5764 devices It didn't list any devices. Then I tried connecting directly to the emulator with the command: adb -P 5764 connect localhost:5763 It successfully connected! Then the 'devices' command showed the emulator. And running adb -P 5764 shell getprop init.svc.bootanim return the 'stopped' result. I have modified the jenkins plugin and I no longer see the timeout problem. I have created a pull request. Hope this help other people! 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods not being recorded for approval
Jesse Glick assigned JENKINS-26541 to Jesse Glick Rejected sandbox methods not being recorded for approval Change By: Jesse Glick (22/Jan/15 4:02 PM) Assignee: KohsukeKawaguchi JesseGlick 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename
Steve Haworth edited a comment on JENKINS-26519 Build records not migrated due to “failed to rename Tried the new war (jenkins_main_trunk #3941) it didn't work for me. I have the same set-up Windows running under a service with many legacy builds. What did work was adding timestamp1420730669680/timestamp To the build.xml file. This resolved all my issues for this build. This value was missing the only value present was startTime1420730669680/startTime Obviously doing this for all 1+ builds will require a script, but that seems to resolve it. 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] [copy-to-slave-plugin] (JENKINS-26353) Copy to slave fails and getting error message Pipe is already closed
Markus Heiden commented on JENKINS-26353 Copy to slave fails and getting error message Pipe is already closed I used a shell script build step as workaround, which sets the privileges to 644 after the file has been copied to the slave. So after doing this once manual, every worked again. 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] [modernstatus-plugin] (JENKINS-26554) Disabled Jobs Have No Modernized Icon (Still Gray Ball)
pixman20 created JENKINS-26554 Disabled Jobs Have No Modernized Icon (Still Gray Ball) Issue Type: Bug Assignee: Oliver Vinn Components: modernstatus-plugin Created: 22/Jan/15 4:15 PM Description: The gray ball is still displaying for disabled jobs when shown in a view. I was expecting to see a modernized icon for disabled jobs, such as a power off icon (the typical open circuit circle) or something similar. Not sure if this is technically a bug or an improvement depending on the intended design. However, from my POV this would be a bug since it is not consistent with the rest of the component's features. Environment: Windows Server 2012 Project: Jenkins Priority: Minor Reporter: pixman20 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename
Steve Haworth commented on JENKINS-26519 Build records not migrated due to “failed to rename Tried the new war it didn't work for me. I have the same set-up Windows running under a service with many legacy builds. What did work was adding timestamp1420730669680/timestamp To the build.xml file. This resolved all my issues for this build. This value was missing the only value present was startTime1420730669680/startTime Obviously doing this for all 1+ builds will require a script, but that seems to resolve it. 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] [workflow-plugin] (JENKINS-26552) @StepContextParameter EnvVars missing Computer.environment
Jesse Glick created JENKINS-26552 @StepContextParameter EnvVars missing Computer.environment Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 22/Jan/15 4:00 PM Description: StepContext.get(EnvVars) is advertised as an option and when run inside node you would expect it to include all environment variables associated with that Computer, but it does not: it only includes those added by Computer.buildEnvironment (node properties, JENKINS_URL), plus anything extra added by the node step (JENKINS_SERVER_COOKIE). This did not matter to sh steps because LocalLauncher.inherit started with the existing environment variables and just added in the overrides. It also did not matter for env.PATH calls from Groovy because EnvActionImpl was hardcoded as of 8eb96e8 (0.1-beta-7) to look up a Computer as a fallback value. I think the right fix is to make PlaceholderExecutable do the call to getEnvironment, then make EnvActionImpl look for EnvVars in the context—also giving those precedence over user settings, for consistency with DefaultStepContext. WorkflowTest.env is also too weak: it does not even test externally set environment variables, does not test per-slave variables (which would presumably require a mock SlaveComputer.getEnvironment override), and does not test EnvVars.override behavior (PATH+X syntax) from a block step. Project: Jenkins Labels: environment-variables Priority: Major Reporter: Jesse Glick 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] [workflow-plugin] (JENKINS-26552) @StepContextParameter EnvVars missing Computer.environment
Jesse Glick started work on JENKINS-26552 @StepContextParameter EnvVars missing Computer.environment Change By: Jesse Glick (22/Jan/15 4:00 PM) Status: Open InProgress 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] [build-failure-analyzer-plugin] (JENKINS-26553) duplicate slash in URL notified back to gerrit
Michael Keppler created JENKINS-26553 duplicate slash in URL notified back to gerrit Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 22/Jan/15 4:07 PM Description: In the message send from BFA back to gerrit there is a link to the respective jenkins build. This link has a duplicate slash after the jenkins url, e.g. it looks like: Please see the unit test results or the console log for more details. ( http://jenkinsurl//job/jobname/buildnumber/ ) However, this works fine in all browsers I know. Project: Jenkins Priority: Trivial Reporter: Michael Keppler 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-plugin] (JENKINS-26549) build.testResultAction was not set and it is always empty
Alex Earl commented on JENKINS-26549 build.testResultAction was not set and it is always empty Why did you file this against the email-ext plugin? It seems like there is nothing related to email-ext. 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename
Steve Haworth updated JENKINS-26519 Build records not migrated due to “failed to rename Change By: Steve Haworth (22/Jan/15 4:25 PM) Attachment: jenkins.err.log_on-startup.txt 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] [core] (JENKINS-26519) Build records not migrated due to “failed to rename
Steve Haworth edited a comment on JENKINS-26519 Build records not migrated due to “failed to rename Tried the new war (jenkins_main_trunk #3941) it didn't work for me. I have the same set-up Windows running under a service with many legacy builds. see err log file attached (jenkins.err.log_on-startup.txt) NOTE: What did work was adding timestamp1420730669680/timestamp To the build.xml file. This resolved all my issues for this build. This value was missing the only value present was startTime1420730669680/startTime Obviously doing this for all 1+ builds will require a script, but that seems to resolve it. 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] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Frédéric COIFFIER commented on JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy With the plugin 2.5, in our case, when setting SVN version to 1.8 (instead of 1.7) in the Jenkins settings, it solves the problem. 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] [core] (JENKINS-26503) Usability and accessibility issues
Andreas Mandel commented on JENKINS-26503 Usability and accessibility issues Daniel Beck Yes I work with Michael - I should have mentioned that. But I'm not one of the authors. 2/9: Can you check page 16 of Kurzbericht_Software-Ergonomie_Jenkins_1.580.1.pdf the red marks on the screen shot. 7 of 9 : I see your point. I try to get more details on this. The ticket should be sufficient. I appreciate that you pick this up, likely there are some quick wins that might be worth to be addressed. Putting this on the agenda of the project governance meeting sounds good. 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] [build-timeout-plugin] (JENKINS-26563) BlockableBuildTrigger invokes build timeout
Steven Christou updated JENKINS-26563 BlockableBuildTrigger invokes build timeout Change By: Steven Christou (22/Jan/15 10:04 PM) Description: Theparameterizedtriggerpluginhastheoptiontotriggerajobbeforecontinuingwiththeoption[BlockableBuildTriggerConfig|https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig.java#L29].Thiswillalsotriggerthebuild-timeoutpluginifthevalueisset.Thereshouldbeanoptiontoignorethetimeoutwhenablockablebuildtriggeriscurrentlybeinginvoked. IpostedtobothcomponentsbecauseIamnotsurewhereanRFEorimprovementlikethiswouldbelong(leaningmoretowardsthebuild-timeoutpluginthough). 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] [customtools-plugin] (JENKINS-19892) TOOL_HOME doesn't work in PATH
Oleg Nenashev commented on JENKINS-19892 TOOL_HOME doesnt work in PATH @Per Sorry for missing your comments due to the business trip. I'll revise the plugin and improve the validation/escaping The initial issue should be fixes as well. 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] [build-timeout-plugin] (JENKINS-26563) BlockableBuildTrigger invokes build timeout
Steven Christou assigned JENKINS-26563 to Unassigned BlockableBuildTrigger invokes build timeout Change By: Steven Christou (22/Jan/15 10:08 PM) Assignee: KohsukeKawaguchi 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] [build-timeout-plugin] (JENKINS-26563) BlockableBuildTrigger invokes build timeout
Steven Christou updated JENKINS-26563 BlockableBuildTrigger invokes build timeout Change By: Steven Christou (22/Jan/15 10:08 PM) Description: Theparameterizedtriggerpluginhastheoptiontotriggerajobbeforecontinuingwiththeoption[BlockableBuildTriggerConfig|https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig.java#L29].Thiswillalsotriggerthebuild-timeoutpluginifthevalueisset.Thereshouldbeanoptiontoignorethetimeoutwhenablockablebuildtriggeriscurrentlybeinginvoked. Stepstoreproduceissue:1.Createajob(calledjob1)withasleepfor5minutes.2.Createanotherjob(calledjob2)withasleepof2minutes.3.Addaparameterizedtriggerinjob2blockingupstreamprojectjob1.4.Haveatimeout(withanytimeoutstrategy)andtriggerarunofjob1. IpostedtobothcomponentsbecauseIamnotsurewhereanRFEorimprovementlikethiswouldbelong(leaningmoretowardsthebuild-timeoutpluginthough). 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods not being recorded for approval
Jesse Glick started work on JENKINS-26541 Rejected sandbox methods not being recorded for approval Change By: Jesse Glick (22/Jan/15 10:26 PM) Status: Open InProgress 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] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Dilip M commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Also see in Jenkins ver. 1.580.1 Project type: Maven 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] [build-timeout-plugin] (JENKINS-26563) BlockableBuildTrigger invokes build timeout
Steven Christou created JENKINS-26563 BlockableBuildTrigger invokes build timeout Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: build-timeout-plugin, parameterized-trigger-plugin Created: 22/Jan/15 10:03 PM Description: The parameterized trigger plugin has the option to trigger a job before continuing with the option Blockable Build Trigger Config. This will also trigger the build-timeout plugin if the value is set. There should be an option to ignore the timeout when a blockable build trigger is currently being invoked. Project: Jenkins Priority: Minor Reporter: Steven Christou 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] [delivery-pipeline-plugin] (JENKINS-25471) Changes in pipelineview is missing the latest commits
Patrik Boström commented on JENKINS-25471 Changes in pipelineview is missing the latest commits I don't think Jenkins picks up changes committed in a VCS from a job, so the view can't find the changes and display them unfortunately. 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] [core] (JENKINS-26564) Update to 1.597 shows 500 error on jobs
David Light created JENKINS-26564 Update to 1.597 shows 500 error on jobs Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jan/15 10:04 PM Description: After upgrading to 1.597 from 1.588 on Windows when a user clicks on a job they get: 500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed. If you create a new job it shows correctly until the first job runs and then it shows the 500 error. You can select the drop-down from the Job instead and go to Configure, etc. and it shows correctly. Last Success, Failure, Duration show N/A I cannot downgrade because trying to run the unmigrate script fails with: Exception in thread "main" java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest at hudson.Util.createSymlinkJava7(Util.java:1224) at hudson.Util.createSymlink(Util.java:1118) at jenkins.model.RunIdMigrator.unmigrateBuildsDir(RunIdMigrator.java:371 ) at jenkins.model.RunIdMigrator.unmigrateJobsDir(RunIdMigrator.java:320) at jenkins.model.RunIdMigrator.main(RunIdMigrator.java:307) Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 5 more Project: Jenkins Priority: Major Reporter: David Light 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] [delivery-pipeline-plugin] (JENKINS-25451) build after other projects
Patrik Boström commented on JENKINS-25451 build after other projects If job Y has an trigger on X it is by definition a downstream dependency and the delivery-pipeline view will show both jobs. 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] [nodejs-plugin] (JENKINS-21953) NodeJs plugin doesn't work on windows based Jenkins machine
pixman20 commented on JENKINS-21953 NodeJs plugin doesnt work on windows based Jenkins machine Nice, worked perfectly! Thanks Zlatan! 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] [delivery-pipeline-plugin] (JENKINS-26210) Configure Jobs to be hidden from the delivery pipeline
Patrik Boström commented on JENKINS-26210 Configure Jobs to be hidden from the delivery pipeline It is an interesting idea to have the possibility hide jobs. Im also curious to understand the problem you have with the Multijob being displayed in the wrong order. Can you give some more details? 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.
HOTLIST
Hi Greetings!!! Hope you are doing great. Please find the below hot list and let me know if you have any matching requirement for my consultants. Please send your requirements to *suni...@sreeinfotech.com suni...@sreeinfotech.com* *NAME* *SKILL* *EXPERIENCE* *VISA* *Prudhvi Nallamothu* *Oracle DBA* *8Yrs* *H1B* Please add my id suni...@sreeinfotech.com in your mailing list and send me your requirements on a daily basis. For further info, please contact me immediately!! Looking forward to work with you… *Thanks Regards,* *Sunitha * *Sree Infotech LLC* *9901 E. Valley Ranch Parkway, Suite 3008, Irving, TX 75063 Phone: 972-332-3471 Extn 114 Fax : 888-660-2844 **Email Id: * suni...@sreeinfotech.com || *ssreei...@gmail.com ssreei...@gmail.com* *Gtalk: archana.sreeinfo* *YM:archana.sreeinfo* *Note: We respect your Online Privacy. This mail cannot be considered Spam as long as we include contact information and a method to be removed from our mailing list. To be removed from our mailing list, please reply with REMOVE in the subject line and your email address in the body. Include Complete Address and/or Domain/Aliases to be removed.* -- 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] [publish-over-ftp-plugin] (JENKINS-26550) publish over ftp plugin ver. 1.11 transfer 0 files
Irene Shcherbakova created JENKINS-26550 publish over ftp plugin ver. 1.11 transfer 0 files Issue Type: Bug Assignee: bap Components: publish-over-ftp-plugin Created: 22/Jan/15 2:44 PM Description: I'm not sure that this is problim with plugin, escpecially because I've never used it before. But after build is finished i see that no files were transfered. The cofiguration of ftp server is probably right, at least when i test configuration, i get success. "ERROR: Exception when publishing, exception message Connection reset" - this is only ecxeption message in my build log. i've looked through ftp server log and found this: 084366)22.01.2015 15:16:56 - (not logged in) (92.39.135.230) 220-FileZilla Server version 0.9.41 beta (084366)22.01.2015 15:16:56 - (not logged in) (92.39.135.230) 220-written by Tim Kosse (tim.ko...@gmx.de) (084366)22.01.2015 15:16:56 - (not logged in) (92.39.135.230) 220 Please visit http://sourceforge.net/projects/filezilla/ (084366)22.01.2015 15:16:56 - (not logged in) (92.39.135.230) USER jenkins (084366)22.01.2015 15:16:56 - (not logged in) (92.39.135.230) 331 Password required for jenkins (084366)22.01.2015 15:16:56 - (not logged in) (92.39.135.230) PASS *** (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) 230 Logged on (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) CWD /Jenkins (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) 250 CWD successful. "/Jenkins" is current directory. (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) TYPE I (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) 200 Type set to I (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) CWD /Jenkins (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) 250 CWD successful. "/Jenkins" is current directory. (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) PASV (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) 227 Entering Passive Mode (192,168,88,10,201,215) (084366)22.01.2015 15:16:56 - jenkins (92.39.135.230) disconnected. It seems that jenkins connents to the server but doesn't even try to publish files. Can you please help me solving this problem? Thanks in advance. Environment: Jenkins ver. 1.565.3 Project: Jenkins Labels: publish-over-ftp Priority: Major Reporter: Irene Shcherbakova 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] [checkstyle-plugin] (JENKINS-19932) Publish FindBugs/Checkstyle from slave failed
Andreas Schopper commented on JENKINS-19932 Publish FindBugs/Checkstyle from slave failed Hi Ulli, is there any progress on this issue. We still have this problem and would appreciate a quick fix. Thanks in advance for your help. Regards, Andreas 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] [doclinks-plugin] (JENKINS-26551) DocLinks: Publish even if build failed
Wolfgang Schnerring created JENKINS-26551 DocLinks: Publish even if build failed Issue Type: Improvement Assignee: sogabe Components: doclinks-plugin Created: 22/Jan/15 3:38 PM Description: It would be nice if one could set a checkbox to force the post-build step to run even when the build failed. I often have the case that test and documentation are independent from each other, so there's no reason not to build the docs just because the tests failed. I can probably glue together a workaround with two jobs where the test job triggers the doc-builder job and some trickery with the "shared workspace plugin", but I'd rather not have to. Project: Jenkins Priority: Minor Reporter: Wolfgang Schnerring 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] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Daniel Beck commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Dilip M: That's probably JENKINS-26048. Maven project type works differently from freestyle. 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] [copyartifact-plugin] (JENKINS-24887) Workflow support of Copyartifact
SCM/JIRA link daemon commented on JENKINS-24887 Workflow support of Copyartifact Code changed in jenkins User: ikedam Path: .gitignore pom.xml src/main/java/hudson/plugins/copyartifact/Copier.java src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/main/java/hudson/plugins/copyartifact/CopyArtifactPermissionProperty.java src/main/java/hudson/plugins/copyartifact/FilePathCopyMethod.java src/main/java/hudson/plugins/copyartifact/FingerprintingCopyMethod.java src/main/resources/hudson/plugins/copyartifact/Messages.properties src/main/resources/hudson/plugins/copyartifact/Messages_de.properties src/main/resources/hudson/plugins/copyartifact/Messages_ja.properties src/test/java/hudson/plugins/copyartifact/CopierTest.java src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java src/test/java/hudson/plugins/copyartifact/CopyArtifactWorkflowTest.java src/test/java/hudson/plugins/copyartifact/DownstreamBuildSelectorTest.java src/test/java/hudson/plugins/copyartifact/TriggeredBuildSelectorTest.java src/test/java/hudson/plugins/copyartifact/testutils/CopyArtifactUtil.java http://jenkins-ci.org/commit/copyartifact-plugin/325f16adb3fc4f5d587b687bcb94b1726eeb033a Log: Merge pull request #55 from tfennelly/BuildStep-Job-v2 FIXED JENKINS-24887 CopyArtifact to implement workflow SimpleBuildStep Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/eda80351b205...325f16adb3fc 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] [copyartifact-plugin] (JENKINS-24887) Workflow support of Copyartifact
SCM/JIRA link daemon resolved JENKINS-24887 as Fixed Workflow support of Copyartifact Change By: SCM/JIRA link daemon (22/Jan/15 11:11 PM) Status: InProgress Resolved Resolution: Fixed 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
SCM/JIRA link daemon commented on JENKINS-26541 Rejected sandbox methods inside parallel not being recorded for approval Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowJobNonRestartingTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/SandboxContinuable.java http://jenkins-ci.org/commit/workflow-plugin/fb174fdabbb46f9f84ef84a83dcccaa85252713f Log: FIXED JENKINS-26541 Need to check for RejectedAccessException wrapped in ParallelStepException. 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
SCM/JIRA link daemon resolved JENKINS-26541 as Fixed Rejected sandbox methods inside parallel not being recorded for approval Change By: SCM/JIRA link daemon (22/Jan/15 11:19 PM) Status: InProgress Resolved Resolution: Fixed 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] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Jackey Cheung commented on JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy Yes, making this change seems to work. However, documentation is necessary for this change. 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.
FW: maleic anhydride
HI We are a leading maleic anhydridesupplier in China ,Now we’d like to offer you maleic anhydride as follows Specifications 1.MaleicAnhydride 2.Casno:108-31-6 3.whitebriquettes/flakes 4.Purity:99.5%min 5.25kgsperbag | Items | Specifications | | Appearance | white briquettes/flakes | | Purity | 99.5% min | | Colority(platinum -cobalt) | 10 max | | crystallization point | 52.4 min | | ash | 0.005% max | | Fe content | 1 ppm max | If you are interested in our products, please let me know and I will offer you most favorable price Thanks Best regards AMENDA ZHANG Shanghai Yancui Import And Export Co., Ltd. ADD:NO. 119,LANE 2729, HUNAN ROAD, PUDONG SHANGHAICHINA TEL: 0086- 21 -38722636-8016, 86-18018675766 FAX: 0086 21 58500043 -- 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
SCM/JIRA link daemon commented on JENKINS-26541 Rejected sandbox methods inside parallel not being recorded for approval Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/d31a8d7b9e6ba7af9dbe238be0e4c2162720b5e3 Log: JENKINS-26541 Noting. 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
Jesse Glick started work on JENKINS-26541 Rejected sandbox methods inside parallel not being recorded for approval Change By: Jesse Glick (22/Jan/15 11:20 PM) Status: Open InProgress 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
Jesse Glick updated JENKINS-26541 Rejected sandbox methods inside parallel not being recorded for approval Change By: Jesse Glick (22/Jan/15 11:20 PM) Status: Reopened Open 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
Jesse Glick reopened JENKINS-26541 Rejected sandbox methods inside parallel not being recorded for approval Change By: Jesse Glick (22/Jan/15 11:20 PM) Resolution: Fixed Status: Resolved Reopened 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] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
Jesse Glick updated JENKINS-26541 Rejected sandbox methods inside parallel not being recorded for approval It works normally, but not inside parallel. Change By: Jesse Glick (22/Jan/15 10:48 PM) Summary: Rejectedsandboxmethods insideparallel notbeingrecordedforapproval 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] [subversion-plugin] (JENKINS-26473) SVN cannot authenticate using Negotiate
Adam Mercer commented on JENKINS-26473 SVN cannot authenticate using Negotiate We're also seeing this error with Jenkins 1.580.2, Credentials plugin 1.20, and Subversion plugin 2.5 We can use the same credentials on the command and successfully access the repository. 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] [hockeyapp-plugin] (JENKINS-26200) Failed to scout net.hockeyapp.jenkins.releaseNotes.ChangelogReleaseNotes$DescriptorImpl
Simone Manganelli commented on JENKINS-26200 Failed to scout net.hockeyapp.jenkins.releaseNotes.ChangelogReleaseNotes$DescriptorImpl We're also seeing this issue with the HockeyApp plugin version 1.2.0. Jenkins 1.578, OS X 10.9.5. The "Upload to HockeyApp" menu item just does not appear. Manually installing version 1.1.0 of the plugin works properly. 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] [subversion-plugin] (JENKINS-26473) SVN cannot authenticate using Negotiate
Adam Mercer commented on JENKINS-26473 SVN cannot authenticate using Negotiate I noticed that version 1.21 of the credentials plugin was available, I updated to this and still see the same problem. 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] [workflow-plugin] (JENKINS-26510) NPE from UnsafeFieldAccessorImpl.ensureObj in SimpleXStreamFlowNodeStorage on J9
Tom Canova
commented on JENKINS-26510
NPE from UnsafeFieldAccessorImpl.ensureObj in SimpleXStreamFlowNodeStorage on J9
Upgrading to the current IBM JDK appears to have resolved the problem. I also refactored the code to reduce the chattiness between the master and slaves, though the refactored code also did not work until the JDK update. Here's the refactored code:
def recipeFileList
def CATEGORY_ID = ''
def branches = [:]
def cloudantSnippets = new com.ibm.devops.CloudantSnippets()
node('A') {
checkout scm: [ $class : 'GitSCM', branches: [[$class: 'hudson.plugins.git.BranchSpec', name: '*/develop']], userRemoteConfigs : [[ url: 'https://hub.jazz.net/git/user/project', credentialsId: '----aaa' ] ] ]
dir('resources') {
sh """
date
echo ' divide list of recipes into files each containing 200 '
rm -f cookbook-recipes*.txt
cat all-cookbook-recipes-*.txt cookbook-recipes.txt
awk 'NR%200==1{x=sprintf("cookbook-recipes-%04d.txt", ++i);}{print x}' cookbook-recipes.txt
ls cookbook-recipes-*.txt | sort sorted-recipe-list.txt
"""
recipeFileList = readFile('sorted-recipe-list.txt').tokenize()
}
sh """
rm -f workspace.b*
tar cjf workspace.bz2 config data logging.properties pom.xml resources src test descriptors
"""
CATEGORY_ID = cloudantSnippets.shareFile('workspace.bz2', VCAP_SERVICE_TYPE, VCAP_SERVICE_NAME, VCAP_SERVICE_USERNAME,VCAP_SERVICE_PASSWORD)
archive 'CLOUDANT_ID'
for (int i = 0; i recipeFileList.size(); i++) {
String recipeFileName = "${recipeFileList.get(i)}"
branches["${recipeFileName}"] = {
node('parsing') {
def mvnHome = tool 'Local maven-3.2.3'
sh 'rm -rf *'
cloudantSnippets.getSharedFile('workspace.bz2', CATEGORY_ID, VCAP_SERVICE_USERNAME,VCAP_SERVICE_PASSWORD)
sh """
tar xjf workspace.bz2
echo ' ${recipeFileName} : generate settings.xml file with encrypted passwords to be used for accessing artifactory '
wget -N --quiet http://artifactory:8081/artifactory/plugins-release-local/com/ibm/devops/GenerateSecureSettings/1.0/GenerateSecureSettings-1.0-all.jar
export PATH=${mvnHome}/bin:${env.PATH}
set +vx
export SOME_PASSWORD='$SOME_PASSWORD'
${tool 'local IBM Java 7'}/bin/java -jar GenerateSecureSettings-1.0-all.jar
unset SOME_PASSWORD
echo " Running RecipeListParseTest with $recipeFileName "
mkdir -p target
set -vx
${tool 'Local maven-3.2.3'}/bin/mvn -s settings.xml -DrunSuite='**/RecipeListParseTest.class' -DrecipeFile='${recipeFileName}' -DDB_SERVER=1.1.1.1 -Duima_datapath='resources' -DDB_LAZY=YES -DoutputDir='output/subset' -DJAVA_ARG_LINE='-Xmx5G -Xms1G -XX:MaxPermSize=256m -XX:HeapDumpPath=/dev/null' test -U | grep -v 'process.*start' | grep -v 'process.*end' | grep -v 'invoked.*returning' | tee target/${recipeFileName}.mvn.log | grep '=='
"""
sh """
echo "Upload JSON Output for ${recipeFileName}"
tar cjf target/classes/output/${recipeFileName}.json.bz2 target/classes/output/subset
tar cjf target/${recipeFileName}.mvn.log.bz2 target/${recipeFileName}.mvn.log
"""
cloudantSnippets.shareFile("target/classes/output/${recipeFileName}.json.bz2", VCAP_SERVICE_TYPE, VCAP_SERVICE_NAME, VCAP_SERVICE_USERNAME,VCAP_SERVICE_PASSWORD, CATEGORY_ID)
cloudantSnippets.shareFile("target/${recipeFileName}.mvn.log.bz2", VCAP_SERVICE_TYPE, VCAP_SERVICE_NAME, VCAP_SERVICE_USERNAME,VCAP_SERVICE_PASSWORD, CATEGORY_ID)
}
}
}
}
parallel branches
node('A') {
for (int i = 0; i recipeFileList.size(); i++) {
String recipeFileName = "${recipeFileList.get(i)}"
try {
cloudantSnippets.getSharedFile("target/classes/output/${recipeFileName}.json.bz2", CATEGORY_ID, VCAP_SERVICE_USERNAME, VCAP_SERVICE_PASSWORD)
cloudantSnippets.getSharedFile("target/${recipeFileName}.mvn.log.bz2", CATEGORY_ID, VCAP_SERVICE_USERNAME, VCAP_SERVICE_PASSWORD)
sh """
echo " Retrieve json for $recipeFileName "
tar xjf target/classes/output/${recipeFileName}.json.bz2
tar xjf target/${recipeFileName}.mvn.log.bz2
"""
} catch
[JIRA] [workflow-plugin] (JENKINS-26510) NPE from UnsafeFieldAccessorImpl.ensureObj in SimpleXStreamFlowNodeStorage on J9
Tom Canova resolved JENKINS-26510 as Not A Defect NPE from UnsafeFieldAccessorImpl.ensureObj in SimpleXStreamFlowNodeStorage on J9 This was a defect with the IBM JDK - likely with the JIT Compiler.Resolved by updating the JDK. Change By: Tom Canova (22/Jan/15 7:15 PM) Status: Reopened Resolved Resolution: NotADefect 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] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Daniel Beck commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden The fix is in 1.598. (Jenkins project has this weird release cycle where a fix takes 1-2 weeks to be released.) The basic issue occurs in every instance, with buttons partially overlapping, but if you have a plugin that increases footer height, the buttons disappear altogether behind it. 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] [checkstyle-plugin] (JENKINS-19932) Publish FindBugs/Checkstyle from slave failed
Ulli Hafner
commented on JENKINS-19932
Publish FindBugs/Checkstyle from slave failed
Actually no. I still can't reproduce so any change would be just like guessing.
Maybe you can download the sources and compile a version that wraps the Checkstyle Parser into
SaxSetup sax = new SaxSetup();
try {
// parse Checkstyle file
}
finally {
sax.cleanup();
}
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] [checkstyle-plugin] (JENKINS-19932) Publish FindBugs/Checkstyle from slave failed
Ulli Hafner
edited a comment on JENKINS-19932
Publish FindBugs/Checkstyle from slave failed
Actually no. I still can't reproduce so any change would be just like guessing.
Maybe you can download the sources and compile a version that wraps the Checkstyle Parser call (at hudson.plugins.checkstyle.parser.CheckStyleParser.parse(CheckStyleParser.java:67)) into:
SaxSetup sax = new SaxSetup();
try {
// parse Checkstyle file
}
finally {
sax.cleanup();
}
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] [core] (JENKINS-26406) description-setter plugin cannot set html anymore
Tom FENNELLY assigned JENKINS-26406 to Tom FENNELLY description-setter plugin cannot set html anymore Change By: Tom FENNELLY (22/Jan/15 7:46 PM) Assignee: TomFENNELLY 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] [core] (JENKINS-26406) description-setter plugin cannot set html anymore
Tom FENNELLY commented on JENKINS-26406 description-setter plugin cannot set html anymore Daniel, you're a star ! Thanks. 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] [remoting] (JENKINS-26559) EC2 slaves not connecting
Steve Donie commented on JENKINS-26559 EC2 slaves not connecting I manually SSH'd to the slave machine, changed to the root directory, and then listed the files there. There was no slave.jar listed. I then ran this command in the root dir: wget http://mybuildserver/jnlpJars/slave.jar which downloaded the jar as expected. Finally I went back to the build server web UI, selected the node in Build Executor status, and selected 'Launch slave agent' - success! ... java full version "1.7.0_51-b13" Copying slave.jar Launching slave agent: java -jar /slave.jar ===[JENKINS REMOTING CAPACITY]===Slave.jar version: 2.49 This is a Unix slave Evacuated stdout Slave successfully connected and online So it appears that the location the slave.jar is copied and the location that is used to launch it are not the same, and it appears to be launching it expecting it to be in the root. 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] [core] (JENKINS-26503) Usability and accessibility issues
Daniel Beck edited a comment on JENKINS-26503 Usability and accessibility issues Loose translation of the short summary report's usability problems (all are classified minor), with additional comments in italics: 1. Inconsistent navigation Bread crumbs don't show up where expected (e.g. viewing an account has no crumb besides 'Jenkins', or no 'Manage Jenkins' crumb anywhere linked from there). Links in the sidepanel sometimes have no relation to the current view. Example is unfortunately just a badly labeled 'My Views' link when viewing another account. Some views don't have a sidepanel. They mention 'Perform Maven Release' (Maven Release Plugin?) but it's in core as well, e.g. some Manage Jenkins items. Recommendations: Breadcrumbs: Show all navigation steps users took to reach the current page, including the current page itself, and don't show anything not navigated through. Sidepanel: Only show items related to the current page, and always allow navigating 'Up'. 2. Multiple links cannot be recognized as such Links are displayed as normal text, so not recognized as such. Meh. That's why the menu has text color. But the basic point is a good one. Not mentioned, but that both the ball and the progress bar of a build in the executors list are clickable and go to the console is pretty obscure (also, one is JS and the other isn't, so only one can be opened in a new tab.) It is recommended is to make links easily recognizable as such. Inconsistent underlining of some links. No examples, unfortunately. I'd guess the not underlined ones are model-links or in special UI sections like side panels or bread crumb. Recommendation is to make it consistent. 3. All tables (build history widget in the example) should have a 'Legend' link with explanation for the symbols used. Maybe we could move the legend link to the footer? 4. Viewing files and raw console output (basically everything not using the regular basic layout) should not open in the same window. 5. Mandatory text fields are not recognizable as such except by their validation error. Recommendation is to add an icon or other marking (such as an asterisk?) to mandatory form fields, and possibly some color highlighting. 6. Translation is incomplete It's kind of ironic that the screenshot includes the 'help us' link from the Translation Assistance plugin. The specific issues highlighted are not in core, but an action and column from installed non-default plugins. Still, I've seen hardcoded strings in plugins that won't be translatable easily, and that must go. 7. Two buttons have the same functionality I don't see the point of this, as with all other forms (consistency!) 'Save' leaves the form while 'Apply' does not. Users should be used to it from Windows. 8. View tabs that show global views (in My Views) are not recognizable as such before clicking them. A horrible feature all around IMO 9. The inline description editor has no 'cancel' button. This issue was much more vaguely described, but it boils down to the inline editor not having a cancel button 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] [core] (JENKINS-26503) Usability and accessibility issues
Daniel Beck edited a comment on JENKINS-26503 Usability and accessibility issues Loose translation of the short summary report's usability problems (all are classified minor), with additional comments in italics: 1. Inconsistent navigation Bread crumbs don't show up where expected (e.g. viewing an account has no crumb besides 'Jenkins', or no 'Manage Jenkins' crumb anywhere linked from there). Links in the sidepanel sometimes have no relation to the current view. Example is unfortunately just a badly labeled 'My Views' link when viewing another account. Some views don't have a sidepanel. They mention 'Perform Maven Release' (Maven Release Plugin?) but it's in core as well, e.g. some Manage Jenkins items. Recommendations: Breadcrumbs: Show all navigation steps users took to reach the current page, including the current page itself, and don't show anything not navigated through. Sidepanel: Only show items related to the current page, and always allow navigating 'Up'. 2. Multiple links cannot be recognized as such Links are displayed as normal text, so not recognized as such. Meh. That's why the menu has text color. But the basic point is a good one. Not mentioned, but that both the ball and the progress bar of a build in the executors list are clickable and go to the console is pretty obscure (also, one is JS and the other isn't, so only one can be opened in a new tab.) It is recommended is to make links easily recognizable as such. Inconsistent underlining of some links. No examples, unfortunately. I'd guess the not underlined ones are model-links or in special UI sections like side panels or bread crumb. Recommendation is to make it consistent. 3. All tables (build history widget in the example) should have a 'Legend' link with explanation for the symbols used. Maybe we could move the legend link to the footer? 4. Viewing files and raw console output (basically everything not using the regular basic layout) should not open in the same window. 5. Mandatory text fields are not recognizable as such except by their validation error. Recommendation is to add an icon or other marking (such as an asterisk?) to mandatory form fields, and possibly some color highlighting. 6. Translation is incomplete It's kind of ironic that the screenshot includes the 'help us' link from the Translation Assistance plugin. The specific issues highlighted are not in core, but an action and column from installed non-default plugins. Still, I've seen hardcoded strings in plugins that won't be translatable easily, and that must go. 7. Two buttons have the same functionality I don't see the point of this, as with all other forms (consistency!) 'Save' leaves the form while 'Apply' does not. Users should be used to it from Windows. 8. View tabs that show global views (in My Views) are not recognizable as such before clicking them. A horrible feature all around IMO 9. The inline description editor has no 'cancel' button. This issue was much more vaguely described, but it boils down to the inline editor not having a cancel button 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.
