Deployment method - Working changes

[dennisnel]

Hi there,

Could someone please explain the "new" deployment method Working Changes?

What is the definition of Working Changes?

Tx

[worksofliam]

This is related to git. Selecting 'working changes' will only upload files that git sees as changed that are not staged.

[andreas-prouza]

Hi Liam,
I use 2 extensions for that:

• Run on Save:
  Automatically sync when source is saved.
  So no need to do some extra sync
• Command Runner
  To trigger the sync manually (e.g. if I switch branch) using STRG+P --> Select: Run Command --> Select: Sync project

.vscode/settings.json

{
    "emeraldwalk.runonsave": {
        "commands": [
            {
                "match": ".*/myapp.*/.*$",
                "isAsync": true,
                "cmd": "rsync -av --rsync-path=/QOpenSys/pkgs/bin/rsync --exclude={'.git','build','logs','.vscode','.project','.gitignore'} /home/andreas/projects/myapp/ ibmi:/home/prouza/myapp/"
            }
        ]
    },
    "command-runner.terminal.name": "Sync project",
    "command-runner.terminal.autoClear": true,
    "command-runner.terminal.autoFocus": true,
    "command-runner.commands": {
        "Sync source to IBM i": "rsync -av --rsync-path=/QOpenSys/pkgs/bin/rsync --exclude={'.git','build','logs','.vscode','.project','.gitignore'} /home/andreas/projects/myapp/ ibmi:/home/prouza/myapp/",
        "Sync logs back": "rsync -avz --rsync-path=/QOpenSys/pkgs/bin/rsync --include={'logs/***','build/***'} --exclude='*' ibmi:/home/prouza/myapp/ /home/andreas/projekte/projects/myapp/",
    }
}

Just for info: I am developing with a Linux machine. So my local directory is /home/andreas instead of C:\users\andreas if you working on a Windows machine.
On Windows you also need to install rsync e.g. via Cygwin.
In Windows you need also to consider the backslash instead of slash in your settings.json.

[andreas-prouza]

In addition I also use the "Work with Actions" possibility in your extension to build the application with gmake.
In "Command to run" I use:

/QOpenSys/pkgs/bin/bash -c "error=*EVENTF lib1=&CURLIB cd ~/myapp; gmake all"

The advantage of this is, that I get the compile information directly in my currently opened source.
So if I am trouble shooting with a source change, this is my choise.
As far as I know it even works if my opened source is a local one and not opened from IBM i IFS.

[andreas-prouza]

I also use the "Work with Actions" to show a list of changed sources which would be compiled (what I already described in my first answer).
This is also greate to do it in vscode directly and no need to use a bash terminal for it.

[worksofliam]

@andreas-prouza Very cool - thanks!

Just so you know, you can also create a .vscode/actions.json file which can then keep your compile options as part of your repo.

[{
    "command": "/QOpenSys/pkgs/bin/bash -c \"error=*EVENTF lib1=&CURLIB cd ~/myapp; gmake all\"",
    "deployFirst": false, // rsync handles this!
    "environment": "pase",
    "extensions": [
        "GLOBAL"
    ],
    "name": "Run build"
},
{
    "command": "/QOpenSys/pkgs/bin/bash -c \"error=*EVENTF lib1=&CURLIB cd ~/myapp; gmake all -n\"",
    "deployFirst": false,
    "environment": "pase",
    "extensions": [
        "GLOBAL"
    ],
    "name": "Dry run content"
}]

[andreas-prouza]

Thanks for the hint Liam!
Cuttently I don't sync the .vscode directory, but it would makes sense to add the actions.json to it.