|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
[JIRA] (JENKINS-14144) Build config history getting spammed
gregory.boissi...@gmail.com (JIRA) Thu, 30 Aug 2012 17:12:53 -0700
- [JIRA] (JENKINS-14144) Build config his... h...@koblmueller.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... h...@koblmueller.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... dbai...@hp.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... h...@koblmueller.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-14144) Build confi... dbai...@hp.com (JIRA)
I'm sorry for not getting back to you sooner.
EnvInject plugin changes the job configuration file during the build: add a build wrapper at startup and remove it at the end.
It is a way to the envinject to achieve specific features (no other way to do it at the moment).
However, Jenkins saves its changes to the filesystem though the config.xml.
I'm looking for how to remove notifications.