[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-06-17 Thread hond...@klab.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nozomu Honda commented on  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
 Liam Newman Jon-Paul Sullivan Sorry for my late reply. I changed the status unintentionally.  Please change it back to open.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.1539.1560760681148%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-06-03 Thread j3p...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon-Paul Sullivan commented on  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
 Nozomu Honda - as you changed the status to in progress, could you answer Liam Newman’s question please?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.19571.1559574841553%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-06-03 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman commented on  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
 Jon-Paul Sullivan What I meant was that JIRA says you changed this issue to "In Progress" and I wanted to know if you were working on it. If not, I'll change it back to open.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.19559.1559573340267%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-05-30 Thread j3p...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon-Paul Sullivan commented on  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
 Liam Newman, I did not change it, but I do think that the default behaviour of the plugin should not be one that allows information loss.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16792.1559236560266%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-05-30 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman commented on  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
 Jon-Paul Sullivan I see you changed this to in-progress. What else needs to be done here?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16703.1559229480205%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-05-30 Thread hond...@klab.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nozomu Honda updated  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55726  
 
 
  GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
Change By: 
 Nozomu Honda  
 
 
Status: 
 In  Review  Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16468.1559196960284%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-05-30 Thread hond...@klab.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nozomu Honda updated  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55726  
 
 
  GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
Change By: 
 Nozomu Honda  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved In Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16464.1559196900301%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-05-29 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman edited a comment on  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
 FYI , this  - Rejoice everyone! This  functionality is available here: "Github Custom Notification Context SCM Behaviour"https://github.com/jenkinsci/github-scm-trait-notification-context-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16058.1559161140360%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-05-29 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman commented on  JENKINS-55726  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
 FYI, this functionality is available here:  "Github Custom Notification Context SCM Behaviour" https://github.com/jenkinsci/github-scm-trait-notification-context-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16052.1559161020443%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-05-29 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55726  
 
 
  GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16054.1559161020475%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-55726) GitHub commit status context not unique enough or configurable - jobs always overwrite each other

2019-05-29 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55726  
 
 
  GitHub commit status context not unique enough or configurable - jobs always overwrite each other   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Summary: 
 GitHub  can incorrectly flag PRs as passing checks if multiple  commit status context not unique enough or configurable -  jobs  run against the same repository  always overwrite each other  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196920.154815684.16030.1559159760256%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.