[JIRA] [config-file-provider] (JENKINS-15687) Config File Provider and SCM Sync causes lots of changes to config files

Tue, 07 May 2013 12:14:00 -0700

domi commented on Bug JENKINS-15687

yes, I do agree with you, but this plugin is not explizitlly saving anyting on the job.
but the problem is most probably the following:

  • the plugin creates some files at the start of the job
  • the plugin adds some information about the files created wrapped in an action (CleanTempFilesAction) and adds this action temporarily to the build.
  • when the job finishes, this action gets read and then removed from the job again

I don't know any other way on how to keep this information long enough on the job, so that this info is available to a RunListener (CleanTempFilesRunListener). These files must be rmoved after everything else is done, otherwise some publisher plugins do not have access to these anymore.
Ideally a plugin would be able register temp files to a job and jenkins would take care of removing these after the build.

If you have any other idea on how to solve this, I'm more then happy to change the current implementation.
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

--
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/groups/opt_out.
 
 

Reply via email to