[JIRA] (JENKINS-40389) Gerrit support for Multibranch Pipeline
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-40389 Gerrit support for Multibranch Pipeline Issue Type: New Feature Assignee: Unassigned Attachments: Branch source options for MB Pipeline.png Components: workflow-multibranch-plugin Created: 2016/Dec/12 7:34 PM Priority: Minor Reporter: Dan Tranter Allow Gerrit "Branch Source" for Pipeline Multi-branch plugin. (currently only Git/GitHub and bitbucket are supported) Add Comment
[JIRA] (JENKINS-39719) Internal workflowLib libraries throwing errors
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-39719 Internal workflowLib libraries throwing errors Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Nov/14 4:09 PM Environment: Pipeline Shared Groovy Libraries Plugin 2.2+ Priority: Minor Reporter: Dan Tranter When importing an internal library (as described at https://github.com/jenkinsci/workflow-cps-global-lib-plugin), I'm encountering an issue: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: -1: You are not allowed to override the final method __cps__2() from class 'com.acme.foo.test.MyTest'. @ line -1, column -1. 1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1073) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:591) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:569) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:546) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:213) at
[JIRA] (JENKINS-24805) Mask credentials in Build Log
Title: Message Title Dan Tranter commented on JENKINS-24805 Re: Mask credentials in Build Log Just curious if there was any recent movement or potential fix for this on credential-binding for FreeStyle jobs 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-37698) Folders support for Stash plugin
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37698 Folders support for Stash plugin Issue Type: Improvement Assignee: nathan m Components: stash-pullrequest-builder-plugin Created: 2016/Aug/25 8:10 PM Priority: Minor Reporter: Dan Tranter We have several teams using the Stash PR plugin on a single Jenkins master. It would be helpful to allow them to specify the repo they should connect to at the Folder level (restricting items in a Folder, owned/managed by a specific team), and not just the master configuration (where same behaviour applies to all teams/users). However, if there are security reasons this shouldn't be done, please ignore this request. Add Comment
[JIRA] (JENKINS-37697) Folders support for Rally plugin
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37697 Folders support for Rally plugin Issue Type: Improvement Assignee: Unassigned Components: rally-plugin Created: 2016/Aug/25 8:06 PM Priority: Minor Reporter: Dan Tranter We have several teams using the Rally plugin on a single Jenkins master. Currently the Rally plugin must be customized for a given SCM at global config level (preventing it's customization in multi-team scenario). It would be nice to configure or override the settings at Folder level (restricting items in a Folder and below) Add Comment
[JIRA] (JENKINS-37696) Folders support for Green Balls
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37696 Folders support for Green Balls Issue Type: Improvement Assignee: asgeirn Components: greenballs-plugin Created: 2016/Aug/25 7:59 PM Priority: Minor Reporter: Dan Tranter We have several teams using the Green Balls plugin on a single Jenkins master. It would be helpful to allow the features to be customized at the Folder level (restricting items in a Folder and below), and not just the master configuration - where the changes affect everyone and all projects. Add Comment
[JIRA] (JENKINS-37695) Folders support for publish-over-ssh
Title: Message Title Dan Tranter updated an issue Jenkins / JENKINS-37695 Folders support for publish-over-ssh Change By: Dan Tranter Priority: Major Minor 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-37695) Folders support for publish-over-ssh
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37695 Folders support for publish-over-ssh Issue Type: Improvement Assignee: bap Components: publish-over-ssh-plugin Created: 2016/Aug/25 7:55 PM Priority: Major Reporter: Dan Tranter We have several teams using the Publish over ssh plugin on a single Jenkins master. It would be helpful to allow them to specify the server information they should connect to at the Folder level (restricting items in a Folder, for limit of access/security best practices), and not just the master configuration (where everything is visible to everyone). However, if there are security reasons this shouldn't be done, please ignore this request. Add Comment
[JIRA] (JENKINS-37475) Add a configurable switch on job that causes CPS to silently not continue on non-serializable code
Title: Message Title
Dan Tranter created an issue
Jenkins / JENKINS-37475
Add a configurable switch on job that causes CPS to silently not continue on non-serializable code
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Aug/17 4:04 PM
Priority:
Minor
Reporter:
Dan Tranter
Allow the addition of a configurable switch on the job that causes CPS to silently not continue on non-serializable code, and a closure that allows you to place arbitrary non-serializable code inline (rather than a method annotation). Example: def myString = 'adsfasdf' def firstTwoLetters = null unsafe { def matcher = (myString ~= /([a-z] {2} ).*/) if(matcher.matches()) { firstTwoLetters = matcher.group(1) } } println(firstTwoLetters)
Add Comment
[JIRA] (JENKINS-37318) Generate a background thread to allow for integration with Plugin Usage Plugin
Title: Message Title Dan Tranter updated an issue Jenkins / JENKINS-37318 Generate a background thread to allow for integration with Plugin Usage Plugin Change By: Dan Tranter Provide the needed ability to generate a list of plugins and usage count on a background thread, and then offer a link when finished. This will circumvent performance issues (especially on large instances with thousands of jobs) that would result from creating the computation inside an HTTP request thread 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-37318) Generate a background thread to allow for integration with Plugin Usage Plugin
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37318 Generate a background thread to allow for integration with Plugin Usage Plugin Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 2016/Aug/10 6:05 PM Priority: Minor Reporter: Dan Tranter Provide the needed generate on a background thread, and then offer a link when finished. This will circumvent performance issues (especially on large instances with thousands of jobs) that would result from creating the computation inside an HTTP request thread Add Comment
[JIRA] (JENKINS-37311) "logout" link doesn't work
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37311 "logout" link doesn't work Issue Type: Bug Assignee: Ben McCann Components: saml-plugin Created: 2016/Aug/10 1:43 PM Priority: Major Reporter: Dan Tranter Clicking the "logout" button causes a redirect to a page which causes Jenkins to automatically login. When the plugin is configured to allow READ permission for Authenticated, but not Anonymous, users, clicking "logout" has no effect. Similar to JENKINS-16350 (GitHub Oath plugin) This is what is really happening when you "logout"... Jenkins logs you out, redirects you back to the Jenkins page you were in. Jenkins sees a new you, now anonymous. It decides to authenticate you. Jenkins sends you to SAML server SAML server is configured to automatically log you in (aka "remember this website") Jenkins logs you right back in. Add Comment
[JIRA] (JENKINS-37126) workflowlibs functions are not available on restarting an existing pipeline
Title: Message Title Dan Tranter updated an issue Jenkins / JENKINS-37126 workflowlibs functions are not available on restarting an existing pipeline Change By: Dan Tranter This is side-effect regression of the resolved issue:Pipeline is unable to locate global libraries when build attempts to continue on restart 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-37126) workflowlibs functions are not available on restarting an existing pipeline
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-37126 workflowlibs functions are not available on restarting an existing pipeline Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/02 5:19 PM Labels: regression Priority: Major Reporter: Dan Tranter This is side-effect of the issue: Pipeline is unable to locate global libraries when build attempts to continue on restart Add Comment
[JIRA] (JENKINS-36275) "RSS for just latest builds" doesn't include build results inside folders
Title: Message Title
Dan Tranter created an issue
Jenkins / JENKINS-36275
"RSS for just latest builds" doesn't include build results inside folders
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Jun/28 1:53 PM
Environment:
Issue seen in multiple versions: 1.642, 1.656, 2.11
Priority:
Minor
Reporter:
Dan Tranter
"RSS for just latest builds" doesn't includes results from subfolders. However the other two RSS feeds ("RSS for all" and "RSS for failures") will include folder results just fine.
Add Comment
[JIRA] [jobconfighistory-plugin] (JENKINS-34151) Add support for Pipeline projects to display config changes in build history
Title: Message Title Dan Tranter updated an issue Jenkins / JENKINS-34151 Add support for Pipeline projects to display config changes in build history Change By: Dan Tranter Attachment: BuildHistory_FreeStyle.png Currently the job configuration history displays in the Build History for FreeStyle projects, but does not show up in Build History for Pipeline projects. This would be a very useful feature to track changes that occur between builds (otherwise the user needs to view the Build History and Job Config history side-by-side and compare timestamps...which can be difficult to visualize events in chronological order) Attached is example of freestyle project's build history, showing a tool (wrench) to view the config history changes that occurred between builds (of which Pipeline lacks this function) 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] [jobconfighistory-plugin] (JENKINS-34151) Add support for Pipeline projects to display config changes in build history
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-34151 Add support for Pipeline projects to display config changes in build history Issue Type: Improvement Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2016/Apr/11 8:27 PM Priority: Minor Reporter: Dan Tranter Currently the job configuration history displays in the Build History for FreeStyle projects, but does not show up in Build History for Pipeline projects. This would be a very useful feature to track changes that occur between builds (otherwise the user needs to view the Build History and Job Config history side-by-side and compare timestamps...which can be difficult to visualize events in chronological order) Add Comment
[JIRA] [p4-plugin] (JENKINS-33880) Option for viewing changes only without updating perfroce server
Title: Message Title Dan Tranter updated an issue Jenkins / JENKINS-33880 Option for viewing changes only without updating perfroce server Change By: Dan Tranter I'm using Jenkins latest p4 plugin with is 1.3.7, I've been looking for the population options but i can't find a way to check the changes only without updating the havefiles. When i select "Preview check only" this issues command p4 sync -k, and that command actually makes perforce think that I've updated my client, so when i try to sync the client in the build scripts it doesn't sync anything. I'd like to have another option in p4 plugin that would do "p4 sync –n" (i.e. just view the changes only, instead of updating the server as well) 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-33880) Option for viewing changes only without updating perfroce server
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-33880 Option for viewing changes only without updating perfroce server Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2016/Mar/29 5:40 PM Priority: Minor Reporter: Dan Tranter When i select "Preview check only" this issues command p4 sync -k, and that command actually makes perforce think that I've updated my client, so when i try to sync the client in the build scripts it doesn't sync anything. I'd like to have another option in p4 plugin that would do "p4 sync –n" (i.e. just view the changes only, instead of updating the server as well) Add Comment
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-33786) Compatibility with Folders plugin - jobs in folders not showing in HP ALM
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-33786 Compatibility with Folders plugin - jobs in folders not showing in HP ALM Issue Type: Improvement Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2016/Mar/24 3:55 PM Environment: HP ALM Jenkins Folders plugin Priority: Major Reporter: Dan Tranter Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title Dan Tranter commented on JENKINS-33050 Re: Monitoring stopped working - exception collecting data Upon update from 1.57 -> 1.58 and restart, monitoring graphs are now displaying again.. However I'm still seeing warnings/exception collecting data, unsure if that's related to previous failure. Unfortunately the current debugging log no longer contains entries from the time of failure: Last collect time: 861 ms Display time: 678 ms Memory overhead estimate: < 5 Mb Disk usage: 39 Mb Purge the obsolete files JavaMelody 1.58.0 Debugging logs Only the last 50 messages are displayed Fri Feb 19 20:07:12 CST 2016 DEBUG Server: jetty/winstone-2.8 Fri Feb 19 20:07:12 CST 2016 DEBUG Webapp context: Fri Feb 19 20:07:12 CST 2016 DEBUG JavaMelody version: 1.58.0 Fri Feb 19 20:07:12 CST 2016 DEBUG JavaMelody classes loaded from: file:/auto/ncs-jenkins/ncs-jenkins/jenkins/plugins/monitoring/WEB-INF/lib/javamelody-core-1.58.0.jar Fri Feb 19 20:07:12 CST 2016 DEBUG Host: host5@123.123.123.123 Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: storage-directory=//auto/ncs-jenkins/ncs-jenkins/jenkins/monitoring Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: http-transform-pattern=/\d+/|/site/. |avadoc/. |/ws/. |obertura/. |estReport/. |iolations/file/. |/user/. |/static/\w /|/adjuncts/\w+/|/bound/[\w\-]+ Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: custom-reports=Jenkins Info,About Monitoring Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: no-database=true Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: gzip-compression-disabled=true Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: system-actions-enabled=true Fri Feb 19 20:07:12 CST 2016 DEBUG log listeners initialized Fri Feb 19 20:07:12 CST 2016 DEBUG counters initialized Fri Feb 19 20:07:12 CST 2016 DEBUG counters data read from files in /auto/ncs-jenkins/ncs-jenkins/jenkins/monitoring/_host5 Fri Feb 19 20:07:12 CST 2016 DEBUG collect task scheduled every 60s Fri Feb 19 20:07:13 CST 2016 DEBUG first collect of data done Fri Feb 19 20:07:13 CST 2016 DEBUG JavaMelody filter init done in 308 ms Fri Feb 19 20:07:13 CST 2016 DEBUG counters data read from files in /auto/ncs-jenkins/ncs-jenkins/jenkins/monitoring/nodes Sat Feb 20 00:00:29 CST 2016 DEBUG Obsolete files deleted. JavaMelody disk usage: 14327 KB Sat Feb 20 00:00:32 CST 2016 DEBUG Obsolete files deleted. JavaMelody disk usage: 134286 KB Sun Feb 21 00:00:35 CST 2016 DEBUG Obsolete files deleted. JavaMelody disk usage: 27464 KB Sun Feb 21 00:00:39 CST 2016 DEBUG Obsolete files deleted. JavaMelody disk usage: 130530 KB Sun Feb 21 07:02:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:03:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:04:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:05:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:06:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:07:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:08:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:09:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:10:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:11:36 CST 2016 WARN exception while collecting
[JIRA] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title Dan Tranter created an issue Jenkins / JENKINS-33050 Monitoring stopped working - exception collecting data Issue Type: Bug Assignee: Unassigned Components: monitoring-plugin Created: 19/Feb/16 9:28 PM Environment: RedHat Enterprise Linux 6.1 JDK 1.8.0_65 Jenkins 1.625 LTS Priority: Major Reporter: Dan Tranter I'm encountering an issue where monitoring stops working. Seeing this javamelody exception: WARNING net.bull.javamelody.JavaLogger#warn: exception while collecting data: java.lang.IllegalArgumentException java.lang.IllegalArgumentException at java.nio.Buffer.position(Buffer.java:244) at net.bull.javamelody.RrdNioBackend.read(RrdNioBackend.java:147) at org.jrobin.core.RrdBackend.readInt(RrdBackend.java:224) at org.jrobin.core.RrdPrimitive.readInt(RrdPrimitive.java:63) at org.jrobin.core.RrdInt.get(RrdInt.java:55) at org.jrobin.core.Archive.(Archive.java:69) at org.jrobin.core.RrdDb.(RrdDb.java:244) at org.jrobin.core.RrdDb.(RrdDb.java:203) at org.jrobin.core.RrdDb.(RrdDb.java:266) at org.jrobin.core.RrdDbPool.requestRrdDb(RrdDbPool.java:103) at net.bull.javamelody.JRobin.addValue(JRobin.java:334) at net.bull.javamelody.Collector.collectJRobinValues(Collector.java:491) at net.bull.javamelody.Collector.collectJavaInformations(Collector.java:382) at
