Adaptor links versus .source adaptor
Our source type adaptors used via adaptor links successfully run, and cancel/purge the build forge project when there are no souce code changes. However, when we remove the adaptor links, and insert a new step (step 1) in the build forge project and have the step run a dot command (.source our-adaptor), the step fails, as it should, when there is no source code changes but the project does not get cancelled/purged. It just stays in the failed state, which is not wanted. Any ideas appreciated ... thank you,
|
3 answers
look at the trigger variable _CI_BUILD_DELETE
If that variable is set, when the build completes, it will be purged and the build tag decremented.
|
Hi Christopher,
It is recommended to add the variable to the project or to the particular step environment. Using the .bset or .tset would make the variable available for followup steps (not the current). Adaptor Links are far different from dot commands in Build Forge. Adaptor Links run as a prestep to the build itself. This means the Link fires first and if the condition is not met, the build is never actually executed. Dot commands require the build start and execute a step.
|
|
Thanks for the reply ....
We don't already have this variable in our project environments, yet the adaptor link works. Is it recommended that we add this variable to our environment variables to be able to use the .source command? Or will .bset/.tset work? thanks, |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.