|
|
|
[
Permlink
| « Hide
]
Beirti [10/Apr/15 10:21 AM]
Switching off 'record svn changes' in the advanced settings seems to have resolved this, but I don't understand why it happens at all
This works fine at my side, with or without the record changes step. Here is what I've done:
1. define a svn repository at root level 2. define configuration "root/QA", with a checkout step 3. define configuration "root/Release", with a record changes step 4. define a promotion named "Release" in "root/QA" pointing to "root/Release" 5. run "root/QA" to generate a build 6. promote QA build above to release without any issues. 7. now release has a successful build, promote QA build again to release still does not exhibit any issues. Can you please show me your detailed setup so that I can verified at my side? I got this again today. I think what happens is:
- Create a new promotion which takes input artifacts from another build and also checks something out from subversion - Have the promotion build fail - Re run the promotion Because the initial build failed, it complains when it tries to run the second promotion and get the changes from the previous build. If I delete the build history, this fixes it. Still can not get this reproduced. It will be of great help if you can find out the detailed reproducing steps.
|