[JIRA] (JENKINS-40002) Add description to POM
Title: Message Title Evaristo Gutierrez updated JENKINS-40002 Jenkins / JENKINS-40002 Add description to POM 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-40372) Clicking re-run won't show up steps when there are no stages
Title: Message Title Michael Neale commented on JENKINS-40372 Re: Clicking re-run won't show up steps when there are no stages cc Ivan Meredith this is similar problem to one you fixed recently but without any stages - I wonder if this sounds familiar to you? 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-40372) Clicking re-run won't show up steps when there are no stages
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-40372
Clicking re-run won't show up steps when there are no stages
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2016/Dec/12 7:07 AM
Priority:
Minor
Reporter:
Michael Neale
To reproduce:
Create a pipeline with the contents below
Run it once
Open results screen and press re-run
Note that it fails to show any in progress steps - they appear all at once
Expected:
Should show up steps as they complete
node {
echo 'first step'
sh 'sleep 1; echo `date` first;'
echo 'first step end'
echo 'Second coming up'
sh 'sleep 1; echo `date` second;'
echo '9th'
sh 'sleep 1; echo `date`;'
echo '10th'
sh 'sleep 1; echo `date`;'
echo 'and we are finished'
sh 'echo end; error 1'
}
[JIRA] (JENKINS-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Michael Neale edited a comment on JENKINS-40369 Re: rerun button in rundetails sometimes redirects to the wrong url Yes when it fails, it is when re-run has opened the incorrect run.I believe this is showing up a real bug. I don't think this stops the ATH however as it does retry things automatically [~kzantow] [~cliffmeyers] any ideas on this? 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-40369 rerun button in rundetails sometimes redirects to the wrong url Change By: Michael Neale Assignee: Michael Neale 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Michael Neale commented on JENKINS-40369 Re: rerun button in rundetails sometimes redirects to the wrong url Yes when it fails, it is when re-run has opened the incorrect run. Keith Zantow Cliff Meyers any ideas on this? 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-40316) 'Publish HP tests result' not works in latest Jenkins plugin version
Title: Message Title Roy Lu resolved as Fixed Jenkins / JENKINS-40316 'Publish HP tests result' not works in latest Jenkins plugin version Change By: Roy Lu 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-40316) 'Publish HP tests result' not works in latest Jenkins plugin version
Title: Message Title Roy Lu commented on JENKINS-40316 Re: 'Publish HP tests result' not works in latest Jenkins plugin version Hi Alex Farion, Your plugins are all old. The issue is fixed after updated them. 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-40371) Multiple packages
Title: Message Title Ido Kaplan created an issue Jenkins / JENKINS-40371 Multiple packages Issue Type: Bug Assignee: Unassigned Components: repository-connector-plugin Created: 2016/Dec/12 6:44 AM Priority: Blocker Reporter: Ido Kaplan Hi, Is it possible to get a key value list of packages and versions? Thanks! Ido Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Daniel Beck assigned an issue to Daniel Spilker Jenkins / JENKINS-40130 Unable to create Jobs using job DSL in pipeline Change By: Daniel Beck Assignee: Kohsuke Kawaguchi Daniel Spilker 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-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40130 Unable to create Jobs using job DSL in pipeline Change By: Daniel Beck Component/s: github-organization-folder-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Daniel Beck commented on JENKINS-40130 Re: Unable to create Jobs using job DSL in pipeline My PR is only an attempt at a workaround by no longer invoking the compatibility code. FWIW based on Allan BURDAJEWICZ's comment, it's unrelated to 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-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly what we would consider "friendly" for an editor accessible feature (though {{when}} will be supported via a text area) and the developer would have to learn the Script syntax to use it correctly.*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly with the introduction of {{branch}} . Ideally we could tell from BO if the user has skipped via {{when}} or via {{branch}} *Example - match single branch*This stage would only be executed if {{master}} was the name of the current branch.{code}stage('deploy') {agent label:'some-node'branch "master" steps {sh './deploy.sh'}}{code}*Example - match branch name pattern*This stage would only be executed if the branch name started with {{feature/}}.{code}stage('deploy to staging') {agent label:'some-node'branch "feature/*" steps {sh './deploy_pr.sh'}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly what we would consider "friendly" for an editor accessible feature (though {{when}} will be supported via a text area) and the developer would have to learn the Script syntax to use it correctly.*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly with the introduction of {{branch}}. Ideally we could tell from BO if the user has skipped via {{when}} or via {{branch}} . *Example - match single branch*This stage would only be executed if {{master}} was the name of the current branch.{code}stage('deploy') {agent label:'some-node'branch "master" steps {sh './deploy.sh'}}{code}*Example - match branch name pattern*This stage would only be executed if the branch name started with {{feature/}}.{code}stage('deploy to staging') {agent label:'some-node'branch "feature/*" steps {sh './deploy_pr.sh'}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-40130
Re: Unable to create Jobs using job DSL in pipeline
{code}Caused by: com.thoughtworks.xstream.converters.ConversionException: Cannot convert type java.util.Vector to type hudson.util.DescribableList Debugging information class : hudson.maven.MavenModuleSetrequired-type : hudson.maven.MavenModuleSetconverter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverterpath: /maven2-moduleset/triggersline number : 10version : not available---{code} This PR should help to fix this: https://github.com/jenkinsci/job-dsl-plugin/pull/964
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-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-40130 Re: Unable to create Jobs using job DSL in pipeline This PR should help to fix this: https://github.com/jenkinsci/job-dsl-plugin/pull/964 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-40370) Run stage when branch name matches
Title: Message Title James Dumay commented on JENKINS-40370 Re: Run stage when branch name matches It does raise the question about when not being declarative - are we doing the right thing here? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title James Dumay commented on JENKINS-40370 Re: Run stage when branch name matches We may also want to do something similar for matching environment variables but I am less bullish on 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-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly what we would consider "friendly" for an editor accessible feature (though {{when}} will be supported via a text area) and the developer would have to learn the Script syntax to use it correctly.*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly.*Example - match single branch*This stage would only be executed if {{master}} was the name of the current branch.{code}stage('deploy') {agent label:'some-node'branch "master" steps {sh './deploy.sh'}}{code}*Example - match branch name pattern*This stage would only be executed if the branch name started with {{feature/}} . {code}stage('deploy to staging') {agent label:'some-node'branch "feature/*" steps {sh './deploy_pr.sh'}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly editor what we would consider " friendly " for an editor accessible feature (though {{when}} will be supported via a text area) and the developer would have to learn the Script syntax to use it correctly .*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly.*Example - match single branch*This stage would only be executed if {{master}} was the name of the current branch.{code}stage('deploy') {agent label:'some-node'branch "master" steps {sh './deploy.sh'}}{code}*Example - match branch name pattern*This stage would only be executed if the branch name started with {{feature/}}{code}stage('deploy to staging') {agent label:'some-node'branch "feature/*" steps {sh './deploy_pr.sh'}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly editor friendly (though {{ when }} will be supported via a text area) and the developer would have to learn the Script syntax to use.*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly.*Example - match single branch*This stage would only be executed if {{master}} was the name of the current branch.{code}stage('deploy') {agent label:'some-node'branch "master" steps {sh './deploy.sh'}}{code}*Example - match branch name pattern*This stage would only be executed if the branch name started with {{feature/}}{code}stage('deploy to staging') {agent label:'some-node'branch "feature/*" steps {sh './deploy_pr.sh'}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly editor friendly (though when will be supported via a text area) and the developer would have to learn the Script syntax to use.*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly.*Example - match single branch* This stage would only be executed if { {master}} was the name of the current branch.{ code}stage('deploy') {agent label:'some-node'branch "master" steps {sh './deploy.sh'}}{code}*Example - match branch name pattern* This stage would only be executed if the branch name started with { {feature/}}{ code}stage('deploy to staging') {agent label:'some-node'branch "feature/*" steps {sh './deploy_pr.sh'}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly editor friendly (though when will be supported via a text area) and the developer would have to jump into learn the Script syntax to use .*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly.*Example - match single branch*{code}stage('deploy') {agent label:'some-node'branch "master" steps {sh './deploy.sh'}}{code}*Example - match branch name pattern*{code}stage('deploy to staging') {agent label:'some-node'branch "feature/*" steps {sh './deploy_pr.sh'}}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40370 Run stage when branch name matches Change By: James Dumay Summary: Run stage when branch branch name matches 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-40370) Run stage when branch branch
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-40370
Run stage when branch branch
Issue Type:
Task
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2016/Dec/12 5:08 AM
Priority:
Major
Reporter:
James Dumay
Motivation Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor. Declarative allows the use of when to condition the stage execution like:
stage('second') {
agent label:'some-node'
branch "master"
when {
env.BRANCH == 'master'
}
}
However, this isn't exactly editor friendly (though when will be supported via a text area) and the developer would have to jump into the Script syntax. Solution We would like to formalise the pattern in a way that is more Editor and user friendly. Example - match single branch
stage('deploy') {
agent label:'some-node'
branch "master"
steps {
sh './deploy.sh'
}
}
Example - match branch name pattern
stage('deploy to staging') {
agent label:'some-node'
branch "feature/*"
steps {
sh './deploy_pr.sh'
}
}
[JIRA] (JENKINS-39413) Errors in LR Scenario set build status to UNSTABLE
Title: Message Title Yafim Kazak resolved as Fixed Jenkins / JENKINS-39413 Errors in LR Scenario set build status to UNSTABLE Change By: Yafim Kazak 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-39429) Builds sporadically failing with errors
Title: Message Title Yafim Kazak resolved as Fixed Jenkins / JENKINS-39429 Builds sporadically failing with errors Change By: Yafim Kazak 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-40316) 'Publish HP tests result' not works in latest Jenkins plugin version
Title: Message Title Roy Lu commented on JENKINS-40316 Re: 'Publish HP tests result' not works in latest Jenkins plugin version I can't reproduce it. Could you please attach how you configure the upload step? And which version you're using. I'm using 2.3.5, the latest weekly release. 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-40315) Pipeline tests for ALM not works in new version of Jenkins Plugin on Windows Jenkins 2.7.4 server
Title: Message Title Yafim Kazak commented on JENKINS-40315 Re: Pipeline tests for ALM not works in new version of Jenkins Plugin on Windows Jenkins 2.7.4 server I believe that we should retest on 2.19,4 the latest and greatest LTS as requested. I saw that the plugins on the test machines weren't updated as well and may caused some issues. 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Michael Neale commented on JENKINS-40369 Re: rerun button in rundetails sometimes redirects to the wrong url Yes I can see this too - not always first time, and doesn't always succeed the second time either, but that is generally a reliable way to see it. Its def not opening the right thing on re-run always. 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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Josh Chandler edited a comment on JENKINS-35132
Re: Pipeline: GitHub webhook received but nothing happens
I have a bit of a problem with this resolution. In short: I disagree entirely this is not a part of the github-plugin, with evidence from the code. Two things:1) It is most certainly from this plugin. The logs I captured indicate it came from this file:https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.javaThe log I posted to Kirill Merkushev indicates it came from this line:https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L68Particularly on line 71 (for reference: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L71), the commentary indicates it will kick a build at this point. This is the behavior I wished to occur which did not happen.2) The github-plugin page at (https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin) indicates this is a primary objective of the plugin itself on the landing page:{ { quote} Trigger a job when you push to the repository by groking HTTP POSTs from post-receive hook and optionally auto-managing the hook setup.Report build status result back to github as Commit Status (documented on SO) {quote } } This is exactly what I was trying to do; and this is exactly not what is happening on my server.If this is, after this body of evidence, somehow _not_ related to this plugin, can you explain to us where we can collect the information required to find the right place to comment, and perhaps point us to this place?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Josh Chandler commented on JENKINS-35132
Re: Pipeline: GitHub webhook received but nothing happens
I have a bit of a problem with this resolution. In short: I disagree entirely this is not a part of the github-plugin, with evidence from the code. Two things: 1) It is most certainly from this plugin. The logs I captured indicate it came from this file: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java The log I posted to Kirill Merkushev indicates it came from this line: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L68 Particularly on line 71 (for reference: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L71), the commentary indicates it will kick a build at this point. This is the behavior I wished to occur which did not happen. 2) The github-plugin page at (https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin) indicates this is a primary objective of the plugin itself on the landing page: {{Trigger a job when you push to the repository by groking HTTP POSTs from post-receive hook and optionally auto-managing the hook setup. Report build status result back to github as Commit Status (documented on SO)}} This is exactly what I was trying to do; and this is exactly not what is happening on my server. If this is, after this body of evidence, somehow not related to this plugin, can you explain to us where we can collect the information required to find the right place to comment, and perhaps point us to this place?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37781) Pipeline Config: ability to skip whole pipeline or stages based on boolean condition
Title: Message Title James Dumay commented on JENKINS-37781 Re: Pipeline Config: ability to skip whole pipeline or stages based on boolean condition Patrick Wolf not sure if this was documented? May have slipped through the cracks. 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-36269) git fetch returned status code 143 after 10 minute timeout
Title: Message Title Halin Lee commented on JENKINS-36269 Re: git fetch returned status code 143 after 10 minute timeout I have the same issue,but still not figure out, My log: My Setting: My Network Record: The third request is successful authenticated 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-36269) git fetch returned status code 143 after 10 minute timeout
Title: Message Title Halin Lee updated an issue Jenkins / JENKINS-36269 git fetch returned status code 143 after 10 minute timeout Change By: Halin Lee Attachment: NetworkRecord.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-36269) git fetch returned status code 143 after 10 minute timeout
Title: Message Title Halin Lee updated an issue Jenkins / JENKINS-36269 git fetch returned status code 143 after 10 minute timeout Change By: Halin Lee Attachment: setting.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-36269) git fetch returned status code 143 after 10 minute timeout
Title: Message Title Mark Waite commented on JENKINS-36269 Re: git fetch returned status code 143 after 10 minute timeout That's great news. Any suggestions on how the plugin could have detected and isolated that problem for you? There is an ongoing pattern of authentication issues which users encounter. They typically result in a bug report (like this one), which I close. It would be much better if I could find ways to provide a detailed diagnosis of the exact location in the chain where the authentication failed. 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-36269) git fetch returned status code 143 after 10 minute timeout
Title: Message Title Halin Lee updated an issue Jenkins / JENKINS-36269 git fetch returned status code 143 after 10 minute timeout Change By: Halin Lee Attachment: 143log.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-40315) Pipeline tests for ALM not works in new version of Jenkins Plugin on Windows Jenkins 2.7.4 server
Title: Message Title Roy Lu commented on JENKINS-40315 Re: Pipeline tests for ALM not works in new version of Jenkins Plugin on Windows Jenkins 2.7.4 server Isn't the latest weekly release version is 2.3.5? 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title James Dumay assigned an issue to Michael Neale Jenkins / JENKINS-40369 rerun button in rundetails sometimes redirects to the wrong url Change By: James Dumay Assignee: Michael Neale 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40369 rerun button in rundetails sometimes redirects to the wrong url Change By: James Dumay Sprint: frank 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-39542) Tests tab "Cannot read property 'trim' of null"
Title: Message Title Ivan Meredith started work on JENKINS-39542 Change By: Ivan Meredith Status: Open In Progress 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-40366) When closing rundetails, sometimes the activities page does not render.
Title: Message Title Ivan Meredith resolved as Cannot Reproduce Jenkins / JENKINS-40366 When closing rundetails, sometimes the activities page does not render. Change By: Ivan Meredith Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40341) Can not view stack trace for NUnit tests
Title: Message Title James Dumay commented on JENKINS-40341 Re: Can not view stack trace for NUnit tests Michael Neale I am reasonably sure that they are not the same thing but this needs verification. 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-40366) When closing rundetails, sometimes the activities page does not render.
Title: Message Title Michael Neale stopped work on JENKINS-40366 Change By: Michael Neale Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-40369 rerun button in rundetails sometimes redirects to the wrong url Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/12 2:30 AM Priority: Major Reporter: Ivan Meredith This is 100% repeatable for me. 1. Start ath running in dev mode. 2. Run nightwatch src/test/js/failing.js 3. If you want to see it again, you MUST restart ath. You will see on step 5 it redirects to run '3' when it should be '2'. HOWEVER for subsuequent runs of failing.js, it works properly. It's only on the first run of failing.js after the ath is started. No idea what is going on here and I havent replicated it outside of ATH. Add Comment
[JIRA] (JENKINS-40341) Can not view stack trace for NUnit tests
Title: Message Title Michael Neale commented on JENKINS-40341 Re: Can not view stack trace for NUnit tests Could this be the same thing that will be solved by: https://issues.jenkins-ci.org/browse/JENKINS-38754 ? 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-38075) Github Plugin build strategy improvement
Title: Message Title Kanstantsin Shautsou commented on JENKINS-38075 Re: Github Plugin build strategy improvement There are multiple separate plugins that has trigger features, githubpush trigger do what initial author did and behaviour can't be changed. Normally it should be named as GitHub gitscm poll trigger. If you want you can wait something in github-plugin but i guess nothing will be done in scope of this plugin because separate already existed. 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-40368) Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Title: Message Title
Denys Digtiar created an issue
Jenkins / JENKINS-40368
Locked resources are not always freed up on Pipeline hard kill when there are other pipelines waiting on the Resource
Issue Type:
Bug
Assignee:
Unassigned
Components:
lockable-resources-plugin
Created:
2016/Dec/12 1:11 AM
Environment:
lockable-resources:1.10
Labels:
pipeline robustness
Priority:
Major
Reporter:
Denys Digtiar
Resource lock is not always released when there is some contention over it. This can, intermittently, be reproduced by running two builds of the below pipeline concurrently. Retry will simulate inability to cancel the build which should make hard kill link to appear. Canceling the builds in turn as they acquire the lock will sometimes produce the dangling lock.
retry(5) {
node('linux') {
lock('my-resource') {
println ("running find")
sh "find / -name hello.txt"
}
}
}
[JIRA] (JENKINS-18598) Deploy created Artifact to Github as a Release
Title: Message Title Kanstantsin Shautsou commented on JENKINS-18598 Re: Deploy created Artifact to Github as a Release Feel free to provide Pull Request. Nobody is working on this feature in github-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-38075) Github Plugin build strategy improvement
Title: Message Title Danny Cosson commented on JENKINS-38075 Re: Github Plugin build strategy improvement That's the whole point of this issue. Kicking off GitSCM.poll (especially if you know it's buggy) should not be the only option. This is a feature request to allow github to trigger a jenkins build directly via a github webhook. 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-19674) Getting exception while adding git repository to jenkins new maven job.
Title: Message Title Kanstantsin Shautsou resolved as Incomplete Jenkins / JENKINS-19674 Getting exception while adding git repository to jenkins new maven job. Change By: Kanstantsin Shautsou Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19674) Getting exception while adding git repository to jenkins new maven job.
Title: Message Title Kanstantsin Shautsou commented on JENKINS-19674 Re: Getting exception while adding git repository to jenkins new maven job. https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+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-16513) Duplicate builds being triggered upon github merges.
Title: Message Title Kanstantsin Shautsou resolved as Not A Defect Jenkins / JENKINS-16513 Duplicate builds being triggered upon github merges. Change By: Kanstantsin Shautsou Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16513) Duplicate builds being triggered upon github merges.
Title: Message Title Kanstantsin Shautsou commented on JENKINS-16513 Re: Duplicate builds being triggered upon github merges. github-plugin contains only githubpush trigger atm that kicks GitSCM.poll() if you have any problems with find commit logic, then it git-plugin issue. You can also search and try other variants of branch/pr triggers. 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-34320) Disable rate_limit check for GitHub Enterprise
Title: Message Title Kanstantsin Shautsou closed an issue as Not A Defect Jenkins / JENKINS-34320 Disable rate_limit check for GitHub Enterprise Change By: Kanstantsin Shautsou Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34320) Disable rate_limit check for GitHub Enterprise
Title: Message Title Kanstantsin Shautsou commented on JENKINS-34320 Re: Disable rate_limit check for GitHub Enterprise This plugin is only wrapper, you should report issues to github-api project. 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-37190) Unauthenticated request to GitHub trigger rate limits when adding organization
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-37190 Unauthenticated request to GitHub trigger rate limits when adding organization Change By: Kanstantsin Shautsou Component/s: github-api-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-31744) Add environment variable containing GitHub project url
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-31744 Add environment variable containing GitHub project url Change By: Kanstantsin Shautsou Comment: Should be GITHUB_REPO_URL to not be too jeneric 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-29827) Github webhook ignore "Github project" field (I.E. projectUrl)
Title: Message Title Kanstantsin Shautsou closed an issue as Incomplete Jenkins / JENKINS-29827 Github webhook ignore "Github project" field (I.E. projectUrl) Change By: Kanstantsin Shautsou Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title Kanstantsin Shautsou closed an issue as Incomplete Jenkins / JENKINS-33908 github plugin generates lots of undesired threaddumps on recreate webhooks Change By: Kanstantsin Shautsou Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33974) Add option to verify "secret" token
Title: Message Title Kanstantsin Shautsou commented on JENKINS-33974 Re: Add option to verify "secret" token CloudBees plugin uses separate connector, so there is no relation. Please report branchsource/orgfolder issues to CloudBees. For secret verification some repository should created trigger and then send ping event. When global configuration configured there is no any repositories that could be used for testing. You can call re-register all hooks and then check mange jenkins page that will have report in case of failed hooks creation. But maybe it doesn't check with ping event that hook succesfully configured... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30144) thinBackup does not backup Slave settings
Title: Message Title Naoki Kawamukai closed an issue as Fixed Thank you. I confirmed that this issue was fixed with thinBackup 1.9.0. Jenkins / JENKINS-30144 thinBackup does not backup Slave settings Change By: Naoki Kawamukai Status: Resolved Closed 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-38075) Github Plugin build strategy improvement
Title: Message Title Kanstantsin Shautsou commented on JENKINS-38075 Re: Github Plugin build strategy improvement new commits in PRs is not a github-plugin functionality or describe and provide configuration that you has to have any idea how reproduce your issue. 2) As it written in github-plugin docs, this plugin only kicks GitSCM.poll() so any (imho buggy) trigger/choose commit logic is git-plugin issue. You can also try to use other triggers i implemented experimental branch trigger in https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Integration+Plugin that kicks builds exactly for commits. 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-38075) Github Plugin build strategy improvement
Title: Message Title Kanstantsin Shautsou closed an issue as Not A Defect Jenkins / JENKINS-38075 Github Plugin build strategy improvement Change By: Kanstantsin Shautsou Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37845) GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
Title: Message Title Kanstantsin Shautsou commented on JENKINS-37845 Re: GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with github plugin provides only simple trigger that kicks GitSCM.poll() if you expect something other for Jenkinsfiles/workflows then it not github-plugin issue. choose Jenkinsfile also has no relation, probably you are using CB plugins, reassigned. 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 Kanstantsin Shautsou assigned an issue to Stephen Connolly Jenkins / JENKINS-37845 GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with Change By: Kanstantsin Shautsou Assignee: Kirill Merkushev 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-37845) GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-37845 GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with Change By: Kanstantsin Shautsou Component/s: github-branch-source-plugin Component/s: github-organization-folder-plugin Component/s: github-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-38649) Add support to Job-dsl
Title: Message Title Kanstantsin Shautsou resolved as Not A Defect job-dsl supported for a long time you can find examples in github repository tests. Jenkins / JENKINS-38649 Add support to Job-dsl Change By: Kanstantsin Shautsou Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-39517) Choose GitHub Server for each job
Title: Message Title Kanstantsin Shautsou commented on JENKINS-39517 Re: Choose GitHub Server for each job Makes sense. This change would require deep github-plugin refactoring that may be not possible easily. I have some experimental stuff but it not ended and not opensourced yet, but part of it is already prepared in https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Integration+Plugin I will reply if i find something. 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-39553) Make GitHub plugin BuildableItem aware
Title: Message Title Kanstantsin Shautsou updated JENKINS-39553 Jenkins / JENKINS-39553 Make GitHub plugin BuildableItem aware Change By: Kanstantsin Shautsou 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-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins
Title: Message Title Kanstantsin Shautsou commented on JENKINS-39632 Re: Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins at com.cloudbees.jenkins.Cleaner.doRun(Cleaner.java:67) what is this? 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-39845) GitHub project URL property should not trim off tree/branch
Title: Message Title Kanstantsin Shautsou closed an issue as Won't Do GithubProjectProperty is used and expected by all plugins to have repository URL, that's why it strip everything unrelated. Jenkins / JENKINS-39845 GitHub project URL property should not trim off tree/branch Change By: Kanstantsin Shautsou Status: Open Closed 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 Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-40150) Git operations fail after global lib is loaded
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-40150 Git operations fail after global lib is loaded Change By: Kanstantsin Shautsou Component/s: github-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-40150) Git operations fail after global lib is loaded
Title: Message Title Kanstantsin Shautsou edited a comment on JENKINS-40150 Re: Git operations fail after global lib is loaded Workflow, cps or whatever it is probably should set context of executed code to job. I see nothing that github-plugin could do for workflow magic. If somebody will know solution, issue could be reopened get github-plugin component back . 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-40150) Git operations fail after global lib is loaded
Title: Message Title Kanstantsin Shautsou commented on JENKINS-40150 Re: Git operations fail after global lib is loaded Workflow, cps or whatever it is probably should set context of executed code to job. I see nothing that github-plugin could do for workflow magic. If somebody will know solution, issue could be reopened. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40192) java.io.IOException: Cannot run program "git" (in directory "/home/jenkins/workspace/pipeline"): error=2, No such file or directory
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-40192 java.io.IOException: Cannot run program "git" (in directory "/home/jenkins/workspace/pipeline"): error=2, No such file or directory Change By: Kanstantsin Shautsou Component/s: github-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-40359) Webhook registration fails for private Github repositories
Title: Message Title Kanstantsin Shautsou commented on JENKINS-40359 Re: Webhook registration fails for private Github repositories How much github servers do you have in global settings? Have you ensured that global user accepted invite to repository? 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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Kanstantsin Shautsou edited a comment on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens Github pullrequest trigger in screenshot issues doesn't belong to github-plugin. You should ensure from what plugin do you use functionality, follow plugin docs and report issues according to docs. Github-org-folder especially offtopic for issue. This issue has the mess of unrelated to github-plugin questions -> Issue closed. 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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Kanstantsin Shautsou closed an issue as Not A Defect Github pullrequest trigger in screenshot issues doesn't belong to github-plugin. You should ensure from what plugin do you use functionality, follow plugin docs and report issues according to docs. Jenkins / JENKINS-35132 Pipeline: GitHub webhook received but nothing happens Change By: Kanstantsin Shautsou 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
[JIRA] (JENKINS-40323) No SCM selected when adding a shared library
Title: Message Title James Dumay commented on JENKINS-40323 Re: No SCM selected when adding a shared library Jesse Glick whats the difference as far as the users concerned? Any behavioural difference or is it just a implementation detail? 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-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40326 Pipeline results (karaoke) doesn't reload when master is restarted Change By: James Dumay * Steps to reproduce** Run a long running pipeline* Open pipeline results screen and follow along* While running, restart the master* Note that results screen never subsequently updates * What should happen : * Results screen should trigger a full reload (which may involve logging in) but then continue following along. Discovered by [~rtyler] discovered this recently . 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-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40326 Pipeline results (karaoke) doesn't reload when master is restarted Change By: James Dumay Sprint: kraken 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-40367) Investigate making use of categories in with SCM 2.0 API
Title: Message Title James Dumay commented on JENKINS-40367 Re: Investigate making use of categories in with SCM 2.0 API Stephen Connolly will the SCMCategory have ordinal value? e.g. if I call getCategories will the return value of these always be the same? 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-40367) Investigate making use of categories in with SCM 2.0 API
Title: Message Title
James Dumay edited a comment on JENKINS-40367
Re: Investigate making use of categories in with SCM 2.0 API
[~stephenconnolly] will the SCMCategory have ordinal value? e.g. if I call {{getCategories}} will the return value of these returned collection order always be the same?
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-40367) Investigate making use of categories in with SCM 2.0 API
Title: Message Title James Dumay commented on JENKINS-40367 Re: Investigate making use of categories in with SCM 2.0 API Patrick Wolf that's right - it would encompass work for any other implementations we might want to support. 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-40367) Investigate making use of categories in with SCM 2.0 API
Title: Message Title Patrick Wolf commented on JENKINS-40367 Re: Investigate making use of categories in with SCM 2.0 API And other implementations such as Gitlab, Gogs, etc that don't use the term "Pull Requests" 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-37295) Redesign the empty states
Title: Message Title James Dumay commented on JENKINS-37295 Re: Redesign the empty states Brody Maclean thats really quite nice 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-39683) 500 error preventing flow graph and steps from showing :(
Title: Message Title James Dumay commented on JENKINS-39683 Re: 500 error preventing flow graph and steps from showing :( Sean Wild the b13 release is now in the update center! 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-37245) Developer can jump to the run history for a specific branch
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37245 Developer can jump to the run history for a specific branch Change By: James Dumay Sprint: tethys kraken 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-35768) Developer can filter the activity list to a specific branch
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35768 Developer can filter the activity list to a specific branch Change By: James Dumay Sprint: tethys kraken 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-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39628 Handle skipped stages and parallels in the Pipeline Graph Change By: James Dumay Sprint: tethys kraken 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-38540) Add REST API redirects for /runs and /queue
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38540 Add REST API redirects for /runs and /queue Change By: James Dumay Sprint: pacific, atlantic, indian, arctic, tasman , tethys 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-38876) Injection of js libs, dependencies and extension point improvements.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38876 Injection of js libs, dependencies and extension point improvements. Change By: James Dumay Sprint: atlantic, indian, arctic, tasman , tethys 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-39345) Use js-modules to coordinate async loading of i18n translation bundles as part of dependant JavaScript bundle
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39345 Use js-modules to coordinate async loading of i18n translation bundles as part of dependant _javascript_ bundle Change By: James Dumay Sprint: indian, arctic, tasman , tethys 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-39804) Official Blue Ocean docker container
Title: Message Title James Dumay updated JENKINS-39804 Jenkins / JENKINS-39804 Official Blue Ocean docker container Change By: James Dumay Status: In Progress Review 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-39804) Official Blue Ocean docker container
Title: Message Title James Dumay started work on JENKINS-39804 Change By: James Dumay Status: Open In Progress 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-40137) Open in blue ocean button does not work for runs when the branch name contains a /
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40137 Open in blue ocean button does not work for runs when the branch name contains a / Change By: James Dumay Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39345) Use js-modules to coordinate async loading of i18n translation bundles as part of dependant JavaScript bundle
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39345 Use js-modules to coordinate async loading of i18n translation bundles as part of dependant _javascript_ bundle Change By: James Dumay Sprint: indian, arctic, tasman , frank 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-40080) All pages make multiple /classes requests
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40080 All pages make multiple /classes requests Change By: James Dumay Summary: Pipeline summary makes All pages make multiple /classes requests 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.
