Current flow for builds using the generic template_2.x.jenkinsfile (and theia-sources) is to:

• sync upstream or upper-midstream to midstream (crw-images repo), then trigger
• sync-to-downstream job, which will run ./get-sources.sh --nobuild -p job_branch, then trigger
• get-sources-rhpkg-container-build, which will run rhpkg-container-build.sh, which runs
• ./get-sources*.sh --force-build ${JOB_BRANCH}

So if the get-sources script is set up to commit changes into pkgs.devel automatically (eg., for theia) then there's no need to RE-BUILD and RE-FETCH those assets in the container-build job.

Therefore we need a way to either...

• SKIP the collection step in sync-to-downstream and just have it happen in the downstream job, or
• SKIP the collection step in get-sources-rhpkg job, assuming it was already done in the previous job.

Similarly with the new crw-server version of get-sources*.sh, we have a -m flag to disable creating the maven bits, but we're not using it in sync-to-downstream job.

For theia, this could mean using the combination of `-n -p` flags for mean 'pull assets, but don't build' and let the downstream '-f' do the build part.

For other projects, we should move to the same model as we move to the template job in CRW-1621

current list of projects using template jenkinsfile, which need to have the -p flag in their get-sources*.sh mean "pull assets" and the absense of that flag mean "don't pull new assets":

• dashboard
• devfile reg
• dwo
• dwco
• machineexec
• plugin reg
• server