Saving build engine in build definition

Baris,

There are 2 main permissions:
- Save Build Definition
- Save Build Engine

Do you have both turned on?

Did you check out the status of:
- Repository Group for the current user
- Client Access Licenses are their validity?

Thanks

Hi Philippe,
User has:
Repository Permissions: JazzUsers
Client Access Licences: "Floating Developer", "Build System"
In project area: "Modify Build Engine" Permission
Does he need any additional permission?

Baris,

Something is not clear in your post.
Are you trying to modify the content of a Build Definition and more particularly the list of Build Engine your Build Definition can run against or are you trying to modify a build Engine.
On the first case, you need to have the permission "Save Build Definition" because you are changing the Build Definition.

ok. To be more clear I am rephrasing the problem:
Originally the user is trying to create a new build definition.
He fills the parameters of a build definition (except supporting build engine), everything is fine, he saves the build definition. But when he sets a build engine to build definition, and trys to save again, he gets the error:

Problem:
You don't have permission to save build engine

Reason:
In order to carry out this operation, you would need permission to perform the following additional actions:

Action: ID:
Modify Build Engine modify

When you change the engine/definition associations, this actually is an operation on the affected engine(s), i.e. the build engine keeps a list of the build definitions it supports. So you need to have permission to Modify Build Engine.

The operation is run in the context of the project or team area associated with the build engine. Since this may be different than the project or team area associated with the build definition, please double-check the engine ownership and whether the user has permissions there.

The error report should also indicate which project/team area it used.

Since this may be different than the project or team area associated with the build definition, please double-check the engine ownership and whether the user has permissions there.

The error report should also indicate which project/team area it used.

Hi, thanks for the answer;
Do you have any documentation about engine ownership? I am starting all build engines, giving a service user id.
Should it be the same user who is trying to define "build engine" in "build definition"?
I mean in our case, the user should start a build engine with his username/password, then should define his build engine in project area's buidl definition.
Is that correct?

I asked the user to repeat the case to see all other details.
Thanks,

The creator of the build engine / definition does not have to be the same user as the one specified on the JBE command line (aka the build user). You do need to ensure that the build user has the appropriate permissions for operations done by JBE and the build itself, though. This is driven by lookup of role-based permissions in the project/team area associated with the engine or definition (depending on the operation) based on the build user's role(s).

Basically, you need to ensure that:
- in the project/team area associated with the build engine, the build user has some role (e.g. 'builduser', or maybe an existing role like 'contributor'), and that role has at least permission for the Build operations operations, and SCM operations if using Jazz SCM. The permissions may also be inherited from a parent project/team area, as long as they're not revoked in the child one.
- likewise for the project/team area(s) associated with any build definition that the engine supports

For more on how process permissions work in Jazz/RTC, see:
https://jazz.net/library/article/291