[JIRA] (JENKINS-17225) Parantheses in a regex make regex never match
Fabian Pachner
created JENKINS-17225
Parantheses in a regex make regex never match
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
tasks-plugin
Created:
15/Mar/13 12:00 PM
Description:
I tried to use parantheses '(', ')' when searching for open tasks with the Task Scanner Plugin (v4.35). I need the parantheses to group my regex and to apply * operator. For example, I want to search for "TODO(A-Za-z0-9)*. This delivers zero reults, also I have TODOs matching this regex. My actual regex is more complicated, so I definitely need parantheses to group it, this is just a simple example.
If I escape the parantheses, I get hundreds of thousands of results. So this can't be the correct approach. How can I get grouping and using * in my regex to work?
Project:
Jenkins
Priority:
Major
Reporter:
Fabian Pachner
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] (JENKINS-10345) Show ERROR/WARNING trend graph on project page
Fabian Pachner commented on JENKINS-10345 Show ERROR/WARNING trend graph on project page Hi, This feature sounds really interesting for me, too. We are having several custom jobs such as Regex checks and we would like to have a trend graph to display the process of the error or warning count. Has there been any progress on this issue? Are there other possibilities to create such a graph? Thanks a lot! Regards, Fabian 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
[JIRA] (JENKINS-14018) NullPointerException using Cpplint parser in warnings plugin on console log.
Fabian Pachner commented on JENKINS-14018 NullPointerException using Cpplint parser in warnings plugin on console log. The priority mapping isn't important for me. Perhaps anyone else can verify this. Thanks for fixing this in a very fast and uncomplicated way! In which update will this be released? 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
[JIRA] (JENKINS-14018) NullPointerException using Cpplint parser in warnings plugin on console log.
Fabian Pachner updated JENKINS-14018 NullPointerException using Cpplint parser in warnings plugin on console log. There are no relative paths. Attached the file from console output. As you can see I am parsing the console output for MSBuild warnings AND cpplint warnings together. Perhaps this helps. Thank you! Change By: Fabian Pachner (18/Jun/12 8:14 AM) Attachment: cpplint.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
[JIRA] (JENKINS-14018) NullPointerException using Cpplint parser in warnings plugin on console log.
Fabian Pachner created JENKINS-14018: Summary: NullPointerException using Cpplint parser in warnings plugin on console log. Key: JENKINS-14018 URL: https://issues.jenkins-ci.org/browse/JENKINS-14018 Project: Jenkins Issue Type: Bug Components: violations, warnings Affects Versions: current Reporter: Fabian Pachner Assignee: peterkittreilly Priority: Critical I want to use the warnings plugin to display results of cpplint from the console. I am getting the following exception: ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.violations.util.AbsoluteFileFinder.addSourcePaths(AbsoluteFileFinder.java:20) at hudson.plugins.violations.types.cpplint.CppLintParser.parse(CppLintParser.java:44) at hudson.plugins.warnings.parser.ViolationsAdapter.parse(ViolationsAdapter.java:60) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:317) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:296) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:293) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:257) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) at hudson.model.Run.run(Run.java:1433) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) I am using warnings plugin 4.5 and violations plugin 0.7.10. If you need any further information, please ask. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
