mcspr / espurna-nightly-builder Goto Github PK

View Code? Open in Web Editor NEW

8.0 5.0 0.0 240 KB

Development branch builder for ESPurna

Home Page: https://github.com/xoseperez/espurna

License: GNU General Public License v3.0

Python 93.92% Dockerfile 6.08%

espurna home-automation firmware esp8266 esp8266-arduino home automation nightly-build github-actions

espurna-nightly-builder's Introduction

ESPurna Nightly Builder

Nightly build?

This repo is used to build binary release of ESPurna from latest commit to the dev branch.

Technical info

Scheduled events are used to trigger the build. See .github/workflows/prepare.yml, .github/workflows/nightly.yml and espurna_nightly_builder helper scripts.

Both workflows can be triggered with a workflow_dispatch event.

prepare.yml

See .github/workflows/prepare.yml

This workflow is (supposed to be) triggered on a schedule. Unless the following tests pass, this stage will result in an error:

The commit that 'dev' branch points at is different from the 'commit.txt' contents.
All Checks of the target repository 'dev' branch are successful.
'master' branch does not point to the same commit as 'dev', as we don't want to re-do the master release.

Finally, the 'commit.txt' is updated with the latest SHA value of the 'dev' branch.

nightly.yml

See .github/workflows/nightly.yml

When 'prepare.yml' is successful or user triggers the workflow manually:

'nightly' branch is fetched with fetch depth 2, and HEAD and HEAD~1 'commit.txt' contents are saved.
Target repository is fetched using the HEAD commit and the generate_release_sh.py script is called (which is also used to build the master branch release)
New pre-release is created with a tag YYYYMMDD, based on the latest modification date of the 'commit.txt'. Body should contain the HEAD~1...HEAD comparison URL.
All of .bin files are uploaded as assets of the pre-release.

Known issues

Incomplete and not working right now

.gitlab-ci.yml uses the same process as original Travis build script, but with notable differences:

Custom container image (see Dockerfile) is used
It is pretending to be Travis for build.sh
Build takes more time than travis

TODO

GitHub commit status / GitHub Checks for 'nightly' branch
Hide commit status for 'builder' branch
Hide releases until build is complete
Redo build completely when triggered by API (remove tag, release and it's assets)
GitLab integration

espurna-nightly-builder's People

Contributors

Stargazers

Watchers

espurna-nightly-builder's Issues

nightly builds stopped?

Hi, it seems there haven't been any nightly builds for a while. Is something broken?

Hi, I'm trying to upgrade from the stable release to the last nightly, I follow the instruction using the web GUI, so I first upgrade using the file
espurna-1.15.0-dev.git509bbea7+nightly20211004-espurna-core-webui-1MB.bin
but after that, when I try to flash the espurna-1.15.0-dev.git509bbea7+nightly20211004-itead-sonoff-rfbridge.bin
I still receive the message Image it too large to fit in the available space for OTA. Consider doing a two-step update

Is not possible to use this method with the sonoff rf bridge?

Thanks for your help

1.14-0-dev does not respond on MQTT messages

Hi,

With the latest version, the 1.14.0-dev does mqtt not work correctly. It looks like it not responded on MQTT messages from Domoticz. When i downgrade to 1.13.6-dev verything works well. This happen to all my Sonoff Touch, Sonoff S20 and neo-coolcam switches. The Sonoff T1 EU2 does completly nothing and looks like dead. Also no response on the serial port. But maybe was the reboot from the build the trigger for dying hardware to die...

Could you look at this?

Thank you! :)

Encendido automatico no programado

Hola!!!
He detectado que cuando se activa un schedule cualquiera, además el evento programado también se ejecuta un encendido a la 01:30 y otro sobre las 04:00. Esto no ocurre si no hay ningún schedule activo.
Lo he comprobado con dos Sonoff, el S26 y el basic.

Gracias

sonoff-basic nightly build

I''ve used sonoff-th nightly build here over the last 2 days - works perfectly and relay status (th16/relay/0) correctly reports the status of the relay - 1 or 0 for on or off

But sonoff-basic nightly on a sonoff basic board (WIFI) always operates the relay perfectly but the status (sandy/relay/0) always returns 1 using alexa or the button or mqtt.

Strangely if I put the TH nightly build into the Sonof basic WIFI board, everything works perfectly including the status.

NOTICE about the builder

https://docs.travis-ci.com/user/billing-overview/#free-plan-credits

Each new user gets automatically assigned to the Free Plan upon signing up. The Free plan contains a one time pool of Credits, not renewable. This plan is meant to let you familiarize with our usage based plans as well as to try out other Travis CI features.

At Jan 21 credits expired, meaning https://travis-ci.com/github/mcsp account is totally useless now.

Since I ~~am a cheapskate~~ don't want to use Travis CI anymore, will need to adapt some other service. Gitlab still feels too convoluted, and Github already has a serviceable replacement already available. Pending letscontrolit/ESPEasy#3462 to figure out a correct approach to releases

Status responses in Espurna 15.x

Espurna 1.14.1 and nightly build 1.15.x (nightly20220116) have a significant difference that will break a lot of existing code (in my case within node-red). Release 1.14.1 puts out floats and ints in the payload, 1.15.x puts out strings or char arrays. That means a ton of code changes in node-red functions to check and convert the strings to float/int. On a Raspberry Pi that is more memory used. Solution... keep the output consistent between versions (and it would be nice to keep them in the same order too). Here is a printout from a microwave V1.14.1 and a coffee maker V1.15.x:

topic: "Microwave/data"
payload: object
current: 0
voltage: 118
power: 0
reactive: 0
apparent: 0
factor: 100
energy: 0.276
time: "2022-02-07 18:01:43"
mac: "CC:50:E3:1B:B9:00"
host: "Microwave"
ip: "192.168.68.102"
id: 5212
qos: 0
retain: false

topic: "Coffee/data"
payload: object
datetime: "2022-02-07 18:01:59"
mac: "5C:CF:7F:7D:2A:F1"
host: "Coffee"
ip: "192.168.68.52"
id: 1995
energy: "0.250"
factor: "0"
apparent: "0"
reactive: "0"
power: "0"
voltage: "124"
current: "0.000"
qos: 0
retain: false

Settings don't seem to save on my Gosund SP111 (using the Blitzwolf bwshpx.bin)

Hi there,

i flashed espurna-1.15.0-dev.gita2c02a38+nightly20211020-blitzwolf-bwshpx.bin to my Gosund Sp111 which was already using 14.1 fine, but i wanted to see what new was in store with an eventual upgrade.

I flashed the core-webui file first, then flashed the normal file through the webui. All seems to install fine, but there are some weird things i've noticed.

For one, the Power units and the Energy units settings don't seem to work. It shows the energy unit standard in J, but when i set it to W it just says nothing has changed, and i can't seem to this working.

Also have an idea that the http api doesn't work properly, i'm using these plugs with Homey and on 14.1 they were working fine, but with this i cannot seem to connect to my Homey anymore. Even removed and tried readding, even tried different HTTP API keys but unfortunately it didn't work. Last i did a factory reset on the power plug itself, reset everything but above issues kept popping up.

Am i missing a step somewhere, or are there still some issues?

Thanks for all your work!

TRAVIS_TAG is nil in cron

tag_name is direct parameter to the api call: https://developer.github.com/v3/repos/releases/#input
https://github.com/mcspr/espurna-travis-test/blob/5bec13586c3749d0493ca833ff7deaa6390df3e3/.travis.yml#L62

https://github.com/travis-ci/dpl/blob/ff979da136f0737750936e544c64ee970983bd76/lib/dpl/provider/releases.rb#L23-L29
checks for TRAVIS_TAG

maybe just do export TRAVIS_TAG=<generated tag> in before_deploy