[JIRA] (JENKINS-27301) Pipeline support for XTrigger

2019-04-24 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov commented on  JENKINS-27301  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline support for XTrigger   
 

  
 
 
 
 

 
 Please, merge PRs from JENKINS-57078 with fixes from URL Trigger.  
 

  
 
 
 
 

 
 
 

 
 
 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-57078) Pipeline support for urltrigger (and xtrigger)

2019-04-24 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57078  
 
 
  Pipeline support for urltrigger (and xtrigger)   
 

  
 
 
 
 

 
Change By: 
 Valentin Titov  
 

  
 
 
 
 

 
 Pipeline Please, integrate pipeline  support for urltrigger (and xtrigger)Plugin pipeline integration manual: [https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#triggers]Related issue  [ https://issues.jenkins-ci.org/browse/JENKINS-27301 ] Suggested PRs:[https://github.com/jenkinsci/ envinject-lib/pull/17] [https://github.com/jenkinsci/ xtrigger-lib/pull/19][https://github.com/jenkinsci/urltrigger-plugin/pull/21]  
 

  
 
 
 
 

 
 
 

 
 
 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-57079) pass token as registerWebhook Step argument

2019-04-17 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57079  
 
 
  pass token as registerWebhook Step argument   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Chris Pitman  
 
 
Components: 
 webhook-step-plugin  
 
 
Created: 
 2019-04-17 11:07  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Valentin Titov  
 

  
 
 
 
 

 
 Current registerWebhook step implementation always creates new random token as UUID. Sometimes it is preferable to pass such unique token value as an argument. See PR: https://github.com/jenkinsci/webhook-step-plugin/pull/12  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-57078) Pipeline support for urltrigger (and xtrigger)

2019-04-17 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57078  
 
 
  Pipeline support for urltrigger (and xtrigger)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Gregory Boissinot  
 
 
Components: 
 urltrigger-plugin, xtrigger-plugin  
 
 
Created: 
 2019-04-17 10:52  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Valentin Titov  
 

  
 
 
 
 

 
 Pipeline support for urltrigger (and xtrigger) Plugin pipeline integration manual: https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#triggers Related issue https://issues.jenkins-ci.org/browse/JENKINS-27301 Suggested PRs: https://github.com/jenkinsci/xtrigger-lib/pull/19 https://github.com/jenkinsci/urltrigger-plugin/pull/21  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 

[JIRA] (JENKINS-56287) dbcp2 migration

2019-02-26 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56287  
 
 
  dbcp2 migration   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 David van Laatum  
 
 
Components: 
 database-plugin  
 
 
Created: 
 2019-02-26 12:23  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Valentin Titov  
 

  
 
 
 
 

 
 Сonsider migration to dbcp2, please. See PR#6: https://github.com/jenkinsci/database-plugin/pull/6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  

[JIRA] (JENKINS-54949) parameter to add current plugin to custom war

2018-11-29 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54949  
 
 
  parameter to add current plugin to custom war   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 maven-hpi-plugin  
 
 
Created: 
 2018-11-29 16:28  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Valentin Titov  
 

  
 
 
 
 

 
 As hpi:help states, 

 
hpi:custom-war
 Builds a custom Jenkins war that includes all the additional plugins
 referenced in this POM.
 

 Please, consider adding parameter like addThisPluginToCustomWar, see PR: https://github.com/jenkinsci/maven-hpi-plugin/pull/86 There is an issue with my implementation. WarMojo has defaultPhase = PACKAGE, so custom-war does not get built before jenkins plugin was packaged. Changing defaultPhase to PRE_INTEGRATION_TEST does not work. I suppose some rearrangement in the custom lifecycle might help. OTOH coutom-war should not be added to package phase in components.xml, as it should not be built and deployed by default. Meanwhile workaround might be used: 

 

mvn package hpi:custom-war -DaddThisPluginToCustomWar=true
 

  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven

2018-11-29 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov updated  JENKINS-54871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54871  
 
 
  "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven   
 

  
 
 
 
 

 
Change By: 
 Valentin Titov  
 
 
Status: 
 Reopened Fixed but Unreleased  
 
 
Resolution: 
 Won't Fix Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven

2018-11-29 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov updated  JENKINS-54871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54871  
 
 
  "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven   
 

  
 
 
 
 

 
Change By: 
 Valentin Titov  
 
 
Status: 
 Fixed but Unreleased Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven

2018-11-29 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov updated  JENKINS-54871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54871  
 
 
  "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven   
 

  
 
 
 
 

 
Change By: 
 Valentin Titov  
 
 
Status: 
 Reopened Fixed but Unreleased  
 
 
Resolution: 
 Done Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven

2018-11-29 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov updated  JENKINS-54871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54871  
 
 
  "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven   
 

  
 
 
 
 

 
Change By: 
 Valentin Titov  
 
 
Status: 
 Fixed but Unreleased Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven

2018-11-29 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov assigned an issue to Valentin Titov  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54871  
 
 
  "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven   
 

  
 
 
 
 

 
Change By: 
 Valentin Titov  
 
 
Assignee: 
 Valentin Titov  
 

  
 
 
 
 

 
 
 

 
 
 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-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven

2018-11-29 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov updated  JENKINS-54871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54871  
 
 
  "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven   
 

  
 
 
 
 

 
Change By: 
 Valentin Titov  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 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-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven

2018-11-27 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov commented on  JENKINS-54871  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven   
 

  
 
 
 
 

 
 Brad, Could you, please, rerun maven (both as jenkins job and from cmd line) with more diagnostics? E.g., please, set MAVEN_OPTS, than "Re-run Maven using the -X switch": 

 

MAVEN_OPTS='-XshowSettings:vm -XshowSettings:properties -verbose'
export MAVEN_OPTS
mvn -B -X gatling:test >& mvn.log & 

 Pease, pay attention to output of gatling:help: 

 

mvn gatling:help -Ddetail=true 

 You might want to tune  compilerJvmArgs: Extra JVM arguments to pass when running Zinc. User property: gatling.compilerJvmArgs Regards, Valentin  
 

  
 
 
 
 

 
 
 

 
 
 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-54754) JellyTestSuiteBuilder complains about escape-by-default

2018-11-21 Thread y...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Valentin Titov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54754  
 
 
  JellyTestSuiteBuilder complains about escape-by-default   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 ui-samples-plugin  
 
 
Created: 
 2018-11-21 12:51  
 
 
Environment: 
 current version on github  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Valentin Titov  
 

  
 
 
 
 

 
 When running mvn test for ui-samples-plugin I get an error: 

 
 [ERROR] Tests run: 29, Failures: 1, Errors: 4, Skipped: 0, Time elapsed: 17.758 s <<< FAILURE! - in InjectedTest
[ERROR] index.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck)  Time elapsed: 0.009 s  <<< FAILURE!
java.lang.AssertionError:  is missing in file:/E:/Users/Public/vititov/build/github/ui-samples-plugin/target/classes/index.jelly
at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:108)
 

 Please, check PR with a fix: https://github.com/jenkinsci/ui-samples-plugin/pull/6