Ignoring a folder when building files in a gitlab CI process

[pdessus]

dear all,
I'm running marp-cli (v. 4.0.4) in a CI gitlab (deck: zenika/alpine-chrome) and when I build slides all the files in the repo are built, which takes a long time and uses resources. I'm looking for a way to have a specific folder whose files would'nt be built. gitignore doesn't suit because it doesn't allow files sync between account. The best would be to add an option to pass the name of a folder to be ignored when launching the marp command. Is it feasible?

[yhatt]

Try using glob patterns. Marp CLI supports negated glob patterns that will apply to already matched glob pattern.

This command will convert all *.md files in the current directory, but ignore Markdown files in ignored directory.

marp './**/*.md' '!**/ignored/**/*.md'

Note that the negated glob pattern will not apply to non-glob patterns that are pointed existing files and folders.

[yhatt]

I'm running marp-cli (v. 4.0.4) in a CI gitlab (deck: zenika/alpine-chrome) and when I build slides all the files in the repo are built, which takes a long time and uses resources.

You can consider to upgrade Marp CLI to v4.1.0. It has introduced parallel conversion to make the task faster about 4.5 times in the best case.

• Introduce parallelism for batch conversion: --parallel / -P marp-cli#628

[pdessus]

dear yhatt,
thx for this hint about glob patterns; would you like to expand it a bit more? the two marps commands I invoque are:
marp -I . -o ${MARP_OUTPUT_PATH}
marp -I . --pdf --allow-local-files -o ${MARP_OUTPUT_PATH}

how can they be modified to ignore, say, an /archive folder in the root of the repo?
thx!
best,
ph

[pdessus]

… and I'm aware of the v. 4.1.0 changes… that were automatically updated in my gitlab repo, but I was obliged to revert to 4.0.4 because of an error, below:

/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:101
#error = new Errors_js_1.ProtocolError();
^

ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
at <instance_members_initializer> (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:101:14)
at new Callback (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:105:16)
at CallbackRegistry.create (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:23:26)
at Connection._rawSend (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:93:26)
at CdpCDPSession.send (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/CDPSession.js:68:33)
at #evaluate (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/ExecutionContext.js:363:50)
at ExecutionContext.evaluate (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/ExecutionContext.js:278:36)
at IsolatedWorld.evaluate (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/IsolatedWorld.js:100:30)
at CdpFrame.evaluate (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/api/Frame.js:348:43)
at CdpFrame. (/builds/inspe-sciedu/slides/.npm-global/lib/node_modules/@marp-team/marp-cli/node_modules/puppeteer-core/lib/cjs/puppeteer/util/decorators.js:109:27)

Node.js v20.15.1
section_end:1737022993:step_script
�[0Ksection_start:1737022993:cleanup_file_variables
�[0K�[0K�[36;1mCleaning up project directory and file based variables�[0;m�[0;m
section_end:1737022995:cleanup_file_variables
�[0K�[31;1mERROR: Job failed: exit code 1

[yhatt]

how can they be modified to ignore, say, an /archive folder in the root of the repo?

# Convert Markdown files in the current directry (assumed as repository root), but not in `archive` directory
marp './**/*.md' '!**/archive/**/*.md' --theme-set .
marp './**/*.md' '!**/archive/**/*.md' --theme-set . --pdf --allow-local-files

--input-dir (-I) option is not compatible with glob pattern, so -o option cannot use in this case. All Markdown files will convert into next to each Markdown file.

… and I'm aware of the v. 4.1.0 changes… that were automatically updated in my gitlab repo, but I was obliged to revert to 4.0.4 because of an error, below:

If parallel conversion was unstable on CI, you can decrease the number of parallel processes by using the --parallel option (e.g. --parallel 2), or disable parallelism by --no-parallel.

If network I/O on CI environment is unstable, you also can try to increase the browser timeout by using the --browser-timeout option (--browser-timeout=60 to set 60 sec, and 0 to disable).