[JIRA] (JENKINS-60439) Unable to specify ExecuteDslScripts.additionalParameters from Groovy
Title: Message Title
Carsten Pfeiffer created an issue
Jenkins / JENKINS-60439
Unable to specify ExecuteDslScripts.additionalParameters from Groovy
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2019-12-11 11:21
Priority:
Minor
Reporter:
Carsten Pfeiffer
I'm trying to set additionalParameters from Groovy code, similar to JENKINS-44128.
steps {
jobDsl {
additionalClasspath(somePath)
removedJobAction('DELETE')
removedViewAction('DELETE')
targets(someTargets)
additionalParameters([arg1: 'test', arg2: 'test2'])
}
}
Whatever I do, I cannot specify the map of additionalParameters. I always get:
ERROR: (unknown source) No signature of method: javaposse.jobdsl.plugin.structs.DescribableContext.additionalParameters() is applicable for argument types: (java.util.LinkedHashMap) values: ...
Could it be that maps cannot be passed at all, atm, maybe because they are not handled in https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/structs/DescribableContext.groovy#L72 ?
[JIRA] (JENKINS-59218) NullPointerException in logparser buildDataSet(LogParserAction.java:147)
Title: Message Title Carsten Pfeiffer commented on JENKINS-59218 Re: NullPointerException in logparser buildDataSet(LogParserAction.java:147) PR available at https://github.com/jenkinsci/log-parser-plugin/pull/27 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.201668.1567581327000.11293.1573230720219%40Atlassian.JIRA.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Carsten Pfeiffer assigned an issue to Jesse Glick Jenkins / JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace Change By: Carsten Pfeiffer Assignee: Carsten Pfeiffer Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.132184.1216748576000.8722.1569931202287%40Atlassian.JIRA.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Carsten Pfeiffer assigned an issue to Carsten Pfeiffer Jenkins / JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace Change By: Carsten Pfeiffer Assignee: Jesse Glick Carsten Pfeiffer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.132184.1216748576000.8624.1569930542360%40Atlassian.JIRA.
[JIRA] (JENKINS-58929) Bulk API for shelving projects
Title: Message Title
Carsten Pfeiffer commented on JENKINS-58929
Re: Bulk API for shelving projects
Now that shelving of plain {{hudson.model.Item}}s is possible in 5dc264b, it would be great to have an API for shelving a bunch of Item-instances in one go. This would take care of resolving the minimum set of items to shelve (e.g. if a parent item shall be shelved, do not shelve the child items as well). Currently, the job-dsl-plugin invokes the shelving like this:
jenkins.getQueue().schedule(new ShelveProjectTask(item), 0);
The new API might be something as simple as this:
List items = ...;
List itemsToBeShelved = new ShelveItemResolver().resolve(items);
jenkins.getQueue().schedule(new ShelveItemsTask(itemsToBeShelved), 0);
WDYT?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title Carsten Pfeiffer assigned an issue to Carsten Pfeiffer Jenkins / JENKINS-53305 javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; Change By: Carsten Pfeiffer Assignee: Devin Nusbaum Carsten Pfeiffer 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.193384.1535529489000.5931.1566283560501%40Atlassian.JIRA.
[JIRA] (JENKINS-58929) Bulk API for shelving projects
Title: Message Title Carsten Pfeiffer commented on JENKINS-58929 Re: Bulk API for shelving projects It would be great if this bulk mode would transparently handle jobs as well as folders. That way, the jobdsl plugin would not need to take care to first shelve jobs, wait for that to finish and then delete the folders, for example. 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.201273.1565786551000.5419.1566219780484%40Atlassian.JIRA.
[JIRA] (JENKINS-58929) Bulk API for shelving projects
Title: Message Title Carsten Pfeiffer created an issue Jenkins / JENKINS-58929 Bulk API for shelving projects Issue Type: Improvement Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2019-08-14 12:42 Priority: Minor Reporter: Carsten Pfeiffer It would be nice if there was a bulk API for shelving projects in batch. This would be used by seed jobs (via the job-dsl plugin) when unneeded jobs are automatically discarded and shelved. The bulk API would avoid avoid flooding the build queue with shelve tasks when there are many jobs to be discarded. See https://github.com/jenkinsci/job-dsl-plugin/pull/1174#discussion_r292322461 for the request. Add Comment
[JIRA] (JENKINS-57252) Support for shelving projects as RemovedJobAction
Title: Message Title Carsten Pfeiffer commented on JENKINS-57252 Re: Support for shelving projects as RemovedJobAction Ping? 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.199016.1556628449000.12408.1558954321844%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57252) Support for shelving projects as RemovedJobAction
Title: Message Title Carsten Pfeiffer commented on JENKINS-57252 Re: Support for shelving projects as RemovedJobAction Ping? 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.199016.1556628449000.12404.1558954290340%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57252) Support for shelving projects as RemovedJobAction
Title: Message Title Carsten Pfeiffer commented on JENKINS-57252 Re: Support for shelving projects as RemovedJobAction PR at https://github.com/jenkinsci/job-dsl-plugin/pull/1174 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.199016.1556628449000.21896.1557397320109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57252) Support for shelving projects as RemovedJobAction
Title: Message Title Carsten Pfeiffer created an issue Jenkins / JENKINS-57252 Support for shelving projects as RemovedJobAction Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2019-04-30 12:47 Priority: Minor Reporter: Carsten Pfeiffer When a seed job has determined that a job is not needed anymore, it will currently keep the job as is (ignore) disable the job delete the job I would like to have another option: shelve (archive) the job using the https://plugins.jenkins.io/shelve-project-plugin This would allow for automatic job cleanup while being safe against bugs in the seed job with a "delete" policy. Add Comment
[JIRA] (JENKINS-53239) Use default Jetty QueuedThreadPool
Title: Message Title Carsten Pfeiffer commented on JENKINS-53239 Re: Use default Jetty QueuedThreadPool Yes, please backport this, we need it as well! Thanks 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-52150) High CPU sys time consumption after upgrade to 2.107.3
Title: Message Title Carsten Pfeiffer commented on JENKINS-52150 Re: High CPU sys time consumption after upgrade to 2.107.3 One option would be to call FileChannel.force(false) instead of FileChannel.force(true) for the fingerprints in https://github.com/jenkinsci/jenkins/blame/jenkins-2.121.2/core/src/main/java/hudson/util/FileChannelWriter.java#L89 in order not to force-write all metadata. The manpage of fdatasync on Linux says: "The aim of fdatasync() is to reduce disk activity for applications that do not require all metadata to be synchronized with the disk.". Not sure how much this would help, though. 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-19712) [Fingerprint] Excessive Heap consumption during "Waiting for Jenkins to finish collecting data"
Title: Message Title Carsten Pfeiffer commented on JENKINS-19712 Re: [Fingerprint] Excessive Heap consumption during "Waiting for Jenkins to finish collecting data" Found the cause and a workaround, see https://issues.jenkins-ci.org/browse/JENKINS-52150?focusedCommentId=345858=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-345858 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-52150) High CPU sys time consumption after upgrade to 2.107.3
Title: Message Title Carsten Pfeiffer commented on JENKINS-52150 Re: High CPU sys time consumption after upgrade to 2.107.3 So this is rather unrelated to the maven plugin and more of a Jenkins core issue. The maven plugin only brings up the issue because it creates fingerprints by default. 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-52150) High CPU sys time consumption after upgrade to 2.107.3
Title: Message Title Carsten Pfeiffer updated an issue Jenkins / JENKINS-52150 High CPU sys time consumption after upgrade to 2.107.3 Change By: Carsten Pfeiffer Component/s: core 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-52150) High CPU sys time consumption after upgrade to 2.107.3
Title: Message Title Carsten Pfeiffer commented on JENKINS-52150 Re: High CPU sys time consumption after upgrade to 2.107.3 The real cause is the use of AtomicFileWriter in https://github.com/jenkinsci/jenkins/blob/jenkins-2.121.2/core/src/main/java/hudson/model/Fingerprint.java#L1256 The backing FileChannelWriter has an option to force flush (FileChannel.force(true)) and AtomicFileWriter does this by default. Luckily there is a system property that you can set in order to revert to the previous less safe, but better performing behavior: -Dhudson.util.AtomicFileWriter.DISABLE_FORCED_FLUSH=true (See https://github.com/jenkinsci/jenkins/blob/jenkins-2.121.2/core/src/main/java/hudson/util/AtomicFileWriter.java#L57) Setting this brings back the previous performance. 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-52150) High CPU sys time consumption after upgrade to 2.107.3
Title: Message Title
Carsten Pfeiffer commented on JENKINS-52150
Re: High CPU sys time consumption after upgrade to 2.107.3
We're also suffering from this, since we updated one jenkins from 2.89.4 to 2.121.2. It looks like the I/O pattern for writing a single fingerprint could be improved quite a bit, but this is probably not the only cause for the performance degradation.
[pid 8789] stat("/var/jenkins_home/fingerprints/bf/e4", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
[pid 8789] access("/var/jenkins_home/fingerprints/bf/e4", F_OK) = 0
[pid 8789] stat("/var/jenkins_home/fingerprints/bf/e4", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
[pid 8789] lstat("/var/jenkins_home/fingerprints/bf/e4", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
[pid 8789] mkdir("/var/jenkins_home/fingerprints/bf/e4", 0777) = -1 EEXIST (File exists)
[pid 8789] lstat("/var/jenkins_home/fingerprints/bf/e4", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
[pid 8789] stat("/var/jenkins_home/fingerprints/bf/e4/atomic8576544207056275611tmp", 0x7fe62a3e3f00) = -1 ENOENT (No such file or directory)
[pid 8789] open("/var/jenkins_home/fingerprints/bf/e4/atomic8576544207056275611tmp", O_RDWR|O_CREAT|O_EXCL, 0666) = 5
[pid 8789] open("/var/jenkins_home/fingerprints/bf/e4/atomic8576544207056275611tmp", O_WRONLY) = 5
[pid 8789] rename("/var/jenkins_home/fingerprints/bf/e4/atomic8576544207056275611tmp", "/var/jenkins_home/fingerprints/bf/e4/c7f5648f164d878a47abeebea260.xml") = 0
[pid 8789] lstat("/var/jenkins_home/fingerprints/bf/e4/atomic8576544207056275611tmp", 0x7fe62a3e4020) = -1 ENOENT (No such file or directory)
The problem really only shows up when you have lots of fingerprints. In our case, this is around 330k, stored in 6,5k directories in the fingerprints directory.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-50797) Workspace cleanup not removing workspace job@tmp directory on slave
Title: Message Title Carsten Pfeiffer updated an issue Jenkins / JENKINS-50797 Workspace cleanup not removing workspace job@tmp directory on slave Change By: Carsten Pfeiffer I _emphasized text_I am experiencing an issue with the ws-cleanup plugin. In my pipeline I set cleanWs() function on run Always on Post. But I always get a remaining folder *PipelineName_ws-cleanup_timestamp* and after a few builds get a message of no remaining space in device.I am running this on a Slave. 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-42085) Support for ephemeral slaves (unable to delete workspace)
Title: Message Title Carsten Pfeiffer created an issue Jenkins / JENKINS-42085 Support for ephemeral slaves (unable to delete workspace) Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Feb/16 8:19 AM Priority: Minor Reporter: Carsten Pfeiffer We're using Jenkins in a master-slave setup, where slaves are created on demand as Docker containers. The workspace is shared with the master so that one can still access it after the slave has gone away. There is a special WorkspaceBrowser which handles this, see JENKINS-41035. Unfortunately one cannot wipe out the workspace, because AbstractProject#doDoWipeOutWorkspace() fails to find the node on which the job was built (because the node is already gone). So basically we need a mechanism to tell Jenkins that the slave has gone, but the workspace is still available locally. Add Comment
[JIRA] (JENKINS-42063) Master/Slave serialization problems with DefaultTestResultParserImpl
Title: Message Title Carsten Pfeiffer created an issue Jenkins / JENKINS-42063 Master/Slave serialization problems with DefaultTestResultParserImpl Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2017/Feb/15 11:33 AM Priority: Minor Reporter: Carsten Pfeiffer In https://github.com/jenkinsci/junit-plugin/blob/master/src/main/java/hudson/tasks/test/DefaultTestResultParserImpl.java#L79 a Run instance (typically AbstractBuild), and additionally a Launcher are passed into a MasterToSlaveFileCallable. AFAIU, for this to work, they needed to be serializable in a Master/Slave scenario, alas, they are not. The Run is actually not needed in the closure, so this can be fixed easily. See JENKINS-34334 for a similar problem with a not serializable AbstractBuild instance, unrelated to DefaultTestResultParserImpl. Add Comment
[JIRA] (JENKINS-41035) Cannot browse workspaces of jobs using the cloudbees-folder-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-41035 Re: Cannot browse workspaces of jobs using the cloudbees-folder-plugin Any update on this? Should we ping someone else to get this merged? There's also JENKINS-36919 with a useful patch waiting to get merged. 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-37526) Docker Container Cap blanking stops execution
Title: Message Title Carsten Pfeiffer commented on JENKINS-37526 Re: Docker Container Cap blanking stops execution AFAICS this issue should be closed, because the PR got merged on Sep 13, 2016. 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-41928) "Parsed Console Output" page empty
Title: Message Title Carsten Pfeiffer resolved as Not A Defect I'm sorry – this was an nginx proxy that added the DENY header. Jenkins / JENKINS-41928 "Parsed Console Output" page empty Change By: Carsten Pfeiffer Status: Open Resolved 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
[JIRA] (JENKINS-41928) "Parsed Console Output" page empty
Title: Message Title Carsten Pfeiffer commented on JENKINS-41928 Re: "Parsed Console Output" page empty I installed and configured the XFrame-Filter plugin and configured it to send SAMEORIGIN and it still doesn't work. Configuring it to not send the header at all didn't help either. 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-41928) "Parsed Console Output" page empty
Title: Message Title Carsten Pfeiffer created an issue Jenkins / JENKINS-41928 "Parsed Console Output" page empty Issue Type: Bug Assignee: Manuel Recena Soto Components: log-parser-plugin Created: 2017/Feb/10 3:08 PM Priority: Major Reporter: Carsten Pfeiffer Even though the logfile parsing works fine (the "Log Parser Trend" looks correct, the logerrorLinks.html, logwarningLinks.html etc. files look good as well), the "Parsed Console Output" page is simply empty. The browser console says: /job/testing-master/job/snapshot/job/test-p-master-snapshot/4/parsed_conso…aster/job/snapshot/job/test-p-master-snapshot/4/parsed_console/log.html:1 Refused to display 'https://test-local.gebit.de/job/testing-master/job/snapshot/job/test-…-master/job/snapshot/job/test-p-master-snapshot/4/parsed_console/log.html' in a frame because it set 'X-Frame-Options' to 'DENY'. I suppose this is due to using a recent Jenkins version (2.32.2), because it works just fine with the very same browser on Jenkins 2.8 (different job setup, though). This makes the whole plugin pretty much unusable.
[JIRA] (JENKINS-41035) Cannot browse workspaces of jobs using the cloudbees-folder-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-41035 Re: Cannot browse workspaces of jobs using the cloudbees-folder-plugin Here's the link to the pull request: https://github.com/jenkinsci/docker-plugin/pull/473 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-41035) Cannot browse workspaces of jobs using the cloudbees-folder-plugin
Title: Message Title Carsten Pfeiffer created an issue Jenkins / JENKINS-41035 Cannot browse workspaces of jobs using the cloudbees-folder-plugin Issue Type: New Feature Assignee: magnayn Components: cloudbees-folder-plugin, docker-plugin Created: 2017/Jan/12 2:04 PM Priority: Minor Reporter: Carsten Pfeiffer MappedFsWorkspaceBrowser uses this to calculate the workspace directory of a job: new FilePath(getFile(new File(action.remoteFsMapping), "workspace", job.getName())) This works fine for toplevel jobs, but not for jobs whose directory is one or more sub directories below the "workspace" directory. Add Comment
[JIRA] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin I just checked again and in our setup, this bug is gone: jenkins 2.8 git-plugin 2.4.4 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-38164) Group changelog entries by Jenkins build numbers
Title: Message Title Carsten Pfeiffer created an issue Jenkins / JENKINS-38164 Group changelog entries by Jenkins build numbers Issue Type: New Feature Assignee: Paul Wellner Bou Components: git-changelog-plugin Created: 2016/Sep/13 11:33 AM Priority: Minor Reporter: Carsten Pfeiffer It would be nice if the changelog could optionally be grouped by jenkins job build numbers. Not everyone tags every build. So one could use the build number as some kind of "implicit tag" to group those commits that were added for a build. Add Comment
[JIRA] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin FWIW, in a first test, I couldn't reproduce the problem on a new test machine. I'll dig some more to find out the cause. 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] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin I'm beginning to think that this is related to another plugin then. E.g. one of https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Change+Log+History+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Changes+Since+Last+Success+Plugin 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] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin Yes, will do, but cannot do it today anymore. 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] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin Thanks for trying it. I upgraded to latest Jenkins (1.631) and git-plugin 2.4.0. I had to keep the jira-plugin at 1.41, because this jira doesn't have the REST API. The "git changes" block of individual builds still shows HTML code as before. I checked the "Safe HTML" option in Global Security settings. I only have the options "Safe HTML" and "Plain text" (Jenkins with German translation). Changing to "Plain text" doesn't help, the result is still HTML code. Any other idea where this might come from? 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] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin Thanks for you quick response, Mark. We didn't change the security settings – the current value for the markup formatter is Safe HTML. The other available value is Escaped HTML. I just changed the setting to Escaped HTML once and back to Safe HTML again to rule out a weird configuration bug, but I doubt that this is the reason. I guess it's rather the security fix for the git plugin Escape HTML generated into jelly pages with escape=true. The last version without this fix is 2.3.2; I'll see if I can install it to verify this. It would be nice if the escaping could be done at a different level, i.e. before the jira-plugin has processed the message, or if it would use the Safe HTML formatter that would only remove potentially malicious tags like script. 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] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin Yes, I did recently update. And I can confirm that git-plugin 2.3.2 produces correct HTML output. So the change Escape HTML generated into jelly pages with escape=true is mostly likely the cause for this. 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] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer commented on JENKINS-29075 Re: List of changes escapes HTML output of jira-plugin It looks like I was a bit too quick. When I click on Changes, I get a page Changes from Git with a summary table. That one is OK, i.e. the links to Jira issues are good. The page of an individual build that also lists the changes still shows escaped HTML, even with 2.3.2. I tested this with a fresh build, so I can't display information recorded with the previous (newer) git plugin. 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] [git-plugin] (JENKINS-29075) List of changes escapes HTML output of jira-plugin
Title: Message Title Carsten Pfeiffer created an issue Jenkins / JENKINS-29075 List of changes escapes HTML output of jira-plugin Issue Type: Bug Assignee: Nicolas De Loof Attachments: html-escaped.png Components: git-plugin, jira-plugin Created: 25/Jun/15 6:53 AM Environment: Linux, Jira 4.1.x, Jenkins 1.616, jira-plugin 1.41, git-plugin 2.3.5 Priority: Minor Reporter: Carsten Pfeiffer We're using the jira-plugin to link git-commits to jira issues. Recently the Changes box does not properly display the referenced Jira issues as html-links anymore. It escapes the HTML generated by jira-plugin like this: HTML-escaping the git commit message is probably a good idea, but there should be a way for the jira-plugin to create properly displayed links to the referenced Jira issues.
[JIRA] [fitnesse-plugin] (JENKINS-22643) Testsuite html results not shown anymore
Carsten Pfeiffer resolved JENKINS-22643 as Fixed Testsuite html results not shown anymore I'm using 1.11 now and it works again for me. Performance is still sometimes bad, but not always, so I'm resolving this. Thanks. Change By: Carsten Pfeiffer (09/Mar/15 9:34 AM) Status: Open Resolved 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 -- 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] [fitnesse] (JENKINS-22643) Testsuite html results not shown anymore
Carsten Pfeiffer created JENKINS-22643 Testsuite html results not shown anymore Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: fitnesse Created: 16/Apr/14 10:50 AM Description: Since 1.9, it is not possible to drill into the actual fitnesse results as seen in the screenshot at https://wiki.jenkins-ci.org/display/JENKINS/Fitnesse+Plugin?focusedCommentId=59511579#comment-59511579 The "Details" link is still there, but when clicking on it, it takes ages until the page is rendered the resulting page only shows a green or a red bar, not the actual test steps This makes it practically unusable to understand where and why a testcase actually failed. Since 1.9 there is another column "Details-Remote", which displays the following for me (example): TravelDemoCore.SuiteUseCases.TestkStartUmlRunner?pageHistoryresultDate= Note that it doesn't have a resultDate value. Maybe that's the reason for the problem? Project: Jenkins Labels: regression performance Priority: Major Reporter: Carsten Pfeiffer 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] (JENKINS-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer commented on JENKINS-12967 Cannot view HTML report for a specific build. Thanks! Regarding the ant pattern in 1.1: as far as I understood is the ant pattern only used for the actual files, which must reside in the same directory. My use case was multiple files in multiple directories. Thanks again Carsten 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-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer commented on JENKINS-12967 Cannot view HTML report for a specific build. D'oh, I'm so sorry. The patch contained stuff that was not meant to be in there. It appears as though the Eclipse egit plugin created the patch for the entire project instead of just the single file that I had selected. The patch should be tiny and contain only the change in HtmlPublisherTarget.java (i.e. the new method getOwner()). The other changes were an attempt to support reports in arbitrary directories, to be specified by an ant pattern. Please disregard that. 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-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer updated JENKINS-12967 Cannot view HTML report for a specific build. This patch fixes it for me. Change By: Carsten Pfeiffer (30/Nov/12 8:59 PM) Attachment: fix.patch 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-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer edited a comment on JENKINS-12967 Cannot view HTML report for a specific build. I have the same issue with Jenkins 1.488. And it appears to be the same problem as JENKINS-14625. 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-16000) Color bars do not match actual values
Carsten Pfeiffer created JENKINS-16000 Color bars do not match actual values Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Attachments: somewrongbars.png, wrongbars.png Components: jacoco Created: 30/Nov/12 9:51 PM Description: I'm using version 1.0.9 of the plugin with Jenkins 1.488 and some of the graphical bars do not match the actual values. See for example. In the packages-reports some bars look about right, while some others are again wrong. Project: Jenkins Priority: Minor Reporter: Carsten Pfeiffer 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-12967) Cannot view HTML report for a specific build.
Carsten Pfeiffer commented on JENKINS-12967 Cannot view HTML report for a specific build. I have the same issue with Jenkins 1.488. And it appears to be the same problem as JENKINS-12967. 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-15662) Cannot add post-build action for JaCoCo
Carsten Pfeiffer commented on JENKINS-15662 Cannot add post-build action for JaCoCo FWIW, when testing locally with mvn hpi:run, I tried once with the currently set jenkins target version 1.424.6 and another time with version 1488. It worked with both. 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-15662) Cannot add post-build action for JaCoCo
Carsten Pfeiffer created JENKINS-15662 Cannot add post-build action for JaCoCo Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 30/Oct/12 9:18 AM Description: I cannot add the JaCoCo post-build action to any job. Nothing happens when I invoke the entry in the post-build action menu of the job configuration. Also, nothing is logged when I do this. Environment: Linux, Oracle JDK 6, Jenkins 1.488 Project: Jenkins Priority: Major Reporter: Carsten Pfeiffer 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-13792) Support for conditional post-build actions
Carsten Pfeiffer created JENKINS-13792: -- Summary: Support for conditional post-build actions Key: JENKINS-13792 URL: https://issues.jenkins-ci.org/browse/JENKINS-13792 Project: Jenkins Issue Type: Improvement Components: conditional-buildstep Affects Versions: current Reporter: Carsten Pfeiffer Assignee: domi Priority: Minor It would be great if the plugin could also be used for *post*-build actions. Our use case is that we have a parameterized build, and, depending on the input parameters of a build, we would like to tag the workspace, or not. So we would add a run-condition for the Tag post-build action checking whether a specific input parameter was set. -- 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-13792) Support for conditional post-build actions
[ https://issues.jenkins-ci.org/browse/JENKINS-13792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162826#comment-162826 ] Carsten Pfeiffer commented on JENKINS-13792: I found out that one can use the [Flexible Publish Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin] to conditionally execute post-build actions, but unfortunately the Perform CVS Tagging action is not available then. Support for conditional post-build actions -- Key: JENKINS-13792 URL: https://issues.jenkins-ci.org/browse/JENKINS-13792 Project: Jenkins Issue Type: Improvement Components: conditional-buildstep Affects Versions: current Reporter: Carsten Pfeiffer Assignee: domi Priority: Minor It would be great if the plugin could also be used for *post*-build actions. Our use case is that we have a parameterized build, and, depending on the input parameters of a build, we would like to tag the workspace, or not. So we would add a run-condition for the Tag post-build action checking whether a specific input parameter was set. -- 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-13795) NPE with Flexible Publisher job
Carsten Pfeiffer created JENKINS-13795:
--
Summary: NPE with Flexible Publisher job
Key: JENKINS-13795
URL: https://issues.jenkins-ci.org/browse/JENKINS-13795
Project: Jenkins
Issue Type: Bug
Components: conditional-buildstep
Affects Versions: current
Reporter: Carsten Pfeiffer
Assignee: domi
Priority: Minor
I created a new job test-conditional that basically did nothing. I added a
Flexible Publish post-build action and added a boolean condition. The
combobox that should show the available actions to execute was empty.
I the log I found the following exception. When leaving and reopening the
configuration page of the job, the list of actions to execute was available.
{code}
SCHWERWIEGEND: Error while serving
http://trend-test:8080/job/test-conditional/configSubmit
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at
[JIRA] (JENKINS-12250) Critical block can not be added into conditional step
[
https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162805#comment-162805
]
Carsten Pfeiffer commented on JENKINS-12250:
I've often had trouble uploading plugins via the Advanced tab of the plugin
manager. What did work was manually extracting the .hpi file in the jenkins
{{plugins}} folder.
Critical block can not be added into conditional step
-
Key: JENKINS-12250
URL: https://issues.jenkins-ci.org/browse/JENKINS-12250
Project: Jenkins
Issue Type: Bug
Components: conditional-buildstep, exclusion
Environment: Jenkins 1.445
Jenkins Exclusion Plug-in 0.6
conditional-buildstep 0.2
Reporter: Oleksandr Popov
Assignee: Anthony Roux
Priority: Critical
Attachments: critical-block.PNG
I'm not able to add critical block into conditional step. See screen-shot for
details
--
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
