Git Pro

Aucun avis

Git integration for Ignition Designer. Bring Git-based CI/CD to your Ignition gateways. Every change is versioned, reviewed and tested before it reaches production with instant rollback and full team collaboration, all without leaving Ignition.

Démonstration

Inclus

• Licence perpétuelle par gateway
• Activation en ligne (binding au gateway Ignition)
• Compatible Ignition 8.1, 8.3
• Mises à jour incluses pendant la maintenance
• Support technique OperaMetrix

Notes de version

• v2.2.017 sept. 2026

  First release of Git Pro. A single Git-Pro.modl carrying the complete open-core Git module plus the proprietary DevOps add-ons. Requires Ignition 8.3.0 or later. BEFORE YOU UPGRADE Two changes affect remotes that already work today: - TLS certificates are now verified. A remote served over HTTPS with a self-signed or otherwise untrusted certificate will stop connecting until you opt that remote out explicitly. The opt-out is per remote (and per provider connection in the CI/CD page), not global. - SSH host keys are now verified. The first connection to a host shows its fingerprint for you to accept, and the accepted key is remembered. A host that later presents a different key is refused outright rather than offered for acceptance; that is what interception looks like. Installing Git Pro replaces the free Git module in place. It carries the same module id, so registered projects, credentials and repositories are preserved. NEW - DEVOPS ADD-ONS - CI/CD page on the gateway for provider-driven deployments. - Connect a Git provider once: GitHub (via a per-gateway GitHub App created through the manifest flow), GitLab and Gitea (via OAuth). Self-hosted instances are supported through a base URL. - Pick a repository and branch from a list rather than pasting a clone URL. The project is cloned and created on the gateway using short-lived provider tokens, so no personal access token or SSH key is stored. - Deploy on push: there is no webhook to create or paste by hand. GitHub deliveries arrive through the App's own webhook; on GitLab and Gitea a push hook is created on the repository when the project is added, and removed again when it is. A push to the deployed branch fast-forwards the repository and reimports the project; pushes to other branches are ignored. - Deploy now, for a manual trigger. - Renaming a repository at the provider no longer breaks its deployment. Projects follow the provider's stable repository id rather than its name. LICENSING Pro features require an activated Ignition license covering the module, or trial mode for evaluation. When the trial expires, deployments stop while the rest of the module (every open-core Git feature) keeps working. Activating a license resumes deployments without a restart. SECURITY - TLS certificates are verified by default, with a deliberate per-remote opt-out. - SSH host keys are verified against the keys an operator has accepted, and accepting a key now persists. Previously the acceptance silently failed and re-prompted. - Diff requests naming paths outside the repository are rejected. FIXED - Pulling after a merge no longer fails with CheckoutConflictException when the only local difference is JSON property ordering rewritten by the gateway. - Minimised Designer panels no longer flicker, and closing the Commit or History panel is respected instead of the panel reappearing a second later. - The Designer status bar no longer freezes the UI while polling the gateway. - Designer icons render from vectors, so they stay sharp on HiDPI and scaled displays, and the status bar is only as tall as its buttons need. Icon and status-bar work contributed by Tracey, pull request 1. - A branch's stash is matched exactly, so branches with similar names no longer restore each other's stashed changes. - The repository handle opened for each diff is closed. - A stale CSRF token is refreshed instead of failing every save on the Versioning page. - The Versioning remote drawer prefills once the remote has loaded, instead of opening blank. - Removing a remote or deleting versioning reports failures instead of silently doing nothing. - The image snapshot is validated before the gateway's existing images are cleared, so an unreadable file can no longer leave the gateway with no images. - A failed repository registration no longer leaves a half-created repository behind.