shipitjs/shipit

Workspace setting not being respected

Open

#194 opened on May 2, 2018

View on GitHub
 (10 comments) (0 reactions) (0 assignees)JavaScript (5,331 stars) (194 forks)batch import
featgood first issuehelp wanted

Description

hi there,

Just installed latest versions of shipit packages and here's something new:

Running 'deploy:fetch' task...
Create workspace...
Workspace created: "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Initialize local repository in "/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro"
Running "git init" on local.
@ Initialized empty Git repository in /private/var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Ro/.git/
Repository initialized.

☝️ obviously, my workspace isn't set to /var/folders/s0/scv46d414cd28hyzsd5_pcrw0000gn/T/tmp-72206PXTF2WKB77Roso I'm guessing something is wrong with shipit.

Tried chown'ing my workspace folder to 777 to no avail. Don't know where to look, help?

Contributor guide

Tech stack
javascriptnodejsshell
Domain
devopstooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
basic Node.js knowledgeunderstanding of shipit deployment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Start by examining how shipit determines the workspace directory. Look at the source code for workspace creation, particularly the 'deploy:fetch' task. Check if there's a configuration option for workspace path or if it's being overridden. Review comments in the issue for any hints from maintainers. Test by setting a custom workspace path and observing the behavior.