[JIRA] (JENKINS-55853) Customized Post Build Comment ignored for multi-configuration projects
Title: Message Title Pavel Roskin commented on JENKINS-55853 Re: Customized Post Build Comment ignored for multi-configuration projects As I suspected, there is some data that is created in the child builds but consumed in the top level build. Specifically, StashPostBuildComment.perform() is run in child executors and creates StashPostBuildCommentAction objects. Then StashBuilds.onCompleted() is run in the top level project and tries to get comments from StashPostBuildCommentAction. It gets null, quite expectedly. 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-56176) GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Title: Message Title Mark Waite commented on JENKINS-56176 Re: GIT_REVISION macro replaced with GIT_COMMIT but without support for length Thanks. Those details were sufficient that I can see the regression in my environment. Git plugin 3.9 changes the build name as you described and git plugin 4.0.0-rc leaves it an empty string. That is especially surprising for me, since that is not an area of the plugin that I believed had changed. I'll investigate further and seek a fix before the release of git plugin 4.0.0. 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-55840) Doxygen parser not fully compatible with warnings-ng-plugin
Title: Message Title Ulli Hafner commented on JENKINS-55840 Re: Doxygen parser not fully compatible with warnings-ng-plugin I'm not sure if I correctly understand the problem. But I replaced the doxygen parser now with the Gcc parser and all paths should be picked up right, see [commit #fcc606|https://github.com/jenkinsci/analysis-model/commit/fcc6067b2c69f279afb1296218a7ccecf32f37b2.] At least the test parses the two examples in your description quite well. 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-7178) Regular expression of Doxygen parser is too complex for JDK pattern
Title: Message Title Ulli Hafner updated JENKINS-7178 Jenkins / JENKINS-7178 Regular _expression_ of Doxygen parser is too complex for JDK pattern Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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-27973) Doxygen parses the last "warning"-line twice.
Title: Message Title Ulli Hafner updated JENKINS-27973 Jenkins / JENKINS-27973 Doxygen parses the last "warning"-line twice. Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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-56193) Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56193 Warnings-ng plugin cannot parse messages from MSBuild with relative paths Change By: Ulli Hafner Component/s: analysis-model Component/s: warnings-ng-plugin 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-56020) Resolving filenames doesn't work with cmake/ninja generator
Title: Message Title Ulli Hafner updated JENKINS-56020 Jenkins / JENKINS-56020 Resolving filenames doesn't work with cmake/ninja generator Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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-56020) Resolving filenames doesn't work with cmake/ninja generator
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56020 Resolving filenames doesn't work with cmake/ninja generator Change By: Ulli Hafner Component/s: analysis-model Component/s: warnings-ng-plugin 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-56193) Warnings-ng plugin cannot parse messages from MSBuild with relative paths
Title: Message Title Ulli Hafner updated JENKINS-56193 Jenkins / JENKINS-56193 Warnings-ng plugin cannot parse messages from MSBuild with relative paths Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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-55733) Wrong parsing of CppCheck results
Title: Message Title Ulli Hafner commented on JENKINS-55733 Re: Wrong parsing of CppCheck results After reading the manual of cppcheck it is clear that the current implementation is wrong. I added a test case to reproduce the bug. What I also noted after reading the manual: the API of analysis-model is currently not capable of storing all the available information about a cppcheck warning. Currently a warning can have multiple locations in the same file. But in cppcheck we also can have multiple locations in different files. (See example in comment above). So we basically need two things: make the parser return multiple locations per warning change the API to allow different files for the locations 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-55733) Wrong parsing of CppCheck results
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-55733
Wrong parsing of CppCheck results
Change By:
Ulli Hafner
Comment:
[~marne] Can you please check some of your xml reports if there are multiple tags with the same id. I.e. {code}{code}
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-56256) Merge same instance of section into itself
Title: Message Title Vitali Lovich updated an issue Jenkins / JENKINS-56256 Merge same instance of section into itself Change By: Vitali Lovich Summary: Merge one-line sections same instance of section into itself 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-56256) Merge one-line sections
Title: Message Title Vitali Lovich created an issue Jenkins / JENKINS-56256 Merge one-line sections Issue Type: Bug Assignee: Unassigned Components: collapsing-console-sections-plugin Created: 2019-02-23 20:03 Environment: Collapsing plugin version 1.7.0 Jenkins 2.107.3 Linux server Priority: Minor Reporter: Vitali Lovich I can't seem to figure out a way to collapse repeated GCC lines from a makefile. The use-case is that I want to collapse all the command-line output from make until a build failure into 1 section. The best I've found is to have something like: Section name: GCC compilation Section starts with: "^.gcc ." Section ends with: ".*" Collapse only one level per ending string: True However this still ends up creating a huge amount of sections & randomly nests them within each other. It would be nice to have an option that merges all instances of this section (i.e. disallow nesting of the section within itself & merge all siblings). So that instead of 1. Running make 1.1 Gcc compilation 1.2 Gcc compilation 1.3 Gcc compilation 1.4 Gcc compilation 1.5 Gcc compilation 1.6 Gcc compilation 2. Running make 2.1 Gcc compilation 2.2 Gcc compilation 2.3 Gcc compilation 2.4 Gcc compilation 2.5 Gcc compilation 2.6 Gcc compilation It should look like: 1. Running make 1.1 Gcc compilation 2. Running make 2.1 Gcc compilation
[JIRA] (JENKINS-55733) Wrong parsing of CppCheck results
Title: Message Title Ulli Hafner commented on JENKINS-55733 Re: Wrong parsing of CppCheck results Marne Can you please check some of your xml reports if there are multiple tags with the same id. I.e. "shadowVar" severity="style" msg="message 1" cwe="398"> "bar.cpp" line="171" info="Shadow variable"/> "bar.cpp" line="90" info="Shadowed declaration"/> "shadowVar" severity="style" msg="message 1" cwe="398"> "foo.cpp" line="171" info="Shadow variable"/> "foo.cpp" line="90" info="Shadowed declaration"/> 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-55735) Trend line chart by type, category or origin (y-axis)
Title: Message Title Ulli Hafner updated JENKINS-55735 Added a new trend chart that shows the warnings by type. Showing a trend chart by type and category is not that simple as it requires that the required information is persisted in the actions. Currently this data is only available in the whole report. This will degenerate the performance of Jenkins since in this case all reports of all builds need to be loaded into memory. I think it makes sense to create a follow-up feature request for these types of trend charts. Jenkins / JENKINS-55735 Trend line chart by type, category or origin (y-axis) Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed 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..
[JIRA] (JENKINS-54778) add usage of new Error severity in Trend graphics
Title: Message Title Ulli Hafner updated JENKINS-54778 Jenkins / JENKINS-54778 add usage of new Error severity in Trend graphics Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed 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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Sverre Moe commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free An installer for JDK from AdoptOpenJDK would be a welcoming addition. The Oracle OpenJDK 11 LTS builds will only receive updates for 6 months, while AdoptOpenJDK will commit to providing builds until LTS EOL. OpenJDK provides a new feature release every six months, and a maintenance/security update based upon each active release every three months. We will follow this schedule for publishing binary releases from AdoptOpenJDK to ensure you get the latest, most secure builds. In addition, every three years one feature release will be designated as the Long Term Supported (LTS) release. We will produce LTS releases for at least four years. This assurance will allow you to stay on a well-defined code stream, and give you time to migrate to the next, new, stable, LTS release when it becomes available. Though we still need the Oracle JDK Installer, for those who still use an older JDK. We have some legacy application using JDK 1.6 and JDK 1.7. I like Baptiste Mathus suggestion of Using a repository manager like Nexus to get the JDK. Then you could get the JDK from your preferred source. 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-56255) occasionally builds the branch for a PR also
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-56255 occasionally builds the branch for a PR also Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-02-23 17:03 Environment: Jenkins ver. 2.150.3 GitHub Branch Source Plugin 2.4.2 Priority: Major Reporter: Brian J Murrell I have a GitHub Organisation configured and it is operating fairly satisfactorily. It finds PRs when they are opened and builds them, and so on, quite successfully. But every now and then it will build not only the PR but also the branch that the PR is on, adding a continuous-integration/jenkins/branch commit status to the PR. This is wasteful in the least a can be confusing to the PR submitters about why they have this strange new commit status occasionally. I suppose this could happen legitimately if there is latency between pushing to a new branch on GitHub and opening the PR for it. Is there any delay on building new branches to account for this sort of behaviour? If not, perhaps there should be?
[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code
Title: Message Title Andrew Allen commented on JENKINS-38276 Re: Increase size of text area for pipeline script code Made some enhancements to Victor Toulouse's solution/hack (thanks!) that allows resizing by restyling a parent container with resize:both and calling aceEditor.resize() at the proper times. Like his solution, you'll need Tampermonkey installed to run this UserScript, and since it uses ResizeObserver, it only works with modern Chrome versions. https://gist.github.com/a2intl/293a76ae3323ec21d7cdceb6f7cd63af 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-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title awk space commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Having the same issue here on Jenkins 2.165 - even with simple 'sh "sleep 60"' test jobs. Attempting to work around the issue by checking "Do not allow the pipeline to resume after master restarts" and changing the pipeline to PERFORMANCE_OPTIMIZED makes the pipeline attempt to resume after restart (??) and makes me run into JENKINS-50407 instead. 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-15063) support for multiple security realms with failover
Title: Message Title Daniel Beck commented on JENKINS-15063 Re: support for multiple security realms with failover I love open source and am a big Jenkins fan. But this is the type of thing that is hard to defend when talking to business/operations about the benefits of open source. I think this is a nice example of the benefits of open source (at least in open communities like Jenkins'): You don't need to fight through multiple tiers of support (usually after buying a license) until your request reaches a product manager who may or may not consider it important enough to actually do, and even if you're lucky, you still need to wait for work to be prioritized. You can just do it yourself, or, if lacking the necessary skills, pay someone to do this specific thing. I'd be happy to review (and eventually merge) a well thought out implementation of this. I'm sure I can also get a few other maintainers to assist with reviews and provide feedback. If this needs extensive rework in core, I recommend starting with a JEP to make sure the design is sound. 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-15063) support for multiple security realms with failover
Title: Message Title Timothy Harris edited a comment on JENKINS-15063 Re: support for multiple security realms with failover You know, from what I can see this use case has been open for around ten years. See: https://issues.jenkins-ci.org/browse/JENKINS-3404.It seems to have been partially implemented by the Active directory plugin by providing a fallback user if ldap connection is broken. Nothing has happened on ldap plugin about this issue.I love open source and am a big Jenkins fan. But this is the type of thing that is hard to defend when talking to business/operations about the benefits of open source. It is *not* like this is some type of crazy wish. All Atlassian applications, like this Jira I am making this comment on, has support for multiple user directories. A built in internal user directory and support for adding others. 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-15063) support for multiple security realms with failover
Title: Message Title Timothy Harris commented on JENKINS-15063 Re: support for multiple security realms with failover You know, from what I can see this use case has been open for around ten years. See: https://issues.jenkins-ci.org/browse/JENKINS-3404. It seems to have been partially implemented by the Active directory plugin by providing a fallback user if ldap connection is broken. Nothing has happened on ldap plugin about this issue. I love open source and am a big Jenkins fan. But this is the type of thing that is hard to defend when talking to business/operations about the benefits of open source. It is not like this is some type of crazy wish. All Atlassian applications, like this Jira I am making this comment on, has support for multiple user directories. A built in internal user directory and support for adding others. 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-55088) Jenkins Home config.xml reset upon restart
Title: Message Title Oleg Nenashev commented on JENKINS-55088 Re: Jenkins Home config.xml reset upon restart config.xml is managed by Atomic change logic in Jenkins, and in some cases obsolete configs may stay in *.bak files and get applied improperly. It may worth investigation. Michael Schneider could you please check whether there are temporary *.bak files on the disk and which data they contain? 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.
