• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Register
  • Login
XCP-ng
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Register
  • Login

Commit Number Not Updating?

Scheduled Pinned Locked Moved Xen Orchestra
5 Posts 2 Posters 79 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    AlexQuorum
    last edited by 5 Nov 2024, 17:39

    Hi Everyone,

    Just recently updated to the latest commit and noticed the commit number in XOA hasn't changed:
    If I go to about I see the below:
    b33f771e-56cc-4056-bd08-40945a7c609d-image.png

    I thought my script may have just failed so I reran it but I'm on the (as of writing) current commit:
    ec447c7c-0ad3-42f8-8c6d-a8001082417a-image.png

    Any ideas, is this just broken? I restarted the service manually just to be sure.

    D 1 Reply Last reply 5 Nov 2024, 17:57 Reply Quote 0
    • D
      Danp Vates 🪐 Pro Support Team @AlexQuorum
      last edited by 5 Nov 2024, 17:57

      @AlexQuorum This can happen if xo-web hasn't had a commit since the last time you ran the build process. I believe that this has been discussed previously on the forum, so you may want to search for the prior discussions.

      You can also try running the command yarn run turbo run build --filter xo-web to forcibly rebuild that particular module.

      A 1 Reply Last reply 5 Nov 2024, 18:02 Reply Quote 0
      • A
        AlexQuorum @Danp
        last edited by AlexQuorum 11 May 2024, 19:03 5 Nov 2024, 18:02

        @Danp I just tried doing the web package but it's not made any difference it's not a big deal as I know the actual packages are getting updated but just something I noticed and wanted to share. Makes sense if no commits to the XO-WEB service have been made as you say.

        D 1 Reply Last reply 5 Nov 2024, 18:06 Reply Quote 0
        • D
          Danp Vates 🪐 Pro Support Team @AlexQuorum
          last edited by 5 Nov 2024, 18:06

          @AlexQuorum You may want to try the command again, this time adding --force to it.

          A 1 Reply Last reply 7 Nov 2024, 14:59 Reply Quote 0
          • A
            AlexQuorum @Danp
            last edited by 7 Nov 2024, 14:59

            @Danp Sorry for the delay, in the end I waited for a nother commit to come out and update to it, once I'd done so the issue was fixed. Thanks for your help either way.

            1 Reply Last reply Reply Quote 0
            1 out of 5
            • First post
              1/5
              Last post