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 >>> <https://groups.google.com/d/msgid/jenkinsci-users/CAA9S6i74f8-bEzrLi%3D%2BFhq3nvo5TQVPVk71y%3D95WvGJtq0_dWQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> 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 >> <https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwrHeM9vTEhKMsSeRxPuaVsQ27DreX%3DtvtCQ_y3bkbD5g%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> 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 > <https://groups.google.com/d/msgid/jenkinsci-users/CAA9S6i43bDPhQchn%3DAN%2BFHbJyOJwzYmvLLETOeT4JOy_KmctVg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > 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.
