Judge0 API VS Jenkins

For code execution and testing, I used another third-party solution called Judge0 which is an open-source service.

There are services like Judge0 which you can use to execute the code in a sandbox. Just send a code as a string and get a result back. You can either use their cloud offering or deploy the container yourself (it is opensource). https://github.com/judge0/judge0

I'm trying to run a local version of the Judge0 compiler, but I can't seem to access it.

I have a front-end app which exposes a code editor where the user can provide some code and it will be compiled and executed using judge0 (so not on my server). I would like to be able to save the code created by a user, but I'm not sure of the best route to do this. My initial thought was to save the code as a string in a database, passing through my back-end which could potentially have some sanitizing methods to try and minimize any danger with this. However, I'm not sure how practical/feasible it is to try and sanitize code - has anyone attempted to do this previously or have experience in this domain?

You can deploy Judge0 Extra CE on your own servers for free. Here are the release notes that include the deployment procedure.

https://judge0.com/ to run the code, you can can host it on your server for free or use their api.

A signal gets called which gets sent over Django Channels (but you can probably use an mq or something for this) which notifies a microservice that is responsible for sending and receiving submissions to an instance of https://judge0.com/

MLOps slightly modifies the traditional DevOps CI/CD practice with an additional pipeline called continuous training (CT). The CI/CT/CD pipeline for MLOps involves orchestrating a series of automated steps to streamline the development, training, testing, and deployment of machine learning models. Automating these processes enables efficient model deployment. Standard automation tools include Jenkins, GitLab CI, Travis CI, and GitHub Actions. You will typically set up the MLOps CI/CT/CD pipeline using a trigger for the automation strategy:

Jenkins

Jenkins is a popular automation tool for CI/CD, if you have used GitHub Action, similar to it, most automation tools now provide DSL (Domain Specific Language) to describe & orchestrate automation workflows, Jenkins' Pipeline Syntax is the orchestration language provided by Jenkins, the corresponding orchestration file is generally called Jenkinsfile, syntax rules and Groovy is similar.

In addition, Snyk can be easily integrated with various IDEs, including Visual Studio Code and PyCharm, as well as CI pipelines, such as Jenkins, CircleCI, and Maven, and workflows.

Jenkins is a highly extensible Java-based CI/CD automation server. It is open-source and self-hosted and enables you to automate, build, and deploy your software. The tool seamlessly integrates with various version control systems, cloud providers, and third-party applications, making it a versatile choice for modern development environments.

For instance, IDPs can automatically trigger a deployment process in Jenkins or CircleCI when a developer pushes code to a Git repository.

Familiarize yourself with tools like Jenkins, Travis CI, GitLab CI, and others that facilitate these practices.

Jenkins: An open-source automation server that can be used to set up CI/CD pipelines.

Jenkins is an open-source automation tool that allows developers to build, test and deploy software.