[ 
https://issues.jenkins-ci.org/browse/JENKINS-13406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

srini ramamurthy updated JENKINS-13406:
---------------------------------------

    Description: 
1. I am using workspace for doing the build. When there are changes in stream A 
from which workspace was created 
and also in the parent stream B (B is parent of A), the changeLog shows only 
the modified files from stream A.
No changes from stream B is shown in the changeLog.

Reason I see is that jenkins accurev plugin stops going up the parent chain if 
it finds changes in stream A.

When I look at the plugin code, it looks like it should be going up the chain 
and capture all modified files in changeLog.
Is not that correct?  Am I missing something here?


2. In this case, I tried not using accurev workspace but directly doing a build 
from the stream.   If jenkins is configured to do build from stream A, jenkins 
does not trigger a build if changes are promoted directly to the parent stream 
B.
   Transaction type that I am looking for is only 'promote'.  Is this not 
implemented?

Note:  Ignore parent stream checkbox was NOT checked for both cases.

Please let me know if there is any workaround.  

Thanks for the support.

Regards
Srini

  was:
1. I am using workspace for doing the build. When there are changes in stream A 
from which workspace was created 
and also in the parent stream B (B is parent of A), the changeLog shows only 
the modified files from stream A.
No changes from stream B is shown in the changeLog.

Reason I see is that jenkins accurev plugin stops going up the parent chain if 
it finds changes in stream A.

When I look at the plugin code, it looks like it should be going up the chain 
and capture all modified files in changeLog.
Is not that correct?  Am I missing something here?


2. If jenkins is configured to do build from stream A, jenkins does not trigger 
a build if changes are promoted directly to the parent stream B.
   Transaction type that I am looking for is only 'promote'.  Is this not 
implemented?

Note:  Ignore parent stream checkbox was NOT checked for both cases.

Please let me know if there is any workaround.  

Thanks for the support.

Regards
Srini

    
> Accurev  plugin changeLog not showing parent stream files modified while 
> using accurev workspace.
> -------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13406
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13406
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: accurev
>    Affects Versions: current
>            Reporter: srini ramamurthy
>            Assignee: Scott Tatum
>              Labels: accurev, jenkins
>
> 1. I am using workspace for doing the build. When there are changes in stream 
> A from which workspace was created 
> and also in the parent stream B (B is parent of A), the changeLog shows only 
> the modified files from stream A.
> No changes from stream B is shown in the changeLog.
> Reason I see is that jenkins accurev plugin stops going up the parent chain 
> if it finds changes in stream A.
> When I look at the plugin code, it looks like it should be going up the chain 
> and capture all modified files in changeLog.
> Is not that correct?  Am I missing something here?
> 2. In this case, I tried not using accurev workspace but directly doing a 
> build from the stream.   If jenkins is configured to do build from stream A, 
> jenkins does not trigger a build if changes are promoted directly to the 
> parent stream B.
>    Transaction type that I am looking for is only 'promote'.  Is this not 
> implemented?
> Note:  Ignore parent stream checkbox was NOT checked for both cases.
> Please let me know if there is any workaround.  
> Thanks for the support.
> Regards
> Srini

--
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

        

Reply via email to