-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
Component/s: accurev-plugin
-
None
AccuRev synchronization process which runs several times per hour (as the user "accusync").
While I'm not intimately familiar with our synch process, the AccuRev transaction log indicates every "sync" has 'action=dispatch' and no file modifications.
Previous versions (v0.6.27) of the AccuRev Jenkins plugin did not display these dispatch transactions in the changelog, but after upgrading to v0.6.30 our change log is flooded with them.
Documentation available does not indicate that there is a way to manually disable/ignore these changelog entries... so I will assume that in previous versions the plugin was ignoring them and that functionality has been changed.
• [John Doe] updated file to include help file release 1.0.10 • [Jane Doe] Fixed sorted result set. • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • [accusync] • ... about 100 more ... • [accusync]