I noticed that the Git build for ESPEasy_ESP82xx_mega-20220616 shows 'HEAD_56d3225' in the json file and on the 'System Info' screen while prior releases showed something like 'mega-20211224_f162ebf'. I use this to identify what release a device is using and in a Node-RED flow I've created to do backups and identify what devices are active.
Is this an change to how releases are identified and if so will I be able to get something like 'mega-20211224' off a device?
Thanks!
Git build for ESPEasy_ESP82xx_mega-20220616 shows 'HEAD_56d3225' ??
Moderators: grovkillen, Stuntteam, TD-er
Re: Git build for ESPEasy_ESP82xx_mega-20220616 shows 'HEAD_56d3225' ??
I made those builds on my desktop PC, since the GitHub Actions builds were packaged a bit 'clumsy' with all in 1 large ZIP file.
I will look into it, as I apparently did not label it using the tag bit just did a checkout and then build it.
Will check if this is a user error on my side, or an error in the build script.
I will look into it, as I apparently did not label it using the tag bit just did a checkout and then build it.
Will check if this is a user error on my side, or an error in the build script.
Re: Git build for ESPEasy_ESP82xx_mega-20220616 shows 'HEAD_56d3225' ??
Do you have an example of how the Git tag was on other builds? (including quotes)
It seems like the build script does not set the description based on the tag.
Edit:
Nope, it was a user error, I did not build it with the -t option.
It seems like the build script does not set the description based on the tag.
Edit:
Nope, it was a user error, I did not build it with the -t option.
Re: Git build for ESPEasy_ESP82xx_mega-20220616 shows 'HEAD_56d3225' ??
Thanks for looking into it and figuring it out.
Who is online
Users browsing this forum: Ahrefs [Bot], Google [Bot] and 29 guests