Forum Discussion

jeffshurtliff's avatar
jeffshurtliff
Boss
5 years ago

Lithium SDK CI demo (lithiumtech/linc-sdk-demo) not found in GitHub

The Continuous Integration section of the SDK development workflow page in the developer documentation references the GitHub demo project https://github.com/lithiumtech/linc-sdk-demo, which I'm very interested in exploring. 

However, the repository is not found and displays a 404 page.

Can someone at Khoros please investigate or does someone have a fork of it that can share a URL?  Thanks!

  • SuzieH's avatar
    SuzieH
    5 years ago

    jeffshurtliff The repo should be public now. Please let me know if you see something different. The example is pretty old. I've created a ticket for the team responsible to update it, but I don't have an estimate for when they might be able to pick that up. For now, please use the current example as guidance. 

  • jeffshurtliff's avatar
    jeffshurtliff
    Boss
    5 years ago

    Hi bwebster1216,

    This demo repo is specifically demonstrating how to integrate CI with the SDK, and isn't the SDK itself.  Depending on which operating system you're using, I would recommend checking out these references:

    One thing I've learned is that the version of Node and NPM you install is extremely important.  (For example, in Windows I'm running Node v11.15.0 and in CentOS 8 I'm running v6.11.2 to get the SDK to install properly.)

    Hope this helps!

  • SuzieH's avatar
    SuzieH
    Khoros Alumni (Retired)
    5 years ago

    HI jeffshurtliff. I'll look into this. 

     

    UPDATE: The repo was made private. I've sent a request to make it public again. I'll update when I know more.

    UPDATE (27 July 2020): The repo still exists (phew!). We're in the process of going through the channels needed to return something that got changed to private back to public. A bit of red tape. But we're moving forward.

    UPDATE (29 July 2020): Still working on this. One more approval to get and we should be good to get this repo back to public access.

     

     

    • bwebster1216's avatar
      bwebster1216
      Contributor
      5 years ago

      I'm new to Khoros and I'm going to be the Community Manager for our Community. I was trying to get my development environment up and going yesterday by installing the Lithium-SDK on my local and it keeps falling to install. Would this issue of the repo being made private be possibly causing the issue? Also, is there more specific instructions for installing than what I was watching in the Advanced Developer Training course in Campus.lithium.com? Specifically with regards to installing Python correctly for the SDK to work. I know nothing about Python.

      • SuzieH's avatar
        SuzieH
        Khoros Alumni (Retired)
        5 years ago

        Hi bwebster1216. This demo repo shouldn't be affecting your ability to install the Community Plugin SDK. I noticed that I was also running into errors when I tried to install it locally last week. I recommend creating a Support ticket. I have a feeling that there might have been a regression.


  • SuzieH's avatar
    SuzieH
    Khoros Alumni (Retired)
    5 years ago

    jeffshurtliff The repo should be public now. Please let me know if you see something different. The example is pretty old. I've created a ticket for the team responsible to update it, but I don't have an estimate for when they might be able to pick that up. For now, please use the current example as guidance. 

    • jeffshurtliff's avatar
      jeffshurtliff
      Boss
      5 years ago

      Excellent, thanks so much SuzieH! (And DougS!)  Very helpful!

      One thing I'm hoping to figure out (but will likely create a separate topic/thread for after doing some additional research) is performing some Sass linting before submitting the plugin (in an automated way using a CI build) to avoid any skin failures.

      I've learned the hard way that submitting a skin via the SDK that has even a minor syntax error (e.g. typo in a variable name, etc.) will result in bricking the skin and showing an "unexpected error has occurred" message when loading the environment, which I want to avoid.  

      This is my current linting process in the SDK when ready to push up a change:

      1. I run li serve-sass and make sure it doesn't fail with any errors (as it tends to report errors that li submit-plugin doesn't catch that result in bricking the skin)
      2. I use Ctrl+C to stop the server that spins up in the previous step.
      3. I then run li submit-plugin to push the changes, again making sure nothing fails out with errors.

      My hope is to find a linting process that will work within a CI build (i.e. automated / hands-off) so code isn't deployed and pushed to our Stage environment if it has issues.

      Anyway, thanks again for your help in making this public!