[JIRA] (JENKINS-42522) Metadata plugin deletes old data on startup
Title: Message Title recampbell closed an issue as Incomplete Please provide detailed steps to reproduce. Jenkins / JENKINS-42522 Metadata plugin deletes old data on startup Change By: recampbell Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42795) REGRESSION: Bitbucket scan organization folder fails
Title: Message Title recampbell updated an issue Jenkins / JENKINS-42795 REGRESSION: Bitbucket scan organization folder fails Change By: recampbell Labels: regression scm-api-tidy-scrub Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42795) REGRESSION: Bitbucket scan organization folder fails
Title: Message Title recampbell updated an issue Jenkins / JENKINS-42795 REGRESSION: Bitbucket scan organization folder fails Change By: recampbell Summary: REGRESSION: Bitbucket scan organization folder fails Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42368) multibranch pipeline job notified by stash, mutliple job/projects build
Title: Message Title recampbell updated an issue Jenkins / JENKINS-42368 multibranch pipeline job notified by stash, mutliple job/projects build Change By: recampbell Labels: regression scm-api-tidy-scrub Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42432) All branches (SVN) get built periodically, even if nothing has changed (discard old builds)
Title: Message Title recampbell assigned an issue to Unassigned Jenkins / JENKINS-42432 All branches (SVN) get built periodically, even if nothing has changed (discard old builds) Change By: recampbell Assignee: CloudBees Inc. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42432) All branches (SVN) get built periodically, even if nothing has changed (discard old builds)
Title: Message Title recampbell updated an issue Jenkins / JENKINS-42432 All branches (SVN) get built periodically, even if nothing has changed (discard old builds) Change By: recampbell Component/s: multi-branch-project-plugin Component/s: branch-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42432) All branches (SVN) get built periodically, even if nothing has changed (discard old builds)
Title: Message Title recampbell commented on JENKINS-42432 Re: All branches (SVN) get built periodically, even if nothing has changed (discard old builds) This has to do with the MultiBranch project plugin AFAICT Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title recampbell commented on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up What is your orphaned item strategy set to? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42795) Bitbucket scan organization folder fails
Title: Message Title recampbell updated an issue Jenkins / JENKINS-42795 Bitbucket scan organization folder fails Change By: recampbell Labels: scm-api-tidy-scrub Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42774) Add an option to customize Pull Request name
Title: Message Title recampbell updated an issue Jenkins / JENKINS-42774 Add an option to customize Pull Request name Change By: recampbell Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42639) Parameterized trigger hangs when script not approved
Title: Message Title recampbell closed an issue as Incomplete Please provide more details on how to reproduce. ie, what job types are we talking about? Jenkins / JENKINS-42639 Parameterized trigger hangs when script not approved Change By: recampbell Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For mo
[JIRA] (JENKINS-42537) method white/blacklist UX issues - administering them is hard
Title: Message Title recampbell closed an issue as Duplicate Jenkins / JENKINS-42537 method white/blacklist UX issues - administering them is hard Change By: recampbell Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38837) Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Title: Message Title recampbell updated an issue Jenkins / JENKINS-38837 Mutibranch project plugin does not respect "Workspace Root Directory" global configuration Change By: recampbell Labels: regression scm-api-tidy 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-37668) Parent job wait for the downstream job to finish. although the downstream job is Finished.
Title: Message Title recampbell closed an issue as Cannot Reproduce Please reopen with the requested information. Jenkins / JENKINS-37668 Parent job wait for the downstream job to finish. although the downstream job is Finished. Change By: recampbell Status: Open Closed Resolution: Cannot Reproduce 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.
[JIRA] (JENKINS-37668) Parent job wait for the downstream job to finish. although the downstream job is Finished.
Title: Message Title recampbell commented on JENKINS-37668 Re: Parent job wait for the downstream job to finish. although the downstream job is Finished. At this point, this bug report is really more of an incident report than a bug report. To make this actionable, we need steps to reproduce. For example, is there a chain of jobs which can be triggered repeatedly and eventually results in the problem given enough time? Since this is an intermittent bug, we will likely need more diagnostic information (like support bundles) to help us come up with theories of what is happening here. 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-37324) We would like a more meaningful description of a step
Title: Message Title recampbell updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step Change By: recampbell URL: https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/22 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-42296) o.j.p.gl.GoogleUserInfo isn't serializable
Title: Message Title recampbell updated an issue Jenkins / JENKINS-42296 o.j.p.gl.GoogleUserInfo isn't serializable Change By: recampbell Summary: org o . jenkinsci j . plugins p . googlelogin gl .GoogleUserInfo isn't serializable 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-42296) org.jenkinsci.plugins.googlelogin.GoogleUserInfo isn't serializable
Title: Message Title recampbell created an issue Jenkins / JENKINS-42296 org.jenkinsci.plugins.googlelogin.GoogleUserInfo isn't serializable Issue Type: Bug Assignee: recampbell Components: google-login-plugin Created: 2017/Feb/24 3:10 AM Priority: Minor Reporter: recampbell This causes trouble for security realms that want to serialize the user. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title recampbell commented on JENKINS-37324 Re: We would like a more meaningful description of a step For Blue Ocean team to review this: We need examples of what the output would be What steps are supported vs. what aren't How are new steps supported? -> Do plugin authors provide this or must Blue Ocean provide every implementation? --> OK if not for first delivery, but need this for the definition of done. 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-36041) default ldap timeouts are inappropriate
Title: Message Title recampbell stopped work on JENKINS-36041 Change By: recampbell Status: In Progress Open 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-36041) default ldap timeouts are inappropriate
Title: Message Title recampbell assigned an issue to Unassigned Jenkins / JENKINS-36041 default ldap timeouts are inappropriate Change By: recampbell Assignee: Félix Belzunce Arcos 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-41946) Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
Title: Message Title recampbell resolved as Fixed Fixed in credentials-2.1.12 Jenkins / JENKINS-41946 Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes" Change By: recampbell Status: Open Resolved Resolution: Fixed 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...@go
[JIRA] (JENKINS-38723) Stash failed with IOException during scalability testing
Title: Message Title recampbell updated an issue Jenkins / JENKINS-38723 Stash failed with IOException during scalability testing Change By: recampbell Component/s: pipeline Component/s: core 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-38723) Stash failed with IOException during scalability testing
Title: Message Title recampbell updated an issue Jenkins / JENKINS-38723 Stash failed with IOException during scalability testing Change By: recampbell Component/s: workflow-basic-steps-plugin Component/s: pipeline 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-38723) Stash failed with IOException during scalability testing
Title: Message Title recampbell updated an issue Jenkins / JENKINS-38723 Stash failed with IOException during scalability testing Change By: recampbell Issue Type: Improvement Bug 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-42057) Tidy up the GitHub commit statuses
Title: Message Title recampbell commented on JENKINS-42057 Re: Tidy up the GitHub commit statuses This is demo-worthy Patrick Wolf 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-42089) Github API seems to ignore proxy
Title: Message Title recampbell commented on JENKINS-42089 Re: Github API seems to ignore proxy It looks like we correctly apply the proxy, so I'm not sure what could be going on here. However, if this is valid it seems quite severe, so i've bumped it up. 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-42089) Github API seems to ignore proxy
Title: Message Title recampbell updated an issue Jenkins / JENKINS-42089 Github API seems to ignore proxy Change By: recampbell Priority: Trivial Critical 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-34825) Jobs in Folders should show credentials bound in the credential domain
Title: Message Title recampbell edited a comment on JENKINS-34825 Re: Jobs in Folders should show credentials bound in the credential domain BTW, the The workaround is to simply store the credentials at the root level and not try to store them per-folder . 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-34825) Jobs in Folders should show credentials bound in the credential domain
Title: Message Title recampbell commented on JENKINS-34825 Re: Jobs in Folders should show credentials bound in the credential domain BTW, the workaround is to simply store the credentials at the root level. 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-41986) Pipeline view does not have a visual indication that a stage was skipped using the "when" conditional closure
Title: Message Title recampbell commented on JENKINS-41986 Re: Pipeline view does not have a visual indication that a stage was skipped using the "when" conditional closure Hello. We don't plan on adding new features to this plugin. Instead, we are focusing on making Blue Ocean the best way to view your pipeline status. Please give Blue Ocean and let us know what needs improvement there! 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-41986) Pipeline view does not have a visual indication that a stage was skipped using the "when" conditional closure
Title: Message Title recampbell closed an issue as Won't Fix Jenkins / JENKINS-41986 Pipeline view does not have a visual indication that a stage was skipped using the "when" conditional closure Change By: recampbell Status: Open Closed Resolution: Won't Fix 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-41447) Display all commiters in stage-view mouseover instead of "... and others"
Title: Message Title recampbell commented on JENKINS-41447 Re: Display all commiters in stage-view mouseover instead of "... and others" Hello. We don't plan on adding new features to this plugin. Instead, we are focusing on making Blue Ocean the best way to view your pipeline status. Please give Blue Ocean and let us know what needs improvement there! 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-41447) Display all commiters in stage-view mouseover instead of "... and others"
Title: Message Title recampbell closed an issue as Won't Fix Jenkins / JENKINS-41447 Display all commiters in stage-view mouseover instead of "... and others" Change By: recampbell Status: Open Closed Resolution: Won't Fix 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-41815) Expose event origin to listeners
Title: Message Title recampbell commented on JENKINS-41815 Re: Expose event origin to listeners I can't find the PR? 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-41774) Pipeline executes "retry" when pipeline is aborted
Title: Message Title recampbell closed an issue as Duplicate Fix is in review on JENKINS-41276 Jenkins / JENKINS-41774 Pipeline executes "retry" when pipeline is aborted Change By: recampbell Status: Open Closed Resolution: Duplicate 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-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder'
Title: Message Title recampbell commented on JENKINS-41785 Re: Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder' Thanks for the detailed steps to reproduce. Stephen Connolly, I think we need to prioritize this one. 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-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder'
Title: Message Title recampbell assigned an issue to Stephen Connolly Jenkins / JENKINS-41785 Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder' Change By: recampbell Assignee: Stephen Connolly 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-41800) BitBucket organization folder not displaying after SCM 2.0
Title: Message Title recampbell commented on JENKINS-41800 Re: BitBucket organization folder not displaying after SCM 2.0 This should be fixed after you scan your repository. is it? 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-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.
Title: Message Title recampbell closed an issue as Incomplete Please reopen with step by step instructions to reproduce the problem and clear description of what you expect to happen. Jenkins / JENKINS-41805 Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace. Change By: recampbell Status: Open Closed Resolution: Incomplete 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
[JIRA] (JENKINS-41807) 100% CPU load on 1 (of 8) core
Title: Message Title recampbell closed an issue as Incomplete Please provide steps to reproduce the problem or at the very least a thread dump. Jenkins / JENKINS-41807 100% CPU load on 1 (of 8) core Change By: recampbell Status: Open Closed Resolution: Incomplete 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://grou
[JIRA] (JENKINS-41813) bitbucket branch source folder no longer can have views
Title: Message Title recampbell commented on JENKINS-41813 Re: bitbucket branch source folder no longer can have views My understanding is that this "view" was an accidental feature and is not a supported use-case. Stephen Connolly, please confirm. 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-41813) bitbucket branch source folder no longer can have views
Title: Message Title recampbell assigned an issue to Stephen Connolly Jenkins / JENKINS-41813 bitbucket branch source folder no longer can have views Change By: recampbell Assignee: Antonio Muñiz Stephen Connolly 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-41820) Builds are not triggered on hook notifications
Title: Message Title recampbell commented on JENKINS-41820 Re: Builds are not triggered on hook notifications Please provide steps to reproduce. Can you check on the GitHub end to see if the hook is configured. 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-41820) Builds are not triggered on hook notifications
Title: Message Title recampbell assigned an issue to Stephen Connolly Jenkins / JENKINS-41820 Builds are not triggered on hook notifications Change By: recampbell Assignee: Stephen Connolly 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-41826) GitHub Organization Pull-Request URL is incorrect
Title: Message Title recampbell commented on JENKINS-41826 Re: GitHub Organization Pull-Request URL is incorrect Stephen Connolly, concerned we have regressed a bug fix for JENKINS-34692. Can you check? 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-41826) GitHub Organization Pull-Request URL is incorrect
Title: Message Title recampbell assigned an issue to Stephen Connolly Jenkins / JENKINS-41826 GitHub Organization Pull-Request URL is incorrect Change By: recampbell Assignee: Matthew DeTullio Stephen Connolly 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-41826) GitHub Organization Pull-Request URL is incorrect
Title: Message Title recampbell updated an issue Jenkins / JENKINS-41826 GitHub Organization Pull-Request URL is incorrect Change By: recampbell Component/s: github-branch-source-plugin 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-41826) GitHub Organization Pull-Request URL is incorrect
Title: Message Title recampbell updated an issue Jenkins / JENKINS-41826 GitHub Organization Pull-Request URL is incorrect Change By: recampbell Component/s: github-organization-folder-plugin Component/s: multi-branch-project-plugin 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-40874) Missing ErrorAction after Jenkins restart
Title: Message Title recampbell commented on JENKINS-40874 Re: Missing ErrorAction after Jenkins restart Sam Van Oort, this looks like a bug in Bismuth, no? If so, something for a followup with the other issues in this area after your current work. 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-28010) Use Google Apps group for Authorization
Title: Message Title recampbell commented on JENKINS-28010 Re: Use Google Apps group for Authorization Thinking about it more, its unclear to me if people would prefer to get the list of groups or organizational units. I suppose that the groups are what are requested here. Perhaps populating the orgunit would be a separate feature request. I notice that the G Suite API's also have notions of roles. I really have no clue what the use-cases and expectations are. Just populating the groups as principles seems like it would address the crux of this request. Then you can go crazy with matrix-auth AFAICT. 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-41407) Bitbucket Pipeline display name should never be calculated
Title: Message Title recampbell assigned an issue to Stephen Connolly Jenkins / JENKINS-41407 Bitbucket Pipeline display name should never be calculated Change By: recampbell Assignee: Antonio Muñiz Stephen Connolly 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-27745) A `device_id` and `device_name` should be provided to allow private IP.
Title: Message Title recampbell edited a comment on JENKINS-27745 Re: A `device_id` and `device_name` should be provided to allow private IP. Or this? http://stackoverflow.com/questions/ 10296681 24736168 / is error - there invalid - an request - oauth device - 2 id - 0 and - provider device - implementation name - in are - java required - not for - oauth private - client ip 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-27745) A `device_id` and `device_name` should be provided to allow private IP.
Title: Message Title recampbell commented on JENKINS-27745 Re: A `device_id` and `device_name` should be provided to allow private IP. Or this? http://stackoverflow.com/questions/10296681/is-there-an-oauth-2-0-provider-implementation-in-java-not-oauth-client 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-27467) Also authenticate users using Jenkins built-in database (aka "On the side mode")
Title: Message Title recampbell edited a comment on JENKINS-27467 Re: Also authenticate users using Jenkins built-in database (aka "On the side mode") OK, so in this case, it sounds like you want Google Apps to be your primary source of truth but then have the built-in database available for users who are not in Google Apps, right?So perhaps the right way to do this is to have add an option to the Google Oauth Security Realm which allows you to "Also authenticate users using the Jenkins User database". In this case, the login screen would show a username password login with a "Login with Google" button below it.This is *not* how the "on the side" feature works in the old OpenID plugin. In that case, the user must explicitly configure their account to allow access using OpenID. But that doesn't seem like what you want in the use-case you are describing. You want someone known as "u...@mygoogledomain.com" to be able to authenticate as that identity on Jenkins using their Google session without having to take special steps prior. And I imagine you want their Jenkins account to automatically be created if it does not exist. Finally, I think you want them to lose access to Jenkins if you disable their account in your Google Apps domain.So this is not exactly like the "On the side" feature. And what is especially important is that Google Apps users lose access to Jenkins once you decommission them in Google Apps.The more I think about it, this is going to require a bit of work and especially thought to make sure we don't accidentally prevent logins somehow or (even worse) open up some kind of security hole.Given the risks, the work to get this right and the relatively low votes on this issue, I think its safe to say we have no plans in the foreseeable future to add this feature. This may change if someone steps up to do the work or the demand increases.I will say that if someone actually volunteers to add this change, I think it may be possible by creating another plugin which somehow wraps this one. This would be much lower risk than adding the feature to this plugin. If someone wants this enough to do the investigation to tell me what they need, I can make changes to support that. Add Comment
[JIRA] (JENKINS-27467) Also authenticate users using Jenkins built-in database (aka "On the side mode")
Title: Message Title recampbell updated an issue Jenkins / JENKINS-27467 Also authenticate users using Jenkins built-in database (aka "On the side mode") Change By: recampbell Summary: Also authenticate users using Jenkins built-in database (aka "On the side mode") 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-27467) Also authenticate users using Jenkins built-in database
Title: Message Title recampbell updated an issue Jenkins / JENKINS-27467 Also authenticate users using Jenkins built-in database Change By: recampbell Summary: Add an "On the side" mode similar to the OpenID plugin Also authenticate users using Jenkins built-in database 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-27467) Add an "On the side" mode similar to the OpenID plugin
Title: Message Title recampbell commented on JENKINS-27467 Re: Add an "On the side" mode similar to the OpenID plugin OK, so in this case, it sounds like you want Google Apps to be your primary source of truth but then have the built-in database available for users who are not in Google Apps, right? So perhaps the right way to do this is to have add an option to the Google Oauth Security Realm which allows you to "Also authenticate users using the Jenkins User database". In this case, the login screen would show a username password login with a "Login with Google" button below it. This is not how the "on the side" feature works in the old OpenID plugin. In that case, the user must explicitly configure their account to allow access using OpenID. But that doesn't seem like what you want in the use-case you are describing. You want someone known as "u...@mygoogledomain.com" to be able to authenticate as that identity on Jenkins using their Google session without having to take special steps prior. And I imagine you want their Jenkins account to automatically be created if it does not exist. Finally, I think you want them to lose access to Jenkins if you disable their account in your Google Apps domain. So this is not exactly like the "On the side" feature. And what is especially important is that Google Apps users lose access to Jenkins once you decommission them in Google Apps. The more I think about it, this is going to require a bit of work and especially thought to make sure we don't accidentally prevent logins somehow or (even worse) open up some kind of security hole. Given the risks, the work to get this right and the relatively low votes on this issue, I think its safe to say we have no plans in the foreseeable future to add this feature. This may change if someone steps up to do the work or the demand increases. I will say that if someone actually volunteers to add this change, I think it may be possible by creating another plugin which somehow wraps this one. If someone wants this enough to do the investigation to tell me what they need, I can make changes to support that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-s
[JIRA] (JENKINS-27467) Add an "On the side" mode similar to the OpenID plugin
Title: Message Title recampbell closed an issue as Won't Fix Jenkins / JENKINS-27467 Add an "On the side" mode similar to the OpenID plugin Change By: recampbell Status: Open Closed Resolution: Won't Fix 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-27745) A `device_id` and `device_name` should be provided to allow private IP.
Title: Message Title recampbell commented on JENKINS-27745 Re: A `device_id` and `device_name` should be provided to allow private IP. Uh, OK. Anyone have a link to the docs for these? I guess we could just add them to the form and pass them through. 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-28010) Use Google Apps group for Authorization
Title: Message Title recampbell edited a comment on JENKINS-28010 Re: Use Google Apps group for Authorization As to the first commenter, you are doing something wrong. Just enter a valid Google apps domain and you will get a 401 if you select a user who isn't a member of that domain. Please open a seperate bug report with steps to reproduce if that doesn't work. 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-28010) Use Google Apps group for Authorization
Title: Message Title recampbell commented on JENKINS-28010 Re: Use Google Apps group for Authorization As to the first commenter, you are doing something wrong. Just enter a valid Google apps domain and you will get a 401 if you select a user who isn't a member of that domain. 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-28010) Use Google Apps group for Authorization
Title: Message Title recampbell edited a comment on JENKINS-28010 Re: Use Google Apps group for Authorization Yeah, I've thought about this. I guess this would be per-domain. Like "cloudbees.com:engineering" for a group called "engineering" in the cloudbees.com domain. This would just be a list of principle's principals for the user which you could then map into an Authorization realm like matrix-auth or cloudbees RBAC.Perhaps this can be requested as a part of the oauth dance or as an optional followup API request.If you want this to happen faster, please confirm the above information and provide me with links to which API's I should use. Or provide a patch! #lazyoss 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-28152) Better error messages
Title: Message Title recampbell commented on JENKINS-28152 Re: Better error messages I think the current experience is correct. Jenkins is broken because your environment is broken. Perhaps the generic Jenkins error page could be improved, but I think even that directs users in the right direction. 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-28152) Better error messages
Title: Message Title recampbell closed an issue as Not A Defect Jenkins / JENKINS-28152 Better error messages Change By: recampbell Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35124) Allow limiting by domain without google apps
Title: Message Title recampbell closed an issue as Fixed This is present in 1.3 Jenkins / JENKINS-35124 Allow limiting by domain without google apps Change By: recampbell Status: Open Closed Resolution: Fixed 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-40976) NullPointerException in soFinishLogin()
Title: Message Title recampbell closed an issue as Incomplete Please provide steps to reproduce with expected and actual experience. Jenkins / JENKINS-40976 NullPointerException in soFinishLogin() Change By: recampbell Status: Open Closed Resolution: Incomplete 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
[JIRA] (JENKINS-28010) Use Google Apps group for Authorization
Title: Message Title recampbell commented on JENKINS-28010 Re: Use Google Apps group for Authorization Yeah, I've thought about this. I guess this would be per-domain. Like "cloudbees.com:engineering" for a group called "engineering" in the cloudbees.com domain. This would just be a list of principle's for the user which you could then map into an Authorization realm like matrix-auth or cloudbees RBAC. Perhaps this can be requested as a part of the oauth dance or as an optional followup API request. If you want this to happen faster, please confirm the above information and provide me with links to which API's I should use. Or provide a patch! #lazyoss 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-32536) Allow for multiple domains
Title: Message Title recampbell closed an issue as Fixed Added in 1.3 thanks to https://github.com/gkrat https://github.com/jenkinsci/google-login-plugin/commit/6fea3b29a0c35301ed16024e4d2f07d2a8ab402b Jenkins / JENKINS-32536 Allow for multiple domains Change By: recampbell Status: Open Closed Resolution: Fixed 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...@googl
[JIRA] (JENKINS-31362) Google authentication with Swarm plugin
Title: Message Title recampbell closed an issue as Not A Defect This plugin doesn't authenticate you with your google username & password. Just set an API key on your user for this use-case. Please google Jenkins API key. Jenkins / JENKINS-31362 Google authentication with Swarm plugin Change By: recampbell Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an ema
[JIRA] (JENKINS-37607) Get user name from google?
Title: Message Title recampbell closed an issue as Not A Defect Jenkins / JENKINS-37607 Get user name from google? Change By: recampbell Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36706) When OAuth session expires, an ugly NPE is shown in Jenkins
Title: Message Title recampbell commented on JENKINS-36706 Re: When OAuth session expires, an ugly NPE is shown in Jenkins OK, I was able to reproduce this by restarting Jenkins instead of step 5 above. And you were nice enough to tell me exactly where the bug was, so thanks for that. The full stack trace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.S
[JIRA] (JENKINS-36706) When OAuth session expires, an ugly NPE is shown in Jenkins
Title: Message Title recampbell commented on JENKINS-36706 Re: When OAuth session expires, an ugly NPE is shown in Jenkins What would make this bug report more useful: Cut and paste the entire error message. Your screen shot cuts off the most important part and I can't cut&paste this into my editor to find the relevant lines. Provide actual steps to reproduce. I have no idea what you mean by "oauth session expires" I'm just guessing, but I think this is? Login to google with at least two accounts Setup the security realm with a valid oauth token and secret Attempt to login to Jenkins using the login link in the upper right hand side You are presented with a list of accounts to use for login Wait for some long period? Finally select the account you want to login with Is that what you mean? 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 G
[JIRA] (JENKINS-33286) logging-out with google-login-plugin is not work
Title: Message Title recampbell closed an issue as Fixed Fixed in 1.3 Jenkins / JENKINS-33286 logging-out with google-login-plugin is not work Change By: recampbell Status: In Progress Closed Resolution: Fixed 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-37749) Client-id and Secret gets overwritten by username and password hash
Title: Message Title recampbell closed an issue as Fixed Fixed in 1.3 Jenkins / JENKINS-37749 Client-id and Secret gets overwritten by username and password hash Change By: recampbell Status: In Progress Closed Resolution: Fixed 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-36483) Unable to login with google-login plugin with 401 error
Title: Message Title recampbell edited a comment on JENKINS-36483 Re: Unable to login with google-login plugin with 401 error Well, Jenkins is returning a 401 because the domain of Google account selected by the user doesn't match the domain you have provided. However, I think you have a space in the Google Apps Domain field.Or at least I've reproduced this problem by adding trailing spaces. I'll just clean that input up. 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-36483) Unable to login with google-login plugin with 401 error
Title: Message Title recampbell resolved as Fixed resolved toward 1.4 Jenkins / JENKINS-36483 Unable to login with google-login plugin with 401 error Change By: recampbell Status: Open Resolved Resolution: Fixed 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-36483) Unable to login with google-login plugin with 401 error
Title: Message Title recampbell edited a comment on JENKINS-36483 Re: Unable to login with google-login plugin with 401 error I think you have a space in the Google Apps Domain field.I'll just clean that input up. 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-36483) Unable to login with google-login plugin with 401 error
Title: Message Title recampbell commented on JENKINS-36483 Re: Unable to login with google-login plugin with 401 error I think you have a space in the Google Apps Domain field. I'll just clean that input up. 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-27117) google login plugin not working
Title: Message Title recampbell edited a comment on JENKINS-27117 Re: google login plugin not working I'm fairly certain that this is some kind of configuration problem. I tried to reproduce this by changing my Jenkins location to something invalid, but this gave me a reasonable error message from Google, not this NPE. It seems like Google is returning an error code, but that Google's own oauth client isn't able to parse this correctly. Maybe some weird servlet api issue getting in the way. For the record, I don't think this has anything to do with your Google apps domain configuration.To reproduce this effectively, I'm going to need to know the following information from someone experiencing the problem:* Jenkins Location URL* The "Authorized redirect URIs" from your google "Client ID for Web application" in the Google oauth console. * Servlet container, ie, Tomcat or just the default jetty or what? Ideally this plugin would provide better input validation or diagnostics in the logs to help you determine the problem. 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-27117) google login plugin not working
Title: Message Title recampbell edited a comment on JENKINS-27117 Re: google login plugin not working I'm fairly certain that this is some kind of configuration problem. I tried to reproduce this by changing my Jenkins location to something invalid, but this gave me a reasonable error message from Google, not this NPE.For the record, I don't think this has anything to do with your Google apps domain configuration.To reproduce this effectively, I'm going to need to know the following information from someone experiencing the problem:* Jenkins Location URL* The "Authorized redirect URIs" from your google "Client ID for Web application" in the Google oauth console. Ideally this plugin would provide better input validation or diagnostics in the logs to help you determine the problem. 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-27117) google login plugin not working
Title: Message Title recampbell closed an issue as Cannot Reproduce I'm fairly certain that this is some kind of configuration problem. I tried to reproduce this by changing my Jenkins location to something invalid, but this gave me a reasonable error message from Google, not this NPE. For the record, I don't think this has anything to do with your Google apps domain configuration. To reproduce this effectively, I'm going to need to know the following information from someone experiencing the problem: Jenkins Location URL The "Authorized redirect URIs" from your google "Client ID for Web application" in the Google oauth console. Jenkins / JENKINS-27117 google login plugin not working Change By: recampbell Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41711) Prevent installation of plugins with unresolvable dependencies
Title: Message Title recampbell updated an issue Jenkins / JENKINS-41711 Prevent installation of plugins with unresolvable dependencies Change By: recampbell The update center and setup wizard allows users to install plugins with unresolved dependencies. In this case, the update center meta-data presents a plugin having a dependency which cannot be resolved from any available update center. The user is presently able to install the plugin, but when Jenkins starts up, it will fail to initialize due to the unresolved dependencies.The setupwizard and update center should not allow the user to screw up their installation and thereby protect the user from mistakes or time-delays in publishing dependencies. Instead, the setupwizard and the update center should display warnings that the plugin dependencies cannot be satisified and which dependencies are missing. 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 "J
[JIRA] (JENKINS-41711) Prevent installation of plugins with unresolvable dependencies
Title: Message Title recampbell updated an issue Jenkins / JENKINS-41711 Prevent installation of plugins with unresolvable dependencies Change By: recampbell Issue Type: Bug Improvement 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-41711) Prevent installation of plugins with unresolvable dependencies
Title: Message Title recampbell created an issue Jenkins / JENKINS-41711 Prevent installation of plugins with unresolvable dependencies Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Feb/03 6:13 PM Labels: robustness Priority: Major Reporter: recampbell The update center and setup wizard allows users to install plugins with unresolved dependencies. In this case, the update center meta-data presents a plugin having a dependency which cannot be resolved from any available update center. The user is presently able to install the plugin, but when Jenkins starts up, it will fail to initialize due to the unresolved dependencies. The setupwizard and update center should not allow the user to screw up their installation and thereby protect the user from mistakes or time-delays in publishing dependencies. Add Comment
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title recampbell reopened an issue Not a duplicate, but clearly related. Jenkins / JENKINS-40899 Transitive plugin dependencies not correctly checked when using snapshots Change By: recampbell Resolution: Fixed Status: Closed Reopened 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
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title recampbell closed an issue as Fixed Alvaro, this looks like a clear duplicate, please reopen if not. Jenkins / JENKINS-40899 Transitive plugin dependencies not correctly checked when using snapshots Change By: recampbell Status: Open Closed Resolution: Fixed 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, v
[JIRA] (JENKINS-41398) Bitbucket Branch Source Plugin 2.0.1 Won't load
Title: Message Title recampbell resolved as Fixed This version has been blocked, so this issue is resolved. Jenkins / JENKINS-41398 Bitbucket Branch Source Plugin 2.0.1 Won't load Change By: recampbell Status: Open Resolved Resolution: Fixed 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-41580) Branches gone missing after SCM-API upgrades applied
Title: Message Title
recampbell edited a comment on JENKINS-41580
Re: Branches gone missing after SCM-API upgrades applied
{code} - Jan 30, 2017 2:15:36 PM org.apache.commons.httpclient.HttpMethodDirector processWWWAuthChallengeINFO: Failure authenticating with BASIC 'Bitbucket.org HTTP'@bitbucket.org:443Jan 30, 2017 2:15:36 PM hudson.model.listeners.ItemListener forAllWARNING: failed to send event to listener of class com.cloudbees.jenkins.plugins.bitbucket.CustomComputedFolderItemListenercom.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: Unauthorized.{code} It looks to me like we can't rebuild the state because we can't authenticate to Bitbucket. Are the BitBucket credentials still present and valid? -Ah nevermind, this bug is about GitHub, not BitBucket, sorry.
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-41580) Branches gone missing after SCM-API upgrades applied
Title: Message Title recampbell edited a comment on JENKINS-41580 Re: Branches gone missing after SCM-API upgrades applied - It looks to me like we can't rebuild the state because we can't authenticate to Bitbucket. Are the BitBucket credentials still present and valid? -Ah nevermind, this bug is about GitHub, not BitBucket, sorry. 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-41580) Branches gone missing after SCM-API upgrades applied
Title: Message Title recampbell commented on JENKINS-41580 Re: Branches gone missing after SCM-API upgrades applied Jan 30, 2017 2:15:36 PM org.apache.commons.httpclient.HttpMethodDirector processWWWAuthChallenge INFO: Failure authenticating with BASIC 'Bitbucket.org HTTP'@bitbucket.org:443 Jan 30, 2017 2:15:36 PM hudson.model.listeners.ItemListener forAll WARNING: failed to send event to listener of class com.cloudbees.jenkins.plugins.bitbucket.CustomComputedFolderItemListener com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: Unauthorized. It looks to me like we can't rebuild the state because we can't authenticate to Bitbucket. Are the BitBucket credentials still present and valid? 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-41580) Branches gone missing after SCM-API upgrades applied
Title: Message Title recampbell commented on JENKINS-41580 Re: Branches gone missing after SCM-API upgrades applied We really need the Jenkins logs. Can you just attach these? I guess they were excluded from the support bundle because you didn't include the node logs. 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-41551) Deadlock between support core plugin and workflow-step-api-plugin
Title: Message Title recampbell updated an issue Jenkins / JENKINS-41551 Deadlock between support core plugin and workflow-step-api-plugin Change By: recampbell Issue Type: Improvement Bug 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-40652) origin pr builds not treated as trusted
Title: Message Title recampbell assigned an issue to Stephen Connolly Jenkins / JENKINS-40652 origin pr builds not treated as trusted Change By: recampbell Assignee: Stephen Connolly 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-40652) origin pr builds not treated as trusted
Title: Message Title recampbell commented on JENKINS-40652 Re: origin pr builds not treated as trusted Provisionally marked as SCM 2.0 Upgrade Fallout until we determine otherwise. 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-40652) origin pr builds not treated as trusted
Title: Message Title recampbell edited a comment on JENKINS-40652 Re: origin pr builds not treated as trusted Was this issue present in github-branch-source-plugin prior to 2.0 ?We are trying to determine if this is a regression introduced by the github-branch-source-plugin 2.0 beta releases. 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-40652) origin pr builds not treated as trusted
Title: Message Title recampbell commented on JENKINS-40652 Re: origin pr builds not treated as trusted Was this issue present in github-branch-source-plugin prior to 2.0 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-37311) "logout" link doesn't work
Title: Message Title recampbell commented on JENKINS-37311 Re: "logout" link doesn't work Related GitHub Oauth bug is fixed, I wonder if this is a quick fix. 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-38548) Freestyle Job hangs when running on a JNLP Mac OSX agent
Title: Message Title recampbell closed an issue as Cannot Reproduce Seems to be an llvm bug https://llvm.org/bugs/show_bug.cgi?id=30764 Jenkins / JENKINS-38548 Freestyle Job hangs when running on a JNLP Mac OSX agent Change By: recampbell Status: Open Closed Resolution: Cannot Reproduce 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 opt
[JIRA] (JENKINS-34712) "master is offline" preventing Pipeline from executing
Title: Message Title recampbell updated an issue Jenkins / JENKINS-34712 "master is offline" preventing Pipeline from executing Change By: recampbell Labels: pipeline pipeline-hangs robustness 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.
