5. staging ci know how

1. Branch development

Development is made on staging branches

PR branches are merged into staging branch after

• solidos dependencies updated to most recent between latest and dev tags https://github.com/SolidOS/solidos/blob/main/.github/workflows/update-solidos-deps.yml
• guard on build steps node 22 and 24
• merging to staging should be approved by one maintainer
• pre-release dev version is published on push to staging and tagged with dev https://github.com/SolidOS/solidos/blob/main/.github/workflows/publish-prerelease.yml
• nota: solid-ui: gh-pages storybook is build on staging branch

Nota : before merging to main and publish mashlib MUST be validated

• locally by developers
• by maintainers on the tests servers that are updated every night

2. Test servers update

Test servers

There are 3 tests servers running NSS and PIVOT servers

• Pivot subdomain https://pivot-test.solidproject.org:3000
• Pivot suffix https://pivot-test.solidproject.org:3100
• NSS or JSS https://pivot-test.solidproject.org:8443

Nightly update

• cron job is running at 20:00 UTC every evening

  • notifications (validity 3 hours, free tier) with details on staging branch failure is send
    • just after the cron job ends (10-15 minutes)
    • at 6:00 UTC
  • link https://ntfy.sh/solidos-staging-CHANGE-ME

• Nightly mashlib build

  • pm2 stop all
  • script :
    • clone all staging branches
    • build staging branches with symlinks to solidos staging branch dependencies
    • mashlib staging branch is linked in each test server
  • pm2 restart [server list]