Pipeline Remote File Loader Plugin error `/develop@2/libLoader/`
I am trying to use the Pipeline Remote File Loader Plugin and am facing an
issue.
My current `jenkinsfile looks as follows:
```
node('docker-slave') {
stage 'Setup'
fileLoader.fromGit('build-snippet',
'', 'develop', '', '')
}
```
The content of build-snippet:
```
stage 'Publish'
publishHTML(target: [
allowMissing: false, alwaysLinkToLastBuild: true,
keepAll: false, reportDir: 'build/apidocs',
reportFiles: 'index.html', reportName: 'API Documentation'
]
)
```
When running it i get an error `/develop@2/libLoader/build/apidocs` does
not exist.. The `@2/libLoader/` is the problem when i paste in the code
from the build-snippet into the jenkinsfile it works ok. Then the
`@2/libLoader/`
is not added to the path.
Any hints or suggestion what i am doing wrong?
--
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/d4c6adcf-6cb4-4bcf-9493-9d5e0f3badf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
How to simplify creation/maintenance of builds that are comparable?
We just took to step to move our CI environment to Jenkins 2. We see that we are creating the same build over and over. The jenkinsfile is great, but now we see that we need to repeat it in every project. At the end that becomes it maintenance nightmare.. We have multiple git projects that are equal in structure and need to be build in the same way. Example: gitrepo - App1 - Jenkinsfile (MultiBranchPipeline) gitrepo - App2 - Jenkinsfile (MultiBranchPipeline) gitrepo - App3 - Jenkinsfile (MultiBranchPipeline) We are actually coping the same Jenkinsfile to these projects and if we need a change we need to adapt all of them. So this becomes a nightmare. Is there a better way of organizing this and getting a repeatable way of doing things? - Marco -- 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/ace83cef-7c94-4087-9556-d0f42f38da53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Pipeline: How to cache downloaded (gradle) dependencies using Docker SSH Slave
I was hoping that these dependencies could be cached somewhere in the workspace instead or relying on Gradle specific things. We have the same thing for NPM related dependencies. Continuous downloading of the related dependencies is just to slow. On Thursday, June 23, 2016 at 8:48:32 AM UTC+2, Craig Rodrigues wrote: > > In 2011, this discussion thread talked about this topic: > https://discuss.gradle.org/t/cache-dependencies-into-local-maven-repository-from-gradle/7525 > > and it didn't seem possible. > > However, I advise you to post your question to https://discuss.gradle.org/ > , because there may be new information that can make this possible. > > -- > Craig > > > On Wed, Jun 22, 2016 at 4:48 AM, Marco Pas <marco@gmail.com > > wrote: > >> Now that we have a first successful build using a Jenkinsfile Pipeline we >> are looking on how to cache downloaded dependencies. >> Currently when we build our Gradle applications the dependencies are >> downloaded each time the Docker Slave is executed on a remote host. Is >> there a way to cache the downloaded dependencies for later reuse so we can >> speedup the build process? >> >> -- 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/a5effc39-cfeb-4f11-a639-7cfa61a4a044%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Pipeline: How to cache downloaded (gradle) dependencies using Docker SSH Slave
Now that we have a first successful build using a Jenkinsfile Pipeline we are looking on how to cache downloaded dependencies. Currently when we build our Gradle applications the dependencies are downloaded each time the Docker Slave is executed on a remote host. Is there a way to cache the downloaded dependencies for later reuse so we can speedup the build process? - Marco -- 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/b552e554-93fa-41f7-864c-0d25cb62feb4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
