Skip to content

Run a JPLAG analysis as a container job#1

Draft
AlexandreDoneux wants to merge 16 commits into
mainfrom
run_as_job
Draft

Run a JPLAG analysis as a container job#1
AlexandreDoneux wants to merge 16 commits into
mainfrom
run_as_job

Conversation

@AlexandreDoneux

@AlexandreDoneux AlexandreDoneux commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

The point of this PR is to change the way JPLAG code analysis are made by running them in a job, similarly to any INGInious submission. Steps of this PR :

  • Basic Run with
    • submission selection
    • code language selection
    • similarity threshold
  • Ability to download the results (.jplag file)
  • Run analysis also on input files
  • Add the use of other JPLAG parameters (template archive, old submissions, excluded files, etc.

Additional possible features that fall outside of the scope of this PR :

  • Automatically detect the code language
  • Run multiple analysis, one per language present in the submission
  • Visual feedback through the JPLAG UI directly in INGInious
  • List all previous analysis

…itory

This commit implements the environments as previously introduced by the PR number 1111 in the main INGInious repository (INGInious/INGInious/#1111). It will be followed by changes requested in that PR.
Comment thread __init__.py
@@ -0,0 +1,250 @@
# -*- coding: utf-8 -*-
#
# Copyright (c) 2017 Ludovic Taffin

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Copyright (c) 2017 Ludovic Taffin
# Copyright (c) 2017-2026 Université catholique de Louvain

@anthonygego anthonygego left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're modifying the generic structure of plugins by stripping the main python module folder. Does the pip setup file supports this now ?

Is there a way of ensuring the module name apart of doing a pip edit install ? Adding the repo path the the PYTHONPATH and making import module_name was quite consistent until now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants