Closed jakub-kocka closed 3 months ago
FYI @tomassebestik
The python part LGTM! Overall, this is a really nice improvement to the release process, thank you!
@georgik I have implemented Jinja2 templating engine for changing (creating) the index.html.
Also, other suggestions were improved. Can you please take a look at it?
Here is the test PR created by the workflow: https://github.com/espressif/idf-installer/pull/233/files
I have added automatically assigned reviewers for PR and branch name with IDF version if there are multiple releases at the same time before the PR gets merged.
Based on the in-person discussion, I am merging this.
update-index
workflow is automatically triggered to update the download page with the releaseSuccessful workflow example: (espressif-ide installer)
Successful PR with installer release created by the workflow:
Automatic "release" mechanism explanation:
build-installer-any
workflow) is configured with all needed parameters (installer type
,ESP-IDF version
,IDE version
,Online installer version
(app version) ... not all parameters are needed every time)Online installer
andIDE installer
are updated every timeOffline installer
is updated if theMAJOR
andMINOR
versions of ESP-IDF are already present in any buttonOffline installer
is not present in any button, a new button is created at the top (=> if the most top button of offline installers has version v5.2.1
and configured ESP-IDF version will be set to v5.3
, the new button will be added above this button)releases.json
is updated by adding the new installer release information as the first objectIdfToolsSetup.iss
is updated with the App or IDE versionupdate-index
workflow is automatically triggered and the download page is updated! WARNING - After this is merged, the original process of running installer build workflows will be changed (with the tag or manual run) => not backward compatible change