That way it’s easy to see if you caused the build to fail for a real reason (configuration) or if it’s due to code change (triggered builds).

2) Go to your build job where you usually run your tests and everything else; I recommend to always build after having done any modification. Edward A Webb. A Bamboo Agent is a service that provides capabilities to run job builds.There are two types of Bamboo agents: local agents run as part of the Bamboo server.

That capability will point to the

In Jenkins, we can define labels and group number of build slaves under the label. bamboo_agent_capabilities: [] A list of Bamboo capabilities. This label then can be mapped to job so jenkins will automatically pick the available build slaves in the pool and
4) Enter the argument to the full path of your CppDepend project file (.cdproj extension). Since there’s no As stated previously, this section is more for those who already have a project with no severe issue that causes a quality gate to fail, or if you want to fail upon quality gate but still want to generate reports. Once this is complete, select the

Now, we can use that capability during our build. See the Agent specific capabilities. Install a remote agent (i) From the Administration menu, select Overview and download the agent on the remote machine. Any version greater than 8 won’t work. Retrieve the build results for a specific plan in a project. It is common to keep those capabilities or executable in that screen.

Once the artifact will open, it will show the content of the ZIP file. In this case, we will add the CppDepend capability to a Windows agent.

Let’s consider that your build already exists and that you want to add the The report will exist even on failure, however the build will be red and your artifact will probably not be even available. In this case, instead of creating a command, we will create a script (or add to current Dotnet Core build script) As you can see, after doing the previous steps, you will have your Agent specific capability added. Bamboo Build configuration – PowerShell Script (Complex)1) Go in your Build configuration, default stage (or specific one) and click on 3) Click on the artifact name that interest you (CppDepend in this case) Bereinigung des Remote Agent workspace. 2) The description of the task, in this case: CppDepend;

This should prevent the Windows remote agent from picking up that job. So on the linux agent, define a custom capability for that agent. To do so, we need to add the artifact configuration. It groups all your agent(s) features. 3) Select the executable you created for your agent capability: CppDepend;

The PowerShell is using the existing CppDepend project file (
; remote agents run on computers, other than the Bamboo server, that run the remote agent tool. Each job inherits the requirements from individual tasks that it contains.You can define the following capabilities for an agent:Capabilities typically define the path to an executable that has already been installed, and must be defined in Bamboo before Bamboo or its agents can make use of those.Capabilities can be defined specifically for an agent, or they can be shared between all remote agents.

Thanks Richard. Please, go back in the Build configuration and your default stage where you have the CppDepend script. Each job inherits the requirements from individual tasks that it contains. Yes No.

Feel free to create a feature request and explain use case you dont see being met.