I don't know if I fully understand your question... but here is something I 
did to solve getting scripts for execution in RepoA from repo's B,C,D... I 
now know the specific directories to execute the scripts from and the files 
that needed to be updated for Puppet. 

If you find a better way or this is not what you're looking for, please let 
me know. 
        stage('Pre-Build') {
            steps { 
                parallel (
                    R10K_Git: { dir(
"${env.WORKSPACE}\\${params.R10K_PROJECT}") {
                        git ([url: "${GIT_URL}/${params.R10K_PROJECT}.git", 
credentialsId:"creds"])
                    } },

                    Hieradata_Git: { dir(
"${env.WORKSPACE}\\${params.HIERADATA_PROJECT}") {
                        git ([url: "${GIT_URL}
/${params.HIERADATA_PROJECT}.git", credentialsId:"creds"])
                    } },

                    Jenkins_Scripts_Git: { dir(
"${env.WORKSPACE}\\build\\scripts") {
                        git ([url: "${GIT_URL}/Jenkins_Scripts.git", 
credentialsId:"creds"])
                    } }
                )
            }
        }


On Friday, September 29, 2017 at 11:45:20 AM UTC-5, dandeliondodgeball 
wrote:
>
> Maybe I am not understanding shared libraries.  I have another repo, in 
> which there are python scripts I need to call to be able to build the repo 
> for which I have the pipeline created.  So I make pipeline A for repo B, 
> but I need to call scripts in repo C to build.  It looked like shared 
> libraries were the way for pipeline A to know about repo C.  Is there 
> another/better way of doing that?  Thx
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9569de8f-84f5-4bcd-9c5b-5adcad2823c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to