Usage of BuildEngine on system-i

Yes, a single JBE can support multiple build definitions, and those definitions may be in separate projects.

Just ensure that:
- the user specified on the JBE command line has the relevant Build and SCM permissions in the process areas associated with both build definitions (or their parent process areas)
- each build definition has its own build workspace (for proper isolation of changes)

It's also recommended that each build definition have its own load directory, particularly if the "delete before build" option is unchecked. You can use the ${buildDefinitionId} substitution if needed.

Yes, a single JBE can support multiple build definitions, and those definitions may be in separate projects.

Just ensure that:
- the user specified on the JBE command line has the relevant Build and SCM permissions in the process areas associated with both build definitions (or their parent process areas)
- each build definition has its own build workspace (for proper isolation of changes)

It's also recommended that each build definition have its own load directory, particularly if the "delete before build" option is unchecked. You can use the ${buildDefinitionId} substitution if needed.

Thanks Nick for your answer. I've found the problem today. It's only a little problem with understanding RTCp and RDp. I've thougt each project needs a BuildEngine, but now I've understood that I must only create the BuildDefinition for each Project with the i-mapping libraries needed.

I hope for the future, that I will not make so easy mistakes.
Thanks

Andreas

Can I use the BuildSpecification for more projects or must I create the BuildSpecifications for each project?

Andreas

I'm not all that familiar with the BuildSpecification concept in RTC/p, but if it's a separate file referred to by the build definition, then I would expect it to be possible to share it across build definitions, as long as the build workspace for each had access to the same file.

Hi Andreas,

A few questions:

- Are the i Projects different applications?

- Do you simply need to load and build the projects into different libraries on the same system?

If they are separate applications and you just need to build them in different libraries, then you can simply create two different build definitions and select the project that you want to build in each build definition. You can use the same build engine for both build definitions.

Note that each project will have to have its build specification which will be used to determine what to compile and what commands to run.

Can I use the BuildSpecification for more projects or must I create the BuildSpecifications for each project?

Andreas

Hi Andreas,

A few questions:

- Are the i Projects different applications?

- Do you simply need to load and build the projects into different libraries on the same system?

If they are separate applications and you just need to build them in different libraries, then you can simply create two different build definitions and select the project that you want to build in each build definition. You can use the same build engine for both build definitions.

Note that each project will have to have its build specification which will be used to determine what to compile and what commands to run.

Can I use the BuildSpecification for more projects or must I create the BuildSpecifications for each project?

Andreas

I have two project areas with one team area for each project.
One is for Demo's and education and the other is our developement.

The sources we use for demo and education are similiar to those in development. The demo project only uses different libraries.

Hi Andreas,

Since they are in two different project areas, you will certainly need two build definitions, one in each project area, to build the source in the project areas. You will also need a build specification in each project.

Cheers,
Kushal

Hi Andreas,

A few questions:

- Are the i Projects different applications?

- Do you simply need to load and build the projects into different libraries on the same system?

If they are separate applications and you just need to build them in different libraries, then you can simply create two different build definitions and select the project that you want to build in each build definition. You can use the same build engine for both build definitions.

Note that each project will have to have its build specification which will be used to determine what to compile and what commands to run.

Can I use the BuildSpecification for more projects or must I create the BuildSpecifications for each project?

Andreas

I have two project areas with one team area for each project.
One is for Demo's and education and the other is our developement.

The sources we use for demo and education are similiar to those in development. The demo project only uses different libraries.