RTC and Build Forge Integration - Post-build Deliver problem
Hi guys,
I have installed RTC 3.0.1.1, Build Forge 7.1.3 and JBE 3.0.1.1. Everything is configured and the builds are running ok.
The problem is, when I am creating a new RTC build definition and select the post build deliver option, it does not do the deliver on the stream, actually, it does not do any deliver at all. I can see on RTC that the snapshot of the workspace are created, but that is all.
On the build forge log execution for the accept and fetch from RTC (Calling .source JazzJBE), The following snippet can be seen:
This log only appears when the post build deliver option is selected for the build definition.
Also, if I call the com.ibm.team.build.autoDeliver participant for this build on any build step after the accept and fetch, the deliver to the stream occurs without any problem
Is this some bug on the build definition creation? Should I continue to call the autoDeliver participant at the time I wish the deliver to stream?
Regards,
Marcelo Sousa Ancelmo
I have installed RTC 3.0.1.1, Build Forge 7.1.3 and JBE 3.0.1.1. Everything is configured and the builds are running ok.
The problem is, when I am creating a new RTC build definition and select the post build deliver option, it does not do the deliver on the stream, actually, it does not do any deliver at all. I can see on RTC that the snapshot of the workspace are created, but that is all.
On the build forge log execution for the accept and fetch from RTC (Calling .source JazzJBE), The following snippet can be seen:
[Jazz build engine] Invoking pre-build participant "com.ibm.team.build.jazzscm"
[Jazz build engine] CRRTC3507W: Warning: No engine participant found for post_build configuration element "Post-build Deliver"
This log only appears when the post build deliver option is selected for the build definition.
Also, if I call the com.ibm.team.build.autoDeliver participant for this build on any build step after the accept and fetch, the deliver to the stream occurs without any problem
Is this some bug on the build definition creation? Should I continue to call the autoDeliver participant at the time I wish the deliver to stream?
Regards,
Marcelo Sousa Ancelmo
9 answers
I have the same issue.
Same setup, except without BuildForge. With one small difference: My post-build deliver worked when I had a CI build deliver changes to an integration stream, and then I had my Integration build do a post-build deliver back to the Dev stream.
It seems this issue is only duplicable when you try to do a post-build deliver back to the same stream.
Same setup, except without BuildForge. With one small difference: My post-build deliver worked when I had a CI build deliver changes to an integration stream, and then I had my Integration build do a post-build deliver back to the Dev stream.
It seems this issue is only duplicable when you try to do a post-build deliver back to the same stream.
I have the same issue.
Same setup, except without BuildForge. With one small difference: My post-build deliver worked when I had a CI build deliver changes to an integration stream, and then I had my Integration build do a post-build deliver back to the Dev stream.
It seems this issue is only duplicable when you try to do a post-build deliver back to the same stream.
Hi Gregory,
Glad to hear that I'm not alone on this one.
About your observation, i have had this issue doing the deliver to the same stream, and also on a different stream.
Regards,
Marcelo Sousa Ancelmo
Is the problem occuring with all build definitions? If even new build definitions have the problem I would open a ticket with support. I am not aware of a bug with build definitions in 3.0.1.1 that would cause the participant to not show up.
~Spencer
Hi Gregory,
Glad to hear that I'm not alone on this one.
About your observation, i have had this issue doing the deliver to the same stream, and also on a different stream.
Regards,
Marcelo Sousa Ancelmo
~Spencer
I have the same issue.
Same setup, except without BuildForge. With one small difference: My post-build deliver worked when I had a CI build deliver changes to an integration stream, and then I had my Integration build do a post-build deliver back to the Dev stream.
It seems this issue is only duplicable when you try to do a post-build deliver back to the same stream.
Hi Gregory,
Glad to hear that I'm not alone on this one.
About your observation, i have had this issue doing the deliver to the same stream, and also on a different stream.
Regards,
Marcelo Sousa Ancelmo
Hi Spencer,
I had the JBE 3.0.1.1 installed on a RHEL 5.4
For me, the log always appears when the build definition is created with the post-build deliver option checked.
Regards,
Marcelo Sousa Ancelmo
Hi Gregory,
Glad to hear that I'm not alone on this one.
About your observation, i have had this issue doing the deliver to the same stream, and also on a different stream.
Regards,
Marcelo Sousa Ancelmo
I had the JBE 3.0.1.1 installed on a RHEL 5.4
For me, the log always appears when the build definition is created with the post-build deliver option checked.
Regards,
Marcelo Sousa Ancelmo
Is the problem occuring with all build definitions? If even new build definitions have the problem I would open a ticket with support. I am not aware of a bug with build definitions in 3.0.1.1 that would cause the participant to not show up.
~Spencer
I have the same issue.
Same setup, except without BuildForge. With one small difference: My post-build deliver worked when I had a CI build deliver changes to an integration stream, and then I had my Integration build do a post-build deliver back to the Dev stream.
It seems this issue is only duplicable when you try to do a post-build deliver back to the same stream.
Hi Gregory,
Glad to hear that I'm not alone on this one.
About your observation, i have had this issue doing the deliver to the same stream, and also on a different stream.
Regards,
Marcelo Sousa Ancelmo
Hi Guys,
I am using RTC 3.0.1,JBE 3.0.1 and Build forge ....Everything is running ok...my build is successfull ,but post build deliver option does not do the deliver on the stream, actually, it does not do any deliver at all and getting follwing error: "Aborting post-build deliver. A build workspace must be provided"
please help...
I am facing the same issue. RTC 4.0.1 on RHEL with BF 7.1.3.2. We have a standard build in RTC integrated to a standard build in Build Forge. Everything works fine accept the post build deliver step. The error below is thrown in the first step when we source the JBE as well in the end when it tries to deliver.
CRRTC3507W: Warning: No engine participant found for post_build configuration element "Post-build Deliver".
This configuration works just fine without BF integration when build is done in RTC itself with the JBE.
What is the recommended solution? Is this a defect? Do I need to write a custom and target to perform the delivery?
This seems like something that should be working out of the box.
Matt
CRRTC3507W: Warning: No engine participant found for post_build configuration element "Post-build Deliver".
This configuration works just fine without BF integration when build is done in RTC itself with the JBE.
What is the recommended solution? Is this a defect? Do I need to write a custom and target to perform the delivery?
This seems like something that should be working out of the box.
Matt
Just to get this answered, the approach of having an additional build step on Build Forge invoking the Post-build Delivery - Jazz Wiki