CODECOMPOSER: Automate build for Code Composer Studio projects

Hello,

Stefan Kessler said:

software-dl.ti.com/.../quote]

I would refer to the content in the user's guide for your CCS version.

https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs_20.4.0/index_project-management.html

Stefan Kessler said:

ccs-server-cli.bat -noSplash -workspace <git_repository_root> -data <git_repository_root> -application com.ti.ccs.apps.importProject -ccs.location <git_repository_root>\Project1 -ccs.recurse -ccs.autoBuild

You can remove the "-data <git_repository_root>" parameter. 

Stefan Kessler said:

  !ERROR: A project with the name 'Project1' already exists in workspace

Looks like the project has already been imported to CCS in the past from that same location. If you want to reimport it anyway, then used the -ccs.overwrite option so that it will overwrite the project metadata information in the CCS project server cache.

Stefan Kessler said:

headless build complete – 0 out of 0 projects have errors

I'm not sure if you omitted some of the build output (perhaps for privacy issues) or if that all the actual build output. Is that the full build output? If that is the full output, then are you able to build each individual project if you explicitly specify it with the -ccs.projects command?

[/quote]

Hi,

1) I need the -data <git_repostiroy_root>, otherwise I the the following error output. I can see in https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs_20.4.0/index_project-management.html that there is no such option, but I need it, otherwise it get the error below.

Usage:
ccs-server-cli.bat -workspace '<workspace-dir>' -application <application-id> [<application-arguments>]
ccs-server-cli.bat -help

where:
<workspace-dir> - the absolute path to the workspace directory

<application-id> - the headless application ID, e.g. 'com.ti.ccs.apps.projectBuild' or simply 'projectBuild'
currently supported applications:
1. com.ti.ccs.initialize (or simply 'initialize')
2. com.ti.ccs.apps.projectCreate (or simply 'projectCreate' or 'createProject')
3. com.ti.ccs.apps.projectImport (or simply 'projectImport' or 'importProject')
4. com.ti.ccs.apps.projectModify (or simply 'projectModify' or 'modifyProject')
5. com.ti.ccs.apps.projectBuild (or simply 'projectBuild' or 'buildProject')
6. com.ti.ccs.apps.inspect (or simply 'inspect')

2) I tried to work with -ccs.projects. But that did not work either. However, doing it in a completely new cloned repository again, I realized, that the -ccs.autoBuild option in the com.ti.ccs.apps.importProject command already startet a build (but only if the project is not yet in the workspace)

3) Then I realized that I can easily repeate the behaviour by doing a complete cleanup of all generated files inside the repository, if I only have excuted builds from the command line. However, if once I openend the workspace within the GUI, afterwards I will always get the error message !ERROR: A project with the name 'Project1' already exists in workspace, even though I cleaned up all files inside the repository. It seams that the GUI version is using another workspace but I can't find out the location in order to also remove it.

4) What is the official recommended way of automating builds from exisiting CCS Theia projects.