[JIRA] (JENKINS-58217) Support Maven repository as an installation source
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58217 Support Maven repository as an installation source Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-26 17:18 Labels: plugin-manager gsoc Priority: Minor Reporter: Natasha Stopa Supporting Maven repository as an installation source was feedback given in the Phase 1 presentation. Related to: https://issues.jenkins-ci.org/browse/JENKINS-58147 Add Comment
[JIRA] (JENKINS-58217) Support Maven repository as an installation source
Title: Message Title Natasha Stopa commented on JENKINS-58217 Re: Support Maven repository as an installation source Copying over some of the questions and discussions from Gitter channel: 1) Would this be done by using a process builder and calling the mvn dependency plugin? It looked like this is what was being done in the Custom War Packager 2) Since this would require the groupId, should the plugins.txt file and plugin CLIOption input format be changed so that it could accept the groupId as a parameter? Or if the user wants to download plugins from the maven repository, they would enter this in a yaml file or some other method? Feedback from Tim and Kristin: Yaml files would be similer, don't want to change plugins.txt format too much The way that the custom war packager is doing it is right; some of the "dependencies" might not be plugins but most will be. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200277.1561569498000.11549.1563226620164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58217) Support Maven repository as an installation source
Title: Message Title Natasha Stopa edited a comment on JENKINS-58217 Re: Support Maven repository as an installation source Copying over some of the questions and discussions from Gitter channel:1) Would this be done by using a process builder and calling the mvn dependency plugin? It looked like this is what was being done in the Custom War Packager2) Since this would require the groupId, should the plugins.txt file and plugin CLIOption input format be changed so that it could accept the groupId as a parameter? Or if the user wants to download plugins from the maven repository, they would enter this in a yaml file or some other method? Feedback from Tim [~timja] and Kristin [~kwhetstone] :Yaml files would be similer, don't want to change plugins.txt format too much The way that the custom war packager is doing it is right; some of the "dependencies" might not be plugins but most will be. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200277.1561569498000.11550.1563226680061%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58217) Support Maven repository as an installation source
Title: Message Title Natasha Stopa commented on JENKINS-58217 Re: Support Maven repository as an installation source Some questions: 1) Should a user be able to enter plugins they want to download from the update center and from maven during the same run of the CLI Tool? 2) Should the yaml file entered to specify plugins from maven be different from the yaml file used by configuration as code? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200277.1561569498000.11570.1563230820045%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58217) Support Maven repository as an installation source
Title: Message Title Kristin Whetstone commented on JENKINS-58217 Re: Support Maven repository as an installation source 1) Yes. each plugin should be processed separately, I don't see why individual lines can't specify where the download happens. 2) Tim Jacomb would be in a better position to answer this. I think they should be together, but I'm not very involved with CasC. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200277.1561569498000.12548.1563300120696%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58217) Support Maven repository as an installation source
Title: Message Title Tim Jacomb commented on JENKINS-58217 Re: Support Maven repository as an installation source 2) Yes can be together. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200277.1561569498000.12672.1563305940286%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.