# Homey CLI CI/CD publising

**URL:** <https://community.homey.app/t/homey-cli-ci-cd-publising/103976>\
**Category:** Developers\
**Tags:** app\
**Created:** [February 14, 2024, 10:15am UTC](https://community.homey.app/t/homey-cli-ci-cd-publising/103976 "2024-02-14T10:15:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![julianao](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/julianao/32/79652_2.png) [@julianao](https://community.homey.app/u/julianao)\
**Post date:** [February 14, 2024, 10:15am UTC](https://community.homey.app/t/homey-cli-ci-cd-publising/103976/1 "2024-02-14T10:15:05Z")

</div>

Hi,

I am looking into automating my Homey app publishing process using a CI/CD pipeline in Azure DevOps

The main challenge I’ve encountered is automating the `homey login` step. As you might know, the standard login process is interactive and requires navigating to a URL and then logging in on the web page. This interactive step doesn’t lend itself well to the automated nature of CI/CD pipelines.

Are there any supported methods for non-interactive authentication with the Homey CLI that I might have missed? Perhaps something using API tokens, service accounts, or other mechanisms that are more CI/CD friendly?

Thanks for the help!

---

<div class="post-metadata">

**Author:** ![M\_Corten](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/m_corten/32/79647_2.png) [@M\_Corten](https://community.homey.app/u/M_Corten)\
**Post date:** [February 29, 2024, 7:28am UTC](https://community.homey.app/t/homey-cli-ci-cd-publising/103976/2 "2024-02-29T07:28:43Z")

</div>

We have the same problem.

Trying to automate a build in the pipeline so we can publish to our acceptance device one a merge request is merged. Having the same problem with authentication ☹

---

<div class="post-metadata">

**Author:** ![Mel](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Mel](https://community.homey.app/u/Mel)\
**Post date:** [March 4, 2024, 11:15am UTC](https://community.homey.app/t/homey-cli-ci-cd-publising/103976/3 "2024-03-04T11:15:34Z")

</div>

I also have the same issue, we would like to automate our application building for testing and also optimize the code that is shipped so it does not include development dependencies.

**Does anyone know if we can send a feature request for this to Homey?**

I looked into the CLI tool, but it seems like there’s no way at the moment.

> <https://github.com/athombv/node-homey/blob/develop/lib/AthomApi.js>

It either opens the URL and uses the token automatically, or you need to open the page manually and have a way to add the token in the CLI interactively which will not work for a pipeline. ☹