[JIRA] (JENKINS-57683) ClassCastException in git plugin on GitHub branch scan
Title: Message Title Mark Waite updated JENKINS-57683 Jenkins / JENKINS-57683 ClassCastException in git plugin on GitHub branch scan Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.12068.1558842180058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in git plugin on GitHub branch scan
Title: Message Title Mark Waite started work on JENKINS-57683 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.12067.1558842120104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46094) "Checkout over SSH" fails the build since it still uses HTTPS urls
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-46094 "Checkout over SSH" fails the build since it still uses HTTPS urls Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184329.1502287878000.12056.1558839960663%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title Scott Hebert updated JENKINS-57642 Jenkins / JENKINS-57642 Wrong parameter type and squashing its content when trigger a job Change By: Scott Hebert Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199573.1558615641000.12053.1558834080195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title Scott Hebert commented on JENKINS-57642 Re: Wrong parameter type and squashing its content when trigger a job Pavel Janoušekakostadinov You can try out a patched version with a fix here: https://ci.jenkins.io/job/Plugins/job/jms-messaging-plugin/job/PR-124/1/artifact/target/jms-messaging.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199573.1558615641000.12050.1558833060186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in git plugin on GitHub branch scan
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57683
ClassCastException in git plugin on GitHub branch scan
Change By:
Mark Waite
Git plugin 4.0 pre-release reports a class cast exception when scanning in a multibranch pipeline definition for the hello-world-plugin.The stack trace is:{noformat}Started by user Mark Waite[Sat May 25 13:03:00 MDT 2019] Starting branch indexing...13:03:00 Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password)Examining MarkEWaite/hello-world-pluginERROR: [Sat May 25 13:03:01 MDT 2019] Could not fetch branches from source 8b33b746-db40-4839-901f-d94e4a4f3148java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)[Sat May 25 13:03:01 MDT 2019] Finished branch indexing. Indexing took 0.36 secFATAL: Failed to recompute children of Hello World Plugin Folder » hello world pipeline (GitHub)java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at
[JIRA] (JENKINS-57683) ClassCastException in git plugin on GitHub branch scan
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57683 ClassCastException in git plugin on GitHub branch scan Change By: Mark Waite Summary: ClassCastException in git plugin on GitHub Branch Source scanning repository branch scan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.12047.1558825260075%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57686) A list of improvements in GitLab Server Configuration
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57686 A list of improvements in GitLab Server Configuration Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin, gitlab-plugin Created: 2019-05-25 22:53 Labels: gsoc-2019 Priority: Major Reporter: Parichay Barpanda 1) Add support for generating personal access token via username/password credentials like GitHub Plugin 2) Add support for GitLab Ultimate (self hosted) and Gold (saas) with premium support 3) Add Java 8 functional interfaces for behavioural design pattern Add Comment
[JIRA] (JENKINS-57685) Add button for Server config doesn't work
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-57685 Add button for Server config doesn't work Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-05-25 22:48 Labels: gsoc-2019 Priority: Blocker Reporter: Parichay Barpanda The Add dropdown in the Global Configuration should show an option to add server, clicking which a set of form fields will be shown to give server information. UI has been implemented like Gitea Plugin but doesn't work for some reason. Add Comment
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Parichay Barpanda updated an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Change By:
Parichay Barpanda
For the GSoC project [gitlab-branch-source-plugin|https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+gitlab-branch-source-plugin] the student is requesting a new repo be created titled "gitlab-branch-pluginDetailed reasoning for this is here: 2) I read the documentation of {{SCM API}} and {{Branch API}} Plugins to understand the classes needs to be implemented in {{GitLab Branch Source Plugin}}. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it.3) I have been studing the codebases of {{ArgelBargel's GitLab Branch Source Plugin}}, {{GitHub Branch Source Plugin}} and {{Gitea Plugin}}. My takeaway was {{GitLab BS}} has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example,i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like {{SCMSource}} has been broken down to other sub classes , {{SCMHeadCategory}} has some different implementation, {{SCMFileSystem}} is not implemented, APIs implementation also needs to be changed and the list goes on..ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new {{GitLab Branch Source Plugin}} which will be heavily inspired from {{Gitea Plugin}} (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from {{GitLab Branch Source}} and {{GitHub Branch Source}} Plugins.iii) I will send my compelete complete list of reasons not to develop the existing {{GitLab Branch Source}} Plugin.
Add Comment
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Parichay Barpanda updated an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Change By:
Parichay Barpanda
For the GSoC project [gitlab-branch-source-plugin|https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+gitlab-branch-source-plugin] the student is requesting a new repo be created titled "gitlab-branch-plugin Detailed reasoning for this is here: 2) I read the documentation of {{SCM API}} and {{Branch API}} Plugins to understand the classes needs to be implemented in {{GitLab Branch Source Plugin}}. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it.3) I have been studing the codebases of {{ArgelBargel's GitLab Branch Source Plugin}}, {{GitHub Branch Source Plugin}} and {{Gitea Plugin}}. My takeaway was {{GitLab BS}} has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example,i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like {{SCMSource}} has been broken down to other sub classes , {{SCMHeadCategory}} has some different implementation, {{SCMFileSystem}} is not implemented, APIs implementation also needs to be changed and the list goes on..ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new {{GitLab Branch Source Plugin}} which will be heavily inspired from {{Gitea Plugin}} (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from {{GitLab Branch Source}} and {{GitHub Branch Source}} Plugins.iii) I will send my compelete list of reasons not to develop the existing {{GitLab Branch Source}} Plugin.
Add Comment
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin GitLab Branch Source Plugin has been created here - [#https://github.com/baymac/gitlab-branch-source-plugin] The repository will also contain server configuration implementation and later moved into a different plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.12031.1558821120277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57677 Create new repo for GSoC gitlab-branch-source-plugin Change By: Parichay Barpanda URL: https://github.com/baymac/gitlab-branch-source-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.12035.1558821120369%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57677 Create new repo for GSoC gitlab-branch-source-plugin Change By: Parichay Barpanda Labels: gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.12027.1558820820186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57684) PluginWrapper#whichPlugin does not work in tests
Title: Message Title
Daniel Beck updated an issue
Jenkins / JENKINS-57684
PluginWrapper#whichPlugin does not work in tests
Change By:
Daniel Beck
{{whichPlugin}} will always return {{null}} in tests: The {{PluginWrapper}}'s class loader is the expected one, but the actual one for plugin classes is surefire's.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199619.1558819501000.12024.1558819620117%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57684) PluginWrapper#whichPlugin does not work in tests
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-57684 PluginWrapper#whichPlugin does not work in tests Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-25 21:25 Priority: Minor Reporter: Daniel Beck The PluginWrapper's class loader is the expected one, but the actual one for plugin classes is surefire's. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55110) BFA 1.21.0 fails to create a failure cause / scan jobs
Title: Message Title Tim Jacomb commented on JENKINS-55110 Re: BFA 1.21.0 fails to create a failure cause / scan jobs I've had a brief look at this so far, you don't even need to upgrade by the looks of it. Configure the plugin and restart it makes it work =/ Some problem with jackson, but hard to debug due to anytime you make a change and restart it fixes it... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196171.1544462893000.12016.1558817280163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47882) Unable to connect MongoDB with MONGODB-CR authentication
Title: Message Title Tim Jacomb updated JENKINS-47882 Jenkins / JENKINS-47882 Unable to connect MongoDB with MONGODB-CR authentication Change By: Tim Jacomb Status: In Review Closed Resolution: Fixed Released As: 1.21.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186399.1510127485000.12007.1558817160460%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in GitHub Branch Source scanning repository
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57683
ClassCastException in GitHub Branch Source scanning repository
Change By:
Mark Waite
Git plugin 4.0 pre-release reports a class cast exception when scanning in a multibranch pipeline definition for the hello-world-plugin.The stack trace is:{noformat}Started by user Mark Waite[Sat May 25 13:03:00 MDT 2019] Starting branch indexing...13:03:00 Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password)Examining MarkEWaite/hello-world-pluginERROR: [Sat May 25 13:03:01 MDT 2019] Could not fetch branches from source 8b33b746-db40-4839-901f-d94e4a4f3148java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)[Sat May 25 13:03:01 MDT 2019] Finished branch indexing. Indexing took 0.36 secFATAL: Failed to recompute children of Hello World Plugin Folder » hello world pipeline (GitHub)java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at
[JIRA] (JENKINS-57683) ClassCastException in GitHub Branch Source scanning repository
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57683
ClassCastException in GitHub Branch Source scanning repository
Change By:
Mark Waite
GitHub Branch Source Git plugin 2 4 . 5.3 0 pre-release reports a class cast exception when scanning in a multibranch pipeline definition for the hello-world-plugin.The stack trace is:{noformat}Started by user Mark Waite[Sat May 25 13:03:00 MDT 2019] Starting branch indexing...13:03:00 Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password)Examining MarkEWaite/hello-world-pluginERROR: [Sat May 25 13:03:01 MDT 2019] Could not fetch branches from source 8b33b746-db40-4839-901f-d94e4a4f3148java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)[Sat May 25 13:03:01 MDT 2019] Finished branch indexing. Indexing took 0.36 secFATAL: Failed to recompute children of Hello World Plugin Folder » hello world pipeline (GitHub)java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164)
[JIRA] (JENKINS-57683) ClassCastException in GitHub Branch Source scanning repository
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-57683 ClassCastException in GitHub Branch Source scanning repository Change By: Mark Waite Assignee: Liam Newman Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.12003.1558816200096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in GitHub Branch Source scanning repository
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57683 ClassCastException in GitHub Branch Source scanning repository Change By: Mark Waite Component/s: git-plugin Component/s: github-branch-source-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.12001.1558816140099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57543) Support PostgreSQL database
Title: Message Title Cyrille Le Clerc commented on JENKINS-57543 Re: Support PostgreSQL database Download: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.6.15-beta-1/pipeline-maven-3.6.15-beta-1.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199451.1558248334000.11999.1558816020076%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change
Title: Message Title Wisen Tanasa closed an issue as Won't Fix Jenkins / JENKINS-57620 JIRA Trigger not triggering on status change Change By: Wisen Tanasa Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199548.1558551175000.11998.1558815600197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) How to mapping Custom Field key in JIRA trigger plugin
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: How to mapping Custom Field key in JIRA trigger plugin Can you confirm if this is "Multi User Picker" field? It looks like an array to me. If it is, this is currently not supported yet. The currently supported fields can be seen at CustomFieldParameterResolverTest file. We welcome contribution, feel free to submit a pull request to support this feature. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.11992.1558815480229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-57630 Support Multi User Picker custom field parameter mapping Change By: Wisen Tanasa Summary: How to Support Multi User Picker custom field parameter mapping Custom Field key in JIRA trigger plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.11994.1558815480248%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-57630 Support Multi User Picker custom field parameter mapping Change By: Wisen Tanasa Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.11996.1558815480276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in GitHub Branch Source scanning repository
Title: Message Title Mark Waite assigned an issue to Liam Newman Jenkins / JENKINS-57683 ClassCastException in GitHub Branch Source scanning repository Change By: Mark Waite Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.11990.1558813920163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in GitHub Branch Source scanning repository
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57683
ClassCastException in GitHub Branch Source scanning repository
Change By:
Mark Waite
GitHub Branch Source plugin 2.5.3 reports a class cast exception when scanning in a multibranch pipeline definition for the hello-world-plugin.The stack trace is:{noformat}Started by user Mark Waite[Sat May 25 13:03:00 MDT 2019] Starting branch indexing...13:03:00 Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password)Examining MarkEWaite/hello-world-pluginERROR: [Sat May 25 13:03:01 MDT 2019] Could not fetch branches from source 8b33b746-db40-4839-901f-d94e4a4f3148java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)[Sat May 25 13:03:01 MDT 2019] Finished branch indexing. Indexing took 0.36 secFATAL: Failed to recompute children of Hello World Plugin Folder » hello world pipeline (GitHub)java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at
[JIRA] (JENKINS-57683) ClassCastException in GitHub Branch Source scanning repository
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57683
ClassCastException in GitHub Branch Source scanning repository
Change By:
Mark Waite
GitHub Branch Source plugin 2.5.3 reports a class cast exception when scanning in a multibranch pipeline definition for the hello-world-plugin.The stack trace is:{noformat}Started by user Mark Waite[Sat May 25 13:03:00 MDT 2019] Starting branch indexing...13:03:00 Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password)Examining MarkEWaite/hello-world-pluginERROR: [Sat May 25 13:03:01 MDT 2019] Could not fetch branches from source 8b33b746-db40-4839-901f-d94e4a4f3148java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)[Sat May 25 13:03:01 MDT 2019] Finished branch indexing. Indexing took 0.36 secFATAL: Failed to recompute children of Hello World Plugin Folder » hello world pipeline (GitHub)java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:246) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:888) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:634) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at
[JIRA] (JENKINS-57683) ClassCastException in GitHub Branch Source scanning repository
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-57683 ClassCastException in GitHub Branch Source scanning repository Issue Type: Bug Assignee: Unassigned Attachments: config.xml Components: github-branch-source-plugin Created: 2019-05-25 19:11 Environment: Jenkins 2.176.1 LTS release candidate GitHub Branch Source Plugin 2.5.3 Git plugin 4.0 pre-release Git client plugin 3.0 pre-release Priority: Minor Reporter: Mark Waite GitHub Branch Source plugin 2.5.3 reports a class cast exception when scanning in a multibranch pipeline definition for the hello-world-plugin. The stack trace is: Started by user Mark Waite [Sat May 25 13:03:00 MDT 2019] Starting branch indexing... 13:03:00 Connecting to https://api.github.com using MarkEWaite/** (MarkEWaite github username/password) Examining MarkEWaite/hello-world-plugin ERROR: [Sat May 25 13:03:01 MDT 2019] Could not fetch branches from source 8b33b746-db40-4839-901f-d94e4a4f3148 java.lang.ClassCastException: org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceContext cannot be cast to jenkins.plugins.git.GitSCMSourceContext at jenkins.plugins.git.traits.PruneStaleBranchTrait.decorateContext(PruneStaleBranchTrait.java:54) at jenkins.scm.api.trait.SCMSourceTrait.applyToContext(SCMSourceTrait.java:53) at jenkins.scm.api.trait.SCMSourceContext.withTrait(SCMSourceContext.java:221) at
[JIRA] (JENKINS-57682) Support for declarative trigger
Title: Message Title Mike assigned an issue to rsandell Jenkins / JENKINS-57682 Support for declarative trigger Change By: Mike Assignee: Mike rsandell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199617.1558809614000.11985.1558809900158%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57682) Support for declarative trigger
Title: Message Title Mike assigned an issue to Mike Jenkins / JENKINS-57682 Support for declarative trigger Change By: Mike Assignee: Mike Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199617.1558809614000.11983.1558809900098%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57682) Support for declarative trigger
Title: Message Title
Mike updated an issue
Jenkins / JENKINS-57682
Support for declarative trigger
Change By:
Mike
I am using dockerhub-notification-plugin version 2.4.0.I would like to be able to configure docker registry notifications for my declarative pipeline. i.e. { {pipeline { code:java } }{{ }} pipeline { { triggers { }} {{ dockerhubTriggers dockerHub () } } {{ } }} { { code } }} based on this similar commit in a different plugin, it seems simple? [https://github.com/jenkinsci/generic-webhook-trigger-plugin/commit/9d29aa90ffc2996738cdaca2415f1ef96e384524]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199617.1558809614000.11982.1558809780047%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57682) Support for declarative trigger
Title: Message Title
Mike updated an issue
Jenkins / JENKINS-57682
Support for declarative trigger
Change By:
Mike
I am using dockerhub-notification-plugin version 2.4.0.I would like to be able to configure docker registry notifications for my declarative pipeline. i.e. ``` {{ pipeline { }}{{ }} {{ triggers { }} {{ dockerhubTriggers() }} {{ } }} {{ } }} ``` based on this similar commit in a different plugin, it seems simple?[https://github.com/jenkinsci/generic-webhook-trigger-plugin/commit/9d29aa90ffc2996738cdaca2415f1ef96e384524]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199617.1558809614000.11981.1558809720050%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57682) Support for declarative trigger
Title: Message Title
Mike created an issue
Jenkins / JENKINS-57682
Support for declarative trigger
Issue Type:
Improvement
Assignee:
Unassigned
Components:
dockerhub-notification-plugin
Created:
2019-05-25 18:40
Priority:
Minor
Reporter:
Mike
I am using dockerhub-notification-plugin version 2.4.0. I would like to be able to configure docker registry notifications for my declarative pipeline. i.e. ``` pipeline { triggers { dockerhubTriggers() } } ``` based on this similar commit in a different plugin, it seems simple? https://github.com/jenkinsci/generic-webhook-trigger-plugin/commit/9d29aa90ffc2996738cdaca2415f1ef96e384524
Add Comment
[JIRA] (JENKINS-1182) Discard old builds only if the latest build is stable
Title: Message Title Nisarg Shah commented on JENKINS-1182 Re: Discard old builds only if the latest build is stable Oleg Nenashev Enhanced Old Build Discarder already gives this feature. Enhanced Old Build Discarder : https://github.com/jenkinsci/enhanced-old-build-discarder Actually I started to code few lines and I came across one doubt, and finding solution for that doubt I found that this feature has already been implemented. As a plugin is there for this feature should I continue implementation(maybe both functionalities in single plugin) in Old Discard Plugin or not ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.131255.1200456855000.11977.1558807741133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52325) Archiving artifacts fails if jenkins is not owner of builds dir
Title: Message Title Matt Sicker commented on JENKINS-52325 Re: Archiving artifacts fails if jenkins is not owner of builds dir Can you submit a unit test that reproduces the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192110.153055342.11972.1558806660175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Change By:
Mark Waite
For the GSoC project [gitlab-branch-source-plugin|https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+gitlab-branch-source-plugin] the student is requesting a new repo be created titled "gitlab-branch-plugin Detailed reasoning for this is here: 2) I read the documentation of {{SCM API}} and {{Branch API}} Plugins to understand the classes needs to be implemented in {{GitLab Branch Source Plugin}}. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it.3) I have been studing the codebases of {{ArgelBargel's GitLab Branch Source Plugin}}, {{GitHub Branch Source Plugin}}and {{Gitea Plugin}}. My takeaway was {{GitLab BS}} has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example,i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like {{SCMSource}} has been broken down to other sub classes , {{SCMHeadCategory}} has some different implementation, {{SCMFileSystem}} is not implemented, APIs implementation also needs to be changed and the list goes on..ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new {{GitLab Branch Source Plugin}} which will be heavily inspired from {{Gitea Plugin}} (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from {{GitLab Branch Source}} and {{GitHub Branch Source}} Plugins.iii) I will send my compelete list of reasons not to develop the existing {{GitLab Branch Source}} Plugin.
Add Comment
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Change By:
Mark Waite
For the GSoC project [gitlab-branch-source-plugin|https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+gitlab-branch-source-plugin] the student is requesting a new repo be created titled "gitlab-branch-plugin Detailed reasoning for this is here: 2) I read the documentation of {{SCM API}}and {{Branch API}} Plugins to understand the classes needs to be implemented in {{GitLab Branch Source Plugin}}. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it.3) I have been studing the codebases of {{ArgelBargel's GitLab Branch Source Plugin}}, {{GitHub Branch Source Plugin}}and {{Gitea Plugin}}. My takeaway was {{GitLab BS}} has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example,i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like {{SCMSource}} has been broken down to other sub classes , {{SCMHeadCategory}} has some different implementation, {{SCMFileSystem}} is not implemented, APIs implementation also needs to be changed and the list goes on..ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new {{GitLab Branch Source Plugin}} which will be heavily inspired from {{Gitea Plugin}} (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from {{GitLab Branch Source}} and {{GitHub Branch Source}} Plugins.iii) I will send my compelete list of reasons not to develop the existing {{GitLab Branch Source}} Plugin.
Add Comment
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57664 On Release of a Version recieve a Null Pointer exception Change By: Radek Antoniuk Environment: Jenkins version 2.164.3Jira Plugin version 3. 07 0.7 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11955.1558798260111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk edited a comment on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception Uhm, I'm confused, you're mentioning Slack now. Did the problem occur because of Slack plugin? Or do you mean that after re-saving the job configuration it just started working?If the latter, are you able to dig out the full stacktrace still? It might help figuring out why the jobs needed to be re-saved after plugin update. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11953.1558798080082%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk commented on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception Uhm, I'm confused, you're mentioning Slack now. Did the problem occur because of Slack plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11951.1558798020080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Aaron Sua commented on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception I discovered the individual jobs were not updated to use the new version of the plugin. After editing the jobs to update Slack messages the proper plugin version is referenced in the job config. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11949.1558797900167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Aaron Sua updated an issue Jenkins / JENKINS-57664 On Release of a Version recieve a Null Pointer exception Change By: Aaron Sua Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11947.1558797840175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Rick commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin That's a good idea. We can start from design, coding. When we think it's ready. Then fork it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11944.1558797240251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52325) Archiving artifacts fails if jenkins is not owner of builds dir
Title: Message Title Patrick Trabocchi reopened an issue Sorry to reopen this bug, but this problem is still present in LTS branch. I've installed the last LTS version (2.164.3) on a virtualized Ubuntu (18.04.2) machine hosted on a Windows 10 machine. But when parent job has finished successfully, and the copy artifact plugin execute its work, the builded artifact is copied correctly but the console output the error. Jenkins / JENKINS-52325 Archiving artifacts fails if jenkins is not owner of builds dir Change By: Patrick Trabocchi Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-57676) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.0.51/10.244.0.51:58278
Title: Message Title Nikolas Falco assigned an issue to Unassigned Jenkins / JENKINS-57676 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.0.51/10.244.0.51:58278 Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199609.1558723284000.11937.1558795680159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin I have sent an email to the Jenkins-dev mailing list here: https://groups.google.com/forum/#!topic/jenkinsci-dev/k_12IoFRNHg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11931.1558795200184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin I don't think hosting our plugin I'm 'jenkinsci' org is an urgent requirement. Although I agree we should start this process early lest it takes time. I will start a new repo on the test org I created for GSoC (I'll add you there) and when our plugin reaches releasable state, we can always fork it into 'jenkinsci' org. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11935.1558795200276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk commented on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception Can you attach full stacktrace from Jenkins logs? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11928.1558794420105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Parichay Barpanda Oleg Nenashev I think in the interest of time we should just use the current plugin GitHub repo (https://github.com/jenkinsci/gitlab-branch-source-plugin). So we will need to request access to this by becoming the maintainers, is that correct Oleg Nenashev and to do so we will need to request that through the jenkins-dev mailing? If so, I fear that the usual time it takes for the to happen can be lengthily, is there something we can do to expedite that faster Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11925.1558794300175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57676) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.0.51/10.244.0.51:58278
Title: Message Title venkatesh p assigned an issue to Nikolas Falco Jenkins / JENKINS-57676 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.0.51/10.244.0.51:58278 Change By: venkatesh p Assignee: Nicolas VINOT Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199609.1558723284000.11921.1558793418015%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Marky Jackson I got this. I have already hosted a plugin so I am aware of the procedure. In that case there was also a conflicting plugin name and the older plugin was renamed and archived. You just have to handle this initial part. i.e. discuss with Kohsuke Kawaguchi to either allow us push access to GitLab Branch Source Plugin or follow the archiving procedure. After ^this is done, I will proceed with the hosting process accordingly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11918.1558793346782%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57676) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.0.51/10.244.0.51:58278
Title: Message Title venkatesh p assigned an issue to Nicolas VINOT Jenkins / JENKINS-57676 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.244.0.51/10.244.0.51:58278 Change By: venkatesh p Assignee: Nicolas VINOT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199609.1558723284000.11915.1558793280101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Oleg Nenashev commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Please follow the Plugin Hosting process: https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11913.1558792860262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) How to mapping Custom Field key in JIRA trigger plugin
Title: Message Title Deakey Tan commented on JENKINS-57630 Re: How to mapping Custom Field key in JIRA trigger plugin User Picker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.11911.1558791900092%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57681) Setup wizard does not take into account optional dependencies when ordering plugin installations
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-57681 Setup wizard does not take into account optional dependencies when ordering plugin installations Issue Type: Bug Assignee: Francisco Fernández Components: cloudbees-folder-plugin, core, credentials-plugin Created: 2019-05-25 11:39 Environment: docker run -p 8080:8080 jenkins/jenkins:2.164.3 Priority: Minor Reporter: Daniel Beck Seen this myself, and also reports from others that Jenkins requires a restart after setup wizard plugin installation for things to not be broken. Steps to reproduce: Install suggested plugins in setup wizard Observe that Folders is installed before Credentials New Item, type Folder Expected result Folder config screen loads Actual result It does not Workaround Restart Jenkins after plugin installation.
[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change
Title: Message Title Wisen Tanasa commented on JENKINS-57620 Re: JIRA Trigger not triggering on status change I'm not sure about this one actually, sorry. It seems like configuration issue. Probably best to ask in Jenkins core community? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199548.1558551175000.11906.1558774440108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) How to mapping Custom Field key in JIRA trigger plugin
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: How to mapping Custom Field key in JIRA trigger plugin What's the field type for that custom field? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.11904.1558774320117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
