[JIRA] (JENKINS-30680) Make Custom Tools compatible with Pipeline
Title: Message Title Michael Lasevich commented on JENKINS-30680 Re: Make Custom Tools compatible with Pipeline out of curiosity, what is wrong with just using it via current "tool" step support? Why do we need a custom step for this? 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.165285.1443461181000.9911.1586805720680%40Atlassian.JIRA.
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich commented on JENKINS-59797 Re: AvatarCache does not support authenticated scm access Any thought as to when it may be released? 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.202527.1571192077000.3694.1583812500160%40Atlassian.JIRA.
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich commented on JENKINS-59797 Re: AvatarCache does not support authenticated scm access This PR allows child plugins to work around the issue without rewriting the whole AvatarCache functionality 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.202527.1571192077000.9578.1572985560235%40Atlassian.JIRA.
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich updated an issue Jenkins / JENKINS-59797 AvatarCache does not support authenticated scm access Change By: Michael Lasevich URL: https://github.com/jenkinsci/scm-api-plugin/pull/79 _*PR Provided: [https://github.com/jenkinsci/scm-api-plugin/pull/79]*_ Not sure if this is a bug, request for feature or just need for education but either way I am hoping you can help...I was troubleshooting a plugin based on scm-api-plugin (bitbucket-branch-source-plugin) and discovered something odd. The plugin uses AvatarCache to manage "Org" images, but that was not working. Upon digging into it, I discovered that since our SCM requires authentication, the image URL requires authentication too. But as far as I can see, AvatarCache does not have any support for getting urls with authentication. So my questions are: # Am I seeing this correct? Or am I missing something? # Was this intentional or an oversight? I am guessing most SCM repos that are not OSS projects will require authentication, so how can this work for most SCMs? # Is the expectation for those plugins that use authenticated access to SCM to not use AvatarCache, but to implement it internally? Or is there another mechanism in scm-api-plugin? # Assuming the answer is that each plugin must implement its own avatar handling, are there recommended approaches/patterns for those of us not familiar with Jenkins internals?Thank you so much Add Comment
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich updated an issue Jenkins / JENKINS-59797 AvatarCache does not support authenticated scm access Change By: Michael Lasevich Issue Type: New Feature Improvement 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.202527.1571192077000.9572.1572985260330%40Atlassian.JIRA.
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich commented on JENKINS-59797 Re: AvatarCache does not support authenticated scm access How do we get the PR reviewed/accepted? 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.202527.1571192077000.9569.1572985080214%40Atlassian.JIRA.
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich commented on JENKINS-59797 Re: AvatarCache does not support authenticated scm access I have submitted a PR for partial resolution of this - allowing plugins to provide their own fetch implementation without having to replace the entire AvatarCache functionality: https://github.com/jenkinsci/scm-api-plugin/pull/79 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.202527.1571192077000.18452.1571845320154%40Atlassian.JIRA.
[JIRA] (JENKINS-45852) Bitbucket project icons not displaying properly since 2.2.2.
Title: Message Title Michael Lasevich edited a comment on JENKINS-45852 Re: Bitbucket project icons not displaying properly since 2.2.2. FYI - After some digging, i identified the underlying issue and opened JENKINS- 39977 59797 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.184064.1501247779000.8454.1571192400243%40Atlassian.JIRA.
[JIRA] (JENKINS-45852) Bitbucket project icons not displaying properly since 2.2.2.
Title: Message Title Michael Lasevich commented on JENKINS-45852 Re: Bitbucket project icons not displaying properly since 2.2.2. FYI - After some digging, i identified the underlying issue and opened JENKINS-39977 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.184064.1501247779000.8450.1571192340151%40Atlassian.JIRA.
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich created an issue Jenkins / JENKINS-59797 AvatarCache does not support authenticated scm access Issue Type: New Feature Assignee: Unassigned Components: scm-api-plugin Created: 2019-10-16 02:14 Priority: Minor Reporter: Michael Lasevich Not sure if this is a bug, request for feature or just need for education but either way I am hoping you can help... I was troubleshooting a plugin based on scm-api-plugin (bitbucket-branch-source-plugin) and discovered something odd. The plugin uses AvatarCache to manage "Org" images, but that was not working. Upon digging into it, I discovered that since our SCM requires authentication, the image URL requires authentication too. But as far as I can see, AvatarCache does not have any support for getting urls with authentication. So my questions are: Am I seeing this correct? Or am I missing something? Was this intentional or an oversight? I am guessing most SCM repos that are not OSS projects will require authentication, so how can this work for most SCMs? Is the expectation for those plugins that use authenticated access to SCM to not use AvatarCache, but to implement it internally? Or is there another mechanism in scm-api-plugin? Assuming the answer is that each plugin must implement its own avatar handling, are there recommended approaches/patterns for those of us not familiar with Jenkins internals? Thank you so much
[JIRA] (JENKINS-45852) Bitbucket project icons not displaying properly since 2.2.2.
Title: Message Title Michael Lasevich commented on JENKINS-45852 Re: Bitbucket project icons not displaying properly since 2.2.2. BUMP Hard to believe it takes more than two years to address a basic bug 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.184064.1501247779000.6266.1570831560317%40Atlassian.JIRA.
[JIRA] (JENKINS-39028) [RFE] keep build forever - expose for current build and allow in sandbox
Title: Message Title
Michael Lasevich commented on JENKINS-39028
Re: [RFE] keep build forever - expose for current build and allow in sandbox
+1 Would be nice to have this available directly and properly, however there is a simple (in some cases) workaround - External Global Libraries. Since those are run outside the sandbox, you can simply write a small wrapper in an external lib like this:
// vars/KeepBuild.groovy inside external shared library
def call(boolean keep = true){
currentBuild.rawBuild.keepLog(keep)
}
Of course if you are not already using/needing external libs, this is a bit of a headache -M
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-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Michael Lasevich commented on JENKINS-39154 Re: Can not edit Pipeline script - text not visible on Configure Page Same issue. Downgrading worked for now. 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-38035) Favorites View cannot see MB Pipeline jobs
Title: Message Title Michael Lasevich created an issue Jenkins / JENKINS-38035 Favorites View cannot see MB Pipeline jobs Issue Type: Bug Assignee: Jesse Glick Components: favorite-view-plugin, workflow-multibranch-plugin Created: 2016/Sep/07 6:21 PM Labels: multibranch Priority: Minor Reporter: Michael Lasevich it appears that there is an issue between Favorites, Favorites View and MultiBranch Pipelines: If I mark the MB Pipeline parent job as a favorite, it properly shows up in Favorites View, however if I mark one of the branches as a favorite, it does not. On refresh, the "favorites" star goes away - HOWEVER it does show up in the list of favorites in the user profile editing screen - so the job IS marked as "Favorite" somewhere. It works fine for manually "foldered" jobs - so this issue is specific to MB Pipelines Usi ng: Jenkins 2.7.3 Favorites 1.16 Favorites View 1.0 Pipeline: Multibranch 2.8 In View config I do have selected "Recurse in subfolders" and Select by Regex with regex ".*"
[JIRA] (JENKINS-37858) Group based LDAP authentication does not work
Title: Message Title Michael Lasevich created an issue Jenkins / JENKINS-37858 Group based LDAP authentication does not work Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap-plugin Created: 2016/Aug/31 3:15 PM Environment: Jenkins 2.10 (recreated in 1.566) ldap-plugin 1.12 Labels: ldap authorization Priority: Critical Reporter: Michael Lasevich When using LDAP Plugin, groups are not read unless user is explicitly granted admin rights ahead of time (defeating the point of using LDAP groups). I believe it is not a config issue as if the user is admin, they can, in fact, see groups with same config. To Recreate: 1 - Set up LDAP Plugin to point to a working LDAP server with two user accounts (say, "admin" and "user" - make both have groups attached to them) 2 - Set Authorization to "Anyone Can Do anything" 3 - Verify you can login with each user and each user can see own groups by going to /users/ uri 4 - Set up matrix auth (any conditional auth will do, matrix is the easiest one though) and grant "admin" overall admin rights, and "user" overall "read" 5 - Repeat step 3, - at this point admin will see their own groups, but "user" will not be able too This is not just visual, group based authentication does not work - looking in logs it appears that "user" only has "authorized" permission when no admin rights
[JIRA] [workflow-plugin] (JENKINS-29481) Missing SCM info/data when using Workflow from SCM
Title: Message Title Michael Lasevich created an issue Jenkins / JENKINS-29481 Missing SCM info/data when using Workflow from SCM Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 18/Jul/15 2:54 AM Priority: Minor Reporter: Michael Lasevich When using workflow script directly from SCM , the repository is checked out into a separate workspace, leading to a need to checkout the exact same scm the second time. Would be nice to have an option to work in the same workspace that has the repository already checked out. If that is not possible, would be at least nice to have information about which repository/branch/revision was checked out so that we can check out exact same code the second time instead of having to hardcode same information into the script in SCM and alter it each time we branch. Add Comment
[JIRA] [scriptler] (JENKINS-18973) Unable to create or upload script
Michael Lasevich commented on JENKINS-18973 Unable to create or upload script Yep, plugin not-functional with current jgit 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] [scriptler] (JENKINS-18973) Unable to create or upload script
Michael Lasevich edited a comment on JENKINS-18973 Unable to create or upload script Yep, plugin not-functional with current jgit Update: I have another server with same versions of both git-server and scriptler which works fine. Upon comparing the two, I found that git-client was an older version (1.0.7) on the working server vs 1.1.1 on the one with this issue. I downgraded the server having a problem and it is working now. Hope this helps tracking this down. 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.
