[JIRA] (JENKINS-16291) Support automatic proxy configuration
Title: Message Title Renjith Pillai commented on JENKINS-16291 Re: Support automatic proxy configuration Any plans to implement this? We have a weird requirement that only for accessing Github we need to use a proxy (for organisation folder plugin, all the branch scans as well as the actual cloning of repos). Using the existing setting demands nonProxyHosts for every server in this world and that's a bit annoying. 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-53805) Autofavorite makes the entire Blue Ocean unusable
Title: Message Title
Renjith Pillai updated an issue
Jenkins / JENKINS-53805
Autofavorite makes the entire Blue Ocean unusable
Change By:
Renjith Pillai
The version 1.2.2 causes exception for the first build of every branch and PR. See the exception at the end.Additional data points * We saw this reported in JENKINS-50715 which suggests the pull request [https://github.com/jenkinsci/blueocean-autofavorite-plugin/pull/16] solves the issue. * We built the latest source from [https://github.com/jenkinsci/blueocean-autofavorite-plugin] and the issue still exists * We make made a copy of the code and introduced a hack to have a try catch inside the entire {{onCheckout}} method to avoid this. * This is really a Priority one bug for Blue Ocean. Now since [~jamesdumay] has left CloudBees are we stuck with Blue Ocean not receiving the needed attention? {code:java}java.lang.NullPointerExceptionat io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:109)at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127)at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144)at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:120)at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429) {code}
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-53805) Autofavorite makes the entire Blue Ocean unusable
Title: Message Title Renjith Pillai created an issue Jenkins / JENKINS-53805 Autofavorite makes the entire Blue Ocean unusable Issue Type: Bug Assignee: James Dumay Components: blueocean-autofavorite-plugin Created: 2018-09-27 00:23 Environment: Jenkins ver. 2.136 Blue Ocean 1.8.3 Priority: Minor Reporter: Renjith Pillai The version 1.2.2 causes exception for the first build of every branch and PR. See the exception at the end. Additional data points We saw this reported in JENKINS-50715 which suggests the pull request https://github.com/jenkinsci/blueocean-autofavorite-plugin/pull/16 solves the issue. We built the latest source from https://github.com/jenkinsci/blueocean-autofavorite-plugin and the issue still exists We make a copy of the code and introduced a hack to have a try catch inside the entire onCheckout method to avoid this. This is really a Priority one bug for Blue Ocean. Now since James Dumay has left CloudBees are we stuck with Blue Ocean not receiving the needed attention? java.lang.NullPointerException at io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127) at
[JIRA] [mattermost-plugin] (JENKINS-33855) HTTP/S Proxy Settings Not Taking Effect
Title: Message Title Renjith V resolved as Won't Fix Jenkins / JENKINS-33855 HTTP/S Proxy Settings Not Taking Effect Change By: Renjith V Status: Open Resolved Resolution: Won't Fix 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] [mattermost-plugin] (JENKINS-33855) HTTP/S Proxy Settings Not Taking Effect
Title: Message Title Renjith V closed an issue as Won't Fix Jenkins / JENKINS-33855 HTTP/S Proxy Settings Not Taking Effect Change By: Renjith V Status: Resolved Closed 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] [mattermost-plugin] (JENKINS-33855) HTTP/S Proxy Settings Not Taking Effect
Title: Message Title Renjith V commented on JENKINS-33855 Re: HTTP/S Proxy Settings Not Taking Effect Jo, that was an important hint. I just upgraded to 1.5.0 and it is working perfectly. Thank you so much for spending time on checking 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] [mattermost-plugin] (JENKINS-33855) HTTP/S Proxy Settings Not Taking Effect
Title: Message Title Renjith V created an issue Jenkins / JENKINS-33855 HTTP/S Proxy Settings Not Taking Effect Issue Type: Bug Assignee: Jo Vandeginste Components: mattermost-plugin Created: 2016/Mar/28 6:56 PM Priority: Major Reporter: Renjith V The Jenkins instance is having the proxy settings as per the Jenkins docs (Manage Jenkins > Manage Plugins > Advanced). The test of the Mattermost url at this page works fine in the Jenkins instance. At the same time, the test of the mattermost channel update in the Job configuration fails for reaching the Mattermost servers via proxy. Add Comment
[JIRA] [docker-build-publish-plugin] (JENKINS-31632) Unable to configure Docker Login Credentials
Title: Message Title Renjith V created an issue Jenkins / JENKINS-31632 Unable to configure Docker Login Credentials Issue Type: Bug Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 18/Nov/15 5:01 PM Priority: Major Reporter: Renjith V As per the documentation at https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Build+and+Publish+plugin the below UI is supposed to be present in Manage Jenkins page. Click to see the screenshot Me as well as Jim W is facing issue that this UI is not available anywhere. Please suggest if this is a configuration issue or is it a documentation issue. Raising as Major as it is currently blocking pushing of images due to authentication failure. Add Comment
[JIRA] (JENKINS-743) Detect GCJ and report an error
Renjith V assigned JENKINS-743 to Renjith V Detect GCJ and report an error Change By: Renjith V (15/Sep/12 10:11 AM) Assignee: RenjithV 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-743) Detect GCJ and report an error
Renjith V assigned JENKINS-743 to Unassigned Detect GCJ and report an error Change By: Renjith V (15/Sep/12 10:59 AM) Assignee: RenjithV 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-13922) Subverson Release Manager bombardes SVN server with requests
Renjith V created JENKINS-13922: --- Summary: Subverson Release Manager bombardes SVN server with requests Key: JENKINS-13922 URL: https://issues.jenkins-ci.org/browse/JENKINS-13922 Project: Jenkins Issue Type: Bug Components: svn-release-mgr Reporter: Renjith V Priority: Blocker The credentials that was provided to Sub Version Release Manager was wrong. It was not indicated while configuring Jenkins. At the same time even though the build is not running, SVN Release Manager was bombarding the SVN server (approx 130 requests per minute) and each of them was failing due to bad credentials. It caused a SVN server outage :) -- 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-13429) Nested views not showing up with just read perms for View
[ https://issues.jenkins-ci.org/browse/JENKINS-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163102#comment-163102 ] Renjith V commented on JENKINS-13429: - So which release contains this correction? The [changelogs|http://jenkins-ci.org/changelog] doesn't seem to indicate this. Nested views not showing up with just read perms for View - Key: JENKINS-13429 URL: https://issues.jenkins-ci.org/browse/JENKINS-13429 Project: Jenkins Issue Type: Bug Components: nested-view Affects Versions: current Reporter: M S Assignee: Kohsuke Kawaguchi Labels: jenkins, plugin, views Jenkins 1.459 + Nested View Plugin 1.8 + Role-based Authorization Strategy 1.1.2 User has read permissions for View but Jenkins main page is missing Nested views (even if they have sub views with jobs). Adding configure perms for View results in Nested views showing up correctly. It looks like it's connected with: Added the View.READ permission to control visibility of views, and updated the default implementation to hide empty views. (issue 3681) -- 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-13429) Nested views not showing up with just read perms for View
[ https://issues.jenkins-ci.org/browse/JENKINS-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162783#comment-162783 ] Renjith V commented on JENKINS-13429: - Badly in need of this correction. The workaround to give 'Configure' permission for the same seems to be dangerous. Nested views not showing up with just read perms for View - Key: JENKINS-13429 URL: https://issues.jenkins-ci.org/browse/JENKINS-13429 Project: Jenkins Issue Type: Bug Components: nested-view Affects Versions: current Reporter: M S Assignee: Kohsuke Kawaguchi Labels: jenkins, plugin, views Jenkins 1.459 + Nested View Plugin 1.8 + Role-based Authorization Strategy 1.1.2 User has read permissions for View but Jenkins main page is missing Nested views (even if they have sub views with jobs). Adding configure perms for View results in Nested views showing up correctly. It looks like it's connected with: Added the View.READ permission to control visibility of views, and updated the default implementation to hide empty views. (issue 3681) -- 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
