[JIRA] (JENKINS-58300) Changelog not updated before new Jenkins releases
Title: Message Title Michael Keppler created an issue Jenkins / JENKINS-58300 Changelog not updated before new Jenkins releases Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-07-02 13:15 Priority: Minor Reporter: Michael Keppler My local Jenkins alerts me regularly about new Jenkins releases and links to the Jenkins changelog at https://jenkins.io/changelog/. That changelog often does not contain the changes of the version announced (yet). Therefore I cannot take an informed decision about whether I need to upgrade or not. Example: The alert says 2.183 is available right now while I write this. The changelog only contains 2.182 and earlier. By tomorrow the changelog might be updated, so I will also defer my local upgrade at least until tomorrow. Add Comment
[JIRA] (JENKINS-55564) issue count selector not respected after page reload
Title: Message Title Michael Keppler created an issue Jenkins / JENKINS-55564 issue count selector not respected after page reload Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-14 08:08 Priority: Minor Reporter: Michael Keppler Look at a report with more than 10 issues. Switch the issues count from 10 to 25 (now more than 10 issues are displayed). Click one of the links to navigate to another page and then go back OR just refresh the issue listing. Bad result: The issue count says 25, but only 10 issues are shown in the list. Add Comment
[JIRA] (JENKINS-55442) Need filter by message text
Title: Message Title Michael Keppler commented on JENKINS-55442 Re: Need filter by message text I can try that. I guess both the parser library and warnings plugin need to be modified, according to what I saw when I looked at the existing filters. Give me some days. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55442) Need filter by message text
Title: Message Title Michael Keppler created an issue Jenkins / JENKINS-55442 Need filter by message text Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-08 07:36 Priority: Minor Reporter: Michael Keppler The plugin sometimes detects false positives, even in Maven console output, if it starts with "[WARNING]". Since the console output does not have a type, file name or similar (and the line number changes all the time), this false positive could only be filtered if there were a new filter that works directly on the message itself. Add Comment
[JIRA] [build-failure-analyzer-plugin] (JENKINS-31265) Report failure on absence of pattern
Title: Message Title Michael Keppler created an issue Jenkins / JENKINS-31265 Report failure on absence of pattern Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 29/Oct/15 4:00 PM Priority: Major Reporter: Michael Keppler For us, Maven is simply crashing during tests from time to time. I cannot detect this with BFA, as I would need to check for the absence of the "maven finished" message. So it would be nice to have a third kind of pattern, that is basically used in negated fashion of the standard pattern, only with no match of this pattern in the log an error is reported. Add Comment
[JIRA] [nodelabelparameter-plugin] (JENKINS-30036) node label parameters sorted case sensitive
Title: Message Title Michael Keppler created an issue Jenkins / JENKINS-30036 node label parameters sorted case sensitive Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 19/Aug/15 2:09 PM Priority: Trivial Reporter: Michael Keppler The nodes in a node selection dropdown are sorted, but case sensitive. Therefore it can become hard to easily find nodes in a mixed case naming scenario (with multiple people administrating slaves). Example of how the sorting currently looks like, where the Z...f order is unwanted. Alternative_node My_node Zulu_node fast_node superfast_node Add Comment
[JIRA] [core] (JENKINS-26658) NPE when launching JNLP slave with blank in name in recent JRE
Michael Keppler commented on JENKINS-26658 NPE when launching JNLP slave with blank in name in recent JRE When collecting your requested data, I found there is a totally different root cause. We have that command in a batch file, and Windows interprets the %2 from the escaped blank as batch parameter, replacing it with an empty string. Escaping with another percent sign in the batch file (i.e. blank%%20name) fixes everything. So basically there is no bug in Jenkins. However, everyone just copying the command line of a slave with a blank in the name will easily run into the same trouble. Maybe a note could be added to the slave page? I'm fine if you just close the bug. 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-26658) NPE when launching JNLP slave with blank in name in recent JRE
Michael Keppler
created JENKINS-26658
NPE when launching JNLP slave with blank in name in recent JRE
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
28/Jan/15 9:29 AM
Description:
Reproduction:
1. Have a slave with a blank in the name ("ASCET classic" in our case).
2. Try starting it by launching the JNLP file on a recent Oracle JRE (JRE 7.u75 in my case)
-> NPE during launch, slave not coming up.
Running the same JNLP from the command line shows some additional error messages that leads to the root cause: It tries to access jenkinsUrl/computer/ASCET0Classic instead of jenkinsUrl/computer/ASCET%20Classic (i.e. the blank is encoded wrongly).
Side notes:
1. Replacing the blank in the slave name solves the launch problems.
2. The same slave name worked fine with earlier versions of the Oracle JRE7.
Project:
Jenkins
Priority:
Major
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] [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] [core] (JENKINS-25910) Nodes are not sorted on label overview page
Michael Keppler created JENKINS-25910 Nodes are not sorted on label overview page Issue Type: Improvement Assignee: Unassigned Attachments: label_nodes_unsorted.png Components: core Created: 04/Dec/14 11:31 AM Description: We have nodes named like NODE-1, NODE-2, NODE-3, ... which are all assigned to the same label. When looking at the label via jenkinsurl/label// then the nodes are shown at the top in a non sorted order, e.g. NODE-8, NODE-3, NODE-6, ... Please sort the nodes on the label page alphabetically, as it is really hard to find if a node is missing from the list. Project: Jenkins Priority: Minor 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] [build-failure-analyzer-plugin] (JENKINS-25467) Capture group replacement not working
Michael Keppler
created JENKINS-25467
Capture group replacement not working
Issue Type:
Bug
Assignee:
Tomas Westling
Components:
build-failure-analyzer-plugin
Created:
06/Nov/14 9:43 AM
Description:
The replacement of capture groups in descriptions is not working for me. I've tried this multiple times now.
Example issue description:
Maven build failed in project ${1,1}.
Example indication (single line):
.Failed to execute goal.*on project (.):
The regular _expression_ matches, the failure cause is reported, but the ${1,1} is still contained verbatim in the description of the found issue.
Am I doing it wrong? If so, the documentation of this feature might need an update.
Project:
Jenkins
Priority:
Major
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] [build-failure-analyzer-plugin] (JENKINS-25394) Sort failure causes on management page
Michael Keppler created JENKINS-25394 Sort failure causes on management page Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 31/Oct/14 2:18 PM Description: Looking at a rather large page for managing build failure causes, I always have to scan the complete page, when editing some existing cause, as they seem to be in random order. Any chance for sorting the page by cause name, alphabetical? Or even use a sortable table (with the name being sorted by default), if other people want to sort by category and other columns. Project: Jenkins Priority: Minor 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] [next-executions] (JENKINS-23919) show also for "poll SCM" triggers
Michael Keppler commented on JENKINS-23919 show also for "poll SCM" triggers Sorry for the late answer. Yes, this should be sufficient for my use case. Thanks a lot. 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] [next-executions] (JENKINS-23919) show also for "poll SCM" triggers
Michael Keppler created JENKINS-23919 show also for "poll SCM" triggers Issue Type: Improvement Assignee: Unassigned Components: next-executions Created: 22/Jul/14 9:00 AM Description: The list of next executions contains all projects that are configured using the "build periodically" trigger. In contrast to that, projects using the "Poll SCM" trigger are not displayed, although they are using the same mechanism to schedule builds, they just may skip such a scheduled build if there are no changes. That's why to me it seems reasonable to also list projects using "Poll SCM". Project: Jenkins Priority: Major 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] [core] (JENKINS-22566) XML API does not escape/filter invalid characters
Michael Keppler created JENKINS-22566 XML API does not escape/filter invalid characters Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/Apr/14 10:42 AM Description: In some of our jobs, the build result page gets some text appended using a Groovy postbuild step. The appended text can contain arbitrary characters, even an escape character (character code 27). Everything works fine. On accessing such a build via XML api, there is an exception because the XML output contains invalid characters: error on line 1 at column 9913: PCDATA invalid Char value 27 I'm aware that I can avoid this issue by filtering the appended text in the groovy step, but generally the XML API should filter or escape such invalid characters from the output. Project: Jenkins Priority: Minor 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] [core] (JENKINS-21621) bad path environment set by Jenkins
Michael Keppler created JENKINS-21621 bad path environment set by Jenkins Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 03/Feb/14 10:44 AM Description: Reproduction: Create a freestyle job. As only build step, have a Windows batch containing "set". Run and inspect the console output, look for the PATH environment variable. Result: Jenkins wrongly uses quotes when adding the current JRE path, e.g. in my case the PATH is shown like this Path=C:\Program Files\Java\jre6\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Git\cmd;"C:\Program Files\Java\jre6\bin" Every command which tries to modify the path during a Jenkins job will fail because of those wrong quotes, e.g. you can no longer run batch commands like setx PATH "%PATH%;c:\some\new\path" /m because the quotes are incorrectly nested. Running "set" outside Jenkins produces the same path without the quoted JRE path. Jenkins version 1.527 Environment: Windows Project: Jenkins Priority: Major 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/groups/opt_out.
[JIRA] [next-executions] (JENKINS-21267) show time _span_ until next execution
Michael Keppler created JENKINS-21267 show time _span_ until next execution Issue Type: New Feature Assignee: Unassigned Components: next-executions Created: 08/Jan/14 9:35 AM Description: I use the next executions to estimate whether I need to run a manually triggered build after infrastructure changes for a job, which is triggered all 4 hours anyway (to avoid it running on multiple nodes nearly at the same time). (I know there are all kinds of plugins and settings to avoid concurrent builds, but we cannot use them for this job, as it actually makes sense to have concurrent builds, if people really changed things in between). Currently I have to compare the next execution time against the reported page creation time to see how far away the next job is (which gets even more complicated due to the server being in a timezone 4.5 hours away). I therefore suggest to enhance the output to something like (in ) e.g. regular maintenance 18:05:00(in 01:20:34) Feel free to leave seconds away, or to only create such output for jobs in the next n hours. Or make it just a tooltip on the absolute time, if you feel that the space might not be sufficient. Project: Jenkins Priority: Minor 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/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-18256) Sort node names
Michael Keppler created JENKINS-18256 Sort node names Issue Type: Improvement Assignee: domi Components: nodelabelparameter Created: 07/Jun/13 11:08 AM Description: In the node parameter selection the available nodes have some (arbitrary looking) order. Please sort them alphabetically instead. Project: Jenkins Priority: Minor 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/groups/opt_out.
[JIRA] [github] (JENKINS-18165) NPE in github status notification, if build not triggered by github push trigger
Michael Keppler created JENKINS-18165 NPE in github status notification, if build not triggered by github push trigger Issue Type: Bug Assignee: Unassigned Components: github Created: 01/Jun/13 7:57 AM Description: I tried to use the github status notification post build action on a job that is triggered by a manually configured remote URL (and not by a standard github push trigger). The GitHubCommitNotifier class does not expect this and crashes when querying the push trigger. java.lang.NullPointerException at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:52) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Project: Jenkins Labels: plugin exception git Priority: Major 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/groups/opt_out.
