[JIRA] (JENKINS-58538) Support for relative paths in folder view
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-58538 Support for relative paths in folder view Change By: Andrew Barnish In the legacy version of the warnings plugin the directories were displayed with path relative to the SCM workspace root when the "folders" tab was selected. This made a lot more sense than the current warnings-ng behavior which displays the full absolute path to the folder directory .Please change the back to the old behavior or add a new option to enable to old behavior.!https://wiki.jenkins.io/download/attachments/25591835/image2019-2-12_11-51-24.png?version=1=1549968686000=v2! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200687.1563409751000.14941.1563409860144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58538) Support for relative paths in folder view
Title: Message Title Andrew Barnish created an issue Jenkins / JENKINS-58538 Support for relative paths in folder view Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-07-18 00:29 Priority: Minor Reporter: Andrew Barnish In the legacy version of the warnings plugin the directories were displayed with path relative to the SCM workspace root when the "folders" tab was selected. This made a lot more sense than the current warnings-ng behavior which displays the full absolute path to the folder. Please change the back to the old behavior or add a new option to enable to old behavior. Add Comment
[JIRA] (JENKINS-58048) P4 error - No open file stream in ClientSystemFileCommands.writeFile()
Title: Message Title Andrew Barnish commented on JENKINS-58048 Re: P4 error - No open file stream in ClientSystemFileCommands.writeFile() The issue we were seeing on Linux is resolved in p4-plugin 1.10.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200069.1560779623000.8073.1562860800481%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58048) P4 error - No open file stream in ClientSystemFileCommands.writeFile()
Title: Message Title Andrew Barnish edited a comment on JENKINS-58048 Re: P4 error - No open file stream in ClientSystemFileCommands.writeFile() I'm seeing the following error in linux since plugin version 1.10. 1 0 . Is it the same issue? ERROR: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: No open file stream in ClientSystemFileCommands.writeFile() Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200069.1560779623000.5641.1562686560328%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58048) P4 error - No open file stream in ClientSystemFileCommands.writeFile()
Title: Message Title Andrew Barnish commented on JENKINS-58048 Re: P4 error - No open file stream in ClientSystemFileCommands.writeFile() I'm seeing the following error in linux since plugin version 1.10.1 . Is it the same issue? ERROR: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: No open file stream in ClientSystemFileCommands.writeFile() Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200069.1560779623000.4052.1562589000253%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30870) Reload Configuration from Disk - does not reload job config.xml
Title: Message Title
Andrew Barnish commented on JENKINS-30870
Re: Reload Configuration from Disk - does not reload job config.xml
Running this is the script console seems to reload all jobs: Jenkins.instance.getAllItems(AbstractItem.class).each { it.doReload() }; But this issue should be 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-51394) Add Perforce Job (p4 fix) link for submitting/publishing
Title: Message Title Andrew Barnish commented on JENKINS-51394 Re: Add Perforce Job (p4 fix) link for submitting/publishing We would also like to see this feature implemented for both freestyle and pipeline jobs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51394) Add Perforce Job (p4 fix) link for submitting/publishing
Title: Message Title Andrew Barnish assigned an issue to Paul Allen Jenkins / JENKINS-51394 Add Perforce Job (p4 fix) link for submitting/publishing Change By: Andrew Barnish Assignee: Paul Allen 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-19754) Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
Title: Message Title
Andrew Barnish commented on JENKINS-19754
Re: Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
We are still seeing this issue with jenkins 2.138 and envinject 2.16, although the workaround suggested above still seems to work. Does anyone know how to fix it properly?
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Andrew Barnish commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Oleg Nenashev, is there any progress with this issue? Do you require any further information to help with the debug? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Andrew Barnish commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together Alex Earl, did you find a solution for this issue yet? It is still causing very large emails to be sent from our Jenkins server. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Andrew Barnish commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together Is there any progress with this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Andrew Barnish commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API It happens when copying a job (within a folder) to a new job in a folder. The new job gets created but the configuration is not copied over correctly. It is not preventing users from configuring existing jobs. We have not tried node configuration. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Andrew Barnish commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API We are seeing the same problem when copying a job using Jenkins Web interface as we get a stack trace for users who have manage ownership but no admin permission. the stacktrace includes messages like: Caused: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : is missing the Overall/Administer permission I can provide the full stacktrace if necessary. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49633) Filenames are no longer shown under Summary of Changes - View Detail
Title: Message Title Andrew Barnish commented on JENKINS-49633 Re: Filenames are no longer shown under Summary of Changes - View Detail I have also noticed that when the global config "Maximum number of changes shown in a build" is 0 then changes are still being displayed for each build. There seems to be some inconsistency or bug. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49633) Filenames are no longer shown under Summary of Changes - View Detail
Title: Message Title Andrew Barnish commented on JENKINS-49633 Re: Filenames are no longer shown under Summary of Changes - View Detail Hi Paul, I had assumed that 0 meant infinite as it was set to 0 in previous versions of the plugin. You are correct that it is working if I set it to something non-zero. Probably the default global configuration after p4-plugin 1.8.5 should be non-zero. Where are the changes stored? I thought that the changes were fetched dynamically from the Perforce server when the browser requests the "recent changes" link, but I'm seeing different results for each build so I'm no longer sure about that. Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49633) Filenames are no longer shown under Summary of Changes - View Detail
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-49633 Filenames are no longer shown under Summary of Changes - View Detail Change By: Andrew Barnish After the upgrade to p4-plugin 1.8.5 we are no longer seeing "Submitted files" listed when following the link "Summary Of Changes - View Detail" ** This only seems to affect new builds.Builds from before the upgrade are still showing "Submitted files" correctly.It seems like it could be caused by the fix for - JENKINS-48845 - or - JENKINS-47602 - Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49633) Filenames are no longer shown under Summary of Changes - View Detail
Title: Message Title Andrew Barnish created an issue Jenkins / JENKINS-49633 Filenames are no longer shown under Summary of Changes - View Detail Issue Type: Bug Assignee: Paul Allen Components: p4-plugin Created: 2018-02-19 19:27 Environment: Jenkins 2.89.4 p4-plugin 1.8.5 Priority: Major Reporter: Andrew Barnish After the upgrade to p4-plugin 1.8.5 we are no longer seeing "Submitted files" listed when following the link "Summary Of Changes - View Detail"** This only seems to affect new builds. Builds from before the upgrade are still showing "Submitted files" correctly. It seems like it could be caused by the fix for JENKINS-48845 or JENKINS-47602 Add Comment
[JIRA] (JENKINS-42820) Regression in analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish edited a comment on JENKINS-42820 Re: Regression in analysis-core:1.82 when browsing warnings I tested the snapshot build [1.83-SNAPSHOT| http https ://jenkins -lassen .ci.cloudbees.com / pluginManager job / plugins/job/analysis-core- plugin/ 263/org.jvnet.hudson.plugins$ analysis-core/ thirdPartyLicenses artifact/org.jvnet.hudson.plugins/analysis-core/1.83-SNAPSHOT/analysis-core-1.83-SNAPSHOT.hpi ] on our jenkins server and it solved the issue.Thanks for the very quick fix. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish commented on JENKINS-42820 Re: Regression in analysis-core:1.82 when browsing warnings I tested the snapshot build 1.83-SNAPSHOT on our jenkins server and it solved the issue. Thanks for the very quick fix. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish commented on JENKINS-42820 Re: Regression in analysis-core:1.82 when browsing warnings Also warnings 4.58 and analysis-core 1.82 is not working. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish commented on JENKINS-42820 Re: Regression in analysis-core:1.82 when browsing warnings I upgraded to warnings 4.58 and analysis-core 1.81 and the links are still working properly, so I suspect the regression is in analysis-core 1.82. Unfortunately I cannot try warnings 4.60 with that version of analysis-core as the minimum requirement is 1.82 The type names are like: SGDC_waive27 or WRN_47 Yes, it definitely is still broken even if the build is done with the latest release: warnings:4.60/analysis-core:1.82 Can you create some kind of debug build or give me a hint where I can look for the problem? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in warnings:4.59/analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42820 Regression in warnings:4.59/analysis-core:1.82 when browsing warnings Change By: Andrew Barnish When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin and version 1.82 of the analysis-core plugin.I tried reverting to warnings-plugin version 4.58 and analysis-core version 1. 80 81 and everything is working correctly so there has been a regression here.To give you an example, when I browse to:[http://jenkins/job/jobname/125/warnings2Result/]There is a link shown on the "Types" tab to:[http://jenkins/job/jobname/125/warnings2Result/category.-52074025/]but following that link redirects back to:[http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/]I wonder if it is related to the following bug: - - JENKINS-37195- - Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-42820) Regression in analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42820 Regression in analysis-core:1.82 when browsing warnings Change By: Andrew Barnish Summary: Regression in warnings:4.59/ analysis-core:1.82 when browsing warnings Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in warnings:4.59/analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42820 Regression in warnings:4.59/analysis-core:1.82 when browsing warnings Change By: Andrew Barnish Summary: Regression in warnings ; : 4.59/analysis-core:1.82 when browsing warnings Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in warnings;4.59/analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42820 Regression in warnings;4.59/analysis-core:1.82 when browsing warnings Change By: Andrew Barnish Component/s: analysis-core-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in warnings;4.59/analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42820 Regression in warnings;4.59/analysis-core:1.82 when browsing warnings Change By: Andrew Barnish When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin and version 1 . 82 of the analysis-core plugin. I tried reverting to warnings-plugin version 4.58 and analysis-core version 1.80 and everything is working correctly so there has been a regression here.To give you an example, when I browse to:[http://jenkins/job/jobname/125/warnings2Result/]There is a link shown on the "Types" tab to:[http://jenkins/job/jobname/125/warnings2Result/category.-52074025/]but following that link redirects back to:[http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/]I wonder if it is related to the following bug: - JENKINS-37195 - Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-42820) Regression in warnings;4.59/analysis-core:1.82 when browsing warnings
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42820 Regression in warnings;4.59/analysis-core:1.82 when browsing warnings Change By: Andrew Barnish Summary: Regression in warnings; 4.59 /analysis-core:1.82 when browsing warnings Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in 4.59 browsing warnings
Title: Message Title Andrew Barnish commented on JENKINS-42820 Re: Regression in 4.59 browsing warnings I was using the very latest release of both warnings (4.60) and analysis-core(1.82), but I noticed the original behavior was broken so I reverted to very old releases of both warnings and analysis-core in order to see where the problematic code change occurred. I then moved forward through the warning releases until the regression occurred. I noticed this happened when going from warnings:4.58/analysis-core:1.80 (working) to warnings:4.59/analysis-core:1.82 (not working) Perhaps the problem is coming from analysis-core. I don't think I can run the latest warnings plugin with analysis-core 1.80. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in 4.59 browsing warnings
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42820 Regression in 4.59 browsing warnings Change By: Andrew Barnish Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in 4.59 browsing warnings
Title: Message Title Andrew Barnish commented on JENKINS-42820 Re: Regression in 4.59 browsing warnings in 4.58 the filter on the "Types" tab works correctly and shows the correct result. The version of both "warnings-plugin" and "static-analysis-core" are different so I'm not sure which plugin causes the problem. Is there some way I could enable some extra debugging in order to get to the bottom of the issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42820) Regression in 4.59 browsing warnings
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42820 Regression in 4.59 browsing warnings Change By: Andrew Barnish When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin.I tried reverting to version 4.58 and everything is working correctly so there has been a regression here.To give you an example, when I browse to:[http://jenkins/job/jobname/125/warnings2Result/ |http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/ ]There is a link shown on the "Types" tab to:[http://jenkins/job/jobname/125/warnings2Result/category.-52074025/]but following that link redirects back to:[http://jenkins/job/jobname/125/warnings2Result/|http://jenkins-lassen/job/dev/job/macro-chum.lint-srcg/125/warnings2Result/]I wonder if it is related to the following bug:https://issues.jenkins-ci.org/browse/JENKINS-37195 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are
[JIRA] (JENKINS-42820) Regression in 4.59 browsing warnings
Title: Message Title Andrew Barnish created an issue Jenkins / JENKINS-42820 Regression in 4.59 browsing warnings Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2017/Mar/15 10:34 PM Environment: Jenkins ver. 2.32.3 RHEL 6.4 Java 1.8.0_60-b27 static analysis_core 1.82 Priority: Major Reporter: Andrew Barnish When browsing warnings some of the links appear to be broken since version 4.59 of the warnings plugin. I tried reverting to version 4.58 and everything is working correctly so there has been a regression here. To give you an example, when I browse to: http://jenkins/job/jobname/125/warnings2Result/ There is a link shown on the "Types" tab to: http://jenkins/job/jobname/125/warnings2Result/category.-52074025/ but following that link redirects back to: http://jenkins/job/jobname/125/warnings2Result/ I wonder if it is related to the following bug: https://issues.jenkins-ci.org/browse/JENKINS-37195 Add Comment
[JIRA] (JENKINS-42209) Support for locking of multiple resource labels/groups
Title: Message Title Andrew Barnish updated an issue Jenkins / JENKINS-42209 Support for locking of multiple resource labels/groups Change By: Andrew Barnish Summary: Support for locking for of multiple resource labels/ groups It would be useful if the plugin allowed multiple resources to be locked on each build referenced by different resource group labels.This is the same as requested here:https://github.com/jenkinsci/lockable-resources-plugin/issues/23Also, it would be better if it was possible to specify a quantity of resources required for each resource group. Similar work seems to have been done in this pull request:https://github.com/jenkinsci/lockable-resources-plugin/pull/38 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because
[JIRA] (JENKINS-42209) Support for locking for multiple resource groups
Title: Message Title Andrew Barnish assigned an issue to Antonio Muñiz Jenkins / JENKINS-42209 Support for locking for multiple resource groups Change By: Andrew Barnish Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42209) Support for locking for multiple resource groups
Title: Message Title Andrew Barnish created an issue Jenkins / JENKINS-42209 Support for locking for multiple resource groups Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 2017/Feb/21 12:29 AM Priority: Minor Reporter: Andrew Barnish It would be useful if the plugin allowed multiple resources to be locked on each build referenced by different resource group labels. This is the same as requested here: https://github.com/jenkinsci/lockable-resources-plugin/issues/23 Also, it would be better if it was possible to specify a quantity of resources required for each resource group. Add Comment
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Andrew Barnish commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Yes, we are already using that workaround using the pinned downstream build. However, as I said in the description of the issue that this is not good as you then have to list all downsteam jobs in parameterized trigger section of the upstream job, rather than in the downstream job (which is the usual method to link jobs in jenkins) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38485) BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Title: Message Title
Andrew Barnish closed an issue as Not A Defect
The field contained a space by mistake: i.e. "$ {BUILD_NUMBER } " instead of "$ {BUILD_NUMBER} "
Jenkins / JENKINS-38485
BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Change By:
Andrew Barnish
Status:
Open Closed
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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
[JIRA] (JENKINS-38485) BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Title: Message Title Andrew Barnish commented on JENKINS-38485 Re: BUILD_NUMBER token not replaced in emails generated by email-ext plugin I think there must have been some change to the token substitution algorithm as it looks like we had a space before the final curly bracket that was causing this problem. Now that seems it is not allowed whereas in the old version it was Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38485) BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Title: Message Title
Andrew Barnish updated an issue
Jenkins / JENKINS-38485
BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Change By:
Andrew Barnish
After upgrading to token-macro-plugin 2.0 the {{ ${BUILD_NUMBER } }} token is no longer replaced in emails sent by email-ext-pluginDowngrading to token-macro-plugin version 1.12.1 restores the original behaviour
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38485) BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Title: Message Title
Andrew Barnish updated an issue
Jenkins / JENKINS-38485
BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Change By:
Andrew Barnish
After upgrading to token-macro-plugin 2.0 the {{ ${BUILD_NUMBER } }} token is no longer replaced in emails sent by email-ext-pluginDowngrading to token-macro-plugin version 1.12.1 restores the original behaviour
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38485) BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Title: Message Title
Andrew Barnish updated an issue
Jenkins / JENKINS-38485
BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Change By:
Andrew Barnish
After upgrading to token-macro-plugin 2.0 the ${BUILD_NUMBER } token is no longer replaced in emails sent by email-ext-pluginDowngrading to token-macro-plugin version 1.12.1 restores the original behaviour
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38485) BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Title: Message Title
Andrew Barnish created an issue
Jenkins / JENKINS-38485
BUILD_NUMBER token not replaced in emails generated by email-ext plugin
Issue Type:
Bug
Assignee:
David van Laatum
Components:
email-ext-plugin, token-macro-plugin
Created:
2016/Sep/25 1:34 PM
Environment:
Redhat 6.4 Jenkins 2.7.4 token-macro-plugin 2.0 email-ext-plugin 2.50
Priority:
Major
Reporter:
Andrew Barnish
After upgrading to token-macro-plugin 2.0 the $ {BUILD_NUMBER } token is no longer replaced in emails sent by email-ext-plugin Downgrading to token-macro-plugin version 1.12.1 restores the original behaviour
Add Comment
[JIRA] [p4-plugin] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Andrew Barnish created an issue Jenkins / JENKINS-33163 Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Issue Type: New Feature Assignee: Paul Allen Components: p4-plugin Created: 25/Feb/16 10:12 PM Labels: perforce Priority: Minor Reporter: Andrew Barnish Please could you consider adding a "Use Upstream Project revision" checkbox to the p4-plugin similar to that available in the legacy "perforce-plugin". It is a useful feature when jobs are setup to run after an upstream job with artifacts being copied. In many circumstances like this it is important that the downstream job uses the same file revisions as the upstream job that created the artifacts. I think it may be already possible to do this with "Parameterized Trigger Plugin" in the upstream job setting "change" parameter on the downstream job, but then all the downstream jobs have to be listed in the upstream job which is more complex to configure.
