Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bugfix:Autograding] Fix location of Jupyter Dockerfile #47

Merged
merged 2 commits into from
Sep 9, 2024

Conversation

williamjallen
Copy link
Member

What is the current behavior?

#40 inadvertently put the Jupyter Dockerfile in the wrong directory.

What is the new behavior?

Fixes the directory structure.

Copy link
Member

@bmcutler bmcutler left a comment

Choose a reason for hiding this comment

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

I think instead of jupyter/jupyter, we would like to do jupyter/2.71
and then latestTag would be "2.71".

(but @cjreed121 should confirm)

@cjreed121
Copy link
Member

I think instead of jupyter/jupyter, we would like to do jupyter/2.71 and then latestTag would be "2.71".

(but @cjreed121 should confirm)

Correct. I've been discussing this with him off of GitHub. We may consider also tagging the associated python version.

@williamjallen
Copy link
Member Author

@bmcutler and @cjreed121, the latest commit pins notebook to 7.2.2 and changes the tag to submitty/jupyter:7.2.

@bmcutler bmcutler merged commit 6552c93 into main Sep 9, 2024
3 checks passed
@bmcutler bmcutler deleted the jupyter-fix branch September 9, 2024 19:46
bmcutler pushed a commit that referenced this pull request Sep 9, 2024
### What is the current behavior?
#47 changed the value of the "latestTag" metadata attribute, but did not
change the directory for the Dockerfile, resulting in the image being
tagged `submitty/jupyter:jupyter` instead of `submitty/jupyter:7.2`.

### What is the new behavior?
Fixes the directory structure.
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.

3 participants