Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build hassfest docker image and pushlish it on beta/stable releases #124706

Merged
merged 11 commits into from
Aug 28, 2024

Conversation

edenhaus
Copy link
Contributor

@edenhaus edenhaus commented Aug 27, 2024

Breaking change

Proposed change

Build hassfest docker images when build workflow runs and test that the hassfest docker image successfully validates core.
On beta/stable releases the hassfest docker image will also be publish

Required for home-assistant/actions#111

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@edenhaus edenhaus requested a review from a team as a code owner August 27, 2024 11:59
@home-assistant home-assistant bot added cla-signed small-pr PRs with less than 30 lines. labels Aug 27, 2024
Copy link
Contributor

@emontnemery emontnemery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @edenhaus 👍

@edenhaus edenhaus changed the title Fix hassfest to use hassfest docker image to verify core Add hassfest argument to specify core integration path Aug 28, 2024
@edenhaus edenhaus marked this pull request as draft August 28, 2024 09:52
@edenhaus edenhaus force-pushed the edenhaus-hassfest-docker-fix branch from 8483b76 to 04bb36a Compare August 28, 2024 12:33
@joostlek joostlek changed the title Add hassfest argument to specify core integration path Add hassfest argument to specify core integration path Aug 28, 2024
@edenhaus
Copy link
Contributor Author

edenhaus commented Aug 28, 2024

@edenhaus edenhaus changed the title Add hassfest argument to specify core integration path Build hassfest docker image on beta/stable releases Aug 28, 2024
@edenhaus edenhaus changed the title Build hassfest docker image on beta/stable releases Build hassfest docker image and pushlish it on beta/stable releases Aug 28, 2024
@edenhaus edenhaus added this to the 2024.9.0b0 milestone Aug 28, 2024
@edenhaus edenhaus marked this pull request as ready for review August 28, 2024 13:40
Copy link
Contributor

@emontnemery emontnemery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, but it would be great with a second opinion from someone more familiar with Docker

@home-assistant home-assistant bot marked this pull request as draft August 28, 2024 13:45
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@edenhaus edenhaus marked this pull request as ready for review August 28, 2024 14:18
@edenhaus edenhaus dismissed emontnemery’s stale review August 28, 2024 14:37

Review done by Joost

@edenhaus edenhaus merged commit 45bb2cd into dev Aug 28, 2024
40 checks passed
@edenhaus edenhaus deleted the edenhaus-hassfest-docker-fix branch August 28, 2024 14:38
run: docker run --rm -v ${{ github.workspace }}/homeassistant:/github/workspace/homeassistant ${{ env.HASSFEST_IMAGE_TAG }} --core-integrations-path=/github/workspace/homeassistant/components

- name: Push Docker image
if: needs.init.outputs.channel != 'dev' && needs.init.outputs.publish == 'true'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we did not target dev for this because there was no ":dev" tag.

As we are now inside the builder that also builds dev, is there still a reason to not update this on dev?
As this is used by custom integration authors, its better to get a new version of hassfest out to them as soon as possible right?

@github-actions github-actions bot locked and limited conversation to collaborators Aug 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-signed small-pr PRs with less than 30 lines.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants