Satellite environment node vs in buildInfo node | Community
Skip to main content
C
clestbest
July 12, 2022
Solved

Satellite environment node vs in buildInfo node

  • July 12, 2022
  • 1 reply
  • 1300 views

I have two different tags with the same extensions installed (all on the same versions) and I can't figure out why one of them has the environment property inside the buildInfo section and the other has it's own environment node.

 

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Stewart_Schilling

It looks like they are running on different turbine versions and have vastly different build dates (one was last built over two years ago).   "Turbine" is the internal name for the Tags (Launch) runtime engine. 

 

 

 

1 reply

Stewart_Schilling
Community Advisor
Stewart_SchillingCommunity AdvisorAccepted solution
Community Advisor
July 12, 2022

It looks like they are running on different turbine versions and have vastly different build dates (one was last built over two years ago).   "Turbine" is the internal name for the Tags (Launch) runtime engine. 

 

 

 

    C
    clestbestAuthor
    July 12, 2022

    So is the fix to build it? It's not clear to me how that's done.

    Stewart_Schilling
    Community Advisor
    Stewart_SchillingCommunity Advisor
    Community Advisor
    July 12, 2022

    Yep, I assume that doing a new build and publishing to production (Publishing workflow in Launch) will resolve the issue.  Do you have a person who normally does this job?  If so, speak with them.  If not, let me know and I'll see if I can help out. 

     

    There is a slight chance that your Launch library is self-hosted which might mean that you have to do more than just build and publish.  

      Terms & ConditionsAccessibility statement

      Loading footer...