Skip to content

Adding nopython suffix to the release tag if it's not present - #4458

Open
przepeck wants to merge 2 commits into
mainfrom
przepeck/windows_python_off_change
Open

Adding nopython suffix to the release tag if it's not present#4458
przepeck wants to merge 2 commits into
mainfrom
przepeck/windows_python_off_change

Conversation

@przepeck

Copy link
Copy Markdown
Collaborator

🛠 Summary

CVS-187402
Adding the "_nopython" suffix to the release tag if it's not present and python is disabled.

🧪 Checklist

  • Unit tests added.
  • The documentation updated.
  • Change follows security best practices.
    ``

@przepeck
przepeck requested review from pgladkows and rasapala and a lite review from Copilot August 18, 2026 11:13

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the Windows release Jenkins pipeline to automatically append the _nopython suffix to RELEASE_TAG when Python is disabled, aligning artifact/destination naming with the “no Python” build configuration.

Changes:

  • Add logic in the “Promote package” stage to append _nopython to env.RELEASE_TAG when env.OVMS_PYTHON_ENABLED == "0" and the tag does not already end with the suffix.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread ci/build_test_release.groovy Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants