[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche started work on JENKINS-62087 Change By: Joe Hansche Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205995.1588116528000.19715.1588196820489%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche commented on JENKINS-62087 Re: Detect Gradle module names Pull request has been opened: https://github.com/jenkinsci/analysis-model/pull/362 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205995.1588116528000.19714.1588196820468%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche updated JENKINS-62087 Jenkins / JENKINS-62087 Detect Gradle module names Change By: Joe Hansche Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205995.1588116528000.19717.1588196820527%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche commented on JENKINS-62087 Re: Detect Gradle module names Makes sense - I've pushed the simple case(s) with just looking for parent directory names of build.gradle, to my fork (haven't opened a PR yet), and also working on a way to parse the rootProject name from settings.gradle. The rootProject case might be worth resolving, because most Jenkins projects will checkout their SCM into the workspace directory which matches the Jenkins job name (usually). So this might treat anything in the root project as if moduleName=jenkins-job-name. You can check out current progress here: https://github.com/jhansche/analysis-model/commits/pr-62087 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205995.1588116528000.19687.1588190580159%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche commented on JENKINS-62087 Re: Detect Gradle module names I was planning to put together a PR last night and then I had to stop. One question is: would it be worth it to read the full Gradle model to figure out the resolved and configured module names, or should we just start with a way to detect the common base directory name between the report file and the nearest build.gradle file? The base directory would work for the most common scenario, but it's possible to redefine the module name or the $buildDir in which case it might not even be moduleA/build/. I'll take a first pass at the simple case, and see if it proves useful. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205995.1588116528000.19419.1588174560193%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche created an issue Jenkins / JENKINS-62087 Detect Gradle module names Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-28 23:28 Priority: Major Reporter: Joe Hansche Currently ModuleDetector[1] is capable of detecting module names from pom.xml files, build.xml files, and MANIFEST.MF files. But I would also like to look for Gradle module names. Typically in a multi-module Gradle project, the module name would match the subdirectory that the module is in, but it can also be overridden by settings.gradle[2]. The easy way would be to find the build.gradle file the same way it looks for the other files, and take that file's parent directory name: ./ |-- settings.gradle |-- build.gradle |-- moduleA/ |-- build.gradle |-- build/ (contains for example **/checkstyle-result.xml) |-- moduleB/ |-- build.gradle |-- build/ So as an example, when we find ./moduleA/build/reports/checkstyle/checkstyle-result.xml, that belongs to the ":moduleA" gradle module. [1] https://github.com/jenkinsci/analysis-model/blob/master/src/main/java/edu/hm/hafner/analysis/ModuleDetector.java [2] https://docs.gradle.org/current/userguide/organizing_gradle_projects.html
[JIRA] (JENKINS-61603) Handle Spot Instance Interruption
Title: Message Title Joe Hansche created an issue Jenkins / JENKINS-61603 Handle Spot Instance Interruption Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-20 18:28 Labels: feature-request Priority: Minor Reporter: Joe Hansche According to the Spot Instance documentation, the instance will be notified (best effort) approximately 2 minutes before terminating a spot instance. Currently when the spot instance is being terminated, it will simply interrupt any executing builds, leading to a build failure, and then we have to restart the build. Additionally, the slave's executors remain online during the 2-minute-warning period, so they are available to take new builds, even though it will be terminated imminently. By monitoring the instance-action metadata (or CloudWatch events), we can receive notice that AWS is about to terminate a spot instance, and let the master react by taking the remaining executors offline (i.e., similar to the "Mark this node temporarily offline" button in the node status screen). That will do two things: Give visual notice in the Jenkins UI, that a slave is intentionally going offline Prevents any additional jobs being scheduled on that slave, allowing the built-in scheduling to route it to another online host, or possibly bring up a new instance to take its place We can then add configuration options to the SlaveTemplate to forcefully abort (setting status=Result.ABORTED) an executing job when we get notified that the slave will be terminated, so that the build status can ref
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche commented on JENKINS-36544 Re: Allow setting environment variables for dynamic ec2 slaves Turns out the original PR did resolve this, but only for Jenkins versions up to and including v2.204. As of 2.205, the Configure Clouds block moved to a new page, and that broke the Node Properties block. New PR has been opened to address this, which should now work on versions before and after 2.205: https://github.com/jenkinsci/ec2-plugin/pull/440 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.172564.1468000478000.3495.1583784900282%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche assigned an issue to Joe Hansche Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves Change By: Joe Hansche Assignee: Francis Upton Joe Hansche Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.172564.1468000478000.3471.1583784722079%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche updated JENKINS-36544 Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves Change By: Joe Hansche Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.172564.1468000478000.3483.1583784722294%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche started work on JENKINS-36544 Change By: Joe Hansche Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.172564.1468000478000.3458.1583784721624%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche updated an issue Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves Change By: Joe Hansche Attachment: Screen Shot 2020-03-09 at 11.29.38 AM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.172564.1468000478000.3233.1583767920819%40Atlassian.JIRA.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site/Server
Title: Message Title Joe Hansche updated JENKINS-47309 Jenkins / JENKINS-47309 Plugin || Confluence Publisher || Not working with confluence cloud site/Server Change By: Joe Hansche Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/confluence-publisher-plugin/releases/tag/confluence-publisher-2.0.5 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.185734.1507283628000.8256.1581534780663%40Atlassian.JIRA.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site/Server
Title: Message Title Joe Hansche updated JENKINS-47309 Jenkins / JENKINS-47309 Plugin || Confluence Publisher || Not working with confluence cloud site/Server Change By: Joe Hansche Status: Open Fixed but Unreleased Resolution: Fixed 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.185734.1507283628000.8219.1581525421694%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche commented on JENKINS-36544 Re: Allow setting environment variables for dynamic ec2 slaves It appears that this was implemented in https://github.com/jenkinsci/ec2-plugin/pull/382 However, I don't see a way to edit the properties in the AMI template, even though the config.jelly entry is supposed to be there. Am I missing something? 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.172564.1468000478000.5711.1581365880578%40Atlassian.JIRA.
[JIRA] (JENKINS-55342) Add hashtags support in Jenkins building parameters
Title: Message Title Joe Hansche commented on JENKINS-55342 Re: Add hashtags support in Jenkins building parameters Would be great to also allow a change to be triggered via hashtags. For example, if we push with HEAD:refs/for/branch%t=trivial, that can be a signal that it doesn't need to trigger a build. It could then work just like the Topic filter. 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.196436.1545897906000.8502.1567813320241%40Atlassian.JIRA.
[JIRA] (JENKINS-53067) Android App Bundle upload support
Title: Message Title Joe Hansche commented on JENKINS-53067 Re: Android App Bundle upload support The update to the v3 SDK has been merged and released under plugin v2.0. I've started working on including AAB support – starting with some basic unit tests for now, before starting a larger refactor. 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.193060.1534426687000.4383.1564524120741%40Atlassian.JIRA.
[JIRA] (JENKINS-53067) Android App Bundle upload support
Title: Message Title Joe Hansche assigned an issue to Joe Hansche Jenkins / JENKINS-53067 Android App Bundle upload support Change By: Joe Hansche Assignee: Christopher Orr Joe Hansche 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.193060.1534426687000.18056.1563810241645%40Atlassian.JIRA.
[JIRA] (JENKINS-33403) gcloud-sdk-plugin is unable to find gcloud-sdk directory
Title: Message Title Joe Hansche updated an issue Jenkins / JENKINS-33403 gcloud-sdk-plugin is unable to find gcloud-sdk directory Change By: Joe Hansche Component/s: gcloud-sdk-plugin Component/s: google-cloud-backup-plugin 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.168811.1457459371000.2842.1560893400266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52538) Confluence publishes loses configuration when job edited
Title: Message Title Joe Hansche resolved as Fixed Jenkins / JENKINS-52538 Confluence publishes loses configuration when job edited Change By: Joe Hansche Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53067) Android App Bundle upload support
Title: Message Title Joe Hansche commented on JENKINS-53067 Re: Android App Bundle upload support I've created a PR to migrate to the androidpublisher-v3 SDK: https://github.com/jenkinsci/google-play-android-publisher-plugin/pull/12 That will be a prerequisite for later abstracting the APK publisher to a generic "package" publisher that can then be used by both APK and AAB publishing tasks. 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-17693) Confluence Publisher for Confluence 5x
Title: Message Title
Joe Hansche edited a comment on JENKINS-17693
Re: Confluence Publisher for Confluence 5x
[~qisylvia], Confluence 5 does not store pages in wiki format anymore. It is now stored in an XHTML format.Instead of entering your text using wiki markup, it should be in XHTML format. Thus instead of "{{ \ *strong \ *}}", it should be "{{strong}}" or "{{strong}}".
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-17693) Confluence Publisher for Confluence 5x
Title: Message Title
Joe Hansche edited a comment on JENKINS-17693
Re: Confluence Publisher for Confluence 5x
[~qisylvia], Confluence 5 does not store pages in wiki format anymore. It is now stored in an XHTML format.Instead of entering your text using wiki market markup , it should be in XHTML format. Thus instead of "{{*strong*}}", it should be "{{strong}}" or "{{strong}}".
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-17693) Confluence Publisher for Confluence 5x
Title: Message Title Joe Hansche commented on JENKINS-17693 Re: Confluence Publisher for Confluence 5x Sylvia Qi, Confluence 5 does not store pages in wiki format anymore. It is not stored in an XHTML format. Instead of entering your text using wiki market, it should be in XHTML format. Thus instead of "strong", it should be "strong" or "strong". 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-17693) Confluence Publisher for Confluence 5x
Title: Message Title
Joe Hansche edited a comment on JENKINS-17693
Re: Confluence Publisher for Confluence 5x
[~qisylvia], Confluence 5 does not store pages in wiki format anymore. It is not now stored in an XHTML format.Instead of entering your text using wiki market, it should be in XHTML format. Thus instead of "{{*strong*}}", it should be "{{strong}}" or "{{strong}}".
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] [confluence-publisher-plugin] (JENKINS-32316) Option to publish html report in confleuence page
Title: Message Title Joe Hansche commented on JENKINS-32316 Re: Option to publish html report in confleuence page You can already do this by generating your content using the Confluence XHTML storage format. 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] [confluence-publisher-plugin] (JENKINS-32316) Option to publish html report in confleuence page
Title: Message Title Joe Hansche closed an issue as Not A Defect Jenkins / JENKINS-32316 Option to publish html report in confleuence page Change By: Joe Hansche Status: Open Closed Resolution: Not A Defect 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] [gerrit-trigger-plugin] (JENKINS-31800) Continuous "gerrit.ls-projects" requets
Title: Message Title Joe Hansche commented on JENKINS-31800 Re: Continuous "gerrit.ls-projects" requets Looks like this was caused by the fix for JENKINS-31473 – as prior to that fix (according to the description of that ticket), isSupported would have been returning true, so the project list would never be fetched, so the 0-second interval would never have had a chance to become problematic. 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] [gerrit-trigger-plugin] (JENKINS-31800) Continuous "gerrit.ls-projects" requets
Title: Message Title Joe Hansche commented on JENKINS-31800 Re: Continuous "gerrit.ls-projects" requets Looking at the configuration options that you screenshot above – I see the problem now... My Gerrit configuration in Jenkins was set like this: To be clear, I did not set those values, so this must be an issue with the way the plugin upgrades its configurations? Setting the values to 0 and 3600 as shown in your screenshot does resolve the issue! But how did it get set to 0 in the first place? And why is 0 an acceptable refresh interval? 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] [gerrit-trigger-plugin] (JENKINS-31800) Continuous "gerrit.ls-projects" requets
Title: Message Title Joe Hansche updated an issue Jenkins / JENKINS-31800 Continuous "gerrit.ls-projects" requets Change By: Joe Hansche Attachment: Screen Shot 2015-12-08 at 2.26.46 PM.png 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] [gerrit-trigger-plugin] (JENKINS-31800) Continuous "gerrit.ls-projects" requets
Title: Message Title Joe Hansche reopened an issue Jenkins / JENKINS-31800 Continuous "gerrit.ls-projects" requets Change By: Joe Hansche Resolution: Not A Defect Status: Closed Reopened 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] [gerrit-trigger-plugin] (JENKINS-31800) Continuous "gerrit.ls-projects" requets
Title: Message Title Joe Hansche commented on JENKINS-31800 Re: Continuous "gerrit.ls-projects" requets Jiří Engelthaler, I understand what you're saying, but when the OP says "continuous" – he literally means 6-7 requests every second, continuously. That is eating up ~25% CPU time on the Gerrit server. Why would this be needed if no user is actively trying to type a project name? I don't think this should be closed as "Not a Defect", because 7 requests per second for data that hasn't changed and data that no user is actively trying to use, in my opinion at least, absolutely is a defect. 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] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title Joe Hansche commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Daniel Beck sorry, I've already rolled back to 1.625 (version prior to upgrade) and restored from a backup, because we couldn't run any ruby-related jobs on it. I'll have to try this again on a non-production server and get back to you. I added the -D line mentioned above onto the command line, and confirmed it was on the command line using ps. But at this time that's all that I can recall. It's possible that the argument was in the wrong place (it has to come before the -jar switch, right?) 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] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title Joe Hansche commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass James Nord, -Dhudson.ClassicPluginStrategy.noBytecodeTransformer=true did not appear to have any impact either way in 1.637. The same error persists. 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] [cucumber-testresult-plugin] (JENKINS-29328) NullPointerException parsing a Background section that has a Before hook.
Title: Message Title Joe Hansche commented on JENKINS-29328 Re: NullPointerException parsing a Background section that has a Before hook. The temporary workaround is to lock the cucumber version to 2.0.0 until this is addressed. 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] [cucumber-testresult-plugin] (JENKINS-29328) NullPointerException parsing a Background section that has a Before hook.
Title: Message Title
Joe Hansche updated an issue
Jenkins / JENKINS-29328
NullPointerException parsing a Background section that has a Before hook.
Change By:
Joe Hansche
As of Cucumber 2.0.1 (cucumber-core 1.2.0), the JSON output format has changed. It now adds a {{before}} array into the {{Background}} element. That causes GherkinCallback.java to crash because it assumes {{before}} will only exist for a Scenario:{noformat}ERROR: Build step failed with exceptionjava.lang.NullPointerException at org.jenkinsci.plugins.cucumber.jsontestsupport.GherkinCallback.before(GherkinCallback.java:221) at gherkin.JSONParser.before(JSONParser.java:82) at gherkin.JSONParser.parse(JSONParser.java:48) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:77) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:43) at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl$ParseResultCallable.invoke(DefaultTestResultParserImpl.java:159) at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl$ParseResultCallable.invoke(DefaultTestResultParserImpl.java:105) at hudson.FilePath.act(FilePath.java:991) at hudson.FilePath.act(FilePath.java:969) at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl.parse(DefaultTestResultParserImpl.java:99) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:99) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.perform(CucumberTestResultArchiver.java:112) at hudson.plugins.templateproject.ProxyPublisher.perform(ProxyPublisher.java:71) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1769) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374){noformat}Example feature:{code}Feature:Background:Given I am in the appScenario:When I do somethingThen I should see something{code}Example hooks:{code}Before do |scenario|# Do something.end{code}Produces a JSON output similar to:{code}[{ uri: "features/background_before.feature", line: 1, ... elements: [{keyword: "Background",... before: [] steps: []} ]}]{code} When locking cucumber to version 2.0.0, and all else remaining the same, the old JSON format is produced:{code}[{ uri: "features/background_before.feature, ... elements: [{ keyword: "Background", steps: []},{ keyword: "Scenario", steps: []} ]}]{code}Note that it does not even have the {{before}} array at all.
[JIRA] [cucumber-testresult-plugin] (JENKINS-29328) NullPointerException parsing a Background section that has a Before hook.
Title: Message Title Joe Hansche created an issue Jenkins / JENKINS-29328 NullPointerException parsing a Background section that has a Before hook. Issue Type: Bug Assignee: James Nord Components: cucumber-testresult-plugin Created: 09/Jul/15 10:31 PM Priority: Critical Reporter: Joe Hansche As of Cucumber 2.0.1 (cucumber-core 1.2.0), the JSON output format has changed. It now adds a before array into the Background element. That causes GherkinCallback.java to crash because it assumes before will only exist for a Scenario: ERROR: Build step failed with exception java.lang.NullPointerException at org.jenkinsci.plugins.cucumber.jsontestsupport.GherkinCallback.before(GherkinCallback.java:221) at gherkin.JSONParser.before(JSONParser.java:82) at gherkin.JSONParser.parse(JSONParser.java:48) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:77) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:43) at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl$ParseResultCallable.invoke(DefaultTestResultParserImpl.java:159) at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl$ParseResultCallable.invoke(DefaultTestResultParserImpl.java:105) at hudson.FilePath.act(FilePath.java:991) at hudson.FilePath.act(FilePath.java:969) at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl.parse(DefaultTestResultParserImpl.java:99) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSO
[JIRA] [nodejs-plugin] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Joe Hansche
commented on JENKINS-20636
RVM and NodeJS plugins are incompatible
Kohsuke Kawaguchi, is this an issue with the ruby runtime plugin? Or an issue with how the NodeJS plugin does its set up? The fact that both rbenv and RVM plugins have this issue, and both rely on the ruby runtime. NodeJS modifies the environment from the decorateLauncher() method, injecting the bin dir of the NodeJS installation into the PATH env var from the Launcher#launch(ProcStarter) method:
@Override
public Launcher decorateLauncher(final AbstractBuild build, Launcher launcher, BuildListener listener) throws IOException, InterruptedException, Run.RunnerAbortedException {
return new DecoratedLauncher(launcher){
@Override
public Proc launch(ProcStarter starter) throws IOException {
...
// HACK: Avoids issue with invalid separators in EnvVars::override in case of different master/slave
String overriddenPaths = NodeJSInstaller.binFolderOf(nodeJSInstallation, build.getBuiltOn())
+ pathSeparator
+ vars.get("PATH");
vars.override("PATH", overriddenPaths);
return super.launch(starter.envs(Util.mapToEnv(vars)));
}
Could it be a threading issue between the NodeJS plugin and the ruby runtime?
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] [nodejs-plugin] (JENKINS-27845) Support auto install on Mac OS X
Joe Hansche commented on JENKINS-27845 Support auto install on Mac OS X ^ Using 1.610 as the plugin's parent still produces the same results. The lib/node_modules/npm/node_modules/npmlog/node_modules directory is simply missing. 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] [nodejs-plugin] (JENKINS-27845) Support auto install on Mac OS X
Joe Hansche commented on JENKINS-27845 Support auto install on Mac OS X There seems to be a problem with the installer – although it seems to be an issue with Jenkins, not with the plugin. In my case, the extracted directory structure is missing several directory contents. However, if I extract the tarball myself, the directories are there. I have confirmed (via a unit test of the plugin) that even before the plugin starts deleting anything, the missing directories are not present. This is on Mac OS X. The first example that I have run into consistently is the lib/node_modules/npm/node_modules/npmlog/node_modules directory: it is present in the tarball, and it can be extracted properly; however, it does not exist in the extracted tool directory. All the other files inside npmlog are present, it's just missing node_modules and children. I'm still trying to find a reliable way to reproduce the issue. I'll also try updating the Jenkins hpi version requirement, to see if it was an issue that has been fixed in the Jenkins core. 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] [android-emulator-plugin] (JENKINS-14493) Send "geo fix" command to Android Emulator
Joe Hansche commented on JENKINS-14493 Send "geo fix" command to Android Emulator On Linux and Mac OS X, you can do this without telnet by doing: echo "geo fix" | nc localhost ${ANDROID_AVD_USER_PORT} nc is the netcat tool, which can open a connection, send stdin to the remote server, and disconnect, all in a single command, so you don't have to worry about the fact that telnet will block the console. 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] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Joe Hansche commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I tend to agree with Christopher Orr. Out of the last ~7 builds that were attempted, these were the results: -ports 5743,5744 – Worked -ports 5849,5850 – Failed to start -ports 5705,5706 – Failed to start -ports 5886,5887 – Worked -ports 5719,5720 – Worked -ports 5619,5620 – Failed to start -ports 5866,5867 – Worked -ports 5822,5823 – Worked So this means it does not seem to be affected by the even/odd pairs. 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] [confluence-publisher] (JENKINS-15472) Option to create a new page
Joe Hansche closed JENKINS-15472 as Fixed Option to create a new page Change By: Joe Hansche (22/Aug/14 3:41 PM) Status: Resolved Closed 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche commented on JENKINS-20185 Long pause after end of run To add a little more info to this: I've noticed the slowdown getting worse as the master has been running for a long time. Seems like a restart of Jenkins tends to clear something out, and the delays are not as bad (not really noticeable as "problematic"). Our last restart was when the master had been running for about 5-6 weeks, and the post-build delay was around 2 minutes. After the restart, the jobs finished without a noticeable lag. 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche assigned JENKINS-20185 to Unassigned Long pause after end of run Change By: Joe Hansche (11/Apr/14 5:02 PM) Assignee: Ulli Hafner 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche
edited a comment on JENKINS-20185
Long pause after end of run
I'm seeing this as well, long pause on "Computing warning deltas". The job has already been updated to SUCCESS, and the build time has already been recorded (as ~30-45 seconds). But the job continues to spin for about another 2-3 minutes, which blocks the executors, and blocks pending builds of the same job in the queue ("Build #1234 is already in progress ..."). There does not appear to be a way to disable the computation of deltas, only option is to disable the collection of the checkstyle stats.
EDIT: spoke too soon... I disabled the checkstyle plugin for this build, and the build continues to spin even after setting the build status and duration, and without the [CHECKSTYLE] entries in the log. I have no other post-build actions, so I'm not sure what it's doing in the meantime...
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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche
commented on JENKINS-20185
Long pause after end of run
I'm seeing this as well, long pause on "Computing warning deltas". The job has already been updated to SUCCESS, and the build time has already been recorded (as ~30-45 seconds). But the job continues to spin for about another 2-3 minutes, which blocks the executors, and blocks pending builds of the same job in the queue ("Build #1234 is already in progress ..."). There does not appear to be a way to disable the computation of deltas, only option is to disable the collection of the checkstyle stats.
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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche assigned JENKINS-20185 to Ulli Hafner Long pause after end of run Change By: Joe Hansche (11/Apr/14 4:38 PM) Assignee: Ulli Hafner 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] [analysis-core] (JENKINS-20185) Long pause after end of run
Joe Hansche updated JENKINS-20185 Long pause after end of run Change By: Joe Hansche (11/Apr/14 4:35 PM) Component/s: analysis-core Component/s: checkstyle 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] [confluence-publisher] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Joe Hansche commented on JENKINS-21104 Confluence Publisher Plugin ignores Jenkins proxy settings I'm just trying to find a way to get the axis2 SOAP client to take a proxy configuration, and haven't had any luck yet. the JIRA plugin also does not do anything with proxies – does that plugin work for you? 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] [confluence-publisher] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Joe Hansche assigned JENKINS-21104 to Markus Helm Confluence Publisher Plugin ignores Jenkins proxy settings Markus Helm, when you configure the proxy in the Jenkins instance, is it being set as a system property (http.proxyHost)? For more info see http://stackoverflow.com/questions/120797/how-do-i-set-the-proxy-to-be-used-by-the-jvm and http://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html Change By: Joe Hansche (03/Feb/14 5:43 PM) Assignee: Joe Hansche Markus Helm 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] [confluence-publisher] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Joe Hansche commented on JENKINS-21104 Confluence Publisher Plugin ignores Jenkins proxy settings I will try to get 1.9 released in the next week or so. There haven't been a lot of changes recently, mostly just pull requests. I'll update this issue when the change is being merged into the codebase and being released. In the meantime, if I don't get to it, I do accept pull requests: https://github.com/jenkinsci/confluence-publisher-plugin/pulls 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] [confluence-publisher] (JENKINS-21624) Unable to integrate Confluence Publisher Plugin
Joe Hansche started work on JENKINS-21624 Unable to integrate Confluence Publisher Plugin Change By: Joe Hansche (03/Feb/14 3:55 PM) Status: Open In Progress 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] [confluence-publisher] (JENKINS-21624) Unable to integrate Confluence Publisher Plugin
Joe Hansche commented on JENKINS-21624 Unable to integrate Confluence Publisher Plugin Roopendra Vishwakarma: I believe the problem here is that you have checked the "Attach archived artifacts" option, but your job does not archive any artifacts... So, getArtifactsDir() returns null, because the job doesn't save anything. Instead, uncheck that checkbox and add the Ant-syntax path to the file(s) that you want uploaded to Confluence into the "Other files to attach" box. If you are not intending to upload attachments at all – and only want to edit the contents of the page itself – then you need to uncheck the checkbox AND leave the "other files to attach" field empty. I'm recategorizing this as an improvement, because the error itself is caused by a misconfiguration; however, the plugin should detect that there are no artifacts and simply skip that step, instead of raising an error. 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] [confluence-publisher] (JENKINS-21624) Unable to integrate Confluence Publisher Plugin
Joe Hansche updated JENKINS-21624 Unable to integrate Confluence Publisher Plugin Change By: Joe Hansche (03/Feb/14 3:41 PM) Issue Type: Bug Improvement Priority: Major Minor 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] [confluence-publisher] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Joe Hansche commented on JENKINS-21104 Confluence Publisher Plugin ignores Jenkins proxy settings Thanks for the report! I hadn't considered proxy requirements initially. I'll see what I can do to add this in the next release. (Note to self, for similar implementation details: https://github.com/jenkinsci/stashnotifier-plugin/commit/bf0ee1981348a7cbaefd37b2bed27cdc6e30d50e) 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] [confluence-publisher] (JENKINS-19028) ERROR: Publisher com.myyearbook.hudson.plugins.confluence.ConfluencePublisher aborted due to exception
Joe Hansche resolved JENKINS-19028 as Postponed ERROR: Publisher com.myyearbook.hudson.plugins.confluence.ConfluencePublisher aborted due to exception I'd like to address this just to avoid the NPE error, and give a more meaningful message in the console. Change By: Joe Hansche (01/Aug/13 6:00 PM) Status: Open Resolved Resolution: Postponed 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] [confluence-publisher] (JENKINS-19028) ERROR: Publisher com.myyearbook.hudson.plugins.confluence.ConfluencePublisher aborted due to exception
Joe Hansche commented on JENKINS-19028 ERROR: Publisher com.myyearbook.hudson.plugins.confluence.ConfluencePublisher aborted due to exception I wonder if this is specific to Maven artifacts? Do you have the "archive the artifacts" option checked on the job configuration? Typically Maven jobs do not require that option, because they automatically archive the build artifacts based on what the Maven POM decides should be archived (usually the POM and .jar). I don't know when I'll be able to get around to fixing this, but I have a feeling that is probably the reason. I had not tested the plugin with a Maven project. Perhaps trying to enable that option might fix it as a workaround? 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] [confluence-publisher] (JENKINS-18829) Add ability to create page labels
Joe Hansche commented on JENKINS-18829 Add ability to create page labels It appears you are correct, I have not been paying attention to pull requests on the github repository (they tend to get lost in a sea of about 50+ github emails I receive per day :). However, that should never stop you from submitting the pull request anyway, and then open an issue here to reference the PR. I haven't had a chance to work on this plugin in quite a while, as $DAY_JOB has demanded the majority of my time. I just looked through those pending PRs and commented on them. I'm certainly open to merging anything that people are willing contribute to the project I'll do a cursory review of the code, but barring any glaringly obvious issues/errors, it is likely to be accepted. I'm not really sure what to tell you about not being able to build the plugin. As you can see from the other pull requests on github, the automated build bot is able to build the plugin from the PR code, so it's not an issue with the repository. You may be missing some key development environment steps (such as adding the jenkins maven repository in your ~/.m2/settings.xml file..?) Have you had a look at https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial? 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] [confluence-publisher] (JENKINS-18829) Add ability to create page labels
Joe Hansche assigned JENKINS-18829 to Todd Orr Add ability to create page labels Change By: Joe Hansche (18/Jul/13 7:51 PM) Assignee: Joe Hansche Todd Orr 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] [confluence-publisher] (JENKINS-18383) Out of memory errors when uploading
Joe Hansche commented on JENKINS-18383 Out of memory errors when uploading "should not be used with large files" is incorrect, though. If the JVM allows the attachment to be added, it will work. So having the stacktrace showing an error because of OOM shows the Jenkins site administrator that the attachment puts it over its heap limit. I could catch the OOME and and show a more friendly error message in the console, but if it's a failure, the stacktrace is probably helpful to have. 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] [confluence-publisher] (JENKINS-18383) Out of memory errors when uploading
Joe Hansche commented on JENKINS-18383 Out of memory errors when uploading Unfortunately, there's not much I can do to fix that. I haven't tried uploading a 25MB file via the plugin. You might need to increase your java heap space given to the Jenkins server. Can you tell what the upward limit is for the attachment in your JVM? There's only one way to add an attachment in this API, and if the axis client is unable to attach it within the JVM heap provided, the plugin will not be able to do anything to fix that. From the Confluence documentation, it states: Attachment addAttachment(String token, long contentId, Attachment attachment, byte[] attachmentData) - add a new attachment to a content entity object. Note that this uses a lot of memory - about 4 times the size of the attachment. The 'long contentId' is actually a String pageId for XML-RPC. 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] [confluence-publisher] (JENKINS-18383) Out of memory errors when uploading
Joe Hansche
updated JENKINS-18383
Out of memory errors when uploading
Change By:
Joe Hansche
(18/Jun/13 2:05 PM)
Description:
I get Out of memory errors when uploading files to Confluence (v5.1.2). This happens with files > 25 MB.{
quote
noformat
}[confluence] - Uploading file: Ipsos.MediaCell_v2.8_PanelistWebsite.zip (application/zip)ERROR: Unable to upload file...AxisFault faultCode: \{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException faultSubcode: faultString: java.lang.OutOfMemoryError: Java heap space; nested exception is: java.lang.OutOfMemoryError: Java heap space faultActor: faultNode: faultDetail: {}faultData:null \{http://xml.apache.org/axis/}hostname:barraljava.lang.OutOfMemoryError: Java heap space; nested exception is: java.lang.OutOfMemoryError: Java heap space at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222) at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope(Message.java:435) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at jenkins.plugins.confluence.soap.v1.ConfluenceserviceV1SoapBindingStub.addAttachment(ConfluenceserviceV1SoapBindingStub.java:4896) at com.myyearbook.hudson.plugins.confluence.ConfluenceSession.addAttachment(ConfluenceSession.java:181) at com.myyearbook.hudson.plugins.confluence.ConfluenceSession.addAttachment(ConfluenceSession.java:201) at com.myyearbook.hudson.plugins.confluence.ConfluencePublisher.performAttachments(ConfluencePublisher.java:241) at com.myyearbook.hudson.plugins.confluence.ConfluencePublisher.perform(ConfluencePublisher.java:314) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241){
quote
noformat
}
[JIRA] [maven] (JENKINS-18223) Classloader error while executing surefire archiver
Joe Hansche created JENKINS-18223 Classloader error while executing surefire archiver Issue Type: Bug Assignee: Unassigned Components: maven Created: 05/Jun/13 4:27 PM Description: This job was working yesterday using version 1.514. Today, it started failing, and I don't know why. This is the stacktrace: [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ api-client --- [INFO] Surefire report directory: /var/lib/jenkins/workspace/android-gerrit-verify-api-client/target/surefire-reports --- T E S T S --- Running JsonRpcCodecTest WARNING: no system properties value for ro.build.date.utc Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.196 sec Running JsonCodecTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.085 sec Results : Tests run: 5, Failures: 0, Errors: 0, Skipped: 0 [JENKINS] Recording test results java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading for a different type with name "com/google/common/base/Predicate" at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:637) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:649) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:145) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:453) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:435) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecut
[JIRA] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x
Joe Hansche edited a comment on JENKINS-17693 Confluence Publisher for Confluence 5x Interesting... I see two potential issues here: The SSL exception seems to imply that your Confluence instance is requiring HTTPS, but the certificate can't be validated by the Jenkins server. Is your instance accessible via non-SSL (http:// only)? If your server allows that, what happens if you change the URL in the Jenkins system configuration to remove the https requirement? If your server requires HTTPS, then it will likely require importing the SSL certificate from the Confluence server into the Jenkins server's JVM. I've had to do this a couple times in the past, particularly with newer Certificate Authorities that weren't available (or weren't widely popular) at the time the JVM you use was released. If this is what's required, I will look up instructions for importing that certificate and see if it helps. On a side note, how many Jenkins servers are in your cluster? Because I believe all servers (master and slaves) will need to have the certificate imported in order to support this. It sounds like your Confluence instance does not have the remote APIs enabled, based on the "There is no SOAP service at this location" error. Can you try these steps to enable the SOAP API? https://confluence.atlassian.com/display/DOC/Enabling+the+Remote+API 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] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x
Joe Hansche commented on JENKINS-17693 Confluence Publisher for Confluence 5x Interesting... I see two potential issues here: The SSL exception seems to imply that your Confluence instance is requiring HTTPS, but the certificate can't be validated by the Jenkins server. Is your instance accessible via non-SSL (http:// only)? If your server allows that, what happens if you change the URL in the Jenkins system configuration to remove the https requirement? If your server requires HTTPS, then it will likely require importing the SSL certificate from the Confluence server into the Jenkins server's JVM. I've had to do this a couple times in the past, particularly with newer Certificate Authorities that weren't available (or weren't widely popular) at the time the JVM you use was released. If this is what's required, I will look up instructions for importing that certificate and see if it helps. On a side note, how many Jenkins servers are in your cluster? Because I believe all servers (master and slaves) will need to have the certificate imported in order to support this. It sounds like your Confluence instance does not have the remote APIs enabled, based on the "There is no SOAP service at this location " error. Can you try these steps to enable the SOAP API? https://confluence.atlassian.com/display/DOC/Enabling+the+Remote+API 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] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x
Joe Hansche edited a comment on JENKINS-17693 Confluence Publisher for Confluence 5x Keven Bauke, until I have a chance to test this against a 5.x confluence instance, can you provide more information about what failures you're experiencing? Any log messages would be useful (from either Jenkins or Confluence side), etc. Also, can you please attach your SOAP WSDL file from your instance of Confluence? Should be accesible from http:///rpc/soap-axis/confluenceservice-v2?wsdl 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] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x
Joe Hansche assigned JENKINS-17693 to Keven Bauke Confluence Publisher for Confluence 5x Keven Bauke, until I have a chance to test this against a 5.x confluence instance, can you provide more information about what failures you're experiencing? Any log messages would be useful (from either Jenkins or Confluence side), etc. Change By: Joe Hansche (22/Apr/13 4:26 PM) Assignee: Joe Hansche Keven Bauke 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] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Joe Hansche updated JENKINS-13995 Would like the ability to disable hover-over context menus. Change By: Joe Hansche (17/Apr/13 3:29 PM) Attachment: Screen Shot 2013-04-17 at 11.18.51 AM.png 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] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Joe Hansche updated JENKINS-13995 Would like the ability to disable hover-over context menus. Change By: Joe Hansche (17/Apr/13 3:28 PM) Attachment: Screen Shot 2013-04-17 at 11.18.39 AM.png 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] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Joe Hansche commented on JENKINS-13995 Would like the ability to disable hover-over context menus. IMO, there is a pretty simple way to fix this for both camps. The example I'm going to use is in JIRA (5.2 – this version does not behave the same). Several of the fields on the View-Issue page can be edited inline by just hovering over the field (which changes the appearance immediately, making it obvious that it's editable, and introducing a pencil/edit icon next to the field), and when you click (either on the text or on the pencil icon), it transforms into an editable field. You can see that with the 3 screenshots I'm attaching. I think a good way to fix this problem would be to follow similar logic: instead of having the menu pop up on hover of the link itself, change it so hovering on the link transforms the appearance of the link into something that has the down-arrow icon and draws attention to that icon. Then you can make it where hovering (or clicking, if people are still adamant that it gets in the way) on the down-arrow icon brings up the context menu. That way the hover effect will not be as distracting to people who dislike it, and the context menu is still discoverable and easy to access for people who do like it. I use the context popup all the time, because it does take so long to jump around, especially when the important part of a build that I need to get to quickly is the build's console. But yes, it does have many quirks – especially when I'm trying to reconfigure several jobs at a time (hover, cmd+click "Configure" link; next job: hover, cmd+click configure; etc...), the menu from one used to always cause the menu for the one I'm aiming for to disappear prematurely, etc. Sounds like KK fixed that particular issue, so that's nice .. but too little too late, since now the hover feature itself is completely gone :\ I think if the down-arrow appears on hover of the link, and hovering on the down-arrow brings up the menu, it would appease those who prefer not to see the context menu, while still making it easily discoverable and accessible for people who do (no clicking required, just hover on the link, move over to the arrow icon, and the menu comes out) 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] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Joe Hansche edited a comment on JENKINS-13995 Would like the ability to disable hover-over context menus. Screenshots attached IMO, there is a pretty simple way to fix this for both camps. The example I'm going to use is in JIRA (5.2 – this version does not behave the same). Several of the fields on the View-Issue page can be edited inline by just hovering over the field (which changes the appearance immediately, making it obvious that it's editable, and introducing a pencil/edit icon next to the field), and when you click (either on the text or on the pencil icon), it transforms into an editable field. You can see that with the 3 screenshots I'm attaching. I think a good way to fix this problem would be to follow similar logic: instead of having the menu pop up on hover of the link itself, change it so hovering on the link transforms the appearance of the link into something that has the down-arrow icon and draws attention to that icon. Then you can make it where hovering (or clicking, if people are still adamant that it gets in the way) on the down-arrow icon brings up the context menu. That way the hover effect will not be as distracting to people who dislike it, and the context menu is still discoverable and easy to access for people who do like it. I use the context popup all the time, because it does take so long to jump around, especially when the important part of a build that I need to get to quickly is the build's console. But yes, it does have many quirks – especially when I'm trying to reconfigure several jobs at a time (hover, cmd+click "Configure" link; next job: hover, cmd+click configure; etc...), the menu from one used to always cause the menu for the one I'm aiming for to disappear prematurely, etc. Sounds like KK fixed that particular issue, so that's nice .. but too little too late, since now the hover feature itself is completely gone :\ I think if the down-arrow appears on hover of the link, and hovering on the down-arrow brings up the menu, it would appease those who prefer not to see the context menu, while still making it easily discoverable and accessible for people who do (no clicking required, just hover on the link, move over to the arrow icon, and the menu comes out) 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] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Joe Hansche updated JENKINS-13995 Would like the ability to disable hover-over context menus. Change By: Joe Hansche (17/Apr/13 3:29 PM) Attachment: Screen Shot 2013-04-17 at 11.20.23 AM.png 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-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Joe Hansche commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files Same here, we had to downgrade to 1.20 and 1.0.3, and also had to enable the useCLI flag. 1.30 and 1.0.4 broke most of our jobs, and downgrading to 1.1.27 is impossible because the 1.20 upgrade causes a backward-incompatible change in all build.xml and config files. 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-16710) Confluence publisher: Add boolean to choose whether to perform publish action if plugin sees page does not exist
Joe Hansche commented on JENKINS-16710 Confluence publisher: Add boolean to choose whether to perform publish action if plugin sees page does not exist I'm not sure I would make it a checkbox based on if the page exists, but making it so the plugin does not cause the build to fail (or give the option to fail the build if publishing does not succeed) makes sense. 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-15472) Option to create a new page
Joe Hansche closed JENKINS-15472 as Fixed Option to create a new page Sorry for the delay. 1.8 was just released to the update center. Change By: Joe Hansche (14/Jan/13 7:08 PM) Status: Resolved Closed 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-10593) Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL
Joe Hansche commented on JENKINS-10593 Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL Thanks, didn't know about that. However, it appears that is only available in the CloudBees Jenkins Enterprise package, which is not free and must be installed as a separate Jenkins installation. It's also not part of the CloudBees Free Enterprise Plugin that is available in the update center. This solution isn't as feature-rich as CloudBees's, of course But it does solve the one-off use case when an administrator just wants to restrict a single job to a smaller subset of users than the rest of the instance is configured to allow. Though I may consider revising this once more just to make sure that only an "overall administrator" can enable the option – so that non-administrator users who have access to configure the job cannot lock out the instance administrators unwittingly. 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-10593) Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL
Joe Hansche commented on JENKINS-10593 Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL Pull request has been created at https://github.com/jenkinsci/jenkins/pull/622 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-15472) Option to create a new page
Joe Hansche commented on JENKINS-15472 Option to create a new page This has been implemented in an upcoming 1.8 release. 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-14976) Deserializing parameter 'in2': could not find deserializer for type {http://beans.soap.rpc.confluence.atlassian.com}RemotePageUpdateOptions
Joe Hansche
commented on JENKINS-14976
Deserializing parameter 'in2': could not find deserializer for type {http://beans.soap.rpc.confluence.atlassian.com}RemotePageUpdateOptions
Looks like this is because Confluence 2.5 does not support the updatePage() method, according to https://confluence.atlassian.com/display/CONF25/Remote+API+Specification#RemoteAPISpecification-methodsRemoteMethods and instead uses storePage() to update a page. That means that 2.5 also does not support the ability to add a comment for the page edit (e.g., to explain what you're changing/why, etc). That is the primary purpose of the RemotePageUpdateOptions encapsulation class.
I'll consider adding a fallback for Confluence 2.5 support, but have you considered upgrading Confluence? The current version is 4.3, with 5.0 already available for developer early access. IMO, this is poor SOAP implementation, because both 2.5 and 3.x have a "v1" WSDL file that is supposed to describe the SOAP API, yet Confluence 2.5 does not support the actual v1 APIs mentioned above.
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-15308) "+" in the Page name not supported
Joe Hansche closed JENKINS-15308 as Cannot Reproduce "+" in the Page name not supported Change By: Joe Hansche (16/Nov/12 10:10 PM) Status: Resolved Closed 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-15308) "+" in the Page name not supported
Joe Hansche resolved JENKINS-15308 as Cannot Reproduce "+" in the Page name not supported Change By: Joe Hansche (16/Nov/12 10:10 PM) Status: Open Resolved Resolution: Cannot Reproduce 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-15472) Option to create a new page
Joe Hansche started work on JENKINS-15472 Option to create a new page Change By: Joe Hansche (16/Nov/12 10:09 PM) Status: Open In Progress 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-15419) TAP published results hide JUnit published results
Joe Hansche commented on JENKINS-15419 TAP published results hide JUnit published results How funny, I was just noticing this and about to file an issue, but I see it's already been fixed. Has 1.6 already been published to the update center? I just installed 1.5 a few hours ago. 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
