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 installations do not share that security model (i.e.
letting users create/configure at least some jobs) and thus in those
installations the JobDSL plugin would essentially be a big glaring
security hole waiting for attack...

To be clear, I am not saying that the JobDSL plugin is insecure,
rather that its use mandates a specific security model and if you do
not share that model then it may not be for you.

As to the evil job type...
http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html

On 30 September 2015 at 07:23, Nick Stolwijk <[email protected]> wrote:
> 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" <[email protected]>
> wrote:
>>
>> 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 <[email protected]>
>> 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 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 JobDSL. (I have a few of the same type of
>>> jobs). Everywhere I see examples of the Maven job in combination with the
>>> JobDSL. (And I find a lot of out of date blog posts and mails to these and
>>> other mailinglists).
>>>
>>> Is there somewhere a "Best Practices with Jenkens and JobDSL in 2015"
>>> reference?
>>>
>>> With regards,
>>>
>>>
>>> Nick Stolwijk
>>>
>>> ~~~ Try to leave this world a little better than you found it and, when
>>> your turn comes to die, you can die happy in feeling that at any rate you
>>> have not wasted your time but have done your best ~~~
>>>
>>> Lord Baden-Powell
>>>
>>> On Tue, Sep 29, 2015 at 6:13 PM, Nigel Magnay <[email protected]>
>>> wrote:
>>>>
>>>> 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 better suits your needs these days. I may
>>>> dig around in MRSP too as we're switching to workflow+multi-branch from a
>>>> large array of jobs that use MSRP.
>>>>
>>>> On Tue, Sep 29, 2015 at 4:35 PM, Nick Stolwijk <[email protected]>
>>>> wrote:
>>>>>
>>>>> 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 have multiple fases in the build. Unittests and
>>>>> packaging, integrationtests, regressiontests, and if all that succeeds, a
>>>>> deploy to Nexus, so other developers can use the artifacts produced.
>>>>> We want Project B to start as early as possible (so with the artifacts
>>>>> from the unittest build of Project A), and so I stumbled into the MRSP.
>>>>>
>>>>> Does anyone have any tips on how to organize this in Jenkins?
>>>>>
>>>>> With regards,
>>>>>
>>>>> Nick Stolwijk
>>>>>
>>>>> ~~~ Try to leave this world a little better than you found it and, when
>>>>> your turn comes to die, you can die happy in feeling that at any rate you
>>>>> have not wasted your time but have done your best ~~~
>>>>>
>>>>> Lord Baden-Powell
>>>>>
>>>>> On Tue, Sep 29, 2015 at 9:25 AM, Stephen Connolly
>>>>> <[email protected]> wrote:
>>>>>>
>>>>>> 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 with the folders plugin. The newer plugins
>>>>>> that do multi-branch or repository scanning plus multi-branch will 
>>>>>> trigger
>>>>>> the same issue in the repository plugin)
>>>>>>
>>>>>>
>>>>>> On Tuesday 29 September 2015, Nick Stolwijk <[email protected]>
>>>>>> wrote:
>>>>>>>
>>>>>>> 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 group my builds into folders.
>>>>>>>
>>>>>>> So I have:
>>>>>>> - Folder C
>>>>>>>   * Build of Project A
>>>>>>> - Folder D
>>>>>>>   * Build of Project B
>>>>>>>
>>>>>>> When build B is triggered, MRSP gives it the URL of build A, but the
>>>>>>> URL of the repository given to the build is malformed:
>>>>>>>
>>>>>>>
>>>>>>> http://localhost:8080/plugin/repository/project/folder_c/build_of_project_A/Build/4/repository
>>>>>>>
>>>>>>> When I look into the repository offered by the MRSP I see:
>>>>>>>
>>>>>>>
>>>>>>> http://localhost:8080/plugin/repository/project/build_of_project_A/Build/4/repository
>>>>>>>
>>>>>>> It seems that the folder is prepended to the path the plugin gives to
>>>>>>> the triggered builds.
>>>>>>>
>>>>>>> Did I configure something wrong or is this an issue with one of the
>>>>>>> plugins?
>>>>>>>
>>>>>>> Hope someone can help me.
>>>>>>>
>>>>>>> With regards,
>>>>>>>
>>>>>>> Nick Stolwijk
>>>>>>>
>>>>>>> ps. I use the latest versions of Jenkins (1.631), MRSP (1.2) and CFP
>>>>>>> (4.10).
>>>>>>>
>>>>>>> [1]
>>>>>>> http://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Maven+Repository+Server
>>>>>>> [2]
>>>>>>> https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin
>>>>>>>
>>>>>>> ~~~ Try to leave this world a little better than you found it and,
>>>>>>> when your turn comes to die, you can die happy in feeling that at any 
>>>>>>> rate
>>>>>>> you have not wasted your time but have done your best ~~~
>>>>>>>
>>>>>>> Lord Baden-Powell
>>>>>>>
>>>>>>> --
>>>>>>> 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 [email protected].
>>>>>>> To view this discussion on the web visit
>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAA9S6i74f8-bEzrLi%3D%2BFhq3nvo5TQVPVk71y%3D95WvGJtq0_dWQ%40mail.gmail.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sent from my phone
>>>>>>
>>>>>> --
>>>>>> 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 [email protected].
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwrHeM9vTEhKMsSeRxPuaVsQ27DreX%3DtvtCQ_y3bkbD5g%40mail.gmail.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>> --
>>>>> 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 [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAA9S6i43bDPhQchn%3DAN%2BFHbJyOJwzYmvLLETOeT4JOy_KmctVg%40mail.gmail.com.
>>>>>
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>>
>>>> --
>>>> 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 [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAPYP83SxqfXogu0Z%3DiUyV3YUxqmNoFzeLd-ysXmNtx8f-5BkKg%40mail.gmail.com.
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> --
>>> 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 [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAA9S6i4jwOLZYgffmwjBB8Ji_xkx8cimv8vf%2BbYz7Ua8BaT_ww%40mail.gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Sent from my phone
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMypAo-Mdhrb677y9EYFdzPk_Rj_HHkechZ6gxeYxXkAXQ%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAA9S6i6ghN%3D%2BLsviGVPpdV9%3DxmVHvTGjqStyvbeZaQzdUE9xHg%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzKWXqhUBwMoWME2LjQ%3Dx9%2Bur1d1r8K8ALjCGyH-FAsTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to