For now we have chosen to not use the Folder plugin, but go with the
Repository Server Plugin.
At the moment the Maven job is good enough for us, but I guess we will move
over to the Freestyle job in time. I would be very interested if the MRSP
would also work for that type of job.
Also, I wonder
On 30 September 2015 at 12:10, Nick Stolwijk wrote:
>
> For the JobDSL, we have a small department and everyone with a login can
> create jobs and security is not the issue. I like the way it circumvents the
> copy-paste way of maintaining jobs.
>
Like I said, the plugin assumes a specific securi
That sounds like our usecase.
We have a shared component-tree (ComponentA), which we use in different
projects. Some of these projects depend on a released version of the
ComponentA and others on a SNAPSHOT version.
We are now looking for a Jenkins process, that when there is a commit to
Componen
So the JobDSL plugin requires that you have a specific view on the
security model of your Jenkins instance (i.e. only administrators can
explicitly create/configure jobs, all other users get jobs created /
updated via the JobDSL using scripts managed by administrators)
A large chunk of installatio
I'll describe my use-case (which led to MRSP), and maybe that'll help.
We do CI builds on every check-in (actually more complicated than that as
we only have pre-tested commits).
We have 'customer' projects that use these artifacts.
We don't want to build the 'customer' projects at the same cade
I'm sorry I make you feel like a sad panda. :( Would you set me on the
right way as I'm just a young padawan on the road to enlightment. ;)
With regards,
Nick
On 29 Sep 2015 22:27, "Stephen Connolly"
wrote:
> All this talk of the evil job type and the JobDSL plugin makes me a sad
> panda.
>
>
All this talk of the evil job type and the JobDSL plugin makes me a sad
panda.
- Stephen
On Tuesday, 29 September 2015, Nick Stolwijk
wrote:
> When you are talking about the "evil job type", do you mean the Maven
> jobtype?
>
> I'm using those to let Jenkins find out which jobs depend on each o
When you are talking about the "evil job type", do you mean the Maven
jobtype?
I'm using those to let Jenkins find out which jobs depend on each other. :S
Should I reconsider my strategy?
I'm currently busy to make little changes to my jobs to fulfill my needs
and then automate them with the Job
It's probably what stephen says -- when I wrote the plugin was some time
ago - either before (or before my awareness of) multi-branches and other
non-root project types. Probably not a big fix..
It's also (currently, but am fixing) tied to the 'evil job type' :-)
You might find workflow-plugin be
Did you already check jira?
Is the MRSP not used that often, and is their a better way to consume
artifacts from another build? Or do we just have a strange usecase?
We are switching from one big code tree to multiple subprojects and we are
reorganising our Jenkins builds.
Project A is going to
Looks like the repository plugin has invalid assumptions about all jobs
being at the root of Jenkins. It's probably using Item.getName in place of
Item.getFullName and the corresponding reverse lookups
I'd check jira and if there isn't an issue already then create one.
(FYI this is not an issue w
I'm trying to use both the Maven Repository Server Plugin[1] and the
CloudBees Folders Plugin[2], but I have some trouble with it.
I have 2 projects, A and B, and I want the build of B to use the artifacts
of a build of A. A is being triggered by a successful build of A. I also
use the CFP to grou
12 matches
Mail list logo
