[JIRA] (JENKINS-59496) Render HTML in the Extended Choice Parameter Description field
Title: Message Title Ben Langton created an issue Jenkins / JENKINS-59496 Render HTML in the Extended Choice Parameter Description field Issue Type: Improvement Assignee: vimil Components: extended-choice-parameter-plugin Created: 2019-09-24 00:48 Environment: Jenkins 2.195 Extended Choice Parameter Plugin 0.78 Priority: Minor Reporter: Ben Langton Some Parameter types render HTML in the Description field. Please make the Extended Choice Parameter Description field render HTML. An example (for a different plugin) is here: https://issues.jenkins-ci.org/browse/JENKINS-45029 Add Comment
[JIRA] (JENKINS-59495) Render HTML in Parameter Description field in Node and Label Parameter Plugin
Title: Message Title Ben Langton created an issue Jenkins / JENKINS-59495 Render HTML in Parameter Description field in Node and Label Parameter Plugin Issue Type: Improvement Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 2019-09-24 00:45 Environment: Jenkins 2.195 Node and Label Parameter Plugin 1.7.2 Priority: Minor Reporter: Ben Langton Some parameter Description fields (ex. built-in string parameter, et al) render HTML that is entered in the Description field. This is handy for improving the look, and calling users' attention to important parameters, etc. Please make the Description field of the Node parameter render HTML. Add Comment
[JIRA] (JENKINS-53448) PowerShell plugin - Write-Debug shows blank lines in the console for carriage returns
Title: Message Title
Ben Langton created an issue
Jenkins / JENKINS-53448
PowerShell plugin - Write-Debug shows blank lines in the console for carriage returns
Issue Type:
Improvement
Assignee:
Unassigned
Components:
powershell-plugin
Created:
2018-09-06 18:55
Environment:
Windows Server 2012 R2 PowerShell 5.1 Jenkins 2.135 PowerShell Plugin 1.3
Priority:
Minor
Reporter:
Ben Langton
Using a Windows PowerShell build step (PowerShell Plugin) and calling Write-Debug with a string that has carriage returns (0x13) results in Jenkins console output that is double-spaced. This does not happen with Out-Host, however. In Windows, the default line-ending characters ([Environment]::NewLine) are 0x13 0x10, so all Write-Debug calls that specify a multi-line message end up double-spaced. It is just a cosmetic issue, but it is sloppy-looking, and harder to read, especially when dumping an object with many properties to Write-Debug. Example: Put this in a Windows PowerShell build step and run the job: $s1 = "s1Line1" + [Environment]::NewLine + "s1Line2" $s2 = "s2Line1`ns2Line2" "Out-Host:" | Out-Host $s1 | Out-Host $s2 | Out-Host "Write-Debug:" | Out-Host Write-Debug $s1 Write-Debug $s2 The Jenkins console output looks like this: Out-Host: s1Line1 s1Line2 s2Line1 s2Line2 Write-Debug: DEBUG: s1Line1 s1Line2 DEBUG: s2Line1 s2Line2 note the blank line after "DEBUG: s1Line1", but not after "DEBUG: s2Line1"}}{{
[JIRA] (JENKINS-40608) Job Summary Of Changes disappeared in version 1.4.12
Title: Message Title Ben Langton commented on JENKINS-40608 Re: Job Summary Of Changes disappeared in version 1.4.12 Sorry for the long delay. I finally got back to upgrading again and looking at this. Using P4 Plugin 1.5.1, I still had the issue; the job was correctly triggered when there was a change, however the list of changes showed "No changes". (This particular job parses the from the job/build/api/xml URL to determine what it does next, so it was a problem for me). The issue is now resolved for me; it seems to have been fixed by deleting the local workspace folder, submitting a change to Perforce, and allowing the P4 plugin to completely resync the workspace. 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-40608) Job Summary Of Changes disappeared in version 1.4.12
Title: Message Title Ben Langton commented on JENKINS-40608 Re: Job Summary Of Changes disappeared in version 1.4.12 I saw this issue when using Jenkins 2.38. I am using the Tikal MultiJob plugin. The multijob polls Perforce using a workspace defined in a *.p4s file in the depot. After upgrading to the P4 Plugin 1.4.12, it would correctly recognize when a file within the workspace view had changed, and would trigger the multijob, but the changes list was empty. I am using the XML api to parse the changeset node, and it was an empty node (it did have the class attribute set). I downgraded (had some trouble getting things synched up again; it's still not clear to me how the plugin knows which changelist to start polling at), then my job was working fine again; the api/xml/multiJobBuild/changeSet node was populated again. I upgraded again; same issue, downgraded again; issue went away. 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-40608) Job Summary Of Changes disappeared in version 1.4.12
Title: Message Title Ben Langton commented on JENKINS-40608 Re: Job Summary Of Changes disappeared in version 1.4.12 I cannot upgrade the plugin until this is resolved. 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-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Ben Langton commented on JENKINS-34924 Re: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace I was able to work around this issue in 1.4.3, by using the new "Poll on Master using Last Build" option. Thanks! Ben Langton 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] [p4-plugin] (JENKINS-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Ben Langton updated an issue Jenkins / JENKINS-34924 p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace Change By: Ben Langton *** Update: This issue occurs on plugin version 1.4.0, as well. Issue begins immediately after upgrading p4-plugin to 1.3.9, and goes away as soon as I downgrade to 1.3.8 (I tried it multiple times). I verified that the workspace was at the latest revision, and cstat reported status "have" for all changelists, before upgrading the plugin.I have several jobs that poll Perforce for changes; all are affected. Polling triggers a build when there are no new changes. When the build syncs the workspace, it syncs not to the latest changelist, but to what I *think* is the oldest changelist containing files from the workspace.I think this is because it is not correctly parsing the status field returned from cstat, when it polls. Polling log is attached. It says "found change" on changelists that cstat reported were status "have" (I ran it independently of Jenkins) immediately prior to upgrading the plugin.Here is part of the build console output that demonstrates the issue; the raw text is attached. The latest changelist is 605049, but it syncs to changelist 530996...p4 changes -m1 -ssubmitted //FmsDbPatches_P4Poll/...Change 605049 on 2016/05/18 by jwb@jwb-netmenu 'MDIA - Edit Service Menus: Menu'...P4 Task: syncing files at change: 530996...p4 sync D:\Workspaces\FmsDbPatches_P4Poll/...@530996D:\Workspaces\FmsDbPatches_P4Poll/...@530996 - file(s) up-to-date... p4 changes -m100 //FmsDbPatches_P4Poll/...@605008,530996 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34864) MultiJob predefined parameters no longer passed to phase project
Title: Message Title Ben Langton commented on JENKINS-34864 Re: MultiJob predefined parameters no longer passed to phase project https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 Jenkins > 2.2 is also affected. This new behavior is by design. I suspect a lot of people will disable it An option to hide parameters on the Build With Parameters screen would be useful. It is sometimes necessary to pass parameters from one job to another, but you don't necessarily want those parameters exposed when the job is run by itself. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-34924) p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace
Title: Message Title Ben Langton updated an issue Jenkins / JENKINS-34924 p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace Change By: Ben Langton Summary: p4-plugin 1.3.9 triggers build when there is no new changelists, and syncs to oldest changelist in the workspace when polling Environment: Server 2012Jenkins 2.2p4-plugin 1.3.9 Perforce Server Server 2013.2 Attachment: polling.log Attachment: Console.log Issue begins immediately after upgrading p4-plugin to 1.3.9, and goes away as soon as I downgrade to 1.3.8 (I tried it multiple times). I tried recreating verified that the workspace was at the latest revision, and force syncing it cstat reported status "have" for all changelists , but it did not help before upgrading the plugin .I have several jobs that poll Perforce for changes; all are affected. Polling triggers a build when there are no new changes. When the job build syncs the workspace, it syncs not to the latest changelist, but to what I *think* is the oldest changelist containing files from the workspace. I think this is because it is not correctly parsing the status field returned from cstat, when it polls. Polling log is attached. It says "found change" on changelists that cstat reported were status "have" (I ran it independently of Jenkins) immediately prior to upgrading the plugin. Here is part of the log build console output that demonstrates the issue; the raw text is attached. The latest changelist is 605049, but it syncs to changelist 530996...p4 changes -m1 -ssubmitted //FmsDbPatches_P4Poll/...Change 605049 on 2016/05/18 by jwb@jwb-netmenu 'MDIA - Edit Service Menus: Menu'...P4 Task: syncing files at change: 530996...p4 sync D:\Workspaces\FmsDbPatches_P4Poll/...@530996D:\Workspaces\FmsDbPatches_P4Poll/...@530996 - file(s) up-to-date... p4 changes -m100 //FmsDbPatches_P4Poll/...@605008,530996
[JIRA] [p4-plugin] (JENKINS-34924) p4-plugin 1.3.9 syncs to oldest changelist in the workspace when polling
Title: Message Title Ben Langton created an issue Jenkins / JENKINS-34924 p4-plugin 1.3.9 syncs to oldest changelist in the workspace when polling Issue Type: Bug Assignee: Unassigned Attachments: p4-plugin 1.3.9 syncs to oldest changelist.log Components: p4-plugin Created: 2016/May/18 5:21 PM Environment: Server 2012 Jenkins 2.2 p4-plugin 1.3.9 Labels: oldest changelist perforce p4 sync 1.3.9 Priority: Major Reporter: Ben Langton Issue begins immediately after upgrading p4-plugin to 1.3.9, and goes away as soon as I downgrade to 1.3.8 (I tried it multiple times). I tried recreating the workspace and force syncing it, but it did not help. I
[JIRA] [nunit-plugin] (JENKINS-32999) Failed to transform nunit3 TestResult.xml
Title: Message Title Ben Langton commented on JENKINS-32999 Re: Failed to transform nunit3 TestResult.xml As an alternative, I am successfully using NUnit3 with the Jenkins NUnit plugin, by running the tests using a command line that includes: format=nunit2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [conditional-buildstep-plugin] (JENKINS-31992) Exception when saving MultiJob with MultiJob phase wrapped in Conditional BuildStep
Title: Message Title Ben Langton created an issue Jenkins / JENKINS-31992 Exception when saving MultiJob with MultiJob phase wrapped in Conditional BuildStep Issue Type: Bug Assignee: Dominik Bartholdi Components: conditional-buildstep-plugin, multijob-plugin Created: 09/Dec/15 8:45 PM Environment: Jenkins 1.640 conditional-buildstep 1.3.3 jenkins-multijob-plugin 1.20 Labels: exception Priority: Blocker Reporter: Ben Langton Recreate: Create a MultiJob Add build step -> Conditional step (single) (same or similar issue occurs when using Conditional step (multiple) Run = Always
[JIRA] [build-flow-plugin] (JENKINS-22779) Build-Flow plugin problems in latest version (0.11.1)
Title: Message Title Ben Langton commented on JENKINS-22779 Re: Build-Flow plugin problems in latest version (0.11.1) I believe the Build Flow plugin is deprecated in favor of the WorkFlow plugin. Some features or extensions of the Workflow plugin require a license from CloudBees, which wasn't in my budget at this time, so I have switched to using the Tikal MultiJob plugin, plus the Conditional BuildStep plugin, and that seems to work well for me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multijob-plugin] (JENKINS-29215) Wrong link to console from multijob view
Title: Message Title Ben Langton commented on JENKINS-29215 Re: Wrong link to console from multijob view Same thing with the Last Duration column; it refers to the last build of the job within the multi-job build. My use case is as follows, I have a single job that runs a test suite. That job accepts a parameter indicating which test suite to run. The job gets called several times within the same multijob (for different test suites). It would be helpful when looking at the multijob build to see the Console Output and Last Duration columns be connected to the build of the job that actually ran for that phase. As it is now, the results are little misleading. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [change-assembly-version-plugin] (JENKINS-26763) Assembly Version field value is not loaded when editing job
Ben Langton created JENKINS-26763 Assembly Version field value is not loaded when editing job Issue Type: Bug Assignee: Unassigned Components: change-assembly-version-plugin Created: 03/Feb/15 9:03 PM Description: Recreate: Add a Change Assembly Version task to an existing job (probably doesn't matter if it already exists or not) Set a value in the Assembly Version field Save Edit the job again (Configure) The value that was set in the Assembly Version field is now blank, so when the job is saved, it will no longer have that field populated, and the task will fail. I reverted to the previous release of the plugin, and this does not happen. Environment: Jenkins 1.598 Change Assembly Version Plugin 1.5 Project: Jenkins Priority: Major Reporter: Ben Langton 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-flow] (JENKINS-22779) Build-Flow plugin problems in latest version (0.11.1)
Ben Langton commented on JENKINS-22779 Build-Flow plugin problems in latest version (0.11.1) The post-build actions not being triggered persists in Build-Flow 0.12. In particular, when a build flow fails (ex. due to a Groovy Script error), it does not trigger the postbuild email action, to tell me it failed. 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.
