[JIRA] (JENKINS-28245) ChannelPinger timeout should be configurable
Title: Message Title Oleg Nenashev commented on JENKINS-28245 Re: ChannelPinger timeout should be configurable Released it jenkins-2.37 Thanks to Alvaro Lobato for finishing 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-28245) ChannelPinger timeout should be configurable
Title: Message Title Oleg Nenashev edited a comment on JENKINS-28245 Re: ChannelPinger timeout should be configurable Released it in jenkins-2.37Thanks to [~alobato] for finishing 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-38903) Split the Exceptions handling for node provision and adding a node to Jenkins in NodeProvisioner
Title: Message Title Oleg Nenashev commented on JENKINS-38903 Re: Split the Exceptions handling for node provision and adding a node to Jenkins in NodeProvisioner Released it jenkins-2.37 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-40286) EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it
Title: Message Title Oleg Nenashev updated JENKINS-40286 Released it jenkins-2.37 Jenkins / JENKINS-40286 EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it Change By: Oleg Nenashev Status: In Review 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 http
[JIRA] (JENKINS-39700) Saving external job throws "null object"
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-39700 Saving external job throws "null object" Change By: Oleg Nenashev Labels: lts-candidate 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-39300) View.getDisplayName() is ignored when rendering tabs
Title: Message Title Oleg Nenashev commented on JENKINS-39300 Re: View.getDisplayName() is ignored when rendering tabs Released in jenkins-2.37, marking as LTS candidate 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-39300) View.getDisplayName() is ignored when rendering tabs
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-39300 View.getDisplayName() is ignored when rendering tabs Change By: Oleg Nenashev Labels: lts-candidate 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-40489) Confusing Jenkins initialization stage names
Title: Message Title Oleg Nenashev commented on JENKINS-40489 Re: Confusing Jenkins initialization stage names Released in jenkins-2.37, marking as LTS candidate 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-40435) Job configuration submission should be a bulk change
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40435 Job configuration submission should be a bulk change Change By: Oleg Nenashev Labels: disk lts-candidate performance 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-40489) Confusing Jenkins initialization stage names
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40489 Confusing Jenkins initialization stage names Change By: Oleg Nenashev Labels: lts-candidate 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-40435) Job configuration submission should be a bulk change
Title: Message Title Oleg Nenashev resolved as Fixed Released in jenkins-2.37, marking as LTS candidate Jenkins / JENKINS-40435 Job configuration submission should be a bulk change Change By: Oleg Nenashev Status: In Progress 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.c
[JIRA] (JENKINS-39547) Corrupt node jar cache causes node to malfunction
Title: Message Title Oleg Nenashev commented on JENKINS-39547 Re: Corrupt node jar cache causes node to malfunction Released in jenkins-2.37, marking as LTS candidate 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-40365) Node should have a getProperty method to get aNodeProperty for specific class
Title: Message Title Oleg Nenashev resolved as Fixed Released in jenkins-2.37 Jenkins / JENKINS-40365 Node should have a getProperty method to get aNodeProperty for specific class Change By: Oleg Nenashev 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/opt
[JIRA] (JENKINS-40532) git not available in "modern SCM" option
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-40532 git not available in "modern SCM" option Issue Type: Improvement Assignee: Jesse Glick Components: workflow-cps-global-lib-plugin Created: 2016/Dec/19 8:09 AM Priority: Minor Reporter: Dominik Bartholdi The documentation [1] says this: The best way to specify the SCM is using an SCM plugin which has been specifically updated to support a new API for checking out an arbitrary named version (Modern SCM option). As of this writing, the latest versions of the Git and Subversion plugins support this mode; others should follow. so git should be available in the "Modern SCM" option, but but as with version 2.4 of the 'workflow-cps-global-lib-plugin' this seems not to be the case, git is only available in the "Legacy SCM" option. [1] https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md#defining-external-libraries Add Comment
[JIRA] (JENKINS-39433) Make checkURIEncoding an admin monitor
Title: Message Title Oleg Nenashev commented on JENKINS-39433 Re: Make checkURIEncoding an admin monitor Released it jenkins-2.37 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-39547) Corrupt node jar cache causes node to malfunction
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-39547 Corrupt node jar cache causes node to malfunction Change By: Oleg Nenashev Labels: lts-candidate 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-40362) SSHD Module - Handshake fails (wrong shared secret) 1 out of 256 times (SSHD-330)
Title: Message Title Oleg Nenashev commented on JENKINS-40362 Re: SSHD Module - Handshake fails (wrong shared secret) 1 out of 256 times (SSHD-330) Released in jenkins-2.37, marking as LTS candidate 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-40362) SSHD Module - Handshake fails (wrong shared secret) 1 out of 256 times (SSHD-330)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40362 SSHD Module - Handshake fails (wrong shared secret) 1 out of 256 times (SSHD-330) Change By: Oleg Nenashev Labels: lts-candidate 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-40286) EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it
Title: Message Title Oleg Nenashev edited a comment on JENKINS-40286 Re: EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it Released it in jenkins-2.37 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-32797) Access to check for unprotected/never secured paths
Title: Message Title Oleg Nenashev resolved as Fixed Released in jenkins-2.37 Jenkins / JENKINS-32797 Access to check for unprotected/never secured paths Change By: Oleg Nenashev 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-40252) Items should have a Iterable getAllItemsUnsorted(Class)
Title: Message Title Oleg Nenashev updated JENKINS-40252 Released in jenkins-2.37 Jenkins / JENKINS-40252 Items should have a Iterable getAllItemsUnsorted(Class) Change By: Oleg Nenashev Status: In Review 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-40491) Improve diagnostics of the preliminary FifoBuffer termination
Title: Message Title Oleg Nenashev resolved as Fixed Released in jenkins-2.37. Will be an LTS candidate as a part of remoting 3.3 Jenkins / JENKINS-40491 Improve diagnostics of the preliminary FifoBuffer termination Change By: Oleg Nenashev 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, v
[JIRA] (JENKINS-39971) Manual update button hidden if no plugins to update availabe.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39971 Re: Manual update button hidden if no plugins to update availabe. Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/ca8aa7748a6aee08f4b188571abd035d3b0842a8 Log: Changelog: fix the wrong link to JENKINS-39971 in 2.37 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-38903) Split the Exceptions handling for node provision and adding a node to Jenkins in NodeProvisioner
Title: Message Title Oleg Nenashev edited a comment on JENKINS-38903 Re: Split the Exceptions handling for node provision and adding a node to Jenkins in NodeProvisioner Released it in jenkins-2.37 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-39862) Make stash/unstash work in container.inside
Title: Message Title Julien Pivotto closed an issue as Won't Do I do not need this anymore Jenkins / JENKINS-39862 Make stash/unstash work in container.inside Change By: Julien Pivotto Status: Open Closed Assignee: Julien Pivotto Resolution: Won't Do 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 Gr
[JIRA] (JENKINS-39739) NPE when using a credentials parameter with multi-configuration project
Title: Message Title Alexander Z assigned an issue to Stephen Connolly Jenkins / JENKINS-39739 NPE when using a credentials parameter with multi-configuration project Change By: Alexander Z Assignee: Kohsuke Kawaguchi 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-39749) Parallel SCM fetches are shown in random order in builds menu
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39749 Parallel SCM fetches are shown in random order in builds menu Change By: Julien Pivotto Component/s: git-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-39749) Parallel SCM fetches are shown in random order in builds menu
Title: Message Title Julien Pivotto assigned an issue to Mark Waite Jenkins / JENKINS-39749 Parallel SCM fetches are shown in random order in builds menu Change By: Julien Pivotto Assignee: Mark Waite 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-40499) PublishOverSSHPluginTest is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40499 Re: PublishOverSSHPluginTest is failing Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/plugins/publish_over/PublishOverSSHGlobalConfig.java http://jenkins-ci.org/commit/acceptance-test-harness/f74e79e4fe84aa31cb696e8745f51f368b998b99 Log: Merge pull request #244 from mafraba/JENKINS-40499 JENKINS-40499 Fix PublishOverSSHGlobalConfig#addAdvancedConfig Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/c8aeef9e12ea...f74e79e4fe84 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-40499) PublishOverSSHPluginTest is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40499 Re: PublishOverSSHPluginTest is failing Code changed in jenkins User: Manuel Franco Path: src/main/java/org/jenkinsci/test/acceptance/plugins/publish_over/PublishOverSSHGlobalConfig.java http://jenkins-ci.org/commit/acceptance-test-harness/f468e4b52bca5b771c0bb6628ef8bb4516b0abb8 Log: JENKINS-40499 Fix PublishOverSSHGlobalConfig#addAdvancedConfig 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-40476) WorkflowMultibranchTest#testMultibranchPipeline is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40476 Re: WorkflowMultibranchTest#testMultibranchPipeline is failing Code changed in jenkins User: Oliver Gondža Path: src/test/java/plugins/WorkflowMultibranchTest.java http://jenkins-ci.org/commit/acceptance-test-harness/585360128a9dbdcda03c0ff78830596c8169d153 Log: Merge pull request #242 from varyvol/JENKINS-40476 JENKINS-40476 WorkflowMultibranchTest#testMultibranchPipeline is failing Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/f74e79e4fe84...585360128a9d 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-40476) WorkflowMultibranchTest#testMultibranchPipeline is failing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40476 Re: WorkflowMultibranchTest#testMultibranchPipeline is failing Code changed in jenkins User: Evaristo Gutiérrez Path: src/test/java/plugins/WorkflowMultibranchTest.java http://jenkins-ci.org/commit/acceptance-test-harness/647b6beb1720b05c929dd0bcd90e500a59475ad0 Log: JENKINS-40476 Request last version of Javadoc 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-39410) Clover-Plugin crash (InvocationTargetException)
Title: Message Title Marek Parfianowicz commented on JENKINS-39410 Re: Clover-Plugin crash (InvocationTargetException) Fixed in Clover 4.7.1 (http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/clover/4.7.1/) 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-40476) WorkflowMultibranchTest#testMultibranchPipeline is failing
Title: Message Title Evaristo Gutierrez updated JENKINS-40476 Jenkins / JENKINS-40476 WorkflowMultibranchTest#testMultibranchPipeline is failing Change By: Evaristo Gutierrez Status: In Review 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-39410) Clover-Plugin crash (InvocationTargetException)
Title: Message Title Marek Parfianowicz closed an issue as Fixed Jenkins / JENKINS-39410 Clover-Plugin crash (InvocationTargetException) Change By: Marek Parfianowicz 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-38956) can't add clover publisher
Title: Message Title Marek Parfianowicz commented on JENKINS-38956 Re: can't add clover publisher Fixed in Clover 4.7.1 (http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/clover/4.7.1/) 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-38956) can't add clover publisher
Title: Message Title Marek Parfianowicz closed an issue as Fixed Jenkins / JENKINS-38956 can't add clover publisher Change By: Marek Parfianowicz 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-40533) allow definition of sandboxed libraries on global scope
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-40533 allow definition of sandboxed libraries on global scope Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Dec/19 9:08 AM Priority: Minor Reporter: Dominik Bartholdi Because this plugin does not allow the definition of sandboxed libraries on global scope, but only on folder level. It is not possible on managed/secured environments (e.g. DEV@cloud by cloudbees) to take advantage of this plugin, unless every job is placed within a folder. Add Comment
[JIRA] (JENKINS-40533) allow definition of sandboxed libraries on global scope
Title: Message Title Dominik Bartholdi assigned an issue to Jesse Glick Jenkins / JENKINS-40533 allow definition of sandboxed libraries on global scope Change By: Dominik Bartholdi Assignee: Jesse Glick 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-40352) Duplicate changesets in pipeline jobs
Title: Message Title Reinhold Degenfellner updated an issue Jenkins / JENKINS-40352 Duplicate changesets in pipeline jobs Change By: Reinhold Degenfellner Attachment: jenkins-change-log-issue.png 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-40352) Duplicate changesets in pipeline jobs
Title: Message Title Reinhold Degenfellner commented on JENKINS-40352 Re: Duplicate changesets in pipeline jobs We have as similar issue (see added jenkins-change-log-issue.png) it's Git plugin 3.0.1 in a multi branch pipeline scenario the 3 line entry is ok (it's from a jenkins pipeline library) but the 25 line entry duplicates entries from the 49 line entry where the 25 line entry would be all we need (the 49 line entry also lists older changes that are not new to this build) 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-40331) Create a way to trigger build in pipeline
Title: Message Title aurelien leboulanger updated an issue Jenkins / JENKINS-40331 Create a way to trigger build in pipeline Change By: aurelien leboulanger Priority: Minor Major Currently i'm not able to define the gitlab trigger build configuration in my pipeline definition file (Jenkinsfile); i have to set the configuration in the jenkins job. It will be nice to be able to define the configuration directly in the Jenkinsfile. [https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Trigger-runs#other-available-triggers] I guess the addition of the _@Symbol_ on the GitlabPushTrigger will be enough to 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 unsubscr
[JIRA] (JENKINS-40526) Add expand all button
Title: Message Title Alex Radinsky commented on JENKINS-40526 Re: Add expand all button Looking for the separated log of parallel. 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-26799) Multiple SCMs plugin support
Title: Message Title Oleksii Shevchenko commented on JENKINS-26799 Re: Multiple SCMs plugin support Boguslaw Klimas Thanks. So I have 2 git repositories. First is cloned at root of workspace, second to subdir of first repo. Having this setup I am not able to Regexp second repo, only first matching. 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-39739) NPE when using a credentials parameter with multi-configuration project
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-39739 NPE when using a credentials parameter with multi-configuration project Change By: Stephen Connolly Component/s: credentials-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-39739) NPE when using a credentials parameter with multi-configuration project
Title: Message Title Stephen Connolly assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-39739 NPE when using a credentials parameter with multi-configuration project Change By: Stephen Connolly Assignee: Stephen Connolly Kohsuke Kawaguchi 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-39739) NPE when using a credentials parameter with multi-configuration project
Title: Message Title Stephen Connolly commented on JENKINS-39739 Re: NPE when using a credentials parameter with multi-configuration project Not a bug in the credentials plugin: http://javadoc.jenkins.io/hudson/model/ParameterValue.html#createVariableResolver(hudson.model.AbstractBuild) describes the build parameter: The build for which this parameter is being used. Never null. While the matrix plugin is passing an explicit null: https://github.com/jenkinsci/matrix-project-plugin/blob/3d7eb2b13fce78fe71d0ad84cb992856209cbca2/src/main/java/hudson/matrix/FilterScript.java#L97 Clearly a bug in the matrix 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-38826) Add SSH Credential support to track where a credential is used
Title: Message Title Stephen Connolly closed an issue as Not A Defect SSH Credentials plugin is not a consumer plugin Jenkins / JENKINS-38826 Add SSH Credential support to track where a credential is used Change By: Stephen Connolly 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, visi
[JIRA] (JENKINS-40180) Allow global post-build steps
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-40180 Allow global post-build steps Change By: Stephen Connolly Component/s: pipeline-model-definition-plugin Component/s: github-organization-folder-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-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Title: Message Title Jean-Frédéric commented on JENKINS-40224 Re: Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly > would the jobs you received 404 for happen to be Matrix projects or any other non-Pipeline or non-Freestyle job type? No, these are all Freestyle jobs. I think the root problem lies more with the Mailer plugin, which monospaced text 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-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Title: Message Title
Jean-Frédéric edited a comment on JENKINS-40224
Re: Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
> would the jobs you received 404 for happen to be Matrix projects or any other non-Pipeline or non-Freestyle job type? No, these are all Freestyle jobs.I think the root problem lies more with the Mailer plugin, which creates links like {{ monospaced text jenkins.acme.com/job/jobB/777/---/ }} . But these links are redirect properly with classic URLs, not with BlueOcean URLs.
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-40499) PublishOverSSHPluginTest is failing
Title: Message Title Manuel Franco resolved as Fixed Jenkins / JENKINS-40499 PublishOverSSHPluginTest is failing Change By: Manuel Franco Status: In Progress 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-40065) Some repos look empty even when they have branches and PRs
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantlyrefactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-40065 Some repos look empty even when they have branches and PRs Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39939) Github organization folder plugin not downloading while settiing up jenkins
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-39939 Github organization folder plugin not downloading while settiing up jenkins Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39785) Error in "Folder Computation" - any possibility to be notified?
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-39785 Error in "Folder Computation" - any possibility to be notified? Change By: Stephen Connolly Component/s: github-organization-folder-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-39727) Any way to control builds from PR comments?
Title: Message Title Stephen Connolly resolved as Fixed The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-39727 Any way to control builds from PR comments? Change By: Stephen Connolly Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39727) Any way to control builds from PR comments?
Title: Message Title Stephen Connolly commented on JENKINS-39727 Re: Any way to control builds from PR comments? With GitHub Branch Source 2.0.0-beta-1 (or later) you just close and re-open the PR to trigger a re-build 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-39726) Don't rebuild all PRs on base branch update
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-39726 Don't rebuild all PRs on base branch update Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39510) Need way to specify Git Tool when using Github Org Folder plugin
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-39510 Need way to specify Git Tool when using Github Org Folder plugin Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39393) When "origin branches also filed as PRs" is set, FileNotFoundException from malformed GitHub "open PR" query
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-39393 When "origin branches also filed as PRs" is set, FileNotFoundException from malformed GitHub "open PR" query Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39475) Add basic documentation in wiki
Title: Message Title Stephen Connolly resolved as Fixed The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-39475 Add basic documentation in wiki Change By: Stephen Connolly Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38962) New Item 'GitHub Organisation' does not show progress
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-38962 New Item 'GitHub Organisation' does not show progress Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38937) GitHub API cache is not working
Title: Message Title Stephen Connolly commented on JENKINS-38937 Re: GitHub API cache is not working Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) 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-38707) Scheduled builds in the GitHub Org folder shouldn't fail if the rate limit is exceeded
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-38707 Scheduled builds in the GitHub Org folder shouldn't fail if the rate limit is exceeded Change By: Stephen Connolly Status: In Progress Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38654) The plugin occasionally reports back to Github before a build is done
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-38654 The plugin occasionally reports back to Github before a build is done Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38577) Need a way to determine if build is commit to branch or base
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-38577 Need a way to determine if build is commit to branch or base Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38577) Need a way to determine if build is commit to branch or base
Title: Message Title Stephen Connolly commented on JENKINS-38577 Re: Need a way to determine if build is commit to branch or base With GutHub Branch Source 2.0.0-beta-1 or newer. BRANCH_NAME will contain the branch name CHANGE_ID, etc will be populated for PRs, see: https://github.com/jenkinsci/branch-api-plugin/blob/0172fa54b0d920a89801006785c7021b26084841/src/main/java/jenkins/branch/BranchNameContributor.java#L60-L74 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-38545) Jenkins does not select the "Pull Request" event under Webhook
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-38545 Jenkins does not select the "Pull Request" event under Webhook Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38545) Jenkins does not select the "Pull Request" event under Webhook
Title: Message Title Stephen Connolly commented on JENKINS-38545 Re: Jenkins does not select the "Pull Request" event under Webhook With GitHub Branch Source 2.0.0-beta-1 (or newer) this should not be an issue, see https://github.com/jenkinsci/github-branch-source-plugin/blob/5cf69cafee239d6fb946601b97452a1c9ab00cf4/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubOrgWebHook.java#L49 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-38409) Cancel ongoing testing of current PR if the PR gets updated with new/changed commits
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-38409 Cancel ongoing testing of current PR if the PR gets updated with new/changed commits Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38277) The webhook registration didn't register the push hook
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-38277 The webhook registration didn't register the push hook Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38277) The webhook registration didn't register the push hook
Title: Message Title Stephen Connolly commented on JENKINS-38277 Re: The webhook registration didn't register the push hook see https://github.com/jenkinsci/github-branch-source-plugin/blob/5cf69cafee239d6fb946601b97452a1c9ab00cf4/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubOrgWebHook.java#L49 for GitHub Branch Source 2.0.0-beta-1 (or newer) 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-38001) Cannot rename a GitHub Org Folder
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-38001 Cannot rename a GitHub Org Folder Change By: Stephen Connolly Component/s: github-branch-source-plugin Component/s: github-organization-folder-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-37907) Include abililty to hook branch deletion.
Title: Message Title Stephen Connolly resolved as Fixed The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-37907 Include abililty to hook branch deletion. Change By: Stephen Connolly Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37907) Include abililty to hook branch deletion.
Title: Message Title Stephen Connolly commented on JENKINS-37907 Re: Include abililty to hook branch deletion. With GitHub Branch Source 2.0.0-beta-1 (or newer) the branch being deleted (or no longer being recognised as a project - e.g. removing Jenkinsfile) will mark the branch as a Dead Branch, which can then either be manually deleted or will be deleted on the next index (as the branch retention policy is implicit to only get applied on each index and also otherwise things like "close PR -> reopen PR -> trigger rebuild" would destroy the PR build history) 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-37845) GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
Title: Message Title Stephen Connolly commented on JENKINS-37845 Re: GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) 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-37845) GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-37845 GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with Change By: Stephen Connolly Component/s: github-organization-folder-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-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java A possible work around is to use the 'Force clean' option, this avoids the reconcile command and should use less memory. Enabling parallel sync should speed sync time and my use less memory in the Java Heap. If you are using slaves then parallel sync will require the 'p4' executable installed on the slave. 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Stephen Connolly commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes With GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) When you push a change to the base branch, it should trigger only the base branch. The PR-merge branches will get rebuilt when the indexing kicks in as indexing will detect that the merge commit is now different, but that should only happen once a day/week (depending on how often you configure indexing) so should be much less of an issue 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-37365) Automatically configured webhooks should include pull requests
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-37365 Automatically configured webhooks should include pull requests Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37365) Automatically configured webhooks should include pull requests
Title: Message Title Stephen Connolly commented on JENKINS-37365 Re: Automatically configured webhooks should include pull requests Should be fixed in GitHub Branch Source 2.0.0-beta-1 (or newer) https://github.com/jenkinsci/github-branch-source-plugin/blob/5cf69cafee239d6fb946601b97452a1c9ab00cf4/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubOrgWebHook.java#L49 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-37191) Organization WebHook misses PR updates
Title: Message Title Stephen Connolly commented on JENKINS-37191 Re: Organization WebHook misses PR updates See https://github.com/jenkinsci/github-branch-source-plugin/blob/5cf69cafee239d6fb946601b97452a1c9ab00cf4/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubOrgWebHook.java#L49 This should be fixed in GitHub Branch Source 2.0.0-beta-1 (and newer) 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-37191) Organization WebHook misses PR updates
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-37191 Organization WebHook misses PR updates Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37190) Unauthenticated request to GitHub trigger rate limits when adding organization
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-37190 Unauthenticated request to GitHub trigger rate limits when adding organization Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37190) Unauthenticated request to GitHub trigger rate limits when adding organization
Title: Message Title Stephen Connolly commented on JENKINS-37190 Re: Unauthenticated request to GitHub trigger rate limits when adding organization The GitHub Branch Source 2.0.0-beta-1 (and newer) behaviour is to wait until the organization folder is saved before starting any indexing. You may still hit the anonymous API rate limit if you configure anonymous against an organization that requires more than 60 API calls to scan, but there is not much we can do about that 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-36724) Branch indexing hangs
Title: Message Title Stephen Connolly commented on JENKINS-36724 Re: Branch indexing hangs Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) 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-36357) Caching of pull requests in indexing
Title: Message Title Stephen Connolly commented on JENKINS-36357 Re: Caching of pull requests in indexing Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) 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-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Stephen Connolly commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) 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-36026) Implement getLastSuccessfullBuild to support displaying column results for Last {Success, Failure, Duration}
Title: Message Title
Stephen Connolly resolved as Fixed
The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017)
Jenkins / JENKINS-36026
Implement getLastSuccessfullBuild to support displaying column results for Last {Success, Failure, Duration}
Change By:
Stephen Connolly
Status:
Open Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35552) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down
Title: Message Title Stephen Connolly resolved as Fixed Fixed in 2.0.0-beta-1 Jenkins / JENKINS-35552 Upgrade to Credentials 2.1.0+ API for populating credentials drop-down Change By: Stephen Connolly Status: Open Resolved Assignee: Jesse Glick Stephen Connolly Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you ar
[JIRA] (JENKINS-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-34612 Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..." Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35111) Failure to respond to interruption of indexing
Title: Message Title Stephen Connolly resolved as Fixed See https://github.com/jenkinsci/github-branch-source-plugin/blob/5cf69cafee239d6fb946601b97452a1c9ab00cf4/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L503 Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-35111 Failure to respond to interruption of indexing Change By: Stephen Connolly Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40534) HP Plugin: Unable to run SSE test set from ALM with plugi verion 4.5 and 5.0 on Jenkins version 2.0+
Title: Message Title Igor Tereshchuk created an issue Jenkins / JENKINS-40534 HP Plugin: Unable to run SSE test set from ALM with plugi verion 4.5 and 5.0 on Jenkins version 2.0+ Issue Type: Bug Assignee: xiwen zhao Attachments: Capture.PNG Components: hp-application-automation-tools-plugin Created: 2016/Dec/19 10:41 AM Environment: Linux/Windows Jenkins 2.1.19, 2.13 Plugin version 4.5 and 5.0 Labels: sse, hp-application-automation-tools Priority: Critical Reporter: Igor Tereshchuk When trying run build step "Execute HP test using HP ALM LAB Managment" error in log Note: You can run only functional test sets and build verification suites using this plugin. Check to make sure that the configured ID is valid (and that it is not a performance test ID). Works fine on same Jenkins server in case if we use pipeline. Not reproduce with plugin 4.5 and Jenkins 1.6. steps to reproduce: 1.Log in to ALM and create functional test set 2.Add simple test inside 3.go to Jenkins and create build step for run SSE test set 4.run Job Inspect log
[JIRA] (JENKINS-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine
Title: Message Title Stephen Connolly resolved as Fixed 2.0.0-beta-1 Jenkins / JENKINS-34563 Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine Change By: Stephen Connolly Status: In Progress 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.co
[JIRA] (JENKINS-34293) GHOF - Stacktraces in logs
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-34293 GHOF - Stacktraces in logs Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33903) github-organization fails to detect new repositories, probably due to pagination
Title: Message Title Stephen Connolly resolved as Won't Fix The GitHub Org Folders plugin is being tombstoned. The functionality provided by the GitHub Org Folders plugin has been significantly refactored and migrated to the GitHub Branch Source plugin. Please verify if this issue is an issue with GitHub Branch Source 2.0.0-beta-1 (available from the experimental update center now or 2.0.0 (available in early January 2017) Jenkins / JENKINS-33903 github-organization fails to detect new repositories, probably due to pagination Change By: Stephen Connolly Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33903) github-organization fails to detect new repositories, probably due to pagination
Title: Message Title Stephen Connolly commented on JENKINS-33903 Re: github-organization fails to detect new repositories, probably due to pagination I suspect that this was a bug in GHOF. In GitHub Branch Source 2.0.0-beta-1 (and newer) the addition of a Jenkinsfile to a repository that was previously seen but did not have a branch with a Jenkinsfile now will trigger the repository being created: https://github.com/jenkinsci/branch-api-plugin/blob/0172fa54b0d920a89801006785c7021b26084841/src/main/java/jenkins/branch/OrganizationFolder.java#L738 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-33272) GitHub-specific SCMFileSystem
Title: Message Title Stephen Connolly resolved as Fixed 2.0.0-beta-1 Jenkins / JENKINS-33272 GitHub-specific SCMFileSystem Change By: Stephen Connolly Status: In Progress 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-40526) Developer would like to get the logs for a stage or parallel
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40526 Developer would like to get the logs for a stage or parallel Change By: James Dumay Summary: Add expand all button Developer would like to get the logs for a stage or parallel 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-40526) Developer would like to get the logs for a stage or parallel
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40526 Developer would like to get the logs for a stage or parallel Change By: James Dumay *Problem*There is no way to get the log for the whole stage or parallel. The full log is not useful as it intermingles logs from different parallel branches.*Original request* Will be nice to have "expand all" button to see all steps (view whole log doesn't help due multiple parallels) !image-2016-12-18-12-41-56-651.png|thumbnail! 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.
