Closed sshepel closed 8 years ago
There used to be an option in early 0.x versions, but I have removed it in versions 1.0 / 2.0 (I didn't think it would be ever used and made the code slightly more complex).
In which way would you use it?
Thanks, Damien.
For example, if you have project structure which been approved and could not be changed. In this case you need to put all your scripts in:
If you put seed.groovy
in src/main/groovy
it might be considered a project source file, compiled as such and giving compilation errors. Unless you exclude it in your build files, but this gives extra configuration work, no? That's why a location outside of the main source code makes more sense to me, either in a separate folder (like seed
) or at the root of the project.
I think you are right, it it was just an example, also I believe that it's always good when you have an option;)
I'll think about it. Ok to do this in version 2.x ?
Ok, sounds good! Many thanks for considering my request!
There are actually two locations to consider:
seed.properties
file for pipelines defined using fully or part of a pipeline libraryseed.groovy
file for pipelines defined using directly a DSL (with or without a pipeline library)I'll just make the folder containing those one or two files configurable.
Thanks a lot, @dcoraboeuf!
Not ready yet. Still need to create some integration tests, to document and to release. Should be available end of September.
Np, anyway it's a good news for me that you decided to bring this option back!
Tests failing in Jenkins, not locally. I will investigate before releasing.
Available in 2.1.1. See documentation at https://github.com/jenkinsci/seed-plugin/wiki/Configuration (Script directory).
@dcoraboeuf sorry for the late reply, but thanks a lot for this quick integration of this issue!
There is no option in the plugin to specify the location for groovy script if you want to put it not in seed folder.