[JIRA] (JENKINS-7274) Building by label does not work on StarTeam 6.0
[ https://issues.jenkins-ci.org/browse/JENKINS-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160130#comment-160130 ] tiger tiger commented on JENKINS-7274: -- Hello jan_ruzicka,do we have recent progress for this problem?I can reproducible this problem with plugin 0.6.7,And my environment set as below: System is Windows XP SP3; Jenkins version is :jenkins-1.450; Starteam SDK is:StarTeam SDK 10.0 Error informations: A view can only be modified from its current configuration. at com.starbase.starteam.ServerException.wrap(Unknown Source) at com.starbase.starteam.Server.wrap(Unknown Source) at com.starbase.starteam.File.checkout(Unknown Source) at hudson.plugins.starteam.StarTeamConnection.checkOut(StarTeamConnection.java:232) at hudson.plugins.starteam.StarTeamCheckoutActor.invoke(StarTeamCheckoutActor.java:146) at hudson.plugins.starteam.StarTeamCheckoutActor.invoke(StarTeamCheckoutActor.java:34) at hudson.FilePath.act(FilePath.java:788) at hudson.FilePath.act(FilePath.java:770) at hudson.plugins.starteam.StarTeamSCM.checkout(StarTeamSCM.java:130) at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:576) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:465) at hudson.model.Run.run(Run.java:1409) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Building by label does not work on StarTeam 6.0 --- Key: JENKINS-7274 URL: https://issues.jenkins-ci.org/browse/JENKINS-7274 Project: Jenkins Issue Type: Bug Components: starteam Environment: Windows Server 2008. StarTeam 6.0 Reporter: andersrb Assignee: jan_ruzicka Building from a label on StarTeam 6.0 immediately fails with the following error: A view can only be modified from its current configuration. at com.starbase.starteam.ServerException.wrap(Unknown Source) at com.starbase.starteam.Server.wrap(Unknown Source) at com.starbase.starteam.File.checkout(Unknown Source) at hudson.plugins.starteam.StarTeamConnection.checkOut(StarTeamConnection.java:230) at hudson.plugins.starteam.StarTeamCheckoutActor.invoke(StarTeamCheckoutActor.java:129) at hudson.plugins.starteam.StarTeamCheckoutActor.invoke(StarTeamCheckoutActor.java:30) at hudson.FilePath.act(FilePath.java:753) at hudson.FilePath.act(FilePath.java:735) at hudson.plugins.starteam.StarTeamSCM.checkout(StarTeamSCM.java:125) at hudson.model.AbstractProject.checkout(AbstractProject.java:1038) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411) at hudson.model.Run.run(Run.java:1257) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:129) FATAL: A view can only be modified from its current configuration. A view can only be modified from its current configuration. at com.starbase.starteam.ServerException.wrap(Unknown Source) at com.starbase.starteam.Server.wrap(Unknown Source) at com.starbase.starteam.File.checkout(Unknown Source) at hudson.plugins.starteam.StarTeamConnection.checkOut(StarTeamConnection.java:230) at hudson.plugins.starteam.StarTeamCheckoutActor.invoke(StarTeamCheckoutActor.java:129) at hudson.plugins.starteam.StarTeamCheckoutActor.invoke(StarTeamCheckoutActor.java:30) at hudson.FilePath.act(FilePath.java:753) at hudson.FilePath.act(FilePath.java:735) at hudson.plugins.starteam.StarTeamSCM.checkout(StarTeamSCM.java:125) at hudson.model.AbstractProject.checkout(AbstractProject.java:1038) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411) at hudson.model.Run.run(Run.java:1257) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:129) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more
[JIRA] (JENKINS-7920) Access denied when copy files from a network computer in Windows batch script
[
https://issues.jenkins-ci.org/browse/JENKINS-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160131#comment-160131
]
Mattias Vannergård commented on JENKINS-7920:
-
Same thing here.
Neither net use or copy works when running as a Execute Windows batch command
(but it works on a Command console), and I can't find a work-around either.
Have someone found a work-around?
regards
/Mattias
Access denied when copy files from a network computer in Windows batch script
-
Key: JENKINS-7920
URL: https://issues.jenkins-ci.org/browse/JENKINS-7920
Project: Jenkins
Issue Type: Bug
Components: core
Reporter: bakerzhang
I have a problem (Access is denied) when I try to copy files across network
in a Windows batch script.
Hudson will call a script, say, a.bat and inside a.bat I have the followings
{code}
...
setlocal ENABLEDELAYEDEXPANSION
...
if DEFINED abc (
set xyz=\\computer\path
set filename=mm*.dll
copy /Y !xyz!\!filename!
)
...
endlocal
{code}
The 'copy' command will fail and I Google for the problem but there's no
particular one. There's one paper saying UNC should be used
(http://stackoverflow.com/questions/1284561/hudson-continuous-integration-server-how-to-see-windows-mapped-directories-that).
So I did the following experiments:
{code}
1) set xyz=//computer/path
...
copy /Y !xyz!\!filename!
2) ...
copy /Y //computer/path\mm*.dll
{code}
The 1) doesn't work and produces the same problem - Access is denied. but
the 2) is working. However, copy /Y //computer/path\!file_name! won't work
either.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13037) TestLink Plugin with jUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160133#comment-160133 ] Bogdan Girbea commented on JENKINS-13037: - Hello, Sorry for the late reply, i was out for the weekend. I've attached a scrrenshot with the job configuration, the teslink result and the junit xml. If you need anything else, please let me know :) Thank you so much! Bogdan TestLink Plugin with jUnit -- Key: JENKINS-13037 URL: https://issues.jenkins-ci.org/browse/JENKINS-13037 Project: Jenkins Issue Type: Bug Components: junit, testlink Affects Versions: current Environment: Ubuntu 10.04 Reporter: Bogdan Girbea Assignee: Bruno P. Kinoshita Labels: jenkins Attachments: Screenshot.png Hello I am using the 3.1 testlink plugin. I am running a test class, with 4 tests using JUnit 4.8.One of the 4 tests throws an error and still the testlink report marks the test class as passed. If needed i can attach the configurations and/or the results.. Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13037) TestLink Plugin with jUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bogdan Girbea updated JENKINS-13037: Attachment: Screenshot.png TestLink Plugin with jUnit -- Key: JENKINS-13037 URL: https://issues.jenkins-ci.org/browse/JENKINS-13037 Project: Jenkins Issue Type: Bug Components: junit, testlink Affects Versions: current Environment: Ubuntu 10.04 Reporter: Bogdan Girbea Assignee: Bruno P. Kinoshita Labels: jenkins Attachments: Screenshot.png Hello I am using the 3.1 testlink plugin. I am running a test class, with 4 tests using JUnit 4.8.One of the 4 tests throws an error and still the testlink report marks the test class as passed. If needed i can attach the configurations and/or the results.. Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12521) java.lang.IllegalArgumentException with TMP Cleaner Plugin after Jenkins update to version 1.449
[ https://issues.jenkins-ci.org/browse/JENKINS-12521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160135#comment-160135 ] Mike Doherty commented on JENKINS-12521: I'm also seeing the same issue with version 1.424.6 from the LTS release and I don't have Tmp Cleaner Plugin installed. The error message is identical, Caused by: java.lang.IllegalArgumentException: Multiple command line argument specified:. Reverting to the previous version solved the problem without any command line changes. Installed plugin details below: Maven Integration plugin 1.424.6 Static Analysis Utilities This plug-in provides utilities for the static code analysis plug-ins. 1.38 Checkstyle Plugin This plug-in collects the Checkstyle analysis results of the project modules and visualizes the found warnings. 3.23 Analysis Collector Plugin This plug-in is an add-on for the plug-ins Checkstyle, Dry, FindBugs, PMD, Tasks, and Warnings: the plug-in collects the different analysis results and shows the results in a combined trend graph. Additionally, the plug-in provides health reporting and build stability based on these combined results. 1.19 Jenkins Artifact Deployer Plug-in This plug-in makes it possible to deploy artifacts from workspace to output directories. Only the artifacts of the latest build will be keept. 0.13 Backup plugin Backup or restore your Hudson configuration files 1.6.1 built-on-column Shows the actual node that a job was built on 1.1 Jenkins Email Extension Plugin This plugin is a replacement for Jenkins's email publisher 2.17-SNAPSHOT (private-11/28/2011 11:36-mike) Jenkins Subversion Plug-in 1.39 Jenkins CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.0 Configuration Slicing plugin 1.28.1 Copy Artifact Plugin Adds a build step to copy artifacts from another project. 1.20 Dependency Graph Viewer Plugin This plugin shows a dependency graph of the projects. It uses dot (from graphviz) for drawing. 0.2 Jenkins disk-usage plugin This plugin counts disk usage. 0.15 Downstream build view This plug-in allows you to view the full status all the downstream builds so that we can graphically see that everything for this build has been completed successfully. See Downstream build view. 1.6 Jenkins Parameterized Trigger plugin 2.13 Jenkins GIT plugin This plugin integrates GIT with Jenkins. 1.1.16 HTML Publisher plugin This plugin publishes HTML reports. 0.7 next-executions 1.0.4 Performance plugin This plugin integrates JMeter reports and the JUnit reports to Hudson. 1.7 Priority Sorter This plugin allows for the build queue to be sorted based on pre-assigned priorities for each job. 1.3 Jenkins SSH Slaves plugin 0.21 Timestamper 1.2.2 Jenkins Version Column plugin This plugin shows the version of slaves column on Manage Nodes page. 0.2 Jenkins Violations plugin This plugin does reports on checkstyle, csslint, pmd, cpd, fxcop, pylint, jcReport, and findbugs violations. 0.7.10 java.lang.IllegalArgumentException with TMP Cleaner Plugin after Jenkins update to version 1.449 Key: JENKINS-12521 URL: https://issues.jenkins-ci.org/browse/JENKINS-12521 Project: Jenkins Issue Type: Bug Components: plugin Affects Versions: current Environment: Jenkins 1.449, Tmp Cleaner Plugin 1.1 Reporter: Jürgen Prechtl Priority: Minor Labels: jenkins, plugin After Jenkins update to version 1.449 Jenkins throws java.lang.IllegalArgumentException and does not start. The problem does not exist until version 1.448. The issue affects Tmp Cleaner Plugin 1.0 and 1.1 (i've tested those two versions). Here is the complete logfile entry: Exception in thread main java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at Main._main(Main.java:273) at Main.main(Main.java:98) Caused by: java.lang.IllegalArgumentException: Multiple command line argument specified:
[JIRA] (JENKINS-13046) Field for additional options for Xvfb
[ https://issues.jenkins-ci.org/browse/JENKINS-13046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160136#comment-160136 ] SCM/JIRA link daemon commented on JENKINS-13046: Code changed in jenkins User: zregvart Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/config.jelly src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/help-additionalOptions.html http://jenkins-ci.org/commit/xvfb-plugin/8b6ee550848dfb53aaebdd685268619470ab9330 Log: JENKINS-13046: Field for additional options for Xvfb https://issues.jenkins-ci.org/browse/JENKINS-13046 Field for additional options for Xvfb - Key: JENKINS-13046 URL: https://issues.jenkins-ci.org/browse/JENKINS-13046 Project: Jenkins Issue Type: New Feature Components: xvfb Affects Versions: current Reporter: Shein Alexey Assignee: zregvart Hello! First, thanks for the awesome plugin! But I need some more options when running Xvfb, could you please add field so Xvfb can be run with some custom options? Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13048) dropdown-viewstabbar: cannot save checkbox 'Show Job Counts'
Bruno Marti created JENKINS-13048: - Summary: dropdown-viewstabbar: cannot save checkbox 'Show Job Counts' Key: JENKINS-13048 URL: https://issues.jenkins-ci.org/browse/JENKINS-13048 Project: Jenkins Issue Type: Bug Components: dropdown-viewstabbar Affects Versions: current Environment: jenkins 1.454 Reporter: Bruno Marti Assignee: jieryn Attachments: dropdown-viewstabbar.jpg selected checkbox 'Show Job Counts' for Views Tab Bar in general configure screen wont be saved. It is always un-checked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13046) Field for additional options for Xvfb
[ https://issues.jenkins-ci.org/browse/JENKINS-13046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zregvart resolved JENKINS-13046. Resolution: Fixed Field for additional options for Xvfb - Key: JENKINS-13046 URL: https://issues.jenkins-ci.org/browse/JENKINS-13046 Project: Jenkins Issue Type: New Feature Components: xvfb Affects Versions: current Reporter: Shein Alexey Assignee: zregvart Hello! First, thanks for the awesome plugin! But I need some more options when running Xvfb, could you please add field so Xvfb can be run with some custom options? Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13037) TestLink Plugin with jUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160137#comment-160137 ] Bogdan Girbea commented on JENKINS-13037: - Ok... It might be that i got this wrong. But on previous versions of the plugin when a test case throwed an error so did the test link report. With the new 3.1 version an error isn't considered as a fail so the test is marked as passed. Is this to be the normal behaviour? Thank you! Bogdan TestLink Plugin with jUnit -- Key: JENKINS-13037 URL: https://issues.jenkins-ci.org/browse/JENKINS-13037 Project: Jenkins Issue Type: Bug Components: junit, testlink Affects Versions: current Environment: Ubuntu 10.04 Reporter: Bogdan Girbea Assignee: Bruno P. Kinoshita Labels: jenkins Attachments: Screenshot.png Hello I am using the 3.1 testlink plugin. I am running a test class, with 4 tests using JUnit 4.8.One of the 4 tests throws an error and still the testlink report marks the test class as passed. If needed i can attach the configurations and/or the results.. Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12979) can not upload file to filestore in collabnet teamforge
[ https://issues.jenkins-ci.org/browse/JENKINS-12979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Haubold closed JENKINS-12979. -- Assignee: Jens Haubold (was: whsu) Resolution: Not A Defect Meanwhile i find that this relates to new Teamforge 6.1.1.0 Version which have a more granular permission matrix on file releases. The Uploader was not able to delete old version first because the used user has no delete permission. This look like a bug because there was no log you find that permission is missing and job says OK including the promotion!! Would be nice to have a more detailed feedback from promotion in the future. can not upload file to filestore in collabnet teamforge --- Key: JENKINS-12979 URL: https://issues.jenkins-ci.org/browse/JENKINS-12979 Project: Jenkins Issue Type: Bug Components: collabnet Affects Versions: current Environment: - HP-UX 11.31 - Java 1.6 - tomcat 7.0.21 Reporter: Jens Haubold Assignee: Jens Haubold Attachments: catalina.out The file release upload to collabnet temaforge does not work. Think the root cause it the TeamForgeShareDescriptor exception (see attached file). i use promoted build 2.4 and Collabnet 1.1.6 BR and thx Jens -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12002) NPE when saving global config
[
https://issues.jenkins-ci.org/browse/JENKINS-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160141#comment-160141
]
sogabe commented on JENKINS-12002:
--
ndeloof has already fixed this.
See
https://github.com/jenkinsci/maven-repo-cleaner-plugin/commit/90d596ffe1489dfdccab072659c41ca9aa1b2b58
NPE when saving global config
-
Key: JENKINS-12002
URL: https://issues.jenkins-ci.org/browse/JENKINS-12002
Project: Jenkins
Issue Type: Bug
Components: maven-repo-cleaner
Environment: Jenkins 1.442
Winstone
Reporter: Christopher Orr
lpe in IRC reported this stack trace when saving the global job configuration.
The Schedule field was empty. He said adding a space to the Schedule field
fixed the problem.
{noformat}
Status Code: 500
Exception:
Stacktrace:
java.lang.NullPointerException
at
org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty$DescriptorImpl.configure(MavenRepoCleanerProperty.java:99)
at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2560)
at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2523)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:104)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12002) NPE when saving global config
[
https://issues.jenkins-ci.org/browse/JENKINS-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sogabe resolved JENKINS-12002.
--
Resolution: Duplicate
NPE when saving global config
-
Key: JENKINS-12002
URL: https://issues.jenkins-ci.org/browse/JENKINS-12002
Project: Jenkins
Issue Type: Bug
Components: maven-repo-cleaner
Environment: Jenkins 1.442
Winstone
Reporter: Christopher Orr
lpe in IRC reported this stack trace when saving the global job configuration.
The Schedule field was empty. He said adding a space to the Schedule field
fixed the problem.
{noformat}
Status Code: 500
Exception:
Stacktrace:
java.lang.NullPointerException
at
org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty$DescriptorImpl.configure(MavenRepoCleanerProperty.java:99)
at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2560)
at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2523)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
at
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:104)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11859) java.io.IOException: Stream closed when monitoring a jenkins job build number
[
https://issues.jenkins-ci.org/browse/JENKINS-11859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160142#comment-160142
]
Oliver Walsh commented on JENKINS-11859:
Working with jenkins 1.452 urltrigger 0.14.
Thanks,
Ollie
java.io.IOException: Stream closed when monitoring a jenkins job build
number
---
Key: JENKINS-11859
URL: https://issues.jenkins-ci.org/browse/JENKINS-11859
Project: Jenkins
Issue Type: Bug
Components: urltrigger, xtrigger
Affects Versions: current
Reporter: Oliver Walsh
Assignee: gbois
Priority: Minor
Attachments: config.xml, config.xml
I have a URL trigger on jenkins server A (v1.439) setup to monitor the build
number of job on jenkins server B (v1.437).
This is the URL trigger log:
{noformat}
Polling started on Nov 24, 2011 9:46:30 AM
Invoking the url:
http://jenkinsB/job/somejob/lastSuccessfulBuild/buildNumber
Inspecting the content
The line '124' matches the pattern '[0-9]+'
[ERROR] - SEVERE - Polling error java.io.IOException: Stream closed
{noformat}
This is the response header for the url when viewing it in chrome debugger:
{noformat}
HTTP/1.1 200 OK
Server: Winstone Servlet Engine v0.9.10
Content-Type: text/plain;charset=US-ASCII
Connection: Close
Date: Thu, 24 Nov 2011 10:11:31 GMT
X-Powered-By: Servlet/2.5 (Winstone/0.9.10)
{noformat}
I can workaround this by using the api url to fetch the build number
http://jenkinsB/job/somejob/lastSuccessfulBuild/api/xml?xpath=string(*/number)
which does not close the connection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11859) java.io.IOException: Stream closed when monitoring a jenkins job build number
[
https://issues.jenkins-ci.org/browse/JENKINS-11859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Walsh closed JENKINS-11859.
--
java.io.IOException: Stream closed when monitoring a jenkins job build
number
---
Key: JENKINS-11859
URL: https://issues.jenkins-ci.org/browse/JENKINS-11859
Project: Jenkins
Issue Type: Bug
Components: urltrigger, xtrigger
Affects Versions: current
Reporter: Oliver Walsh
Assignee: gbois
Priority: Minor
Attachments: config.xml, config.xml
I have a URL trigger on jenkins server A (v1.439) setup to monitor the build
number of job on jenkins server B (v1.437).
This is the URL trigger log:
{noformat}
Polling started on Nov 24, 2011 9:46:30 AM
Invoking the url:
http://jenkinsB/job/somejob/lastSuccessfulBuild/buildNumber
Inspecting the content
The line '124' matches the pattern '[0-9]+'
[ERROR] - SEVERE - Polling error java.io.IOException: Stream closed
{noformat}
This is the response header for the url when viewing it in chrome debugger:
{noformat}
HTTP/1.1 200 OK
Server: Winstone Servlet Engine v0.9.10
Content-Type: text/plain;charset=US-ASCII
Connection: Close
Date: Thu, 24 Nov 2011 10:11:31 GMT
X-Powered-By: Servlet/2.5 (Winstone/0.9.10)
{noformat}
I can workaround this by using the api url to fetch the build number
http://jenkinsB/job/somejob/lastSuccessfulBuild/api/xml?xpath=string(*/number)
which does not close the connection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13048) dropdown-viewstabbar: cannot save checkbox 'Show Job Counts'
[ https://issues.jenkins-ci.org/browse/JENKINS-13048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160143#comment-160143 ] jieryn commented on JENKINS-13048: -- Yes, this is a bug. I will try to get to it ASAP. dropdown-viewstabbar: cannot save checkbox 'Show Job Counts' Key: JENKINS-13048 URL: https://issues.jenkins-ci.org/browse/JENKINS-13048 Project: Jenkins Issue Type: Bug Components: dropdown-viewstabbar Affects Versions: current Environment: jenkins 1.454 Reporter: Bruno Marti Assignee: jieryn Attachments: dropdown-viewstabbar.jpg selected checkbox 'Show Job Counts' for Views Tab Bar in general configure screen wont be saved. It is always un-checked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13037) TestLink Plugin with jUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160144#comment-160144 ] Bruno P. Kinoshita commented on JENKINS-13037: -- Hi Bogdan, Before 3.1, the plug-in had its own JUnit parser. Now we've switched to Jenkins internal JUnit parser (it's in Jenkins core). This is a bug :-) nice catch. I'll have a look now to see how to fix it. Many thanks! Bruno TestLink Plugin with jUnit -- Key: JENKINS-13037 URL: https://issues.jenkins-ci.org/browse/JENKINS-13037 Project: Jenkins Issue Type: Bug Components: junit, testlink Affects Versions: current Environment: Ubuntu 10.04 Reporter: Bogdan Girbea Assignee: Bruno P. Kinoshita Labels: jenkins Attachments: Screenshot.png Hello I am using the 3.1 testlink plugin. I am running a test class, with 4 tests using JUnit 4.8.One of the 4 tests throws an error and still the testlink report marks the test class as passed. If needed i can attach the configurations and/or the results.. Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12679) Matrix-Build Console Links to Hudson instead of Jenkins
[ https://issues.jenkins-ci.org/browse/JENKINS-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160145#comment-160145 ] Alex Lehmann commented on JENKINS-12679: some links are created based on the request, some use the base url if it is present (there are two methods in the Jenkins class to get a base url) Matrix-Build Console Links to Hudson instead of Jenkins --- Key: JENKINS-12679 URL: https://issues.jenkins-ci.org/browse/JENKINS-12679 Project: Jenkins Issue Type: Bug Components: matrix Affects Versions: current Reporter: Daniel Schaarschmidt Labels: console, matrix Fix For: current I have configured a Matrix-Build using multiple slave nodes. The parent console output contains the following: Löse OS11.4-64 aus OS11.4-64 beendet mit Ergebnis SUCCESS Löse OS11.1-32 aus OS11.1-32 beendet mit Ergebnis SUCCESS Finished: SUCCESS The Labels OSS11.4-64 and OS11.1-32 are links, but instead of pointing to http://myserver/jenkins/job/myjob/label=OS11.4-64/ they link to http://myserver/hudson/job/myjob/label=OS11.4-64/ Even better would be a direct link to the corresponding console log:http://myserver/jenkins/job/myjob/6/label=OS11.1-32/console -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13027) Perforce plugin will sometimes set an incorrect workspace view
[ https://issues.jenkins-ci.org/browse/JENKINS-13027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160146#comment-160146 ] Richard Taylor commented on JENKINS-13027: -- Hi Rob, Thanks for getting back to me. It's actually failed again over the weekend. The issue appears to be orrucing every 1 to 2 days. I think a debug build is probably the best option as it looks like a strange problem. There is some info about the recient builds. We have a pool of 2 machines gbwwsrunbld08 and gbwwsrunbld09 for building packages. I got everything working on Friday and both machines build successful packages. The recient run of build is as follows. Failed #56 19 sec gbwwsrunbld08 Failed #55 32 sec gbwwsrunbld08 Failed #54 1 min 45 secgbwwsrunbld08 Success #53 13 min gbwwsrunbld09 Success #52 9 min 35 secgbwwsrunbld08 Success #51 6 min 3 sec gbwwsrunbld09 Success #50 6 min 11 secgbwwsrunbld08 Success #49 7 min 52 secgbwwsrunbld09 The parameters as recorded on the build summary page are the same for all builds. CHANGELIST = now BRANCH = branches/evo11dx11 SLAVE_LABEL = evo11release I've verified these against the build logs for the above builds and all params are present and correct as environment variables. From the build log of #54 we see this 21:01:35 Using remote perforce client: jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ c:\\program files\\perforce\\p4.exe workspace -o jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ c:\\program files\\perforce\\p4.exe login -p 21:01:35 [evo11main] $ c:\\program files\\perforce\\p4.exe -P 831EC39454600F1AF16985DE3AD2AFCD workspace -o jenkins_gbwwsrunbld08_evo11main 21:01:35 Changing P4 Client View from: 21:01:35 //depot/evolution/evo11/branches/evo11dx11/... //jenkins_gbwwsrunbld08_evo11main/... 21:01:35-//depot/evolution/evo11/branches/evo11dx11/MS3/mb //jenkins_gbwwsrunbld08_evo11main/MS3/mb 21:01:35-//depot/evolution/evo11/branches/evo11dx11/MS3/pds //jenkins_gbwwsrunbld08_evo11main/MS3/pds 21:01:35-//depot/evolution/evo11/branches/evo11dx11/MS3/ma //jenkins_gbwwsrunbld08_evo11main/MS3/ma 21:01:35-//depot/evolution/evo11/branches/evo11dx11/MS3/ZTL //jenkins_gbwwsrunbld08_evo11main/MS3/ZTL 21:01:35//depot/evolution/evo11/external/3rdParty/... //jenkins_gbwwsrunbld08_evo11main/3rdParty/... 21:01:35//depot/evolution/evo11/external/Platform/... //jenkins_gbwwsrunbld08_evo11main/Platform/... 21:01:35//depot/evolution/evo11/external/WWS/... //jenkins_gbwwsrunbld08_evo11main/WWS/... 21:01:35 -//depot/evolution/evo11/external/WWS/ATG/1.33.0/ATGTools/UnitTests/... //jenkins_gbwwsrunbld08_evo11main/WWS/ATG/1.33.0/ATGTools/UnitTests/... 21:01:35 21:01:35 Changing P4 Client View to: 21:01:35//depot/evolution/evo11/external/3rdParty/... //jenkins_gbwwsrunbld08_evo11main/3rdParty/... 21:01:35//depot/evolution/evo11/external/Platform/... //jenkins_gbwwsrunbld08_evo11main/Platform/... 21:01:35//depot/evolution/evo11/external/WWS/... //jenkins_gbwwsrunbld08_evo11main/WWS/... 21:01:35 -//depot/evolution/evo11/external/WWS/ATG/1.33.0/ATGTools/UnitTests/... //jenkins_gbwwsrunbld08_evo11main/WWS/ATG/1.33.0/ATGTools/UnitTests/... 21:01:35 Saving modified client jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ c:\\program files\\perforce\\p4.exe -P 831EC39454600F1AF16985DE3AD2AFCD -s client -i 21:01:48 Last build changeset: 9913 21:01:48 [evo11main] $ c:\\program files\\perforce\\p4.exe -P 831EC39454600F1AF16985DE3AD2AFCD -s changes -s submitted -m 1 //jenkins_gbwwsrunbld08_evo11main/...@now 21:01:49 [evo11main] $ c:\\program files\\perforce\\p4.exe -P 831EC39454600F1AF16985DE3AD2AFCD -s changes -s submitted //jenkins_gbwwsrunbld08_evo11main/...@9914,@9930 21:01:49 [evo11main] $ c:\\program files\\perforce\\p4.exe -P 831EC39454600F1AF16985DE3AD2AFCD describe -s 9930 21:01:49 [evo11main] $ c:\\program files\\perforce\\p4.exe -P 831EC39454600F1AF16985DE3AD2AFCD -G where //... 21:01:50 Sync'ing workspace to label now. 21:01:50 [evo11main] $ c:\\program files\\perforce\\p4.exe -P 831EC39454600F1AF16985DE3AD2AFCD -s sync //jenkins_gbwwsrunbld08_evo11main/...@now 21:03:19 Sync complete, took 89265 ms The failed builds after this then continue to update the workspace and the client view is left in the broken state. 21:01:35 Using remote perforce client: jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ c:\\program files\\perforce\\p4.exe workspace -o jenkins_gbwwsrunbld08_evo11main 21:01:35 [evo11main] $ c:\\program files\\perforce\\p4.exe login -p 21:01:35 [evo11main] $ c:\\program files\\perforce\\p4.exe -P 831EC39454600F1AF16985DE3AD2AFCD workspace -o jenkins_gbwwsrunbld08_evo11main 21:01:35 Last build changeset: 9930 21:01:35 [evo11main] $ c:\\program
[JIRA] (JENKINS-12820) Unable to start Jenkins Service in Windows 7 Slave machine
[
https://issues.jenkins-ci.org/browse/JENKINS-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160147#comment-160147
]
Naga Venkatesh Gowru commented on JENKINS-12820:
We have solved the issue. To configure Windows 7 PC as Slave in jenkins,
for the first time it needs to be connected to master through the launch method
Launch slave agents via java web start after that if it is necessary we can
reconfigure the connection through launch method Windows slave as a Windows
Service.
Step by Step procedure to configure Windows 7 as Slave:
===
In Master PC:
1.Open jenkins home page in browser, Manage Jenkins-Configure System
2.Set Jenkins URL as http://Master_PC_name:8080/;
3.Create a new node(Slave node)
4.Configure the launch method as Lauch slave agents via java web start. Save
the configuration
In Slave PC:
1.Open the URL http://Master_PC_name:8080/ through a browser in Slave PC.
2.Go to the newly created slave node, Click on launch button which is available
there
3.It will connect slave to master PC. A pop up window will be visible with a
message as Connected.
Now a Master Slave connection has established, if slave needs to be connected
through the launch method Windows slave as a Windows Service, then continue
from the above step 3. In that pop up window click File- Install as Windows
Service. Now jenkins service has installed as windows service. Now in Master PC
reconfigure launch method as Windows slave as a Windows Service and give
log in credentials. here after connection will be through windows service
Unable to start Jenkins Service in Windows 7 Slave machine
--
Key: JENKINS-12820
URL: https://issues.jenkins-ci.org/browse/JENKINS-12820
Project: Jenkins
Issue Type: Bug
Components: master-slave
Affects Versions: current
Environment: Master: Windows XP (or) Windows 7
Slave: Windows 7
Jenkins 1.432
Reporter: Naga Venkatesh Gowru
Priority: Blocker
Launch Method: control this Windows slave as Windows Service
==
When I try to establish Master (XP) and Slave (Windows 7) connection, I saw
the below error
ERROR: Access is denied. See
http://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM
for more information about how to resolve this.
org.jinterop.dcom.common.JIException: Access is denied, please check whether
the [domain-username-password] are correct. Also, if not already done please
check the GETTING STARTED and FAQ sections in readme.htm. They provide
information on how to correctly configure the Windows machine for DCOM
access, so as to avoid such exceptions. [0x0005]
at
org.jinterop.winreg.smb.JIWinRegStub.winreg_CreateKey(JIWinRegStub.java:297)
at org.jinterop.dcom.core.JIComServer.initialise(JIComServer.java:480)
at org.jinterop.dcom.core.JIComServer.init(JIComServer.java:427)
... ...
I browsed the web and found a work around for this, I did the below steps
1.Launch 'regedit.exe' as 'Administrator'
2.Find the following registry key:
'HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}'
3.Right click and select 'Permissions'
4.Change owner to administrators group.
5.Change permissions for administrators group. Grant Full Control.
6.Change owner back to TrustedInstaller (user is NT
Service\TrustedInstaller)
7.Restart Remote Registry Service
Now the above mentioned error got rectified and connection has established,
but Master is unable to start the Jenkins slave service.
Connecting to X
Checking if Java exists
java full version 1.4.2_13-b06
Copying slave.jar
Starting the service
Jenkins in Master hangs here, After this nothing is being displayed in the
log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13049) Expand environment variables in definition of CMake generator
Anthony Berent created JENKINS-13049:
Summary: Expand environment variables in definition of CMake
generator
Key: JENKINS-13049
URL: https://issues.jenkins-ci.org/browse/JENKINS-13049
Project: Jenkins
Issue Type: Improvement
Components: cmakebuilder
Affects Versions: current
Reporter: Anthony Berent
Priority: Minor
Expand environment variables in definition of CMake generator, so that one can
set the generator to the value of an environment variable.
Justification:
I have a number of Jenkins jobs using CMake that are multi-configuration
projects have to build on both Windows and Linux. Because the environments are
different I have to use different CMake generators on Windows and Linux (CMake
doesn't support Unix Makefiles on Windows or Visual Studio 9 2008 on
Linux). At the moment the only way to do this is to use conditional build
steps. This means that I have to define everything about the CMake step twice.
This would be much cleaner if I could set an environment variable in the node
configuration (e.g. CMakeDefaultGenerator) and then set the Makefile
Generator entry to ${CMakeDefaultGenerator} in the configuration of the CMake
builder.
Environment variables already work in some of the other configuration fields of
the CMake builder. For example on Windows I am setting my make command to
${Msbuild35Exe} /t:rebuild Project.sln
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Myakushkin reopened JENKINS-12916:
--
Hello, Bruno,
Sorry, I didnt have time to check alpha release, I was in vacation.
Today, I have tried to check assigned test results by test methode name. But
testlink plugin(3.1) didn't find test results in testng-results.xm (Found 0
test result(s).)
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13050) No feedback when invalid configuration refuses to save
mdp created JENKINS-13050: - Summary: No feedback when invalid configuration refuses to save Key: JENKINS-13050 URL: https://issues.jenkins-ci.org/browse/JENKINS-13050 Project: Jenkins Issue Type: Bug Components: periodicbackup Environment: Jenkins 1.454 Periodic backup plugin 1.1 Reporter: mdp Priority: Minor When trying to configure backup there is no feedback that 0 is not a valid value for Maximum backups in location, the save button just refuses to work with no message. (BTW: it could be nice if there was a valid value for this field that meant 'unlimited'.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160151#comment-160151
]
Bruno P. Kinoshita commented on JENKINS-12916:
--
Hi Nikolay! Hope you enjoyed your vacations :-)
Could you attach the testng-results.xml file as well, please? And maybe a
sample test case in TestLink.
That would be helpful.
Thanks for your feedback
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi, testlink_settings.png
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160152#comment-160152
]
Nikolay Myakushkin commented on JENKINS-12916:
--
All tests in testlink have Custom Fileds : Java Class, Automated, Test Methode
Name.
I think that I'M working wrong with Custom Fileds?
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi, testlink_settings.png
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Myakushkin updated JENKINS-12916:
-
Attachment: testlink_settings.png
My Testlink settings
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi, testlink_settings.png
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160149#comment-160149
]
Nikolay Myakushkin edited comment on JENKINS-12916 at 3/12/12 3:06 PM:
---
Hello, Bruno,
Sorry, I didnt have time to check alpha release, I was in vacation.
Today, I have tried to check assigned test results by test methode name. But
testlink plugin(3.1) didn't find test results in testng-results.xm (Found 0
test result(s).)
Below is console log.
Preparing TestLink client API.
Using TestLink URL: http://localhost:8000/lib/api/xmlrpc.php
Found 25 automated test cases in TestLink.
Sorting automated test cases by TestLink test plan execution order.
Executing single Build Steps.
Executing iterative Build Steps.
Looking for the test results of TestLink test cases.
Looking for test results in TestNG suites.
Found 0 test result(s).
TestNG Reports Processing: START
Looking for TestNG results report in workspace using pattern:
**/target/surefire-reports/testng-results.xml
Saving reports...
Processing
'C:\dev\JENKINS_HOME\jobs\Manager\builds\2012-03-12_17-52-36\testng\testng-results.xml'
TestNG Reports Processing: FINISH
was (Author: anm110c):
Hello, Bruno,
Sorry, I didnt have time to check alpha release, I was in vacation.
Today, I have tried to check assigned test results by test methode name. But
testlink plugin(3.1) didn't find test results in testng-results.xm (Found 0
test result(s).)
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13047) Add a class name + method name result seeker
[ https://issues.jenkins-ci.org/browse/JENKINS-13047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno P. Kinoshita resolved JENKINS-13047. -- Resolution: Fixed The pull request has been merged. Unit tests were written. The class name was renamed to match with the TestNG equivalent. Thanks! Add a class name + method name result seeker Key: JENKINS-13047 URL: https://issues.jenkins-ci.org/browse/JENKINS-13047 Project: Jenkins Issue Type: Improvement Components: testlink Affects Versions: current Reporter: Michael van der Westhuizen Assignee: Bruno P. Kinoshita Currently the TestLink plugging can match test results based on JUnit suite names, JUnit class names and JUnit test names, but only in isolation. In our use case, it's the class name with the method name that makes the test unique. The following pull request adds a seeker to meet this requirement: https://github.com/jenkinsci/testlink-plugin/pull/4. In future, I think we should create one flexible JUnit seeker, that matches a (specified) combination of package name, class name and method name (as appropriate). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9117) Jenkins hangs in the shutdown mode after thinBackup is triggered
[ https://issues.jenkins-ci.org/browse/JENKINS-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160154#comment-160154 ] Frank Merrow commented on JENKINS-9117: --- Windows . . . And yes! It took a few minutes, but if I kept hitting refresh eventually the shutdown message went away!!! It was the first time I had seen this, but then typically I don't hit refresh . . . So . . . I get where you are coming from wanting a stable system to backup . . . but this seems like a pretty heavy handed way to get it. It is a pretty shocking thing for a user to see who isn't in the know . . . and if they have the ability, they are likely to cancel on you anyway. Plus on my almost nothing Jenkins the backup took 1 minute or so . . . on our big production Jenkins with all the data and history, it will be interesting to see how long it lasts . . . it could be awhile. Clearly this is upsetting (to users) enough that it will have to be done at night, but we are a world wide 7/24 operation. I have a smaller community to upset in Hyderabad than I do in San Diego, but it is hard to select a backup time that won't alarm one of them. Plus night time is the time for big builds . . . the multi-hour things nobody want to do during the day . . . I am reluctant to take a big chunk of time out of that already busy schedule . . . no easy solutions here. It might be interesting to see if KK would add a new mode . . . shutdown like in that tables/files don't change, but instead of a big red banner saying shutdown, a (say) blue banner saying backup in progress . . . something to clue the user into the real situation. Thanks for looking into this . . . sorry the solution is I just didn't understand . . . Frank Jenkins hangs in the shutdown mode after thinBackup is triggered Key: JENKINS-9117 URL: https://issues.jenkins-ci.org/browse/JENKINS-9117 Project: Jenkins Issue Type: Bug Components: thinBackup Reporter: Thomas Fürer Assignee: Thomas Fürer Attachments: All Jenkins Logs.txt thinBackup triggers a backup job and did not return from the shutdown mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160155#comment-160155
]
Bruno P. Kinoshita commented on JENKINS-12916:
--
It depends on the way you're using them :-)
I think it will help if I explain how the TestNG method name strategy works.
This strategy works by parsing the TestNG XML files, concatenating
package.classname#methodname, and then matching against each automated
test case from Testlink.
It means that in TestLink, your test case would have a custom field value (the
key custom field) equals to something like
com.example.MyAutomatedTest#testSomething
Let me know if that helps :-)
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi, testlink_settings.png
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13047) Add a class name + method name result seeker
[ https://issues.jenkins-ci.org/browse/JENKINS-13047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160157#comment-160157 ] SCM/JIRA link daemon commented on JENKINS-13047: Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/hudson/plugins/testlink/result/JUnitCaseMethodNameResultSeeker.java src/main/java/hudson/plugins/testlink/result/JUnitMethodNameResultSeeker.java src/main/resources/hudson/plugins/testlink/result/JUnitCaseMethodNameResultSeeker/config.jelly src/main/resources/hudson/plugins/testlink/result/JUnitMethodNameResultSeeker/config.jelly src/test/java/hudson/plugins/testlink/result/TestJUnitMethodNameResultSeeker.java src/test/resources/hudson/plugins/testlink/result/junit/methodname/TEST-WithManyMethods.xml http://jenkins-ci.org/commit/testlink-plugin/33ee730bcb3c214c960d7121d7846f6a9f090738 Log: JENKINS-13047 changes to new JUnit method name result seeking strategy Add a class name + method name result seeker Key: JENKINS-13047 URL: https://issues.jenkins-ci.org/browse/JENKINS-13047 Project: Jenkins Issue Type: Improvement Components: testlink Affects Versions: current Reporter: Michael van der Westhuizen Assignee: Bruno P. Kinoshita Currently the TestLink plugging can match test results based on JUnit suite names, JUnit class names and JUnit test names, but only in isolation. In our use case, it's the class name with the method name that makes the test unique. The following pull request adds a seeker to meet this requirement: https://github.com/jenkinsci/testlink-plugin/pull/4. In future, I think we should create one flexible JUnit seeker, that matches a (specified) combination of package name, class name and method name (as appropriate). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13037) TestLink Plugin with jUnit
[ https://issues.jenkins-ci.org/browse/JENKINS-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160156#comment-160156 ] Bruno P. Kinoshita commented on JENKINS-13037: -- Hi againn Bogdan, could you send me the JUnit XML file, if it doesn't contain any sensitive data, please? TestLink Plugin with jUnit -- Key: JENKINS-13037 URL: https://issues.jenkins-ci.org/browse/JENKINS-13037 Project: Jenkins Issue Type: Bug Components: testlink Affects Versions: current Environment: Ubuntu 10.04 Reporter: Bogdan Girbea Assignee: Bruno P. Kinoshita Labels: jenkins Attachments: Screenshot.png Hello I am using the 3.1 testlink plugin. I am running a test class, with 4 tests using JUnit 4.8.One of the 4 tests throws an error and still the testlink report marks the test class as passed. If needed i can attach the configurations and/or the results.. Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160158#comment-160158
]
Nikolay Myakushkin commented on JENKINS-12916:
--
Sure Bruno, I have attached testng-results.xml, and
testng-resultstestlinkwithsubs.xml for importing to testlink
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi, testlink_settings.png
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Myakushkin updated JENKINS-12916:
-
Attachment: testng-resultstestlinkwithsubs.xml
testng-results.xml
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi, testlink_settings.png,
testng-results.xml, testng-resultstestlinkwithsubs.xml
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160161#comment-160161
]
Bruno P. Kinoshita commented on JENKINS-12916:
--
Don't mention it Nikolay, thanks for the compliments, I hope the plug-in can
help you to automate your tests with Jenkins, and keep managing them in
TestLink ;-)
Regarding the tutorial, it was due to a bad time management of my part. I
decided to refactor the code to create the result seeking strategy (before
that, the plug-in was using pure OO, with inheritance, and the code was very
tied). My first idea was to refactor, fix bugs, write tests, update Wiki and
tutorial, and then release it. But I ended having to postpone the documentation
step for after the release.
I'll update the docs throughout this week, so by Thursday or Friday we will
have the Wiki and the Tutorial updated.
Thank you again! I'll close this issue, but feel free to comment here, reopen,
or e-mail me directly if you have any further issues.
Cheers, Bruno
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi, testlink_settings.png,
testng-results.xml, testng-resultstestlinkwithsubs.xml
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12916) Can't assign testng results to the testlink by Test Methode Name(only by Java Class )
[
https://issues.jenkins-ci.org/browse/JENKINS-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno P. Kinoshita resolved JENKINS-12916.
--
Resolution: Not A Defect
Can't assign testng results to the testlink by Test Methode Name(only by
Java Class )
--
Key: JENKINS-12916
URL: https://issues.jenkins-ci.org/browse/JENKINS-12916
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: WinXP: Jenkins (org.jenkins-ci.main:jenkins-war:1.449),
Jenkins TestLink Plugin (3.0.2), TestNG Lib (6.4),TestLink 1.9.3 (Prague)
Reporter: Nikolay Myakushkin
Assignee: Bruno P. Kinoshita
Attachments: testlink-3.1-alpha2.hpi, testlink_settings.png,
testng-results.xml, testng-resultstestlinkwithsubs.xml
I'm using testlink plugin for my project. It is very useful and easy to use.
Thanks to the authors. But I have some suggestion.
1.As I understand, test results from testng-results.xml are mapped to the
tests only by Java Class Custom field. Do I have any way to map them by
test-methode?
2.And one more question: I'm using dataproviders in my tests. Do I have any
mechanism to map the pairs (test-methode,dataprovider Object[]) to the tests.
I mean if I have
@DataProvider(name = test1)
public Object[][] createData1() {
return new Object[][] {
{ Cedric, new Integer(36) },
{ Anne, new Integer(37)},
};
}
//This test method declares that its data should be supplied by the Data
Provider
//named test1
@Test(dataProvider = test1)
public void verifyData1(String n1, Integer n2) {
AssertJUnit.assertTrue( n1.equals(Anne));
}
And I have 2 test in Testlink: 1. for { Cedric, new Integer(36) }, 2. for
{ Anne, new Integer(37)}.
And the results should map to each test
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13027) Perforce plugin will sometimes set an incorrect workspace view
[
https://issues.jenkins-ci.org/browse/JENKINS-13027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160163#comment-160163
]
Rob Petti commented on JENKINS-13027:
-
The perforce plugin isn't involved in slave selection, so I'm not sure how that
would be the issue. The plugin simply uses whatever jenkins supplies it with.
What are you specifying for your Workspace (client) name and Client name
format for slaves options?
Perforce plugin will sometimes set an incorrect workspace view
--
Key: JENKINS-13027
URL: https://issues.jenkins-ci.org/browse/JENKINS-13027
Project: Jenkins
Issue Type: Bug
Components: perforce
Affects Versions: current
Environment: Jenkins Master 1.454 OS Windows Server 2008 SP2
Jenkins Slave 2.12 OS Windows Server 2008 R2
Reporter: Richard Taylor
Assignee: Rob Petti
Fix For: current
Perforce plugin will sometimes set an incorrect workspace view.
The job has perforce Client View Type set to View Map with the following
details
//depot/evolution/evo11/${BRANCH}/... //workspace-name/...
-//depot/evolution/evo11/${BRANCH}/MS3/mb //workspace-name/MS3/mb
-//depot/evolution/evo11/${BRANCH}/MS3/pds //workspace-name/MS3/pds
-//depot/evolution/evo11/${BRANCH}/MS3/ma //workspace-name/MS3/ma
-//depot/evolution/evo11/${BRANCH}/MS3/ZTL //workspace-name/MS3/ZTL
//depot/evolution/evo11/external/3rdParty/... //workspace-name/3rdParty/...
//depot/evolution/evo11/external/Platform/... //workspace-name/Platform/...
//depot/evolution/evo11/external/WWS/... //workspace-name/WWS/...
-//depot/evolution/evo11/external/WWS/ATG/1.33.0/ATGTools/UnitTests/...
//workspace-name/WWS/ATG/1.33.0/ATGTools/UnitTests/...
The ${BRANCH} is set as a job parameter but the purposes of our current use
case it is always the same default value.
The job is set to run on a small pool of slaves with label. This pool of
slaved is used for building packages from diferent branches.
We get occasional build failures due to perforce incorrectly setting the
workspace view. These errors can only be fixed by a clean and sync. As a full
clean and sync takes 2 hours this is a significant issue.
- Jenkins build log --
21:02:27 Started by timer
21:02:27 Building remotely on gbwwsrunbld08 in workspace
c:\jenkins\workspace\evo11main
21:02:27 Using remote perforce client: jenkins_gbwwsrunbld08_evo11main
21:02:27 [evo11main] $ c:\\program files\\perforce\\p4.exe workspace -o
jenkins_gbwwsrunbld08_evo11main
21:02:27 [evo11main] $ c:\\program files\\perforce\\p4.exe login -p
21:02:27 [evo11main] $ c:\\program files\\perforce\\p4.exe -P
831EC39454600F1AF16985DE3AD2AFCD workspace -o jenkins_gbwwsrunbld08_evo11main
21:02:27 Changing P4 Client View from:
21:02:27 //depot/evolution/evo11/branches/evo11dx11/...
//jenkins_gbwwsrunbld08_evo11main/...
21:02:27 -//depot/evolution/evo11/branches/evo11dx11/MS3/mb
//jenkins_gbwwsrunbld08_evo11main/MS3/mb
21:02:27 -//depot/evolution/evo11/branches/evo11dx11/MS3/pds
//jenkins_gbwwsrunbld08_evo11main/MS3/pds
21:02:27 -//depot/evolution/evo11/branches/evo11dx11/MS3/ma
//jenkins_gbwwsrunbld08_evo11main/MS3/ma
21:02:27 -//depot/evolution/evo11/branches/evo11dx11/MS3/ZTL
//jenkins_gbwwsrunbld08_evo11main/MS3/ZTL
21:02:27 //depot/evolution/evo11/external/3rdParty/...
//jenkins_gbwwsrunbld08_evo11main/3rdParty/...
21:02:27 //depot/evolution/evo11/external/Platform/...
//jenkins_gbwwsrunbld08_evo11main/Platform/...
21:02:27 //depot/evolution/evo11/external/WWS/...
//jenkins_gbwwsrunbld08_evo11main/WWS/...
21:02:27
-//depot/evolution/evo11/external/WWS/ATG/1.33.0/ATGTools/UnitTests/...
//jenkins_gbwwsrunbld08_evo11main/WWS/ATG/1.33.0/ATGTools/UnitTests/...
21:02:27
21:02:27 Changing P4 Client View to:
21:02:27//depot/evolution/evo11/external/3rdParty/...
//jenkins_gbwwsrunbld08_evo11main/3rdParty/...
21:02:27//depot/evolution/evo11/external/Platform/...
//jenkins_gbwwsrunbld08_evo11main/Platform/...
21:02:27//depot/evolution/evo11/external/WWS/...
//jenkins_gbwwsrunbld08_evo11main/WWS/...
21:02:27 Saving modified client jenkins_gbwwsrunbld08_evo11main
As you can see perforce has removed the part view which was using the
${BRANCH} parameter and has also remove the final -// line which was not
parameterised.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9117) Jenkins hangs in the shutdown mode after thinBackup is triggered
[ https://issues.jenkins-ci.org/browse/JENKINS-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160164#comment-160164 ] Thomas Fürer commented on JENKINS-9117: --- @frank can I close this issue now? i have removed the shutdown state from the backup. only if you restore the system you need the shutdown mode. Jenkins hangs in the shutdown mode after thinBackup is triggered Key: JENKINS-9117 URL: https://issues.jenkins-ci.org/browse/JENKINS-9117 Project: Jenkins Issue Type: Bug Components: thinBackup Reporter: Thomas Fürer Assignee: Thomas Fürer Attachments: All Jenkins Logs.txt thinBackup triggers a backup job and did not return from the shutdown mode -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6748) Analysis of Checkstyle Warnings per User
[ https://issues.jenkins-ci.org/browse/JENKINS-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160165#comment-160165 ] Martin Hanus commented on JENKINS-6748: --- Hey all, It's been a while since last comment :). I'm quite interested in this issue since we would like to use similar behaviour in our build system. We would like to compare checkstyle violations before and after commit. If it get's increased after commit, we would like to send off emails with notification (same as when build fails). Therefore I would like to check on this issue, if it's going to be developed or it's dead and left behind :). Thanks. Analysis of Checkstyle Warnings per User Key: JENKINS-6748 URL: https://issues.jenkins-ci.org/browse/JENKINS-6748 Project: Jenkins Issue Type: New Feature Components: analysis-core, checkstyle Affects Versions: current Reporter: ahhughes Assignee: Ulli Hafner Priority: Minor Checkstyle warnings generally arise because a developer is running an auto format that is not in sync with a project's standard, or they are choosing not to format. The current checkstyle analysis tend to display where warnings are, but not where they come from. What I would like is to see is a 'Warnings By User' analysis (user is the commit user). Then you can easily see who's IDE is out of whack, or who's being slack - even if that's happens to be me :) Example: h3. Warnings by User * mjackson: 23 warnings * jsmith: 1,634 warnings * jdoe: 432 warning h3. New Warnings by User (build #30) * jsmith: 84 warnings * jdoe: 4 warnings Cheers for listening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12910) SDK Fresh Installation should install ARM EABI v7a system Image
[ https://issues.jenkins-ci.org/browse/JENKINS-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160166#comment-160166 ] Kevin Chow commented on JENKINS-12910: -- Hello Chris, My test machine maybe reset, so when we tried to run the jenkins job. I think this is a known issue as you mentioned.. Is it anyway I could update the jenkins job to download r17-preview instead of sdk r16? Do I need to modify the plugin code to do so? Any advice is more than welcomed. Thanks, Kevin [android] No Android SDK found; let's install it automatically... 03:56:04 Downloading and installing Android SDK from http://dl.google.com/android/android-sdk_r16-macosx.zip 03:56:11 [android] Base SDK installed successfully 03:56:11 [android] Going to install required Android SDK components... 03:56:11 [android] Installing the 'platform-tool,tool' SDK component(s)... 03:56:11 $ /tmp/jenkins/tools/android-sdk/tools/android update sdk -o -u -t platform-tool,tool 03:56:13 Refresh Sources: 03:56:13Fetching https://dl-ssl.google.com/android/repository/addons_list-1.xml .. 03:57:01 $ /tmp/jenkins/tools/android-sdk/tools/android list target 03:57:02 [android] The configured Android platform needs to be installed: android-15 03:57:02It appears that the configured platform is based on Android 4.0 or newer. 03:57:02This requires the 'ARM EABI v7a System Image' package which cannot be automatically installed with SDK Tools r16 or earlier. 03:57:02Please install this component manually via the Android SDK Manager, or upgrade to SDK Tools r17 SDK Fresh Installation should install ARM EABI v7a system Image --- Key: JENKINS-12910 URL: https://issues.jenkins-ci.org/browse/JENKINS-12910 Project: Jenkins Issue Type: New Feature Components: android-emulator Environment: Android 4.0.3 (API 15) Reporter: Kevin Chow Assignee: Christopher Orr When the new SDK is downloaded and installed, it only installs SDK Platform but not ARM EABI v7a System Image. That's why I see this error in the run: [android] Using Android SDK: /tmp/jenkins/tools/android-sdk 14:10:38 [android] Setting hardware properties: 14:10:38 disk.cachePartition.size: 768M 14:10:38 $ /tmp/jenkins/tools/android-sdk/platform-tools/adb start-server 14:10:38 [android] Starting Android emulator 14:10:38 $ /tmp/jenkins/tools/android-sdk/tools/emulator -no-boot-anim -ports 53709,53710 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_160_WXGA800_android-15 -no-snapshot-load -no-snapshot-save -partition-size 768 14:10:39 emulator: ERROR: This AVD's configuration is missing a kernel file!! The workaround is to download and install ARM EABI v7a System Image and re-kick off the Emulator run. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13051) Setting branch name prevents branch from building
Adam Westhusing created JENKINS-13051: - Summary: Setting branch name prevents branch from building Key: JENKINS-13051 URL: https://issues.jenkins-ci.org/browse/JENKINS-13051 Project: Jenkins Issue Type: Bug Components: git Environment: Windows Server 2008 R2 Reporter: Adam Westhusing Assignee: Nicolas De Loof Priority: Critical It appears a bug has been introduced in Git plugin 1.1.16: If I set the branch specifier in the Branches to Build section, I always get the following error. ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The only way I found to resolve this is to get rid of the branch specifier and replace it with **. However, I only want to build a specific branch in our Git repo, so in the meantime I've rolled back to 1.1.15 where this functionality is working just fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13051) Setting branch name prevents branch from building
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Westhusing updated JENKINS-13051: -- Environment: Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16 (was: Windows Server 2008 R2) Setting branch name prevents branch from building - Key: JENKINS-13051 URL: https://issues.jenkins-ci.org/browse/JENKINS-13051 Project: Jenkins Issue Type: Bug Components: git Environment: Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16 Reporter: Adam Westhusing Assignee: Nicolas De Loof Priority: Critical Labels: git, plugin, windows It appears a bug has been introduced in Git plugin 1.1.16: If I set the branch specifier in the Branches to Build section, I always get the following error. ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The only way I found to resolve this is to get rid of the branch specifier and replace it with **. However, I only want to build a specific branch in our Git repo, so in the meantime I've rolled back to 1.1.15 where this functionality is working just fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13051) Setting branch name prevents branch from building
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Westhusing updated JENKINS-13051: -- Environment: Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16, Git version 1.7.9-preview20120201 (was: Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16) Setting branch name prevents branch from building - Key: JENKINS-13051 URL: https://issues.jenkins-ci.org/browse/JENKINS-13051 Project: Jenkins Issue Type: Bug Components: git Environment: Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16, Git version 1.7.9-preview20120201 Reporter: Adam Westhusing Assignee: Nicolas De Loof Priority: Critical Labels: git, plugin, windows It appears a bug has been introduced in Git plugin 1.1.16: If I set the branch specifier in the Branches to Build section, I always get the following error. ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. The only way I found to resolve this is to get rid of the branch specifier and replace it with **. However, I only want to build a specific branch in our Git repo, so in the meantime I've rolled back to 1.1.15 where this functionality is working just fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12986) Block build when downstream project is building and fstrigger problem
[ https://issues.jenkins-ci.org/browse/JENKINS-12986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160169#comment-160169 ] Trevor Baker commented on JENKINS-12986: So after spending some more time with this configuration, I think it is working correctly. When the job is blocked by downstream activity, the trigger doesn't execute since the job that polls via fstrigger is blocked. I'l keep an eye on this, but unless you can see a way that the problem could manifest as described, I think this will get closed as a non-issue. Block build when downstream project is building and fstrigger problem --- Key: JENKINS-12986 URL: https://issues.jenkins-ci.org/browse/JENKINS-12986 Project: Jenkins Issue Type: Bug Components: fstrigger Affects Versions: current Environment: fstrigger 0.27 jenkins 1.451 Reporter: Trevor Baker Assignee: gbois It seems that when you enable Block build when downstream project is building that scheduled polling still occurs. If you use fstrigger and a poll sees a file change when builds are blocked due to running downstream jobs, the timestamp or fingerprint or the file/folder watched still gets updated. This means that once the downstream job completes and the block is removed a new job should be triggered. Currently builds are NOT triggered as the plugin is comparing the contents observed during the blockout to current which are the same. When builds are blocked fstrigger should not update its state used for comparisons. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11975) Switch to QuietMode only for backup process
[ https://issues.jenkins-ci.org/browse/JENKINS-11975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Fürer resolved JENKINS-11975. Resolution: Fixed published with 1.5 Switch to QuietMode only for backup process --- Key: JENKINS-11975 URL: https://issues.jenkins-ci.org/browse/JENKINS-11975 Project: Jenkins Issue Type: Improvement Components: thinBackup Reporter: Thomas Fürer Assignee: Thomas Fürer Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
[ https://issues.jenkins-ci.org/browse/JENKINS-11024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160172#comment-160172 ] S Daigle commented on JENKINS-11024: Is this issue ever going to be resolved? In companies like mine where adding anonymous read access is not an option, and relying on many of the CLI commands, an issue like this limits the things we can do with Jenkins jobs outside the UI. If anyone has a workaround to this, that would be welcome. Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others -- Key: JENKINS-11024 URL: https://issues.jenkins-ci.org/browse/JENKINS-11024 Project: Jenkins Issue Type: Bug Components: cli Environment: CLI Reporter: Timothy Meazell Add keys for authenticated login. Works fine with who-am-i, enable-job, disable-job, delete-job, create-job, but get-job and update-job fail claiming there is no job by that name. The very same command line with enable-job (as well as the others) works fine. Workaround is to see if enable-job fails (which it will if there is no job by that name, which was the point of using get-job), then delete-job and create-job instead of update-job if the job already exists. Note that this workaround causes the loss of job history upon deletion. Diagnostics: % java -jar jenkins/_jenkins-cli.jar -s http://localhost:9090/ -i jenkins/id_rsa get-job trunk-pacman.integration.vdev-regression No such job 'trunk-pacman.integration.vdev-regression' java -jar jenkins-cli.jar get-job args... Dumps the job definition XML to stdout JOB : Name of the job --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the password % java -jar jenkins/_jenkins-cli.jar -s http://localhost:9090/ -i jenkins/id_rsa enable-job trunk-pacman.integration.vdev-regression % echo $? 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12628) Executable file permission not set anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160173#comment-160173 ] SCM/JIRA link daemon commented on JENKINS-12628: Code changed in jenkins User: Michael Clarke Path: pom.xml http://jenkins-ci.org/commit/cvs-plugin/2e658b6f4924d78603034f2209cbc2bd552369fa Log: JENKINS-12628 - Silently continue if system doesn't allow setting permissions Executable file permission not set anymore -- Key: JENKINS-12628 URL: https://issues.jenkins-ci.org/browse/JENKINS-12628 Project: Jenkins Issue Type: Bug Components: cvs Environment: CentOS release 5.7 (affected system, Slave), Windows Server 2003 (Master) Reporter: Marco Borm Assignee: Michael Clarke Fix For: current Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the fact that our compile scripts don't have executable permission bit set anymore. The bit is correctly set on the affected files on cvs server side. cvs plugin 1.6: -rwxrwx--- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release cvs plugin 2.0: -rw-rw-r-- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6748) Analysis of Checkstyle Warnings per User
[ https://issues.jenkins-ci.org/browse/JENKINS-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160174#comment-160174 ] Ulli Hafner commented on JENKINS-6748: -- If I remember correctly two volunteers wanted to dig into that issue but since I didn't hear anything I think there is no progress (there are also some GitHub comments or issues about that problem). Martin, I'm not sure if I misunderstand your use case but it looks much simpler that the original request and is already solved: if you set the new warning count to 0, then all committers participating in that build will become an email on any new warning. This is quite similar to the build failed email due to compile errors: Here you also don't know which commit actually broke the build, all committers get that Email. Analysis of Checkstyle Warnings per User Key: JENKINS-6748 URL: https://issues.jenkins-ci.org/browse/JENKINS-6748 Project: Jenkins Issue Type: New Feature Components: analysis-core, checkstyle Affects Versions: current Reporter: ahhughes Assignee: Ulli Hafner Priority: Minor Checkstyle warnings generally arise because a developer is running an auto format that is not in sync with a project's standard, or they are choosing not to format. The current checkstyle analysis tend to display where warnings are, but not where they come from. What I would like is to see is a 'Warnings By User' analysis (user is the commit user). Then you can easily see who's IDE is out of whack, or who's being slack - even if that's happens to be me :) Example: h3. Warnings by User * mjackson: 23 warnings * jsmith: 1,634 warnings * jdoe: 432 warning h3. New Warnings by User (build #30) * jsmith: 84 warnings * jdoe: 4 warnings Cheers for listening. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page
[
https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sogabe updated JENKINS-12787:
-
Priority: Blocker (was: Major)
change priority to Blocker
LOADING overlay does not go away on the Configure System page
-
Key: JENKINS-12787
URL: https://issues.jenkins-ci.org/browse/JENKINS-12787
Project: Jenkins
Issue Type: Bug
Components: gui
Affects Versions: current
Environment: Jenkins
Reporter: Joshua Davis
Priority: Blocker
Labels: gui, jenkins
After navigating to Manage-Configure System, the LOADING overlay never goes
away. It is impossible to save any configuration changes.
EXPECTED:
* You can save your global configuration.
Here is the stack trace from Chrome's JS console:
{code}
Uncaught TypeError: Object #Object has no method 'findMatchingInput'
(anonymous function)
e.targetUrl hudson-behavior.js:338
registerValidator hudson-behavior.js:343
apply behavior.js:73
(anonymous function) behavior.js:79
Behaviour.applySubtree behavior.js:68
Behaviour.applybehavior.js:54
(anonymous function)behavior.js:49
window.onload
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13053) Jenkins doxygen plugin 0.10 - NoSuchMethodError issue
[ https://issues.jenkins-ci.org/browse/JENKINS-13053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Woong Chul Choi updated JENKINS-13053: -- Summary: Jenkins doxygen plugin 0.10 - NoSuchMethodError issue (was: Jenkins doxygen plugin 0.10) Jenkins doxygen plugin 0.10 - NoSuchMethodError issue - Key: JENKINS-13053 URL: https://issues.jenkins-ci.org/browse/JENKINS-13053 Project: Jenkins Issue Type: Bug Components: doxygen Affects Versions: current Environment: [OS] Windows Server 2008 [WAS] Tomcat 5.5.26 - Jenkins 1.454 - Jenkins doxygen plugin 0.10 (Feb 27, 2012) Reporter: Woong Chul Choi Assignee: gbois Attachments: Doxyfile Hi I installed Jenkins Doxygen Plug-in yesterday. I set up properly but the following error was occured. --- Publishing Doxygen HTML results. FATAL: java.lang.String.isEmpty()Z java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z at hudson.plugins.doxygen.DoxygenDirectoryParser.getDoxygenGeneratedDir(DoxygenDirectoryParser.java:142) at hudson.plugins.doxygen.DoxygenDirectoryParser.retrieveDoxygenDirectoryFromDoxyfile(DoxygenDirectoryParser.java:340) at hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:54) at hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:14) at hudson.FilePath.act(FilePath.java:788) at hudson.FilePath.act(FilePath.java:770) at hudson.plugins.doxygen.DoxygenArchiver._perform(DoxygenArchiver.java:219) at hudson.plugins.doxygen.DoxygenArchiver.perform(DoxygenArchiver.java:176) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) at hudson.model.Run.run(Run.java:1433) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) - I'm not sure but I assume that jenkins is using invalid method name to call via reflection. could you check this out plz? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13053) Jenkins doxygen plugin 0.10
Woong Chul Choi created JENKINS-13053: - Summary: Jenkins doxygen plugin 0.10 Key: JENKINS-13053 URL: https://issues.jenkins-ci.org/browse/JENKINS-13053 Project: Jenkins Issue Type: Bug Components: doxygen Affects Versions: current Environment: [OS] Windows Server 2008 [WAS] Tomcat 5.5.26 - Jenkins 1.454 - Jenkins doxygen plugin 0.10 (Feb 27, 2012) Reporter: Woong Chul Choi Assignee: gbois Attachments: Doxyfile Hi I installed Jenkins Doxygen Plug-in yesterday. I set up properly but the following error was occured. --- Publishing Doxygen HTML results. FATAL: java.lang.String.isEmpty()Z java.lang.NoSuchMethodError: java.lang.String.isEmpty()Z at hudson.plugins.doxygen.DoxygenDirectoryParser.getDoxygenGeneratedDir(DoxygenDirectoryParser.java:142) at hudson.plugins.doxygen.DoxygenDirectoryParser.retrieveDoxygenDirectoryFromDoxyfile(DoxygenDirectoryParser.java:340) at hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:54) at hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:14) at hudson.FilePath.act(FilePath.java:788) at hudson.FilePath.act(FilePath.java:770) at hudson.plugins.doxygen.DoxygenArchiver._perform(DoxygenArchiver.java:219) at hudson.plugins.doxygen.DoxygenArchiver.perform(DoxygenArchiver.java:176) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) at hudson.model.Run.run(Run.java:1433) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) - I'm not sure but I assume that jenkins is using invalid method name to call via reflection. could you check this out plz? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13055) checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed
Tina Zhu created JENKINS-13055: -- Summary: checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed Key: JENKINS-13055 URL: https://issues.jenkins-ci.org/browse/JENKINS-13055 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Reporter: Tina Zhu When I use the jenkins subversion to checkout codes, I offen get the following errors, and I checked the network is well, any idear for fix this probelm? ERROR: Failed to check out http://localhost/svn/hit71/branches/PR_hit7100_1.00 org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:291) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:276) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:264) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:266) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1263) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:820) at org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:564) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:922) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:84) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:120) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:787) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:768) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:752) at hudson.FilePath.act(FilePath.java:783) at hudson.FilePath.act(FilePath.java:765) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:742) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:684) at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:568) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:457) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: REPORT /svn/hit71/!svn/vcc/default failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89) ... 27 more Caused by: org.tmatesoft.svn.core.SVNException: svn: REPORT request failed on '/svn/hit71/!svn/vcc/default' svn: Processing REPORT request response failed: XML document structures must start and end within the same entity. (/svn/hit71/!svn/vcc/default) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:644) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:285) ... 26 more Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: REPORT request failed on '/svn/hit71/!svn/vcc/default' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:642) ... 27 more Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: Processing REPORT request response failed: XML document structures must start and end within the same entity. (/svn/hit71/!svn/vcc/default) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:181) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:133) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:767) at
[JIRA] (JENKINS-13056) Warnigs Reference Build from SCM/Trigger
Roland Schulz created JENKINS-13056: --- Summary: Warnigs Reference Build from SCM/Trigger Key: JENKINS-13056 URL: https://issues.jenkins-ci.org/browse/JENKINS-13056 Project: Jenkins Issue Type: Bug Components: warnings Reporter: Roland Schulz Assignee: Ulli Hafner It would be great if the SCM would be queried for the reference build. If the builds are not in order (e.g. because the build are triggered by code review (e.g. Gerrit)), it doesn't make sense to use the last build as reference. The SCM (e.g. Git) or the Trigger (e.g. Gerrit) would know the previous commit which should be used as reference. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
