[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc commented on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts You are combining the 2 problems to solve in 1 single use case Understood, the filtering seem to be the way forward for your problems. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title dan tran commented on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts out of 400+ artifacts showing up in the list, my users only care about 2. Paging does not help and the selected artifacts are burried in list, very hard to look up Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc commented on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts To rephrase your RFE. You ask to filter the listed artifacts to only show the artifacts that matter to the users who browse this page (eg. Don't show pom files and intermediate artifacts). Your goal is not related to the number of generated artifacts that would be too big and that would impact the rendering of the page. For this reason, a pagination mechanism would not solve your problem. Correct? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc stopped work on JENKINS-49592 Change By: Cyrille Le Clerc Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc started work on JENKINS-49592 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title dan tran edited a comment on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts in my use case, my My final user's facing artifacts consists of 2 files ( a .ova and .pkg) both using maven attach mechanism using with build-helper-maven plugin to deploy secondary or classify artifacts. So using regular _expression_ should workNote: currently we only see primary artifacts ( .jar .war .rpm ( via rpm-maven-plugin) show up in the deployed list Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title dan tran commented on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts in my use case, my final user's facing artifacts ( .ova and .pkg) using maven attach mechanism using build-helper-maven plugin to deploy secondary or classify artifacts. So using regular _expression_ should work Note: currently we only see primary artifacts ( .jar .war .rpm ( via rpm-maven-plugin) show up in the deployed list Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts Thanks [~dantran] for the feedback. How did you envision the filter definition? I imagined a the capability to define exact-string / regular-expressions filters for each of the following attribute: groupId, artifactId, version (e.g. "0.5-SNAPSHOT"), classifier, type.I had in mind to not propose for the first version filters on: expanded version (e.g. "0.5-20180218.180717-50"), extension (because we can filter on the type).Regarding the classifier, note that for the moment, we just list the "generated artifact" of the maven module and NOT the attached artifacts (e.g. sources, javadocs...) . As you mentionned that you build OVAs and RPM, I found that the rpm-maven-plugin can generate rpm as "primary artifacts (see http://www.mojohaus.org/rpm-maven-plugin/usage.html#RPM_as_Primary_Artifact) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc commented on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts Thanks dan tran for the feedback. How did you envision the filter definition? I imagined a the capability to define exact-string / regular-expressions filters for each of the following attribute: groupId, artifactId, version (e.g. "0.5-SNAPSHOT"), classifier, type. I had in mind to not propose for the first version filters on: expanded version (e.g. "0.5-20180218.180717-50"), extension (because we can filter on the type). Regarding the classifier, note that for the moment, we just list the "generated artifact" of the maven module and NOT the attached artifacts (e.g. sources, javadocs...) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-49592 Add ability to filter out Maven Deploy Artifacts Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title dan tran created an issue Jenkins / JENKINS-49592 Add ability to filter out Maven Deploy Artifacts Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-02-16 08:45 Priority: Minor Reporter: dan tran My project has 300+ plus modules, and I need to show our users ( dev, qa) a few only. For example installer, vmware OVA, etc. This setting must be done at jenkinsfile level Add Comment This message was sent by Atlassian JIRA
