[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title Sandra Parsick commented on JENKINS-47784 Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin Tarun Hasija you have two options: First one is to configure the Maven Deploy Plugin in your POM with the option true Because this feature of Maven Deploy Plugin is experimental you have to test whether it works in your project. Second option is to add the Maven Extension "Deployer Extension" in your project. For more information, see https://github.com/khmarbaise/maven-deployer-extension Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.186282.1509627193000.1302.1571995322150%40Atlassian.JIRA.
[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title Sandra Parsick commented on JENKINS-47784 Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin Cyrille Le Clerc Thank you for your hint. I edited it. No idea what went wrong on my first try. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title Sandra Parsick edited a comment on JENKINS-47784 Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin [~cleclerc] I think, here is a misunderstanding. I don't want to do a "re upload". My use case can be described in following steps: # As Maven goal, I run {{mvn clean install.}} # If this goal run successfully, I want to upload all artifact in bulk. In a classic Jenkins job, I used to use the Post Build Action "Deploy Maven Artifacts to repository" for this task.In my comment to Tai, I only describe a workaround to simulate both step in a pipeline job. This feature of Maven deploy plugin is experimental, so that I would prefer a similar way in pipeline job as I used to have in a classic Jenkins job. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title Sandra Parsick edited a comment on JENKINS-47784 Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin [~cleclerc] I think, here is a misunderstanding. I don't want to do a "re upload". My use case can be described in following steps: # As Maven goal, I run {{mvn clean install.}} # If this goal run successfully, I want to upload all artifact in bulk. In a classic Jenkins job, I used to use the Post Build Action "Deploy Maven Artifacts to repository" for this task.In my comment to Tai, I only describe a workaround to simulate both step in a pipeline job. This feature of Maven deploy plugin is experimental, so that I would prefer a similar way in pipeline job as I used to have in a classic Jenkins job. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title Sandra Parsick commented on JENKINS-47784 Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin Cyrille Le Clerc I think, here is a misunderstanding. I don't want to do a "re upload". My use case can be described in following steps: As Maven goal, I run mvn clean install. # 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title Sandra Parsick commented on JENKINS-47784 Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin Hi Tai Ly I use a Maven feature to simulate it. In Maven Deploy Plugin you can set the flag deployAtEnd. This feature is experimental, but in my project it works as alternative solution. Best regards, Sandra 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-28638) Order of version selection dropdown list should be configurable
Title: Message Title Sandra Parsick created an issue Jenkins / JENKINS-28638 Order of version selection dropdown list should be configurable Issue Type: Improvement Assignee: Unassigned Components: repository-connector-plugin Created: 29/May/15 5:02 AM Priority: Minor Reporter: Sandra Parsick Currently, the version selection drop down list has an ascending order, that is not configurable. If the order of the drop down list is configurable, the selection is more comfortable for artifacts whose newer version is used more than the older one. Add Comment
[JIRA] [rebuild-plugin] (JENKINS-28054) Rebuild Plugin doesn't work with Repository Connector Plugin
Sandra Parsick updated JENKINS-28054 Rebuild Plugin doesn't work with Repository Connector Plugin Change By: Sandra Parsick (23/Apr/15 6:04 AM) Description: If the job contains Maven Repository Artifact parameters (see attachment Build.with.parameter.screen.png), rebuild plugin can't show them on its rebuild page (see attachment rebuild.last.screen.png). If, nonetheless, you try triggering a rebuild, a {{NullPointerException}} is thrown. {code} avax javax .servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
[JIRA] [rebuild-plugin] (JENKINS-28054) Rebuild Plugin doesn't work with Repository Connector Plugin
Sandra Parsick created JENKINS-28054 Rebuild Plugin doesn't work with Repository Connector Plugin Issue Type: Bug Assignee: ragesh_nair Attachments: Build.with.parameter.screen.png, rebuild.last.screen.png Components: rebuild-plugin, repository-connector-plugin Created: 23/Apr/15 6:03 AM Description: If the job contains Maven Repository Artifact parameters (see attachment Build.with.parameter.screen.png), rebuild plugin can't show them on its rebuild page (see attachment rebuild.last.screen.png). If, nonetheless, you try triggering a rebuild, a NullPointerException is thrown. avax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489
[JIRA] [repository-connector-plugin] (JENKINS-27641) Name of version selection build parameter should be customized
Sandra Parsick created JENKINS-27641 Name of version selection build parameter should be customized Issue Type: Improvement Assignee: Unassigned Components: repository-connector-plugin Created: 27/Mar/15 6:47 AM Description: Currently, the name of the version selection build parameter is auto-generated with the pattern groupid.artifactid. This is fine if this token is only used in the build step Artifact Resolver. In an Execute Shell build step, this token is unusable because shell variable must not have dots in its name. Therefore, it would be useful when the name of the version selection build parameter is customizable, so that a shell conformed name can be chose. Environment: Linux Project: Jenkins Priority: Major Reporter: Sandra Parsick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.