[JIRA] [release-plugin] (JENKINS-27723) Overriding build goal while performing a release
Harsh Shah edited a comment on JENKINS-27723 Overriding build goal while performing a release @Hannes, the environment class in Jenkins core can have one more method with a return type boolean which by default always returns false. The method can be override in the release wrapper class of the release plugin. When the release wrapper class of the release plugin returns a new environment. We override the boolean method to return true if the default build needs to be override. I hope this give you some details. The option to override the default build can be provided in the UI too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27723) Overriding build goal while performing a release
Harsh Shah commented on JENKINS-27723 Overriding build goal while performing a release @Hannes, the environment class in Jenkins core can have one more method with a return type boolean which by default always returns false. The method can be override in the release wrapper class of the release plugin. This override method in the release wrapper class of the plugin will return true if the default build needs to be override. I hope this give you some details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-11120) Add a possiblity to skip/override the normal build in case of a release.
Harsh Shah started work on JENKINS-11120 Add a possiblity to skip/override the normal build in case of a release. Change By: Harsh Shah (09/Apr/15 8:18 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-11120) Add a possiblity to skip/override the normal build in case of a release.
Harsh Shah commented on JENKINS-11120 Add a possiblity to skip/override the normal build in case of a release. We found a way to have the jenkins release-plugin to notify Jenkins core to skip the default build 1. Introduce a ‘release build step’, once it is executed and return back to Jenkins core[1] with an instance of Environment [2] 2. Set the return Environment instance to null, or introduce an new flag in the environment class which notifies to override the default build. 3. Jenkins core’s Build.java ( and related concrete class ) skip the default build step base on the status of the return Env instance or the status of the new flag This means we need help from Jenkins core dev to add new capability in Jenkins core to skip the default build step. Will file an RFE with Jenkins core Thanks [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Build.java [2] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Environment.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27723) Overriding build goal while performing a release
Harsh Shah commented on JENKINS-27723 Overriding build goal while performing a release We found a way to have the jenkins release-plugin to notify Jenkins core to skip the default build 1. Introduce a ‘release build step’, once it is executed and return back to Jenkins core[1] with an instance of Environment [2] 2. Set the return Environment instance to null, or introduce an new flag in the environment class which notifies to override the default build. 3. Jenkins core’s Build.java ( and related concrete class ) skip the default build step base on the status of the return Env instance or the status of the new flag This means we need help from Jenkins core dev to add new capability in Jenkins core to skip the default build step. Will file an RFE with Jenkins core Thanks [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Build.java [2] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Environment.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27723) Overriding build goal while performing a release
Harsh Shah assigned JENKINS-27723 to Peter Hayes Overriding build goal while performing a release Change By: Harsh Shah (09/Apr/15 6:35 PM) Assignee: Harsh Shah Peter Hayes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27723) Overriding build goal while performing a release
Harsh Shah started work on JENKINS-27723 Overriding build goal while performing a release Change By: Harsh Shah (09/Apr/15 6:31 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27723) Overriding build goal while performing a release
Harsh Shah assigned JENKINS-27723 to Harsh Shah Overriding build goal while performing a release Change By: Harsh Shah (09/Apr/15 6:31 PM) Assignee: Peter Hayes Harsh Shah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-11120) Add a possiblity to skip/override the normal build in case of a release.
Harsh Shah commented on JENKINS-11120 Add a possiblity to skip/override the normal build in case of a release. Hi, Any updates to this issue? I have the same issue and I am trying to customize the plugin to override build goal with the release goal. Here is the link https://issues.jenkins-ci.org/browse/JENKINS-27723. To remove ambiguity I have added one more field called "release goal" in the configure release settings(see the link) where I add the goals. I am able to work this out but some how it is not overriding the default build goal. It executes the build goal and then the release goal. I am a newbie to Jenkins would appreciate any help provided. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27723) Overriding build goal while performing a release
Harsh Shah updated JENKINS-27723 Overriding build goal while performing a release Change By: Harsh Shah (02/Apr/15 7:13 PM) Description: The current release plugin performs a build twice when a release is done. It does one build using the default build goal and then it builds again using the release goal. I am trying to override the default build goal and just perform the release goal at time of release. To do so we need to have the release goal input from the user so have added one more field in the configuration environment. Kindly see the attached image. Thought this option is available in pre release menu but still it does not override the default build and performs two builds at time of release which take more time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27723) Overriding build goal while performing a release
Harsh Shah created JENKINS-27723 Overriding build goal while performing a release Issue Type: Improvement Assignee: Peter Hayes Attachments: release plugin.jpg Components: release-plugin Created: 02/Apr/15 6:48 PM Description: The current release plugin performs a build twice when a release is done. It does one build using the default build goal and then it builds again using the release goal. I am trying to override the default build goal and just perform the release goal at time of release. To do so we need to have the release goal input from the user so have added one more field in the configuration environment. Kindly see the attached image. Environment: Java 1.7 Project: Jenkins Labels: release plugin Priority: Minor Reporter: Harsh Shah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
Harsh Shah updated JENKINS-27722 upgrade to the release plugin has left the plugin broken Change By: Harsh Shah (02/Apr/15 6:28 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
Harsh Shah created JENKINS-27722 upgrade to the release plugin has left the plugin broken Issue Type: Bug Assignee: Peter Hayes Components: release-plugin Created: 02/Apr/15 6:24 PM Description: I cloned the release plugin repo from github to customize the plugin. The plugin when packaged on local machine it does a successful package but when the hpi package is uploaded to jenkins server the release button on the left panel is not showing up. When I checked out the older branch from the repository the plugin works perfectly fine. May be the recent changes is failing the plugin. Environment: Java 1.7 Project: Jenkins Labels: Plugin Release Priority: Minor Reporter: Harsh Shah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [patch-parameter-plugin] (JENKINS-27169) Patch parameter plugin's patch code is OS dependent which fails to patch cross platform files
Harsh Shah commented on JENKINS-27169 Patch parameter plugin's patch code is OS dependent which fails to patch cross platform files Not yet will update once I work on it again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [patch-parameter-plugin] (JENKINS-27169) Patch parameter plugin's patch code is OS dependent which fails to patch cross platform files
Harsh Shah updated JENKINS-27169 Patch parameter plugin's patch code is OS dependent which fails to patch cross platform files Change By: Harsh Shah (12/Mar/15 11:57 PM) Description: The test case in someTest class (https://github.com/jenkinsci/patch-parameter-plugin/commit/02c684a6e9d9fe40548c839ab15d2231306eb239 ) fails on windows. I am trying to use a patch file created on Unix machine on a windows machine. The code uses cloudbees/diff4j/ContextualPatch which internally uses BufferedReader to read files. BufferedReader does OS specific reading operation. So the end of file is causing the problem for the test case to pass when run on windows machine. Kindly see the attached images.Here is the link of ContextualPatch implementation https://github.com/cloudbees/diff4j/blob/master/src/main/java/com/cloudbees/diff/ContextualPatch.javaThank you for the help.H Shah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [patch-parameter-plugin] (JENKINS-27169) Patch parameter plugin's patch code is OS dependent which fails to patch cross platform files
Harsh Shah commented on JENKINS-27169 Patch parameter plugin's patch code is OS dependent which fails to patch cross platform files Hi Charles The problem lies with the diff4j jar. I tried using System.lineSeparator() and the test case passed but I am concerned with ContextualPatch. It reads a file using bufferedReader which is OS dependent and so will create a problem. I am trying to use a patch file created on Unix machine on a windows machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-24497) Allow free style project to work with this plugin
Harsh Shah assigned JENKINS-24497 to Harsh Shah Allow free style project to work with this plugin Change By: Harsh Shah (11/Mar/15 9:27 PM) Assignee: James Nord Harsh Shah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release-plugin] (JENKINS-27366) Trying to enable "perform maven release" to free style project.
Harsh Shah created JENKINS-27366 Trying to enable "perform maven release" to free style project. Issue Type: New Feature Assignee: James Nord Components: m2release-plugin Created: 11/Mar/15 4:56 PM Description: Hi, I am a novice to Jenkins. I am trying to extend the m2release plugin to free style project. So far I am able to get the "maven release build" option for the Build environment in the configuration of a free style project. But when I select this option for the free style project the "perform maven release" button is not popping up in the left side menu. My concern is am I trying something which is not feasible. I mean asking M2release-plugin to perform release for free style project. If this is feasible which class of the plugin should I look in to get the "perform maven release" enabled for free style project. I am currently trying to modify the M2ReleaseBuildWrapper class and M2ReleaseAction class. I appreciate your help and comments. Environment: Jenkins 1.601 Project: Jenkins Labels: Plugins Priority: Major Reporter: Harsh Shah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [patch-parameter-plugin] (JENKINS-27169) Patch paramter plugin's patch code is OS dependent which fails to patch cross platform files
Harsh Shah created JENKINS-27169 Patch paramter plugin's patch code is OS dependent which fails to patch cross platform files Issue Type: Bug Assignee: Unassigned Attachments: failed test.jpg, noerror.jpg Components: patch-parameter-plugin Created: 27/Feb/15 11:06 PM Description: The test case in someTest class (https://github.com/jenkinsci/patch-parameter-plugin/commit/02c684a6e9d9fe40548c839ab15d2231306eb239 ) fails on windows. The code uses cloudbees/diff4j/ContextualPatch which internally uses BufferedReader to read files. BufferedReader does OS specific reading operation. So the end of file is causing the problem for the test case to pass when run on windows machine. Kindly see the attached images. Here is the link of ContextualPatch implementation https://github.com/cloudbees/diff4j/blob/master/src/main/java/com/cloudbees/diff/ContextualPatch.java Thank you for the help. H Shah Environment: JDK 7, windows 7 Project: Jenkins Priority: Major Reporter: Harsh Shah This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [patch-parameter-plugin] (JENKINS-27168) Patch Parameter plugin fails while using Jdk 1.8
Harsh Shah created JENKINS-27168 Patch Parameter plugin fails while using Jdk 1.8 Issue Type: Bug Assignee: Unassigned Components: patch-parameter-plugin Created: 27/Feb/15 6:51 PM Description: Scanning for projects... [INFO] [INFO] [INFO] Building patch-parameter 1.3-SNAPSHOT [INFO] [INFO] [INFO] — maven-hpi-plugin:1.93:validate (default-validate) @ patch-parameter — [INFO] [INFO] — maven-enforcer-plugin:1.0.1:enforce (enforce-maven) @ patch-parameter — [INFO] [INFO] — maven-enforcer-plugin:1.0.1:display-info (display-info) @ patch-parameter — [INFO] Maven Version: 3.2.5 [INFO] JDK Version: 1.8.0_31 normalized as: 1.8.0-31 [INFO] OS Info: Arch: amd64 Family: dos Name: windows 7 Version: 6.1 [INFO] [INFO] — maven-localizer-plugin:1.14:generate (default) @ patch-parameter — [INFO] [INFO] — maven-resources-plugin:2.5:resources (default-resources) @ patch-parameter — [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 4 resources [INFO] [INFO] — maven-compiler-plugin:2.5:compile (default-compile) @ patch-parameter — [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] — access-modifier-checker:1.4:enforce (default-enforce) @ patch-parameter — [INFO] [INFO] — maven-hpi-plugin:1.93:insert-test (default-insert-test) @ patch-parameter — [INFO] [INFO] — gmaven-plugin:1.3:generateTestStubs (test-in-groovy) @ patch-parameter — [INFO] No sources found for Java stub generation [INFO] [INFO] — maven-resources-plugin:2.5:testResources (default-testResources) @ patch-parameter — [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] [INFO] — maven-compiler-plugin:2.5:testCompile (default-testCompile) @ patch-parameter — [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] — maven-hpi-plugin:1.93:test-hpl (default-test-hpl) @ patch-parameter — [INFO] Generating E:\views\patchpulgin\patch-parameter-plugin-master\target\test-classes\the.hpl [INFO] [INFO] — maven-hpi-plugin:1.93:resolve-test-dependencies (default-resolve-test-dependencies) @ patch-parameter — [INFO] [INFO] — gmaven-plugin:1.3:testCompile (test-in-groovy) @ patch-parameter — [INFO] No sources found to compile [INFO] [INFO] — maven-surefire-plugin:2.9:test (default-test) @ patch-parameter — [INFO] Surefire report directory: E:\views\patchpulgin\patch-parameter-plugin-master\target\surefire-reports --- T E S T S --- Running InjectedTest Picking up existing exploded jenkins.war at E:\views\patchpulgin\patch-parameter-plugin-master\.\target\jenkins-for-test Feb 27, 2015 9:25:33 AM org.mortbay.log.Slf4jLog info INFO: Logging to org.slf4j.impl.JDK14LoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog Feb 27, 2015 9:25:33 AM org.mortbay.log.Slf4jLog info INFO: jetty-6.1.26 Feb 27, 2015 9:25:36 AM org.mortbay.log.Slf4jLog info INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet Feb 27, 2015 9:25:36 AM org.mortbay.log.Slf4jLog info INFO: Copy E:\views\patchpulgin\patch-parameter-plugin-master\target\jenkins-for-test to C:\Users\shahh5\AppData\Local\Temp\Jetty_0_0_0_0_0_jenkins.for.test___.bj8wp3\webapp Feb 27, 2015 9:25:38 AM org.mortbay.log.Slf4jLog info INFO: Started SocketConnector@0.0.0.0:55769 Feb 27, 2015 9:25:38 AM jenkins.InitReactorRunner$1 onAttained INFO: Started initialization Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttained INFO: Augmented all extensions Feb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$
[JIRA] [patch-parameter-plugin] (JENKINS-27168) Patch Parameter plugin fails while using Jdk 1.8
Harsh Shah updated JENKINS-27168 Patch Parameter plugin fails while using Jdk 1.8 Change By: Harsh Shah (27/Feb/15 6:51 PM) Description: The plugin build fails when trying maven build using Jdk 1.8.but it works fine in Jdk 1.7. Scanning for projects...[INFO] [INFO] [INFO] Building patch-parameter 1.3-SNAPSHOT[INFO] [INFO] [INFO] --- maven-hpi-plugin:1.93:validate (default-validate) @ patch-parameter ---[INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-maven) @ patch-parameter ---[INFO] [INFO] --- maven-enforcer-plugin:1.0.1:display-info (display-info) @ patch-parameter ---[INFO] Maven Version: 3.2.5[INFO] JDK Version: 1.8.0_31 normalized as: 1.8.0-31[INFO] OS Info: Arch: amd64 Family: dos Name: windows 7 Version: 6.1[INFO] [INFO] --- maven-localizer-plugin:1.14:generate (default) @ patch-parameter ---[INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ patch-parameter ---[debug] execute contextualize[INFO] Using 'UTF-8' encoding to copy filtered resources.[INFO] Copying 4 resources[INFO] [INFO] --- maven-compiler-plugin:2.5:compile (default-compile) @ patch-parameter ---[INFO] Nothing to compile - all classes are up to date[INFO] [INFO] --- access-modifier-checker:1.4:enforce (default-enforce) @ patch-parameter ---[INFO] [INFO] --- maven-hpi-plugin:1.93:insert-test (default-insert-test) @ patch-parameter ---[INFO] [INFO] --- gmaven-plugin:1.3:generateTestStubs (test-in-groovy) @ patch-parameter ---[INFO] No sources found for Java stub generation[INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ patch-parameter ---[debug] execute contextualize[INFO] Using 'UTF-8' encoding to copy filtered resources.[INFO] Copying 1 resource[INFO] [INFO] --- maven-compiler-plugin:2.5:testCompile (default-testCompile) @ patch-parameter ---[INFO] Nothing to compile - all classes are up to date[INFO] [INFO] --- maven-hpi-plugin:1.93:test-hpl (default-test-hpl) @ patch-parameter ---[INFO] Generating E:\views\patchpulgin\patch-parameter-plugin-master\target\test-classes\the.hpl[INFO] [INFO] --- maven-hpi-plugin:1.93:resolve-test-dependencies (default-resolve-test-dependencies) @ patch-parameter ---[INFO] [INFO] --- gmaven-plugin:1.3:testCompile (test-in-groovy) @ patch-parameter ---[INFO] No sources found to compile[INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ patch-parameter ---[INFO] Surefire report directory: E:\views\patchpulgin\patch-parameter-plugin-master\target\surefire-reports--- T E S T S---Running InjectedTestPicking up existing exploded jenkins.war at E:\views\patchpulgin\patch-parameter-plugin-master\.\target\jenkins-for-testFeb 27, 2015 9:25:33 AM org.mortbay.log.Slf4jLog infoINFO: Logging to org.slf4j.impl.JDK14LoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLogFeb 27, 2015 9:25:33 AM org.mortbay.log.Slf4jLog infoINFO: jetty-6.1.26Feb 27, 2015 9:25:36 AM org.mortbay.log.Slf4jLog infoINFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServletFeb 27, 2015 9:25:36 AM org.mortbay.log.Slf4jLog infoINFO: Copy E:\views\patchpulgin\patch-parameter-plugin-master\target\jenkins-for-test to C:\Users\shahh5\AppData\Local\Temp\Jetty_0_0_0_0_0_jenkins.for.test___.bj8wp3\webappFeb 27, 2015 9:25:38 AM org.mortbay.log.Slf4jLog infoINFO: Started SocketConnector@0.0.0.0:55769Feb 27, 2015 9:25:38 AM jenkins.InitReactorRunner$1 onAttainedINFO: Started initializationFeb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Listed all pluginsFeb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Prepared all pluginsFeb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Started all pluginsFeb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Augmented all extensionsFeb 27, 2015 9:25:46 AM jenkins.InitReactorRunner$1 onAttainedINFO: Loaded all jobsFeb 27, 2015 9:25:48 AM jenkins.InitReactorRunner$1 onAttainedINFO: Completed ini
