[
https://issues.jenkins-ci.org/browse/JENKINS-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
pjdarton resolved JENKINS-5730.
-------------------------------
Resolution: Fixed
That release got done some time ago - marking as resolved.
> Dispatch transactions trigger a build
> -------------------------------------
>
> Key: JENKINS-5730
> URL: https://issues.jenkins-ci.org/browse/JENKINS-5730
> Project: Jenkins
> Issue Type: Bug
> Components: accurev
> Affects Versions: current
> Reporter: ajanes
> Assignee: Scott Tatum
>
> The accurev plugin sees the dispatch transactions as a trigger to run a
> build. Transactions with a type of dispatch are accuwork changes and do not
> have any file changes. The only transaction typs I am interested in are
> promote transactions. Is there a way to specify the transaction type to
> trigger a build? I want to ignore all dispatch transactions.
> Here is the changes page. The file change is the promote transactions 48953
> and 48952. The others are dispatch changes that trigger a build
> Changes
> #4 (Feb 22, 2010 12:21:18 PM)
> 48957. —administrator/detail
> 48956. —administrator/detail
> #3 (Feb 22, 2010 12:15:53 PM)
> 48955. —administrator/detail
> #2 (Feb 22, 2010 12:10:53 PM)
> 48954. —administrator/detail
> #1 (Feb 22, 2010 12:00:51 PM)
> 48953. This is a valid change. —user/detail
> 48952. Another valid change. —user/detail
> Here is the accurev history for the transaction
> C:\egaming_es_qc_build>accurev hist -t 48957 -fx
> <AcResponse
> Command="hist"
> TaskId="851102">
> <transaction
> id="48957"
> type="dispatch"
> time="1266855575"
> user="administrator"/>
> </AcResponse>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
