[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175096.1475589798000.13930.1571794261397%40Atlassian.JIRA.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Roch Devost commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Since I am using pipeline multi-branch jobs with GitHub, I will add a helper to our shared libraries as you suggested. Thank you very much for your help! (I still think however that there should be a way to globally override the default checkout behaviour since it is incompatible with the largest Git provider on the planet) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user I'm not clear which type of pipeline job you're using, since you say that GitHub is the only branch source available. If you're using a GitHub Organization Folders job, then the customization of checkout technique will need to be performed either in a pipeline global library shared with all jobs, or in each job.If you're using a pipeline multi-branch job, then the customization of checkout technique can be performed at job definition, and may then be adjusted or modified in either a pipeline global library shared with all jobs, or in the Jenkinsfile for each branch. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Mark Waite Attachment: Pipeline-Multi-Branch.png Attachment: GitHub-Org-Folders.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Roch Devost commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user According to this article: https://support.cloudbees.com/hc/en-us/articles/226122247-How-to-Customize-Checkout-for-Pipeline-Multibranch the "Additional Behaviours" should appear in Branch Source -> Git, but in branch source I only have GitHub available, which doesn't have this option. Additionally, I want to change the behaviour for all projects if possible and not have to redo this setup on each one (especially since they are created automatically from pushes to the organizations repos). I understand the need for backward compatibility, but since pretty much all commits in GitHub are made by "noreply", there should at least be a way to change the behaviour globally (JAVA_OPTS?) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Roch Devost edited a comment on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Where exactly is this option? I have looked everywhere and cannot seem to find it. I am using the `checkout scm` step in Blue Ocean rc3 if that helps. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user The "pipeline syntax" link on most pipeline job definition pages will let you choose the "checkout" step. That will then guide you through the web page to select various git plugin options. Look for "Additional Behaviours" and you'll find a drop-down list which includes "Use commit author in changelog". We were tempted some years ago to make "Use commit author in changelog" the default, but any change to default behavior tends to result in a loud outcry from users who don't expect defaults to change from one release to the next. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Roch Devost commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Where exactly is this option? I have looked everywhere and cannot seem to find it. I am using the `checkout scm` step in Blue Ocean rc3 if that helps. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Now I see that I can choose "Use commit author in changelog" under Additional Behaviour. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user I am already using the "checkout" syntax: checkout([$class: 'GitSCM', branches: [[name: 'snip']], browser: [$class: 'GithubWeb', repoUrl: 'snip'], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[snip]]) Where can I find the documentation for the available options? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Your pipeline definition needs to use the more general purpose "checkout" step rather than the "git" step. You can use the "pipeline syntax" on most pipeline job pages then choose "checkout" from the dropdown and define the git checkout definition, with full support for extensions., Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user It looks like this setting `authorOrCommitter` has been moved back in 2013 to some "Extensions". Where can I find them? Is it a separate plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J edited a comment on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user I can't find that setting in the "Git plugin" section in the /configure page. I only see "user.name", "user.email", "Create new accounts base on author/committer's email". Could you point to where to find that setting? Also, it'd be useful to see how to do this in a Jenkinsfile pipeline. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user I can't find that setting in the "Git plugin" section in the /configure page. I only see "user.name", "user.email", "Create new accounts base on author/committer's email". Could you point to where to find that setting? Also, it'd be useful to see how to do this in a Jenkinsfile pipeline. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite resolved as Not A Defect Unfortunately, I'm unwilling to change the default behavior because that would change the default behavior for the 80 000+ installations of the git plugin. Some portion of those installations are predictably dependent on the (strange) default behavior of showing the committer name rather than the author name. It was considered to change that default behavior as part of the switch from git plugin 1 to git plugin 2, but then was decided to instead retain compatibility. I kept with that same decision in the switch from git plugin 2 to git plugin 3. Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Thanks Mark Waite, it's works. I had to replace git step in my pipeline, by the generic checkout step. IMHO, it would be great to have this behavior by default. 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Mark Waite 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user There is a setting in the git plugin which will change from showing the committer (likely the noreply in this case) to showing the author. The job definition likely is configured to the default which is to show the committer. 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva assigned an issue to Mark Waite Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Kseniia Nenasheva 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva updated an issue Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Kseniia Nenasheva 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva updated an issue Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Kseniia Nenasheva Labels: changes git github pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva updated an issue Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Kseniia Nenasheva Summary: SCM Changelog: Commits, made via github, displayed with "noreply" user 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.
