Catch Prettier, TypeScript, and ESLint issues in Jenkins

[felipecrs]

This should allow Jenkins to fail if there's some ESLint issue.

Testing done

N/A

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[felipecrs]

@timja, what if we create another pipeline (through GitHub Actions?) that will only run npm lint and npm test? I can send a PR, should be a very simple pipeline anyway.

I think disregarding the exit code is very dangerous...

[felipecrs]

@timja, what if we create another pipeline (through GitHub Actions?) that will only run npm lint and npm test? I can send a PR, should be a very simple pipeline anyway.

I think disregarding the exit code is very dangerous...

The caveat of this PR's approach is not catching tsc or prettier issues.

[timja]

few minor things, CI is a standard env var that Jenkins supports for running in CI

Thanks for this

[timja]

LGTM, thanks