# is CMake a good alternative for general project task automation

**URL:** <https://discourse.cmake.org/t/is-cmake-a-good-alternative-for-general-project-task-automation/3416>\
**Category:** Usage\
**Created:** [May 26, 2021, 12:12pm UTC](https://discourse.cmake.org/t/is-cmake-a-good-alternative-for-general-project-task-automation/3416 "2021-05-26T12:12:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kyle.edwards](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/k/65b543/32.png) [@kyle.edwards](https://discourse.cmake.org/u/kyle.edwards)\
**Post date:** [May 26, 2021, 12:24pm UTC](https://discourse.cmake.org/t/is-cmake-a-good-alternative-for-general-project-task-automation/3416/2 "2021-05-26T12:24:02Z")

</div>

I wouldn’t recommend CMake for syncing with Git - that’s what Git is for 🙂

I haven’t heard of anyone using CMake to post release pages or interact with hardware, though I suppose you could use custom targets for this.

Provide user with information - again, custom targets are good for this.

The build for CMake itself produces non-code artifacts like documentation and resources, so this is a good fit. Same for determining build-id via Git history.

---

_[View the full topic](https://discourse.cmake.org/t/is-cmake-a-good-alternative-for-general-project-task-automation/3416)._