"Push to Orchest branch" style job deployment

[ricklamers]

Describe the feature you'd love to have in Orchest
We've had requests from multiple users to have more comprehensive support for deploying code in Orchest by simply pushing commits to a branch that can then be picked up to deploy the pipeline in Orchest (as a job).

We're developing our thinking in this area, and this GitHub issue is where we want to keep track.

Relevant other issues are:
#483: managing git access on a user level basis
#958: enabling SSH based remote IDE development workflow

Is your feature request related to a problem? Please describe.
A better local development workflow that integrates with Orchest. The idea is to have a similar duality that exists on GitHub today: you can use Codespaces (browser workbench) or develop & push locally to a remote instance (GitHub.com being the "remote instance").

[dingdayu]

Hi, @ricklamers , I have an idea that might be relevant to this issue.

I need to update the code in Job, it is not allowed now. Only rebuild the Job.

Whether allow the switching of the git commits in Edit Job?

[ricklamers]

Hi @dingdayu, the easiest way to do this is to click "Copy job configuration". That will use the latest version of your project's code in the new job with the configuration of the job you're copying from.

You can also run git commands in the project's working directory (JupyterLab -> Terminal -> git checkout <branch>) and then "Copy job configuration" to create a new job for a specific branch.

[dingdayu]

Thanks @ricklamers , I noticed "Copy job configuration", But it often only updates the code, which is inconvenient, and the original Job needs to be deleted.

I also want to ask two questions:

• at “Copy job configuration” use the latest version will git pull?
• Is there any way to automatically update the code in Job when Git webhook?