Running the Jenkins connector while using an Agile Central API key causes the following error to be entered in the log file and no job status is updated within Agile Central.
[2018-10-29 13:43:22 Z] DEBUG: AgileCentralConnection.ensureBuildDefinitionExists - Detected build definition cache for the project: Sample Project is empty, populating ... [2018-10-29 13:43:22 Z] DEBUG: AgileCentralConnection.ensureBuildDefinitionExists - Creating a BuildDefinition for 'my.jenkins.server:8080/job/test_project' in Project 'Sample Project' ... [2018-10-29 13:43:22 Z] ERROR: AgileCentralConnection.ensureBuildDefinitionExists - Unable to create a BuildDefinition for: 'my.jenkins.server:8080/job/test_project'; Response for request: builddefinition/create?key=None&workspace=workspace/<WORKSPACE_OID>&project=project/<PROJECT_OID> either was not JSON content or was an invalidly formed/incomplete JSON structure [2018-10-29 13:43:22 Z] ERROR: AgileCentralConnection.ensureBuildDefinitionExists(535) - <OperationalError> Unable to create a BuildDefinition for: 'my.jenkins.server:8080/job/test_project'; Response for request: builddefinition/create?key=None&workspace=workspace/<WORKSPACE_OID>&project=project/<PROJECT_OID> either was not JSON content or was an invalidly formed/incomplete JSON structure [2018-10-29 13:43:22 Z] ERROR: BLDConnector.reflectBuildsInAgileCentral - OperationalException prepACBuildPrerequisites - Unable to create a BuildDefinition for: 'my.jenkins.server:8080/job/test_project'; Response for request: builddefinition/create?key=None&workspace=workspace/<WORKSPACE_OID>&project=project/<PROJECT_OID> either was not JSON content or was an invalidly formed/incomplete JSON structure
The cause of this error is an invalid API key. When the API key is created it can be created with read only and full access. This can cause conflicts in how the key is read.