-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
Right now, it's not possible to do
githubNotify context: 'something', description: 'Blah blah blah', status: 'PENDING' ... githubNotify context: 'windows', status: 'SUCCESS' // fails when it should not IMO
But in the second call, context should be enough for the plugin to find out which status I want to update. Having to duplicate the description is a bit cumbersome (though I understand it's useful sometimes if one wants to change it afterwards).
Thanks!
[JENKINS-47723] description should only be required for the first call (and even though?)
Description |
Original:
Right now, it's not possible to do {noformat} githubNotify context: 'something', description: 'Blah blah blah', status: 'PENDING' ... githubNotify context: 'windows', status: 'SUCCESS' {noformat} But in the second call, {{context}} should be enough for the plugin to find out which status I want to update. Having to duplicate the {{description}} is a bit cumbersome (though I understand it's useful sometimes if one wants to change it afterwards). Thanks! |
New:
Right now, it's not possible to do {noformat} githubNotify context: 'something', description: 'Blah blah blah', status: 'PENDING' ... githubNotify context: 'windows', status: 'SUCCESS' // fails when it should not IMO {noformat} But in the second call, {{context}} should be enough for the plugin to find out which status I want to update. Having to duplicate the {{description}} is a bit cumbersome (though I understand it's useful sometimes if one wants to change it afterwards). Thanks! |