73
edits
Difference between revisions of "ETL"
Jump to navigation
Jump to search
m
no edit summary
m (Fix markup on →Deploying ETL jobs) |
m |
||
| Line 72: | Line 72: | ||
Assuming that you are developing the ETL job on a separate computer and in a dev branch of <code>rocket-etl</code>, this is a typical deployment workflow: | Assuming that you are developing the ETL job on a separate computer and in a dev branch of <code>rocket-etl</code>, this is a typical deployment workflow: | ||
# Use <code>> git add -p</code> to construct atomic commits (each of which should thematically cluster changes) and <code>> git commit -m "<Meangingful commit description>")</code> to commit them. Repeat until all the code that needs to be deployed has been committed. If you need to add a new file (like "sky_maintenance.py"), try <code>>git add sky_maintenance.py</code> and <code> > git commit -m "Add ETL job for sky-maintenance data"</code>. | # Use <code>> git add -p</code> to construct atomic commits (each of which should thematically cluster changes) and <code>> git commit -m "<Meangingful commit description>")</code> to commit them. Repeat until all the code that needs to be deployed has been committed. If you need to add a new file (like "sky_maintenance.py"), try <code>> git add sky_maintenance.py</code> and <code> > git commit -m "Add ETL job for sky-maintenance data"</code>. | ||
# If you have any other changes to your dev branch that aren't ready for deployment, type <code>> git stash save</code> to temporarily stash those changes (so you can switch to the <code>master</code> branch). | # If you have any other changes to your dev branch that aren't ready for deployment, type <code>> git stash save</code> to temporarily stash those changes (so you can switch to the <code>master</code> branch). | ||
# <code>> git checkout master</code> lets you switch to the <code>master</code> branch. | # <code>> git checkout master</code> lets you switch to the <code>master</code> branch. | ||