Seeq Remote Agent Versioning
For installations of Seeq before adopting the Continuous Delivery (CD) model, the Remote Agent and the Seeq Server shared the same version number because they were released together. In the Continuous Delivery (CD) model, the Seeq Server is shipped independently from the Remote Agent. As a result, the Remote Agent will follow its own versioning scheme, separate from the Seeq Server.
What is happening during the transition to CD
During this transition, you may see version numbers that are significantly different:
The Local Agent installed on the Seeq Server will already use the new agent version pattern if the Seeq Server is on CD.
Your Remote Agent will continue using the older version pattern until we release its updated version.
For example, if your Seeq Server is on CD, you might notice:
The Local Agent (labeled as
Seeq-SERVER-0 Local) has a version like100.x.x.<timestamp>-CD.Remote Agents still have versions like
65.x.x-v<timestamp>or66.x.x-v<timestamp>.
Although it may look confusing to see different version schemes for Local and Remote Agents, the system remains fully compatible. The separate version numbers simply reflect different deployment cycles.
Seeq Agent versions 66.1.0 and 65.1.10 are not available for staging from the Agents tag in the Adminstriation page due to the transition to CD. If you need either version, you must manually upload it to your agent machine.
What to expect during the transition to CD
Backward Compatibility: Remote Agents are compatible with Seeq within a one-year window of their release. They generally need updating only once a year unless a critical issue arises or if you would like to use any new features.
Version Scheme Alignment: The version scheme between the Local and Remote Agents will be aligned in the near future (e.g.
100.x.x.<timestamp>-CD). However, their version numbers will still differ going forward simply reflecting their separate deployment cycles.