Project

General

Profile

Bug #17684

crontab code is generating wrong path to the launcher again..

Added by Marc Mengel over 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
09/11/2017
Due date:
% Done:

100%

Estimated time:
First Occurred:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

Since the latest rework and version we're getting /home/poms/current/poms/current/cron/launcher
instead of $HOME/current/poms/cron/launcher -- the code in there to add a current link path is borked now that $POMS_DIR has the /current in it already...

Associated revisions

Revision 4ab5f771 (diff)
Added by Marc Mengel about 2 years ago

fix for issue #17685 and issue #17684

History

#1 Updated by Anna Mazzacane about 2 years ago

  • Target version changed from v2_1_1 to v2_2_1

#2 Updated by Marc Mengel about 2 years ago

  • Status changed from New to Resolved

So the bug was in the code that tried to replace .../vx_y/poms in $POMS_DIR with .../current/poms. I changed it so it only tries to change it if:
1) there isn't already a "current" in the POMS_DIR
2) the directory it tries to rewrite it to actually exists.

so in our current virtualenv installs, it won't mess things up.

#3 Updated by Marc Mengel about 2 years ago

  • % Done changed from 0 to 100

#4 Updated by Anna Mazzacane about 2 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF