[JIRA] (JENKINS-60229) Jenkins 2.205 unable to get updates / update details
Title: Message Title Raul Arabaolaza commented on JENKINS-60229 Re: Jenkins 2.205 unable to get updates / update details ``` WARNING h.m.DownloadService$Downloadable#updateNow: signature check failed for https://updates.jenkins.io/updates/hudson.tools.JDKInstaller.json ERROR: Signature verification failed in downloadable 'hudson.tools.JDKInstaller' (show details)java.security.cert.CertificateExpiredException: NotAfter: Tue Nov 19 22:21:39 CET 2019 at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274) at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629) at sun.security.provider.certpath.BasicChecker.verifyValidity(BasicChecker.java:190) at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:144) at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125)Caused: java.security.cert.CertPathValidatorException: validity check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:233) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:141) at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:80) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292) at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:88) at hudson.model.DownloadService$Downloadable.updateNow(DownloadService.java:416) at hudson.PluginManager.checkUpdatesServer(PluginManager.java:1769) at hudson.util.Retrier.start(Retrier.java:62) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1733) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:169) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
[JIRA] (JENKINS-60229) Jenkins 2.205 unable to get updates / update details
Title: Message Title Raul Arabaolaza commented on JENKINS-60229 Re: Jenkins 2.205 unable to get updates / update details FTR this not only affects 2.205, I have checked with 2.190.2 also some propietary versions based on the upcoming 2.190.3 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.203204.157429000.4454.1574261520459%40Atlassian.JIRA.
[JIRA] (JENKINS-58051) Add a hook for plugins not having standard tags
Title: Message Title Raul Arabaolaza updated JENKINS-58051 Jenkins / JENKINS-58051 Add a hook for plugins not having standard tags Change By: Raul Arabaolaza Status: In Progress Review 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.200072.1560781245000.1795.1560782220090%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58051) Add a hook for plugins not having standard tags
Title: Message Title Raul Arabaolaza started work on JENKINS-58051 Change By: Raul Arabaolaza Status: Open In Progress 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.200072.1560781245000.1790.1560781262739%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58051) Add a hook for plugins not having standard tags
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-58051 Add a hook for plugins not having standard tags Issue Type: Task Assignee: Raul Arabaolaza Components: plugin-compat-tester Created: 2019-06-17 14:20 Priority: Minor Reporter: Raul Arabaolaza The PCT tries to checkout the source code of a given plugin using github tags. It expects the plugin to be checkout to follow the standard tag format defined by Jenkins community. There is no way for the PCT to checkout a plugin that does not follow this convention, for example it has been rebranded. Add Comment
[JIRA] (JENKINS-56754) PCT should update dependencyManagement
Title: Message Title Raul Arabaolaza started work on JENKINS-56754 Change By: Raul Arabaolaza Status: Open In Progress 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-56754) PCT should update dependencyManagement
Title: Message Title
Raul Arabaolaza updated an issue
Jenkins / JENKINS-56754
PCT should update dependencyManagement
Change By:
Raul Arabaolaza
The PCT updates the dependencies and test dependencies but it does not update the dependency management section of the pom file.Now consider a situation where a plugin `a` uses some test utilities from another plugin `b` but it does not have a direct dependency on `b`. To do that `a` can use a `test` scoped dependency of `b` `tests` artifact. In those circumstances, it makes sense for `a` to use a dependency management section to be sure that `b` version (transitively added by `b` tests artifact to the test classpath) is deterministic and under control. ``` {noformat} b..ateststest ``` {noformat} Problem is that PCT does not update dependencyManagement so in this cases the final version of `b` in the test classpath is different from the version of `b` tests utilities used
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-56754) PCT should update dependencyManagement
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-56754 PCT should update dependencyManagement Change By: Raul Arabaolaza The PCT updates the dependencies and test dependencies but it does not update the dependency management section of the pom file.Now consider a situation where a plugin `a` uses some test utilities from another plugin `b` but it does not have a direct dependency on `b`. To do that `a` can use a `test` scoped dependency of `b` `tests` artifact. In those circumstances, it makes sense for `a` to use a dependency management section to be sure that `b` version (transitively added by `b` tests artifact to the test classpath) is deterministic and under control.```b..ateststest ``` Problem is that PCT does not update dependencyManagement so in this cases the final version of `b` in the test classpath is different from the version of `b` tests utilities used 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-56754) PCT should update dependencyManagement
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-56754 PCT should update dependencyManagement Issue Type: Task Assignee: Raul Arabaolaza Components: plugin-compat-tester Created: 2019-03-26 10:59 Priority: Minor Reporter: Raul Arabaolaza The PCT updates the dependencies and test dependencies but it does not update the dependency management section of the pom file. Now consider a situation where a plugin `a` uses some test utilities from another plugin `b` but it does not have a direct dependency on `b`. To do that `a` can use a `test` scoped dependency of `b` `tests` artifact. In those circumstances, it makes sense for `a` to use a dependency management section to be sure that `b` version (transitively added by `b` tests artifact to the test classpath) is deterministic and under control. ``` b .. a tests test Problem is that PCT does not update dependencyManagement so in this cases the final version of `b` in the test classpath is different from the version of `b` tests utilities used Add Comment
[JIRA] (JENKINS-56481) Detached plugins override embedded ones
Title: Message Title Raul Arabaolaza updated JENKINS-56481 Jenkins / JENKINS-56481 Detached plugins override embedded ones Change By: Raul Arabaolaza Status: In Review Resolved Resolution: Fixed 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-56481) Detached plugins override embedded ones
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-56481 Detached plugins override embedded ones Issue Type: Bug Assignee: Raul Arabaolaza Components: plugin-compat-tester Created: 2019-03-08 14:22 Priority: Minor Reporter: Raul Arabaolaza After https://github.com/jenkinsci/plugin-compat-tester/commit/76930e518a7a369ae0709e1e9be94dc5c7c83b15 PCt inspects detached plugins also, but if a plugin is present as an embedded one and as detached the detached one wrongly overrides the embedded one Add Comment
[JIRA] (JENKINS-56481) Detached plugins override embedded ones
Title: Message Title Raul Arabaolaza started work on JENKINS-56481 Change By: Raul Arabaolaza Status: Open In Progress 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-56321) PCT should inspect detached plugins for group id
Title: Message Title Raul Arabaolaza started work on JENKINS-56321 Change By: Raul Arabaolaza Status: Open In Progress 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-56321) PCT should inspect detached plugins for group id
Title: Message Title Raul Arabaolaza updated JENKINS-56321 Jenkins / JENKINS-56321 PCT should inspect detached plugins for group id Change By: Raul Arabaolaza Status: In Progress Review 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-56312) PCT not taking into account jdk version for detached plugins
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-56312 PCT not taking into account jdk version for detached plugins Change By: Raul Arabaolaza Summary: PCT not taking into accountjdk version for detached plugins 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-56312) PCT not taking into account jdk version for detached plugins
Title: Message Title Raul Arabaolaza updated JENKINS-56312 Jenkins / JENKINS-56312 PCT not taking into account jdk version for detached plugins Change By: Raul Arabaolaza Status: In Progress Review 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-56312) PCT not taking into account
Title: Message Title Raul Arabaolaza started work on JENKINS-56312 Change By: Raul Arabaolaza Status: Open In Progress 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-56321) PCT should inspect detached plugins for group id
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-56321 PCT should inspect detached plugins for group id Issue Type: Bug Assignee: Raul Arabaolaza Components: plugin-compat-tester Created: 2019-02-28 08:32 Priority: Minor Reporter: Raul Arabaolaza The PCT reads the list of detached plugins from the `split-plugins.txt` file but then it just use the default groupid to add them as dependency if needed. Given that the detached plugins are embedded into the war file it is better if it inspect them to get the appropriate group id to add. For example the current behaviour makes the PCT fail for core 2.164 + due to `jaxb` plugin not using the default group id. Add Comment
[JIRA] (JENKINS-56312) PCT not taking into account
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-56312 PCT not taking into account Issue Type: Bug Assignee: Raul Arabaolaza Components: plugin-compat-tester Created: 2019-02-27 16:02 Priority: Minor Reporter: Raul Arabaolaza Since JENKINS-55681 splits can be JVM version dependent, but the PCT is not able to detect the JDK version field on the splits file and is adding those plugins always. As a result the PCT is incorrectly adding `jaxb` plugin even to java 8 runs Add Comment
[JIRA] (JENKINS-54295) Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium
Title: Message Title Raul Arabaolaza updated JENKINS-54295 Jenkins / JENKINS-54295 Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium Change By: Raul Arabaolaza Status: In Progress Review 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-54295) Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium
Title: Message Title Raul Arabaolaza commented on JENKINS-54295 Re: Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium It seems also that the docker install method used by the Dockerfile is now broken... 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-54295) Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium
Title: Message Title Raul Arabaolaza commented on JENKINS-54295 Re: Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium Setting system property jdk.net.URLClassPath.disableClassPathURLCheck to true fixes the problem with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925 That in conjunction with the firefox esr version fix seems to make everything work perfectly in my local tests. Now wondering if we should just wait for this commit https://hg.openjdk.java.net/jdk/jdk/rev/f54dcfc5a5f8 to be backported to debian openjdk package or force it in the ATH run... Oliver Gondža Lucie Votypkova any suggestions? I do not have a strong opinion on the best approach here 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-54295) Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium
Title: Message Title Raul Arabaolaza commented on JENKINS-54295 Re: Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium It also seems affected by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925 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-54295) Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium
Title: Message Title Raul Arabaolaza started work on JENKINS-54295 Change By: Raul Arabaolaza Status: Open In Progress 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-54295) Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-54295 Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium Issue Type: Bug Assignee: Raul Arabaolaza Components: acceptance-test-harness Created: 2018-10-28 18:06 Priority: Major Reporter: Raul Arabaolaza The latest version of the jenkins/ath docker image includes firefox 60.2.0 (as it has been updated in debian strech packages) this version seems to be incompatible with the selenium version used by the ath itself and hence now most of tests are failing Add Comment
[JIRA] (JENKINS-53172) parallel-test-executor-plugin should check that the job is not running
Title: Message Title Raul Arabaolaza updated JENKINS-53172 Jenkins / JENKINS-53172 parallel-test-executor-plugin should check that the job is not running Change By: Raul Arabaolaza Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53172) parallel-test-executor-plugin should check that the job is not running
Title: Message Title Raul Arabaolaza commented on JENKINS-53172 Re: parallel-test-executor-plugin should check that the job is not running PR created to have feedback, I am starting manual testing on my private instance. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53172) parallel-test-executor-plugin should check that the job is not running
Title: Message Title Raul Arabaolaza started work on JENKINS-53172 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53172) parallel-test-executor-plugin should check that the job is not running
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-53172 parallel-test-executor-plugin should check that the job is not running Issue Type: Task Assignee: Raul Arabaolaza Components: parallel-test-executor-plugin Created: 2018-08-21 15:42 Priority: Minor Reporter: Raul Arabaolaza We have seen situations were parallel-test-executor-plugin takes as reference a job that is still running. As consequence, the test split generated is invalid as no all tests have been executed by the reference job. My interpretation of this code suggests that only those jobs in status SUCCESSFULL or UNSTABLE should be candidates to be used as references. But the javadoc of Run#getResult states that it may return a result when the job is still running, so I believe that an extra check to discard running jobs (even if they return a Result) is needed. Add Comment
[JIRA] (JENKINS-51489) Implement an essentials mode in the ATH
Title: Message Title Raul Arabaolaza updated JENKINS-51489 Jenkins / JENKINS-51489 Implement an essentials mode in the ATH Change By: Raul Arabaolaza Status: In Progress Review 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-51489) Implement an essentials mode in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-51489 Re: Implement an essentials mode in the ATH Linked three PRs. ATH#433 add the new mode to the ATH pipeline-library#64 allows runATH to use a custom groovy script for config pipeline-library#65 modifies essentialsTest so it uses the new ATH mode via a custom config groovy script 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-51489) Implement an essentials mode in the ATH
Title: Message Title Raul Arabaolaza started work on JENKINS-51489 Change By: Raul Arabaolaza 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-51489) Implement an essentials mode in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-51489 Re: Implement an essentials mode in the ATH The first step is to have the ability to pass a custom config to runATH, PR here 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-51489) Implement an essentials mode in the ATH
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51489 Implement an essentials mode in the ATH Issue Type: Task Assignee: Raul Arabaolaza Components: acceptance-test-harness Created: 2018-05-22 16:36 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza After conversations with Jesse Glick and Oleg Nenashev regarding JENKINS-51306 we have agreed on that a good solution for ATH and PCT runs based on a BOM is to force a sane dependency graph in your BOM file. This graph should be enough to run the specified tests without any further plugin modification. In this situation makes sense to modify the ATH to have an "essentials mode" where WithPlugins just validates that the war file under tests is able to execute the test but it does not install/update or modify existing plugins in any way. If the validation fails, that is there is a requirement on a plugin not already installed or installed in a lower version than the one needed by the test, the test should fail or optionally be skipped with the proper reason
[JIRA] (JENKINS-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza resolved as Not A Defect The problem is not on the ATH itself, and the root cause needs discussion about the way to be solved Jenkins / JENKINS-51306 ATH does not restart instance when withPlugin() requires newer dependency than the bundled version Change By: Raul Arabaolaza Status: In Progress Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza commented on JENKINS-51306 Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version Oleg Nenashev Closing this as it seems not related to the ATH itself 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-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza commented on JENKINS-51306 Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version Confirmed, with the following BOM all failures related to plugins not being installed are solved metadata: # labels and annotations are key: value string attributes labels: name: bom-it # Needed to make PCT happy groupId: org.jenkins-ci.main artifactId: jenkins-war version: 2.118-artifact-manager-s3-SNAPSHOT spec: core: version: 2.118 plugins: - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-api" version: 2.28-rc333.0675e9e9cb4c - groupId: "org.jenkins-ci.plugins" artifactId: "copyartifact" version: 1.40-rc298.60da56cfabea # Maven HPI Plugin improperly resolves dependency trees, needs upper bounds check - groupId: "org.jenkins-ci.plugins" artifactId: "structs" version: 1.14 - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-step-api" version: 2.14 - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-job" version: 2.21 - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-basic-steps" version: 2.7 - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-support" version: 2.18 - groupId: "org.jenkins-ci.plugins" artifactId: "junit" version: 1.24 - groupId: "org.jenkins-ci.plugins" artifactId: "mailer" version: 1.21 - groupId: "org.jenkins-ci.plugins" artifactId: "scm-api" version: 2.2.7 - groupId: "org.jenkins-ci.plugins" artifactId: "script-security" version: 1.44 - groupId: "org.jenkins-ci.plugins" artifactId: "aws-java-sdk" version: 1.11.264 - groupId: "org.jenkins-ci.plugins" artifactId: "apache-httpcomponents-client-4-api" version: 4.5.5-2.0 - groupId: "org.jenkins-ci.plugins" artifactId: "matrix-project" version: 1.7.1 - groupId: "org.jenkins-ci.plugins" artifactId: "jackson2-api" version: 2.8.11.2 - groupId: "org.jenkins-ci.plugins" artifactId: "display-url-api" version: 2.2.0 environments: - name: aws plugins: #TODO: BOM does not support FileSystem REFs, so somebody needs to add BOM auto-update logic here - groupId: "io.jenkins.plugins" artifactId: "artifact-manager-s3" version: 1.0-alpha-1-rc20.60688a35a736 Jesse Glick Made a very interesting (and right IMO) statement in a conversation if the plugin is bundled by the CWP, then by definition you do _not_ want to update it That means if any transitive one is on the wrong version, you should add explicitly on the right one. As a corollary from that (which I can agree also) in the end we are (IMO) going to need a tool to update/generate the BOM file automatically or maintaining it is going to be so impractical that nobody is going to do that, again Jesse Glick has pointed to
[JIRA] (JENKINS-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza commented on JENKINS-51306 Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version I can confirm this is not an ATH failure, even when starting the war file by itself and trying to update the plugin manually (via UC) it does restart but is not updated... Trying to understand why 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-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza commented on JENKINS-51306 Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version By taking a look at the video and by my local debugging I can confirm that the ATH does restart Jenkins, however, that restart seems to have no effect on the status of the plugin, this is quite strange. I am going to try to reproduce locally (without ATH) to see if is something related to the use of a custom update center or the war itself 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-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title
Raul Arabaolaza edited a comment on JENKINS-51306
Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
{noformat} master50107|WARNING: Call to pin plugin has been ignored. Plugin name: apache-httpcomponents-client-4-apimaster50107|May 14, 2018 3:57:06 PM hudson.PluginManager dynamicLoadmaster50107|INFO: Attempting to dynamic load /mnt/agent-workspace/workspace/act-manager-s3-plugin_PR-20-UBEU36QRPCUL7VA4PQJRQWYU5NJSIGM3MZDPG2NDBVZY4X65OUXA/src/test/it/ath/testfirefox/target/jenkins6150668327098166345home/plugins/apache-httpcomponents-client-4-api.jpi {noformat}
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-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza commented on JENKINS-51306 Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version master50107|WARNING: Call to pin plugin has been ignored. Plugin name: apache-httpcomponents-client-4-api master50107|May 14, 2018 3:57:06 PM hudson.PluginManager dynamicLoad master50107|INFO: Attempting to dynamic load /mnt/agent-workspace/workspace/act-manager-s3-plugin_PR-20-UBEU36QRPCUL7VA4PQJRQWYU5NJSIGM3MZDPG2NDBVZY4X65OUXA/src/test/it/ath/testfirefox/target/jenkins6150668327098166345home/plugins/apache-httpcomponents-client-4-api.jpi 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-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza started work on JENKINS-51306 Change By: Raul Arabaolaza 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-51459) Define a way to test incompatible configurations as code in essentials
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51459 Define a way to test incompatible configurations as code in essentials Issue Type: Task Assignee: Raul Arabaolaza Components: essentials Created: 2018-05-21 15:27 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza We need to define how does Evergreen plan to approach the compatibility concerns of the Configuration-as-Code engine. Currently, it does not guarantee YAML compatibility when switching between LTS baselines E.g. 2.60.x config for agents will fail to load in 2.73+ If Evergreen plans to let users set their configs for Essentials, then the instance may go south once Essentials picks a new baseline. Add Comment
[JIRA] (JENKINS-51452) Set up a live instance for dogfooding essentials client/server setup
Title: Message Title Raul Arabaolaza assigned an issue to Unassigned Jenkins / JENKINS-51452 Set up a live instance for dogfooding essentials client/server setup Change By: Raul Arabaolaza Assignee: R. Tyler Croy 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-51448) Get a list of P1 cases for Essentials M1
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-51448 Get a list of P1 cases for Essentials M1 Change By: Raul Arabaolaza As part of the global quality bar for Essentials client/server setup we need a list of P1 cases to be sure that we are properly testing all of them *Acceptance criteria* * There is a list of P1 cases for milestone 1* Each case contains proper testing notes 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-51448) Get a list of P1 cases for Essentials M1
Title: Message Title Raul Arabaolaza assigned an issue to Unassigned Jenkins / JENKINS-51448 Get a list of P1 cases for Essentials M1 Change By: Raul Arabaolaza Assignee: R. Tyler Croy 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-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza edited a comment on JENKINS-51425 Re: Define quality bar for client/server setup I will let am keeping [~batmat] to be as the assigned person here as he has stated he wants to be the one for tracking purposes. 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-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza commented on JENKINS-51425 Re: Define quality bar for client/server setup I will let Baptiste Mathus to be assigned person here as he has stated he wants to be the one for tracking purposes. 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-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza commented on JENKINS-51425 Re: Define quality bar for client/server setup Quality Bar draft added for further review 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-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza started work on JENKINS-51425 Change By: Raul Arabaolaza 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-51458) Provide documentation for the essentials client/server setup
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51458 Provide documentation for the essentials client/server setup Issue Type: Task Assignee: Unassigned Components: essentials Created: 2018-05-21 13:10 Priority: Minor Reporter: Raul Arabaolaza In order to organize bug bashes and test that the deployment/update of essentials client/server setup is successful, we need to generate documentation with the rollout plan including: Prerequisites for deployment Instructions on how to perform the deployment Testing notes after deployment to verify everything went fine Add Comment
[JIRA] (JENKINS-51456) Code coverage report for essentials client/server setup
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51456 Code coverage report for essentials client/server setup Issue Type: Task Assignee: Unassigned Components: essentials Created: 2018-05-21 11:10 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza In a similar fashion to https://issues.jenkins-ci.org/browse/JENKINS-50535 we need a code coverage report for essentials client/server setup Add Comment
[JIRA] (JENKINS-51455) Performance testing of essentials client/server setup
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51455 Performance testing of essentials client/server setup Issue Type: Task Assignee: Unassigned Components: essentials Created: 2018-05-21 10:48 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza Once we have a clear idea of the performance requirements of the milestone 1 of essentials client/server setup we need to make sure we are fulfilling them Acceptance Criteria There is a defined methodology to test the performance requirements For each P1 case we have tested all performance requirements are meet Please create a subtask/separate ticket for each P1 case test and link it here Add Comment
[JIRA] (JENKINS-51453) Define performance requirements of essentials client/server system
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51453 Define performance requirements of essentials client/server system Issue Type: Task Assignee: Unassigned Components: essentials Created: 2018-05-21 10:41 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza Before doing any kind of performance testing we need to be sure of the performance requirements, this task is about defining them Acceptance criteria There is documentation specifying the performance requirements for milestone 1 of the essentials client/server setup Add Comment
[JIRA] (JENKINS-51452) Set up a live instance for dogfooding essentials client/server setup
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51452 Set up a live instance for dogfooding essentials client/server setup Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-05-21 10:37 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza It would be great to be able to perform some dogfooding on essentials client/server setup before releasing it Acceptance criteria There is a live essentials instance running That instance is used to perform some essentials related tasks like development of essentials itself Add Comment
[JIRA] (JENKINS-51451) BugBash session for essentials client/server setup
Title: Message Title Raul Arabaolaza assigned an issue to Unassigned Jenkins / JENKINS-51451 BugBash session for essentials client/server setup Change By: Raul Arabaolaza Assignee: R. Tyler Croy 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-51451) BugBash session for essentials client/server setup
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51451 BugBash session for essentials client/server setup Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-05-21 10:29 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza To ensure Milestone 1 is delivered with the minimum quality requirements I recommend to do a bug bash session for all the P1 cases defined in JENKINS-51448 Add Comment
[JIRA] (JENKINS-51449) Testing of P1 cases for essentials client/server setup
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-51449 Testing of P1 cases for essentials client/server setup Change By: Raul Arabaolaza For essentials client/server setup we need to test all P1 cases to make sure we arefulfilling our DoDP1 cases are to be defined in JENKINS-51425 and we need a subtask/ticket for testing status of each one of them 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-51449) Testing of P1 cases for essentials client/server setup
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-51449 Testing of P1 cases for essentials client/server setup Change By: Raul Arabaolaza For essentials client/server setup we need to test all P1 cases to make sure we are 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-51449) Testing of P1 cases for essentials client/server setup
Title: Message Title Raul Arabaolaza assigned an issue to Unassigned Jenkins / JENKINS-51449 Testing of P1 cases for essentials client/server setup Change By: Raul Arabaolaza Assignee: R. Tyler Croy 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-51449) Testing of P1 cases for essentials client/server setup
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51449 Testing of P1 cases for essentials client/server setup Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-05-21 10:15 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza edited a comment on JENKINS-51425 Re: Define quality bar for client/server setup I can not create subtasks so I will create independent tickets for needed tasks and mark this as blocked by them link here (and in the quality bar itself) 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-51448) Get a list of P1 cases for Essentials M1
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51448 Get a list of P1 cases for Essentials M1 Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-05-21 10:05 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza As part of the global quality bar for Essentials client/server setup we need a list of P1 cases to be sure that we are properly testing all of them Add Comment
[JIRA] (JENKINS-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza commented on JENKINS-51425 Re: Define quality bar for client/server setup I can not create subtasks so I will create independent tickets for needed tasks and mark this as blocked by them 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-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-51425 Define quality bar for client/server setup Change By: Raul Arabaolaza Issue Type: Task Story 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-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza assigned an issue to Baptiste Mathus Jenkins / JENKINS-51425 Define quality bar for client/server setup Change By: Raul Arabaolaza Assignee: Raul Arabaolaza Baptiste Mathus 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-51425) Define quality bar for client/server setup
Title: Message Title Raul Arabaolaza assigned an issue to Raul Arabaolaza Jenkins / JENKINS-51425 Define quality bar for client/server setup Change By: Raul Arabaolaza Assignee: Baptiste Mathus Raul Arabaolaza 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza commented on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin Not blocked, it was my mistake, using wrong groupIds... 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-51298) Add support for multimodule plugins (like BO) to CWP
Title: Message Title Raul Arabaolaza resolved as Not A Defect Jenkins / JENKINS-51298 Add support for multimodule plugins (like BO) to CWP Change By: Raul Arabaolaza Status: In Progress Resolved Resolution: Not A Defect 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-51298) Add support for multimodule plugins (like BO) to CWP
Title: Message Title Raul Arabaolaza commented on JENKINS-51298 Re: Add support for multimodule plugins (like BO) to CWP Oleg Nenashev is absolutely right, my failure here 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-51298) Add support for multimodule plugins (like BO) to CWP
Title: Message Title Raul Arabaolaza commented on JENKINS-51298 Re: Add support for multimodule plugins (like BO) to CWP This is the config file I am using: bundle: groupId: "org.jenkins-ci.main" artifactId: "jenkins-core-it" vendor: "Jenkins project" title: "Jenkins Integration Tests WAR" description: "Jenkins WAR for integration tests" war: groupId: "org.jenkins-ci.main" artifactId: "jenkins-war" source: version: "2.107.2" plugins: - groupId: "org.jenkins-ci.plugins" artifactId: "ssh-slaves" source: version: "1.25" - groupId: "org.jenkins-ci.plugins" artifactId: "command-launcher" source: version: "1.2" - groupId: "org.jenkins-ci.plugins" artifactId: "windows-slaves" source: version: "1.3.1" - groupId: "org.jenkins-ci.plugins" artifactId: "credentials" source: version: "2.1.10" - groupId: "org.jenkins-ci.plugins" artifactId: "ssh-credentials" source: version: "1.12" - groupId: "org.jenkins-ci.plugins" artifactId: "blueocean-git-pipeline" source: version: "1.5.0" - groupId: "org.jenkins-ci.plugins" artifactId: "blueocean-bitbucket-pipeline" source: version: "1.5.0" - groupId: "org.jenkins-ci.plugins" artifactId: "blueocean-bitbucket-pipeline" source: version: "1.5.0" - groupId: "org.jenkins-ci.plugins" artifactId: "blueocean-autofavorite" source: version: "1.5.0" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51298) Add support for multimodule plugins (like BO) to CWP
Title: Message Title Raul Arabaolaza started work on JENKINS-51298 Change By: Raul Arabaolaza 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-51298) Add support for multimodule plugins (like BO) to CWP
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51298 Add support for multimodule plugins (like BO) to CWP Issue Type: Task Assignee: Raul Arabaolaza Components: custom-war-packager Created: 2018-05-14 14:27 Labels: essentials Priority: Major Reporter: Raul Arabaolaza It seems CWP is not able to properly deal with multimodule plugins like BO [ERROR] Failed to execute goal on project jenkins-core-it: Could not resolve dependencies for project org.jenkins-ci.main:jenkins-core-it:jar:1.0-SNAPSHOT: The following artifacts could not be resolved: org.jenkins-ci.plugins:blueocean-git-pipeline:jar:1.5.0, org.jenkins-ci.plugins:blueocean-bitbucket-pipeline:jar:1.5.0, org.jenkins-ci.plugins:blueocean-autofavorite:jar:1.5.0: Could not find artifact org.jenkins-ci.plugins:blueocean-git-pipeline:jar:1.5.0 I have not tested, but probably the same problem could happen with workflow plugins
[JIRA] (JENKINS-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza commented on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin Currently blocked by JENKINS-51298 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza commented on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin It seems the PCT docker image is not able to deal with multimodule plugins like BO, need to fix that, also there are a bunch of plugins not passing the PCT due to various reasons, I will create tickets to fix them (or I will remove from the 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza commented on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin Unstability has been solved apparently, also there are new facilities in pipeline-library provided by the always amazing Oleg Nenashev that mostly implement all the desired flow, so starting with this again. 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza started work on JENKINS-51008 Change By: Raul Arabaolaza 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza updated JENKINS-50790 The fix for JENKINS-51205 solved this problem Jenkins / JENKINS-50790 GitPluginTest are failing in the ATH Change By: Raul Arabaolaza Status: In Review Resolved Resolution: Fixed 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH Last builds of git-plugin have no failures, so I am going to close this. 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza updated JENKINS-50790 Jenkins / JENKINS-50790 GitPluginTest are failing in the ATH Change By: Raul Arabaolaza Status: In Progress Review 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH It seems it worked, I am going to get this open for a pair of days and close if nothing new arises 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH Not sure if the fix in JENKINS-51205 is enough, I am still receiving email alerts about instability on git-plugin, however at this moment ci.jenkins.io is down so I can not check the status 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH So after a conversation with Jesse Glick it seems the problem is in the core itself since 2.112, the addition of detached plugins causing an exponential explosion in a recursive call. He is working on a fix, in the meanwhile a temporary increase in the timeout should be enough to make everything stable again 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH Maybe you refer to this code path? I am not going that way, I am making a request to trigger the installation via UC instead of using the buttons in the `Available Plugins Page` and let it handle dependencies and all that stuff, not sure however about versioning constraints at this point 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH What I can see is the http call to pluginManager/available performed by the UI when clicking on the Available tab the one that takes too much time. My understanding is that the endpoint calls the mock UC under the covers, as I have checked that same call with an instance run via java -jar (outside ATH) and it takes much less time ~ 10 seconds 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza started work on JENKINS-50790 Change By: Raul Arabaolaza Status: Reopened 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH I am experimenting with skipping the available plugins page and just request the installation via a REST call, initial experiments seem promising 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH I have performed a little experimentation on load time for the available plugins, when running the ATH and using the MockUpdateCenter the call to get all available plugins oscillates between 25 and 56 seconds running locally, when not using the MockUpdateCenter it takes less than 10 seconds. I am starting to believe that the only way to solve this (as I can not increase the page load timeout forever) is to use groovy scripts to install plugins instead of doing directly by the UI. 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH The delay in the rendering of the available plugins page is obvious even running locally (not in the ATH, just starting the war file) when you do not have any plugin installed, that rendering time (which goes worst which heavy load) is the root cause of this issue, 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza commented on JENKINS-50790 Re: GitPluginTest are failing in the ATH Jesse Glick As you are the one that did the original implementation of MockUpdateCenter can you imagine a reason why it should have a performance degradation under core >= 2.112 with heavy load? 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza edited a comment on JENKINS-50790 Re: GitPluginTest are failing in the ATH [~jglick] As you are the one that did the original implementation of [MockUpdateCenter|https://github.com/jenkinsci/acceptance-test-harness/commits/master/src/main/java/org/jenkinsci/test/acceptance/update_center/MockUpdateCenter.java] can you imagine a reason why it should could have a performance degradation under core >= 2.112 with heavy load? 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-50790 GitPluginTest are failing in the ATH Change By: Raul Arabaolaza Sprint: Essentials - Milestone 1 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-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza reopened an issue See here it seems that the ATH is still flaky, I suspect due to load Jenkins / JENKINS-50790 GitPluginTest are failing in the ATH Change By: Raul Arabaolaza Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-50516) Add the run PCT step to run on a PR basis to essentials
Title: Message Title Raul Arabaolaza closed an issue as Duplicate Jenkins / JENKINS-50516 Add the run PCT step to run on a PR basis to essentials Change By: Raul Arabaolaza Status: Open Closed Resolution: Duplicate 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-50621) add the runATH step to the git-plugin in a PR basis
Title: Message Title Raul Arabaolaza updated JENKINS-50621 Jenkins / JENKINS-50621 add the runATH step to the git-plugin in a PR basis Change By: Raul Arabaolaza Status: In Review Resolved Resolution: Done 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-50540) add the runPCT step to the git-plugin on a PR basis
Title: Message Title Raul Arabaolaza updated JENKINS-50540 Jenkins / JENKINS-50540 add the runPCT step to the git-plugin on a PR basis Change By: Raul Arabaolaza Status: In Review Resolved Resolution: Done 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza commented on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin So, it seems there are some unstability on git-plugin current builds, so first step here will be to help with that if necessary as I do not want to change the current flow until is stable 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-51008 Complete the PCT flow started in JENKINS-50540 for git plugin Change By: Raul Arabaolaza Sprint: Essentials - Milestone 1 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza edited a comment on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin [~oleg_nenashev] No, With this and JENKINS-50953 is enough IMO 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-51008) Complete the PCT flow started in JENKINS-50540 for git plugin
Title: Message Title Raul Arabaolaza commented on JENKINS-51008 Re: Complete the PCT flow started in JENKINS-50540 for git plugin Oleg Nenashev No, JENKINS-50953 is enough IMO 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.
