[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Roger Myung created an issue Jenkins / JENKINS-40517 Allow changing delimiter in log output Issue Type: Improvement Assignee: Unassigned Components: audit-trail-plugin Created: 2016/Dec/16 6:05 PM Priority: Minor Reporter: Roger Myung The log outputted to audit.log is difficult to parse, since it uses spaces as delimiters, but there can be spaces in the fields. If we could have alternate delimiters, it would be much easier to parse the output, for example in logstash. Add Comment
[JIRA] (JENKINS-38518) Add ability to specify Mattermost user login credentials
Title: Message Title Roger Myung closed an issue as Not A Defect Jenkins / JENKINS-38518 Add ability to specify Mattermost user login credentials Change By: Roger Myung 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38518) Add ability to specify Mattermost user login credentials
Title: Message Title Roger Myung commented on JENKINS-38518 Re: Add ability to specify Mattermost user login credentials Thanks, it turned out to be a proxy issue 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-38518) Add ability to specify Mattermost user login credentials
Title: Message Title Roger Myung commented on JENKINS-38518 Re: Add ability to specify Mattermost user login credentials I'm not sure the connection between mattermost and Jenkins works, I have not looked at the plugin source. A REST API would not be userless though, it would use http authentication. The errors I see in the Jenkins logs are : Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials 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-38518) Add ability to specify Mattermost user login credentials
Title: Message Title Roger Myung commented on JENKINS-38518 Re: Add ability to specify Mattermost user login credentials Having learned a little more about mattermost authentication, I think OAuth support would solve the authentication problem. 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-38518) Add ability to specify Mattermost user login credentials
Title: Message Title Roger Myung created an issue Jenkins / JENKINS-38518 Add ability to specify Mattermost user login credentials Issue Type: Improvement Assignee: Jo Vandeginste Components: mattermost-plugin Created: 2016/Sep/26 8:05 PM Environment: The plugin seems to take the login information from the Jenkins user. This is major limitation on Windows since Jenkins uses the Active Directory login, but Mattermost can only use Active Directory if you use Mattermost Enterprise. That means this plugin can only be used on Windows with Mattermost Enterprise. Priority: Major Reporter: Roger Myung Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37472) Need debugging information when connection fails
Title: Message Title Roger Myung commented on JENKINS-37472 Re: Need debugging information when connection fails Looks like it is an authentication error. Thanks! 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-37472) Need debugging information when connection fails
Title: Message Title Roger Myung created an issue Jenkins / JENKINS-37472 Need debugging information when connection fails Issue Type: Improvement Assignee: Jo Vandeginste Components: mattermost-plugin Created: 2016/Aug/17 2:26 PM Priority: Major Reporter: Roger Myung I am trying to get the Mattermost integration to connect. I've entered the Endpoint matching the Incoming Webhook I set on Mattermost. When I click Test Connection, I get the message "Failure", with no details. I need more information in order to investigate this. Running the build produces nothing in the build log. Enabling Webhook Debugging on Mattermost produces nothing in the logs. Add Comment
[JIRA] (JENKINS-34426) Changing project-based settings for AD-Groups shows error
Title: Message Title Roger Myung commented on JENKINS-34426 Re: Changing project-based settings for AD-Groups shows error I am using AD 1.47, with Jenkins 1.651.3, and I see this error (or something similar). My message is FATAL: Authentication failed because there was a problem caching user ; nested exception is com.google.common.util.concurrent.UncheckedExecutionException: com4j.ComException: 8007203e The search filter cannot be recognized. : The search filter cannot be recognized. : .\invoke.cpp:517 hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user ; nested exception is com.google.common.util.concurrent.UncheckedExecutionException: com4j.ComException: 8007203e The search filter cannot be recognized. : The search filter cannot be recognized. : .\invoke.cpp:517 at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:209) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:54) 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] [claim-plugin] (JENKINS-19422) Claim publisher exception when trying to claim a build is aborted
Roger Myung commented on JENKINS-19422 Claim publisher exception when trying to claim a build is aborted I am getting the "Allow broken build claiming is waiting for a checkpoint on MY JOB NAME" message on a successful build. It does not seem to have any effect. 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] [cloudbees-folder] (JENKINS-23096) radiatorviewplugin has incorrect links for jobs in folders
Roger Myung created JENKINS-23096 radiatorviewplugin has incorrect links for jobs in folders Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder, radiatorviewplugin Created: 19/May/14 4:35 PM Description: A Radiator view that exists in a folder structure creates incorrect links for the jobs that exist in it. For example: A Radiator view at http://jenkins/job/FolderA/job/FolderB/view/Radiator/ Clicking on a job gives http://jenkins/job/FolderA/job/FolderB/view/Radiator/job/FolderA/job/FolderB/job/JOBNAME/lastBuild instead of http://jenkins/job/FolderA/job/FolderB/view/Radiator/job/JOBNAME/lastBuild Environment: cloudbees-folder 4.5 cloudbees-folders-plus 2.9 radiatorviewplugin 1.18 Project: Jenkins Priority: Major Reporter: Roger Myung 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] [all-changes] (JENKINS-17349) CPU on master node keeps increasing and never come down
Roger Myung commented on JENKINS-17349 CPU on master node keeps increasing and never come down We have this issue too. Two flags that we've tried unsuccessfully are --handlerCountMax=100 --handlerCountMaxIdle=20 I'm curious if there is a performance difference between Winstone and Tomcat. I was planning on moving to Tomcat to try to separate the web server process from the core Jenkins process. 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-14051) A PollingLog would be helpful in setting up dosTrigger
Roger Myung closed JENKINS-14051 as Wont Fix A PollingLog would be helpful in setting up dosTrigger no maintainer of this plugin Change By: Roger Myung (15/Jan/13 4:00 PM) Status: InProgress Closed Resolution: WontFix 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-14053) Being able to read environment variables in dos-trigger would be helpful
Roger Myung closed JENKINS-14053 as Fixed Being able to read environment variables in dos-trigger would be helpful Closing issue. No maintainer of this plugin. Change By: Roger Myung (15/Jan/13 4:00 PM) Status: InProgress Closed Resolution: Fixed 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-14053) Being able to read environment variables in dos-trigger would be helpful
Roger Myung commented on JENKINS-14053 Being able to read environment variables in dos-trigger would be helpful Didn't mean to mark it fixed, sorry. 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-15204) NPE when DownstreamBuildView is used with the Promoted Build plugin
Roger Myung created JENKINS-15204 NPE when DownstreamBuildView is used with the Promoted Build plugin Issue Type: Bug Assignee: shinodkm Components: downstream-buildview, promoted-builds Created: 17/Sep/12 5:44 PM Description: I have a job that is started as Promotion action. When downstream-buildview is turned on, I get : Started by upstream project "JenkinsTestSuite/1_JTS_View/promotion/PromoteToTested" build number 94 FATAL: null java.lang.NullPointerException at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:85) at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:46) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188) 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:239) Environment: Jenkins ver. 1.466.1 Project: Jenkins Priority: Major Reporter: Roger Myung 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-14695) Confluence publisher showing up in email alert, but not in actual page
Roger Myung created JENKINS-14695 Confluence publisher showing up in email alert, but not in actual page Issue Type: Bug Assignee: Joe Hansche Components: confluence-publisher Created: 06/Aug/12 6:33 PM Description: We previously had the confluence publisher working correctly. However, ever since we "upgraded" to Confluence 4.1.10, we have been unable to get the publishing working. We are using "replace content between start/end tokens". We use anchors, and define the tag in the job as ac:macro ac:name="anchor"ac:default-parameterjenkinsStart1/ac:default-parameter/ac:macro ac:macro ac:name="anchor"ac:default-parameterjenkinsEnd1/ac:default-parameter/ac:macro (this was much easier in confluence 3.5) When we run the job, the plugin says confluence EXPERIMENTAL: performing storage format edits on Confluence 4.0 confluence Performing wiki edits: Replace content between start/end tokens Notifying upstream projects of job completion Finished: SUCCESS I get an email notification from Confluence showing the changes. However, when I go to the Confluence page, the page does not show the changes. The changes do not show in the page history. Environment: confluence 4.1.10 jenkins 1.466.1 confluence-publisher 1.7.1 Project: Jenkins Priority: Major Reporter: Roger Myung 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-14695) Confluence publisher showing up in email alert, but not in actual page
Roger Myung commented on JENKINS-14695 Confluence publisher showing up in email alert, but not in actual page I'm accessing the page via the link from the plugin, so I don't think it's a duplicate page issue. 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-14565) Please add support for Cloudbees folder structure
Roger Myung created JENKINS-14565 Please add support for Cloudbees folder structure Issue Type: Improvement Assignee: Unassigned Components: build-pipeline Created: 25/Jul/12 11:56 AM Description: We are using Cloudbees folders. I tried using the Build Pipeline plugin. I'm able to select my job from the drop-down, but the pipeline view does not show any of the downstream jobs, unless I create all the jobs at the base level (not in a folder). Project: Jenkins Priority: Major Reporter: Roger Myung 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-14076) Would like the ability to create a changelog for jobs triggered by scripttrigger
Roger Myung commented on JENKINS-14076 Would like the ability to create a changelog for jobs triggered by scripttrigger Hi Gregory, I'm using the scripttrigger to do a Clearcase operation that I can't do via the plugins. I then run a query to get the change information. Currently, I'm turning the information into html and using the html publisher. However, the build will say "no changes". 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-14076) Would like the ability to create a changelog for jobs triggered by scripttrigger
Roger Myung commented on JENKINS-14076 Would like the ability to create a changelog for jobs triggered by scripttrigger The polling log doesn't have user info, if you want to send emails. It also is not readable for users. I am referring to the changelog.xml file. Jenkins requires an implementation of ChangeLogParser and ChangeLogEntry to read the xml file. However, it does not require any specific way to create the xml file. This does not need to be done by the plugin. 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-14076) Would like the ability to create a changelog for jobs triggered by scripttrigger
Roger Myung created JENKINS-14076: - Summary: Would like the ability to create a changelog for jobs triggered by scripttrigger Key: JENKINS-14076 URL: https://issues.jenkins-ci.org/browse/JENKINS-14076 Project: Jenkins Issue Type: Improvement Components: scripttrigger Reporter: Roger Myung Assignee: Gregory Boissinot Using the ScriptTrigger plugin, I can run a script to decide whether to trigger a build. I would like the ability to create a changelog file so that I could display the reasons why the build was triggered. It's fine if the plugin just implements the parsing. I can create the xml file on my own. -- 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
[JIRA] (JENKINS-14077) rebuild plugin will throw java.lang.IllegalArgumentException: No such parameter definition
Roger Myung created JENKINS-14077: - Summary: rebuild plugin will throw java.lang.IllegalArgumentException: No such parameter definition Key: JENKINS-14077 URL: https://issues.jenkins-ci.org/browse/JENKINS-14077 Project: Jenkins Issue Type: Bug Components: parameterized-trigger, rebuild Reporter: Roger Myung Assignee: huybrechts Some of our jobs pass parameters that aren't used by the downstream jobs. They aren't used, but the downstream job builds fine according to the parameterized-trigger plugin. However, if a job fails, and we try to rebuild using the rebuild plugin, we get java.lang.IllegalArgumentException: No such parameter definition I understand that an argument can be made for strict parameter matching, but if so, it should be at the parameterized-trigger level. Rebuild should allow rebuilding any job that originally built. It should not be more strict. -- 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
[JIRA] (JENKINS-13937) ArtifactDeployer 0.16 messes the filenames for Windows filesystems
[ https://issues.jenkins-ci.org/browse/JENKINS-13937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163314#comment-163314 ] Roger Myung commented on JENKINS-13937: --- We usually access the deployed artifacts from the job page. from Last Successful Deployed Artifacts or from the page of the run Deployed Artifacts ArtifactDeployer 0.16 messes the filenames for Windows filesystems -- Key: JENKINS-13937 URL: https://issues.jenkins-ci.org/browse/JENKINS-13937 Project: Jenkins Issue Type: Bug Components: artifactdeployer Environment: artifactdeployer 0.16 Windows Reporter: Roger Myung Assignee: Gregory Boissinot We deploy our artifacts to a UNC path \\COMPUTERNAME\Artifacts\artifact.file With version 0.16, when a user tries to download this file, the file becomes _COMPUTERNAMEArtifactsartifact.file -- 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
[JIRA] (JENKINS-13937) ArtifactDeployer 0.16 messes the filenames for Windows filesystems
Roger Myung created JENKINS-13937: - Summary: ArtifactDeployer 0.16 messes the filenames for Windows filesystems Key: JENKINS-13937 URL: https://issues.jenkins-ci.org/browse/JENKINS-13937 Project: Jenkins Issue Type: Bug Components: artifactdeployer Environment: artifactdeployer 0.16 Windows Reporter: Roger Myung Assignee: Gregory Boissinot We deploy our artifacts to a UNC path \\COMPUTERNAME\Artifacts\artifact.file With version 0.16, when a user tries to download this file, the file becomes _COMPUTERNAMEArtifactsartifact.file -- 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
[JIRA] (JENKINS-13851) downgrading Jenkins from a version that uses jpi plugins to a version that uses hpi plugins causes plugins to uninstall
Roger Myung created JENKINS-13851: - Summary: downgrading Jenkins from a version that uses jpi plugins to a version that uses hpi plugins causes plugins to uninstall Key: JENKINS-13851 URL: https://issues.jenkins-ci.org/browse/JENKINS-13851 Project: Jenkins Issue Type: Bug Components: core, plugin Environment: Jenkins 1.464 downgraded to Jenkins ver. 1.424.3 (LTS) Reporter: Roger Myung I upgraded to 1.464 from 1.424.3 LTS. After upgrading, I updated some plugins. I found that the new Jenkins broke a plugin I needed (Promote), so I downgraded Jenkins. I found that the old Jenkins did not recognize the plugins I had downloaded with the new one. -- 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
[JIRA] (JENKINS-12746) envinject strips off \ each time config page is opened
Roger Myung created JENKINS-12746: - Summary: envinject strips off \ each time config page is opened Key: JENKINS-12746 URL: https://issues.jenkins-ci.org/browse/JENKINS-12746 Project: Jenkins Issue Type: Bug Components: envinject Environment: envinject 1.20 Jenkins 1.424.1 Windows XP Reporter: Roger Myung Assignee: gbois Priority: Critical I have previously used envinject versions 1.13 and 1.17. envinject always had problems with UNC paths in Windows. (ex. MY_SHARED_FOLDER=\\MYCOMPUTER\Shared) I previously was able to escape these directories by using double slashes (MY_SHARED_FOLDER=MYCOMPUTER\Shared). However, one of the updates between 1.17 and 1.20 introduced functionality that updates the the Properties Content each time the config page is saved. So after I set my value to , and save. If I load the page again, the value is set to \\. If I save and load again, this becomes \. This is a very serious issue that forced me to downgrade the plugin even though I really want the Mask Password fix. -- 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
