[JIRA] (JENKINS-5338) Successfull jobs reported as Failed after restart
[ https://issues.jenkins-ci.org/browse/JENKINS-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-5338. -- Resolution: Incomplete No response from the reporter, so resolving as incomplete. Successfull jobs reported as Failed after restart - Key: JENKINS-5338 URL: https://issues.jenkins-ci.org/browse/JENKINS-5338 Project: Jenkins Issue Type: Bug Affects Versions: current Environment: redhat, java 5 (1.5.0_17), hudson 1.341 Reporter: bryandollery After restarting hudson all previous builds are showing as having failed. Drilling down into a single build, hudson shows the main icon as Failed, despite each separate maven module having succeeded and maven having reported the build a success. This has been happening since before xmas, the last time I upgraded hudson. I was hoping that the latest version may have fixed the problem, but that doesn't seem to be the case. -- 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-12739) Memory leak in Windows slave
Alex Vesely created JENKINS-12739: - Summary: Memory leak in Windows slave Key: JENKINS-12739 URL: https://issues.jenkins-ci.org/browse/JENKINS-12739 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Master: Linux Slave: Windows Server 2008 Reporter: Alex Vesely Jenkins slave (testing on Windows Server 2008) seems to have a memory leak. The process named 'java.exe' eats up several hundred MBs per day. I had to kill it when it was consuming 8 Gigs and was significantly slower than at the start. Sorry if this is a duplicate issue, but I haven't found any fresh thread on this topic. -- 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-11007) TFS plugin should allow multiple workspace folders (like TFS window allows in VS)
[ https://issues.jenkins-ci.org/browse/JENKINS-11007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158941#comment-158941 ] Weine Högberg commented on JENKINS-11007: - I believe it is the same. It is a dealbreaker for me, I have little use of Jenkins without this feature. TFS plugin should allow multiple workspace folders (like TFS window allows in VS) - Key: JENKINS-11007 URL: https://issues.jenkins-ci.org/browse/JENKINS-11007 Project: Jenkins Issue Type: Improvement Components: plugin, tfs Reporter: Kat Lim Ruiz Priority: Critical The TFS plugin should allow to define multiple project folders for the workspace. This means that I should be allowed to say: Project Path 1 = $/Proj/MyProduct/Application Project Path 2 = $/Proj/MyProduct/Config Project Path 3 = $/Proj/MyProduct/Database I want to keep the Database folder out of the Application folder because of better order. SO I can't do it right now, and I have to create three jobs in Hudson to download each separately. -- 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-12741) Improve support for multi-config Jobs
Ross Rowe created JENKINS-12741: --- Summary: Improve support for multi-config Jobs Key: JENKINS-12741 URL: https://issues.jenkins-ci.org/browse/JENKINS-12741 Project: Jenkins Issue Type: Bug Components: sauce-ondemand Reporter: Ross Rowe Assignee: Kohsuke Kawaguchi The current Sauce Connect logic ensures that only a single Sauce Connect instance is active per Job. For multi-config Jobs, this means that each Job waits until previous Jobs have finished. The plugin should be updated such that a single Sauce Connect instance is active for all multi-config Job instances. -- 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-4608) Email notification disabled with the m2-extra-steps plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158947#comment-158947 ] Christophe Demarey commented on JENKINS-4608: - This issue is now fixed. I tested it and it works fine. Thanks! Email notification disabled with the m2-extra-steps plugin -- Key: JENKINS-4608 URL: https://issues.jenkins-ci.org/browse/JENKINS-4608 Project: Jenkins Issue Type: Bug Components: m2-extra-steps Affects Versions: current Environment: Platform: All, OS: Linux Reporter: cdemarey2 Assignee: abayer Hello, I just discover this useful plugin (m2-extra-steps). I tried this plugin and of course, for the first attempt, my second build step (executing a script after maven) failed! It's quite normal as I need to validate my script on the hudson executor. The build is labeled as a failed build = Good. But my job is configured to send an email if the build failed. Here no email was sent. I cannot see the trace Sending e-mails to: ... on the build log. Is the email notification handle by the M2 extra steps plugin or is it a bug? Regards, Christophe. -- 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-12742) XML Reader feature
Eugene Gligalov created JENKINS-12742:
-
Summary: XML Reader feature
Key: JENKINS-12742
URL: https://issues.jenkins-ci.org/browse/JENKINS-12742
Project: Jenkins
Issue Type: New Feature
Components: token-macro
Reporter: Eugene Gligalov
Assignee: Kohsuke Kawaguchi
Hi,
Would be nice if plugin has possibility to read xml using xpath, this might be
useful for reading version from maven pom.xml it might look like:
${PROPFILE,file=somepath/pom.xml,xpath=/project/version/text()}
Regards
Eugene Gligalov
--
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-12742) XML Reader feature
[
https://issues.jenkins-ci.org/browse/JENKINS-12742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158948#comment-158948
]
Eugene Gligalov commented on JENKINS-12742:
---
or even better:
${XML,file=somepath/pom.xml,xpath=/project/version/text()}
XML Reader feature
--
Key: JENKINS-12742
URL: https://issues.jenkins-ci.org/browse/JENKINS-12742
Project: Jenkins
Issue Type: New Feature
Components: token-macro
Reporter: Eugene Gligalov
Assignee: Kohsuke Kawaguchi
Hi,
Would be nice if plugin has possibility to read xml using xpath, this might
be useful for reading version from maven pom.xml it might look like:
${PROPFILE,file=somepath/pom.xml,xpath=/project/version/text()}
Regards
Eugene Gligalov
--
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-12612) CVS plugin creates hundreds of 'cvs server' processes which kill our Jenkins server
[
https://issues.jenkins-ci.org/browse/JENKINS-12612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158949#comment-158949
]
Ulli Hafner commented on JENKINS-12612:
---
Sorry about the late answer, seems that my Jira mails went directly to the SPAM
folder.
Here is our configuration (in 1.6 format):
{code}
scm class=hudson.scm.CVSSCM
cvsroot/usr/local/cvsroot/cvsroot
moduleorg.faktorips.devtarget.galileo
org.faktorips.feature
org.faktorips.feature.nls1
org.faktorips.feature.test
org.faktorips.ormext.feature
org.faktorips.ormext.feature.nls1
org.faktorips.ormext.feature.test
org.faktorips.abstracttest
org.faktorips.devtools.ant
org.faktorips.devtools.ant.test
org.faktorips.devtools.core
org.faktorips.devtools.core.test
org.faktorips.devtools.core.ui
org.faktorips.devtools.core.ui.test
org.faktorips.devtools.htmlexport
org.faktorips.devtools.htmlexport.test
org.faktorips.devtools.htmlexport.nl1
org.faktorips.devtools.ormext
org.faktorips.devtools.ormext.hibernate
org.faktorips.devtools.ormext.test
org.faktorips.devtools.ormext.ui
org.faktorips.devtools.stdbuilder
org.faktorips.devtools.stdbuilder.test
org.faktorips.devtools.stdbuilder.ui
org.faktorips.devtools.stdbuilder.ui.test
org.faktorips.devtools.tableconversion
org.faktorips.devtools.tableconversion.nl1
org.faktorips.devtools.tableconversion.test
org.faktorips.dtflcommon
org.faktorips.dtflcommon.test
org.faktorips.fl
org.faktorips.fl.test
org.faktorips.nls.devtools.core.nl1
org.faktorips.nls.devtools.core.ui.nl1
org.faktorips.nls.devtools.stdbuilder.nl1
org.faktorips.nls.devtools.stdbuilder.ui.nl1
org.faktorips.nls.devtools.ormext.nl1
org.faktorips.nls.devtools.ormext.ui.nl1
org.faktorips.runtime.addons
org.faktorips.runtime.addons.test
org.faktorips.runtime.java5
org.faktorips.runtime.java5.test
org.faktorips.runtime.groovy
org.faktorips.runtime.groovy.test
org.faktorips.runtime.productdataservice
org.faktorips.runtime.productdataservice.common
org.faktorips.runtime.productdataprovider.ejbclient
org.faktorips.runtime.productdataprovider.ejbclient.test
org.faktorips.util
org.faktorips.util.test
org.faktorips.valuetypes.java5
org.faktorips.valuetypes.java5.test
org.faktorips.uml
org.faktorips.uml.feature
org.faktorips.uml.feature.nls1
org.faktorips.uml.feature.test
org.faktorips.uml.nl1
org.faktorips.uml.test
org.faktorips.pluginbuilder/module
canUseUpdatetrue/canUseUpdate
flattenfalse/flatten
isTagfalse/isTag
excludedRegionsorg/faktorips/fl/parser/.*
.*pluginbuilder\.config.*
.*allElements\.xml.*
.*all\.map
.*eclipse.*
/excludedRegions
/scm
{code}
CVS plugin creates hundreds of 'cvs server' processes which kill our Jenkins
server
---
Key: JENKINS-12612
URL: https://issues.jenkins-ci.org/browse/JENKINS-12612
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Linux Ubuntu, Jenkins 1.424.2, cvs Plug-in 2.0
Reporter: Ulli Hafner
Assignee: Michael Clarke
Priority: Blocker
The new plug-in seems to have a severe memory/process leak: After updating
our Jenkisn server to 2.0 it took just half a day until our machine had no
more ressources left. Jenkins had more than 13GByte virtual memory in the
process monitor and we had hundreds of stale cvs processes around:
{noformat}
hudson 14060 1 0 08:16 ?00:00:00 cvs server
hudson 14069 1 0 08:16 ?00:00:00 cvs server
hudson 14081 1 0 08:16 ?00:00:00 cvs server
hudson 14095 1 0 08:16 ?00:00:00 cvs server
hudson 14107 1 0 08:16 ?00:00:00 cvs server
hudson 14117 1 0 08:16 ?00:00:00 cvs server
hudson 14123 1 0 08:16 ?00:00:00 cvs server
hudson 14130 1 0 08:16 ?00:00:00 cvs server
hudson 14212 1 0 08:17 ?00:00:00 cvs server
hudson 14224 1 0 08:17 ?00:00:00 cvs server
hudson 14230 1 0 08:17 ?00:00:00 cvs server
hudson 14234 1 0 08:17 ?00:00:00 cvs server
hudson 14547 1 0 08:17 ?00:00:00 cvs server
hudson 14568 1 0 08:17 ?00:00:00 cvs server
hudson 14576 1 0 08:17 ?00:00:00 cvs server
hudson 14605 1 0 08:17 ?00:00:00 cvs server
hudson 14633 1 0 08:17 ?00:00:00 cvs server
hudson 14651 1 0 08:17 ?00:00:00 cvs server
hudson 14659 1 0 08:17 ?00:00:00 cvs server
hudson 14824 1 0 08:17 ?00:00:00 cvs server
hudson 14830 1 0 08:17 ?00:00:00 cvs server
hudson 14842 1 0 08:17 ?00:00:00 cvs server
hudson 14862 1 0 07:46 ?00:00:00 cvs server
hudson 14890 1 0 08:17 ?00:00:00 cvs server
hudson 14994 1 0 08:17 ?
[JIRA] (JENKINS-12743) Warnings plugin does not aggregate for multi-configuration projects
kd Jm created JENKINS-12743: --- Summary: Warnings plugin does not aggregate for multi-configuration projects Key: JENKINS-12743 URL: https://issues.jenkins-ci.org/browse/JENKINS-12743 Project: Jenkins Issue Type: Bug Components: warnings Environment: Win7, Jenkins ver. 1.450, Warnings Plug-in 3.27 Reporter: kd Jm Assignee: Ulli Hafner When using the warnings plugin in a multi-configuration project, the warnings plugin runs fine on each individual build (a combination of a value of each available axis), but does not report correctly the total number of warning on the job overview page. Instead, it displays the warnings of one sub-build. -- 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-10870) Fitnesse exceptions not failing a build
[ https://issues.jenkins-ci.org/browse/JENKINS-10870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Westcott resolved JENKINS-10870. -- Resolution: Fixed Fixed in 1.5 Fitnesse exceptions not failing a build --- Key: JENKINS-10870 URL: https://issues.jenkins-ci.org/browse/JENKINS-10870 Project: Jenkins Issue Type: Bug Components: fitnesse Environment: Plugins version 1.4 Reporter: Simon Westcott Assignee: Simon Westcott The plugin is not treating Fitnesse exceptions as failures, instead they are being reported as ignored/skipped and the build is remains green. -- 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-10870) Fitnesse exceptions not failing a build
[ https://issues.jenkins-ci.org/browse/JENKINS-10870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Westcott closed JENKINS-10870. Fitnesse exceptions not failing a build --- Key: JENKINS-10870 URL: https://issues.jenkins-ci.org/browse/JENKINS-10870 Project: Jenkins Issue Type: Bug Components: fitnesse Environment: Plugins version 1.4 Reporter: Simon Westcott Assignee: Simon Westcott The plugin is not treating Fitnesse exceptions as failures, instead they are being reported as ignored/skipped and the build is remains green. -- 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-7733) System Message - Doesnt appear on any view other than the default view
[ https://issues.jenkins-ci.org/browse/JENKINS-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe updated JENKINS-7733: Attachment: SystemMessage_OK.png System Message - Doesnt appear on any view other than the default view -- Key: JENKINS-7733 URL: https://issues.jenkins-ci.org/browse/JENKINS-7733 Project: Jenkins Issue Type: Improvement Components: gui Affects Versions: current Reporter: saimad Priority: Minor Fix For: current Attachments: SystemMessage_NG.png, SystemMessage_OK.png System Message Configured to be : h1Official Hudson Server/h1 This message appears only in the default All view. Once you click on any other view, the message is not displayed -- 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-7733) System Message - Doesnt appear on any view other than the default view
[ https://issues.jenkins-ci.org/browse/JENKINS-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe updated JENKINS-7733: Attachment: SystemMessage_NG.png System Message - Doesnt appear on any view other than the default view -- Key: JENKINS-7733 URL: https://issues.jenkins-ci.org/browse/JENKINS-7733 Project: Jenkins Issue Type: Improvement Components: gui Affects Versions: current Reporter: saimad Priority: Minor Fix For: current Attachments: SystemMessage_NG.png, SystemMessage_OK.png System Message Configured to be : h1Official Hudson Server/h1 This message appears only in the default All view. Once you click on any other view, the message is not displayed -- 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-12583) update for cvs plugin to 2.0 doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158953#comment-158953 ] jeremyt commented on JENKINS-12583: --- This may help someone... I cannot comment on whether the CVS plugin works or not, but I upgraded from v1.6 to v2.0 at the same time as upgrading Jenkins from 1.448 to 1.450 and I 'lost' a couple of Jobs (all source in a SVN repo, nothing in CVS). Down-graded the CVS plugin from 2.0 to 1.6 and the Jobs returned. update for cvs plugin to 2.0 doesn't work - Key: JENKINS-12583 URL: https://issues.jenkins-ci.org/browse/JENKINS-12583 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: jenkins 1.449, cvs plugin 1.6 Reporter: Alex Lehmann Assignee: Alex Lehmann Fix For: current I tried to update to the cvs plugin 2.0 today but this doesn't work, I assume there is a name problem due to the extension *.jpi on the new plugin. Before update, the file is called cvs.hpi, the update process creates a new file cvs.jpi that is ignored with the following message: Jan 30, 2012 5:04:26 PM hudson.PluginManager$1$3$1 isDuplicate INFO: Ignoring /home/lehmann/.jenkins/plugins/cvs.jpi because /home/lehmann/.jenkins/plugins/cvs.hpi is already loaded I assume it may work if it were the other way around. The version displayed by the plugin page remains 1.6 but there are a few exceptions in the log about missing classes like this java.lang.NoClassDefFoundError: org/netbeans/lib/cvsclient/admin/AdminHandler these classes are included in the cvs.jpi zip but that is not used. I was able to fix the update manually by copying cvs.jpi to cvs.hpi, which resulted in a pinned plugin 2.0, but the automatic process has to be fixed somehow. -- 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-8947) Allow a build to be restarted X amount of times if it times out
[ https://issues.jenkins-ci.org/browse/JENKINS-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158954#comment-158954 ] jcarsique commented on JENKINS-8947: See [Retry Failed Builds Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Retry+Failed+Builds+Plugin] and [Naginator Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin]. Maybe that feature should preferably be implemented into those plugins as an option to retry the build if it's failed/unstable because of a timeout. Allow a build to be restarted X amount of times if it times out --- Key: JENKINS-8947 URL: https://issues.jenkins-ci.org/browse/JENKINS-8947 Project: Jenkins Issue Type: New Feature Components: build-timeout Reporter: Paul M Assignee: Kohsuke Kawaguchi It would be nice to re-try a build if it failed due to time out. This helps work around bugs in visual studio where the build may hang forever. Rebuilding only that one project would be nice as restarting the build of the whole tree for the same issue to happen again is an annoyance. -- 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-12744) Execute a command before timeout
jcarsique created JENKINS-12744:
---
Summary: Execute a command before timeout
Key: JENKINS-12744
URL: https://issues.jenkins-ci.org/browse/JENKINS-12744
Project: Jenkins
Issue Type: New Feature
Components: build-timeout
Reporter: jcarsique
Assignee: jcarsique
In case of timeout, it would be interesting being able to run some command; for
instance, get a dump of the frozen thread.
Allow to add execution of a command (eg. {{pgrep -n -f surefire | xargs
jstack}}) before thread interruption on timeout.
--
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-12743) Warnings plugin does not aggregate for multi-configuration projects
[ https://issues.jenkins-ci.org/browse/JENKINS-12743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12743. --- Resolution: Duplicate Warnings plugin does not aggregate for multi-configuration projects --- Key: JENKINS-12743 URL: https://issues.jenkins-ci.org/browse/JENKINS-12743 Project: Jenkins Issue Type: Bug Components: warnings Environment: Win7, Jenkins ver. 1.450, Warnings Plug-in 3.27 Reporter: kd Jm Assignee: Ulli Hafner When using the warnings plugin in a multi-configuration project, the warnings plugin runs fine on each individual build (a combination of a value of each available axis), but does not report correctly the total number of warning on the job overview page. Instead, it displays the warnings of one sub-build. -- 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-12746) envinject strips off \ each time config page is opened
Roger Myung created JENKINS-12746: - Summary: envinject strips off \ each time config page is opened Key: JENKINS-12746 URL: https://issues.jenkins-ci.org/browse/JENKINS-12746 Project: Jenkins Issue Type: Bug Components: envinject Environment: envinject 1.20 Jenkins 1.424.1 Windows XP Reporter: Roger Myung Assignee: gbois Priority: Critical I have previously used envinject versions 1.13 and 1.17. envinject always had problems with UNC paths in Windows. (ex. MY_SHARED_FOLDER=\\MYCOMPUTER\Shared) I previously was able to escape these directories by using double slashes (MY_SHARED_FOLDER=MYCOMPUTER\Shared). However, one of the updates between 1.17 and 1.20 introduced functionality that updates the the Properties Content each time the config page is saved. So after I set my value to , and save. If I load the page again, the value is set to \\. If I save and load again, this becomes \. This is a very serious issue that forced me to downgrade the plugin even though I really want the Mask Password fix. -- 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-12619) Failed to test the validity of the user name on all security matrices since upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158956#comment-158956 ] Gwen Georgeault commented on JENKINS-12619: --- I have the same issue on Ubuntu 10.4 using the Project-based Matrix Authorization Strategy Failed to test the validity of the user name on all security matrices since upgrade - Key: JENKINS-12619 URL: https://issues.jenkins-ci.org/browse/JENKINS-12619 Project: Jenkins Issue Type: Bug Components: active-directory Environment: Jenkins 1.450, plugin version 1.26 Windows Server 2003, non-domain server Installed as local user Our Windows domain name specified in configuration as ourdomain.co.uk Reporter: Tom Fanning Priority: Minor Labels: jenkins, plugin, windows Upgraded plugin to version 1.26 just after upgrading Jenkins to 1.450 Now get message Failed to test the validity of the user name x wherever there is a security checkbox matrix. Everything seems to work alright still as far as I can tell. Stack trace: org.acegisecurity.BadCredentialsException: Failed to retrieve user information for x; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 04DC: LdapErr: DSID-0C0906E8, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v1db1]; remaining name 'DC=ourdomain,DC=co,DC=uk' at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:130) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:95) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:27) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:551) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName_(GlobalMatrixAuthorizationStrategy.java:304) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) 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) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] (JENKINS-12747) Perforce Passwords are exposed by the EnvInject plugin
Mike Winters created JENKINS-12747: -- Summary: Perforce Passwords are exposed by the EnvInject plugin Key: JENKINS-12747 URL: https://issues.jenkins-ci.org/browse/JENKINS-12747 Project: Jenkins Issue Type: Bug Components: envinject, perforce Environment: Windows 7 Enterprise SP1 (x64) Jenkins 1.450 EnvInject 1.20 Perforce 1.3.7 Mask Passwords 2.7.2 Reporter: Mike Winters Assignee: gbois Originally reported as part of JENKINS-12423, I am reopening this as a separate defect at the author's request. My original defect report from that issue is as follows: With Jenkins 1.450, Perforce plugin 1.3.7, EnvInject 1.17, and Mask Passwords 2.7.2, the Perforce passwords are being displayed in plain text on the Injected Environment Variables page. I have tried setting the passwords to be masked in the global Jenkins config as well as in the individual jobs, but nothing I have tried is masking the passwords. In the case of the Perforce passwords, the issue was happening before I installed the Mask Passwords plugin (I only installed that in an attempt to hide the passwords). It seems that perhaps the Perforce plugin (and plugins for other source control systems?) are exposing the passwords in a way that the EnvInject plugin doesn't know to look for. I'm not sure where the best place to fix this is, or what the optimal fix should be, as I am not familiar with the Jenkins codebase or the code for any of the relevant plugins. However, the quicker a solution can be implemented, the happier I will be :). Thanks! After updating to EnvInject 1.20, the Perforce password is still being exposed (P4PASSWD variable) on the Injected Environment Variables page available on the left menu on each build. I suspect that this may require changes to both the EnvInject plugin and the Perforce plugin. -- 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-12307) Stack Trace when going to main configuration page
[
https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158958#comment-158958
]
C. S. commented on JENKINS-12307:
-
Are there any news?
Stack Trace when going to main configuration page
-
Key: JENKINS-12307
URL: https://issues.jenkins-ci.org/browse/JENKINS-12307
Project: Jenkins
Issue Type: Bug
Components: warnings
Reporter: mwebber
Assignee: Ulli Hafner
Priority: Minor
When I go (in the web interface) to the main Jenkins configuration page, a
stack trace is generated on the Jenkins console. No adverse results appear on
the web page itself. From the stack track, it looks like it is connected to
the warnings plugin.
This is Jenkins 1.446 and Warnings plugin 3.26 (the latest available at the
time of reporting). I have been noticing this stack track for some time now,
including under earlier releases (I'm not sure how recently it started).
The stack trace:
{noformat}
05-Jan-2012 11:35:26 hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating:
descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
java.lang.reflect.InvocationTargetException
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
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at
org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
(snip)
at
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.AssertionError: null is missing its
[JIRA] (JENKINS-11185) Null Pointer Exception
[
https://issues.jenkins-ci.org/browse/JENKINS-11185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158959#comment-158959
]
Dorin Marinca commented on JENKINS-11185:
-
I think I got the same on Jenkins ver. 1.450 with Job Import Plugin 1.0:
{quote}
Status Code: 500
Exception:
Stacktrace:
java.lang.NullPointerException
at
org.jenkins.ci.plugins.jobimport.JobImportAction.doImport(JobImportAction.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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:111)
at
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
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)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
at
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
at
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at
[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page
[
https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158960#comment-158960
]
mwebber commented on JENKINS-12307:
---
It's still happening for me ... I guess Ulli has not had a chance to fix this
yet.
Stack Trace when going to main configuration page
-
Key: JENKINS-12307
URL: https://issues.jenkins-ci.org/browse/JENKINS-12307
Project: Jenkins
Issue Type: Bug
Components: warnings
Reporter: mwebber
Assignee: Ulli Hafner
Priority: Minor
When I go (in the web interface) to the main Jenkins configuration page, a
stack trace is generated on the Jenkins console. No adverse results appear on
the web page itself. From the stack track, it looks like it is connected to
the warnings plugin.
This is Jenkins 1.446 and Warnings plugin 3.26 (the latest available at the
time of reporting). I have been noticing this stack track for some time now,
including under earlier releases (I'm not sure how recently it started).
The stack trace:
{noformat}
05-Jan-2012 11:35:26 hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating:
descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
java.lang.reflect.InvocationTargetException
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
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at
org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
(snip)
at
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
at
[JIRA] (JENKINS-11887) Support Git for Repository browser setting
[ https://issues.jenkins-ci.org/browse/JENKINS-11887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158970#comment-158970 ] Gerd Zanker commented on JENKINS-11887: --- Can you please explain why the two issues are different? From where to get the repo Name? In the old issue the User has to enter the repo name and it will be added to the url (after Browser, before file). Isn't this what you need too? -- Posted from Bugbox for Android Support Git for Repository browser setting Key: JENKINS-11887 URL: https://issues.jenkins-ci.org/browse/JENKINS-11887 Project: Jenkins Issue Type: Improvement Components: git, trac Environment: Jenkins 1.441, Trac Plugin 1.12 Reporter: Gerd Zanker Assignee: Gerd Zanker Priority: Minor Labels: git, trac Fix For: current In the [Trac Plugin documentation|https://wiki.jenkins-ci.org/display/jenkins/Trac+Plugin] the configuration is described as bq. In the Source Code Management section, choose Trac for the Repository browser setting. This settings Trac is not available for when I use git as a SCM. Can this selection be added? The Trac-plugin code supports TracGit for the Repository browser setting. The given Trac URL at the top of the job settings will be used to generate links for git changesets, files and diffs to your Trac Browse Source area. -- 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-12747) Perforce Passwords are exposed by the EnvInject plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158971#comment-158971 ] Mike Winters commented on JENKINS-12747: Yes- that option is unchecked, but it does not affect the password displayed by the EnvInject plugin. Perforce Passwords are exposed by the EnvInject plugin -- Key: JENKINS-12747 URL: https://issues.jenkins-ci.org/browse/JENKINS-12747 Project: Jenkins Issue Type: Bug Components: envinject, perforce Environment: Windows 7 Enterprise SP1 (x64) Jenkins 1.450 EnvInject 1.20 Perforce 1.3.7 Mask Passwords 2.7.2 Reporter: Mike Winters Assignee: gbois Originally reported as part of JENKINS-12423, I am reopening this as a separate defect at the author's request. My original defect report from that issue is as follows: With Jenkins 1.450, Perforce plugin 1.3.7, EnvInject 1.17, and Mask Passwords 2.7.2, the Perforce passwords are being displayed in plain text on the Injected Environment Variables page. I have tried setting the passwords to be masked in the global Jenkins config as well as in the individual jobs, but nothing I have tried is masking the passwords. In the case of the Perforce passwords, the issue was happening before I installed the Mask Passwords plugin (I only installed that in an attempt to hide the passwords). It seems that perhaps the Perforce plugin (and plugins for other source control systems?) are exposing the passwords in a way that the EnvInject plugin doesn't know to look for. I'm not sure where the best place to fix this is, or what the optimal fix should be, as I am not familiar with the Jenkins codebase or the code for any of the relevant plugins. However, the quicker a solution can be implemented, the happier I will be :). Thanks! After updating to EnvInject 1.20, the Perforce password is still being exposed (P4PASSWD variable) on the Injected Environment Variables page available on the left menu on each build. I suspect that this may require changes to both the EnvInject plugin and the Perforce plugin. -- 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-12747) Perforce Passwords are exposed by the EnvInject plugin
[
https://issues.jenkins-ci.org/browse/JENKINS-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158973#comment-158973
]
Mike Winters commented on JENKINS-12747:
The only place I am providing the P4PASSWD is in the Password parameter of the
Depot section of the Source Code Management configuration in the job(s). I
have tried typing the password as standard plain text, and also referencing it
as ${MyPassword} with the password key/value pair specified in the global
settings of the Mask Password plugin. In both of these scenarios, the full
password is exposed in the link that the EnvInject plugin adds to the left hand
links when viewing a job build.
Perforce Passwords are exposed by the EnvInject plugin
--
Key: JENKINS-12747
URL: https://issues.jenkins-ci.org/browse/JENKINS-12747
Project: Jenkins
Issue Type: Bug
Components: envinject, perforce
Environment: Windows 7 Enterprise SP1 (x64)
Jenkins 1.450
EnvInject 1.20
Perforce 1.3.7
Mask Passwords 2.7.2
Reporter: Mike Winters
Assignee: gbois
Originally reported as part of JENKINS-12423, I am reopening this as a
separate defect at the author's request. My original defect report from that
issue is as follows:
With Jenkins 1.450, Perforce plugin 1.3.7, EnvInject 1.17, and Mask Passwords
2.7.2, the Perforce passwords are being displayed in plain text on the
Injected Environment Variables page. I have tried setting the passwords to
be masked in the global Jenkins config as well as in the individual jobs, but
nothing I have tried is masking the passwords.
In the case of the Perforce passwords, the issue was happening before I
installed the Mask Passwords plugin (I only installed that in an attempt to
hide the passwords). It seems that perhaps the Perforce plugin (and plugins
for other source control systems?) are exposing the passwords in a way that
the EnvInject plugin doesn't know to look for. I'm not sure where the best
place to fix this is, or what the optimal fix should be, as I am not familiar
with the Jenkins codebase or the code for any of the relevant plugins.
However, the quicker a solution can be implemented, the happier I will be :).
Thanks!
After updating to EnvInject 1.20, the Perforce password is still being
exposed (P4PASSWD variable) on the Injected Environment Variables page
available on the left menu on each build. I suspect that this may require
changes to both the EnvInject plugin and the Perforce plugin.
--
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-12747) Perforce Passwords are exposed by the EnvInject plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158974#comment-158974 ] Rob Petti commented on JENKINS-12747: - Does it show up if you provide no password at all? I suspect you may have it set in your node's environment. Either way, the EnvInject plugin should be honoring the Mask Passwords plugin, which according to JENKINS-12423 it does already? Perforce Passwords are exposed by the EnvInject plugin -- Key: JENKINS-12747 URL: https://issues.jenkins-ci.org/browse/JENKINS-12747 Project: Jenkins Issue Type: Bug Components: envinject, perforce Environment: Windows 7 Enterprise SP1 (x64) Jenkins 1.450 EnvInject 1.20 Perforce 1.3.7 Mask Passwords 2.7.2 Reporter: Mike Winters Assignee: gbois Originally reported as part of JENKINS-12423, I am reopening this as a separate defect at the author's request. My original defect report from that issue is as follows: With Jenkins 1.450, Perforce plugin 1.3.7, EnvInject 1.17, and Mask Passwords 2.7.2, the Perforce passwords are being displayed in plain text on the Injected Environment Variables page. I have tried setting the passwords to be masked in the global Jenkins config as well as in the individual jobs, but nothing I have tried is masking the passwords. In the case of the Perforce passwords, the issue was happening before I installed the Mask Passwords plugin (I only installed that in an attempt to hide the passwords). It seems that perhaps the Perforce plugin (and plugins for other source control systems?) are exposing the passwords in a way that the EnvInject plugin doesn't know to look for. I'm not sure where the best place to fix this is, or what the optimal fix should be, as I am not familiar with the Jenkins codebase or the code for any of the relevant plugins. However, the quicker a solution can be implemented, the happier I will be :). Thanks! After updating to EnvInject 1.20, the Perforce password is still being exposed (P4PASSWD variable) on the Injected Environment Variables page available on the left menu on each build. I suspect that this may require changes to both the EnvInject plugin and the Perforce plugin. -- 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-12582) CVS-Plugin: Password file ${user.home}/.cvspass is ignored
[
https://issues.jenkins-ci.org/browse/JENKINS-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158976#comment-158976
]
Alex Lehmann commented on JENKINS-12582:
I tried migrating a cvs test job from cvs-plugin 1.6 to 2.0, that didn't pick
up the password from the .cvspass file.
CVS-Plugin: Password file ${user.home}/.cvspass is ignored
Key: JENKINS-12582
URL: https://issues.jenkins-ci.org/browse/JENKINS-12582
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Tomcat6 / RHEL5
Reporter: chrisabit
Priority: Blocker
Jenkins' new Netbeans-based CVS-Plugin doesn't use the .cvspass file.
Setting the password on every job isn't a suitable solution (huge number of
jobs, security issues). The .cvspass file should be used instead.
--
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-12747) Perforce Passwords are exposed by the EnvInject plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158977#comment-158977 ] Rob Petti commented on JENKINS-12747: - I'm unable to reproduce this... If I uncheck the Expose P4PASSWD in environment option, it does not show up in the Injected Environment variables screen on subsequent builds. This is using envinject 1.20, perforce plugin 1.3.7, and jenkins 1.450. Perforce Passwords are exposed by the EnvInject plugin -- Key: JENKINS-12747 URL: https://issues.jenkins-ci.org/browse/JENKINS-12747 Project: Jenkins Issue Type: Bug Components: envinject, perforce Environment: Windows 7 Enterprise SP1 (x64) Jenkins 1.450 EnvInject 1.20 Perforce 1.3.7 Mask Passwords 2.7.2 Reporter: Mike Winters Assignee: gbois Originally reported as part of JENKINS-12423, I am reopening this as a separate defect at the author's request. My original defect report from that issue is as follows: With Jenkins 1.450, Perforce plugin 1.3.7, EnvInject 1.17, and Mask Passwords 2.7.2, the Perforce passwords are being displayed in plain text on the Injected Environment Variables page. I have tried setting the passwords to be masked in the global Jenkins config as well as in the individual jobs, but nothing I have tried is masking the passwords. In the case of the Perforce passwords, the issue was happening before I installed the Mask Passwords plugin (I only installed that in an attempt to hide the passwords). It seems that perhaps the Perforce plugin (and plugins for other source control systems?) are exposing the passwords in a way that the EnvInject plugin doesn't know to look for. I'm not sure where the best place to fix this is, or what the optimal fix should be, as I am not familiar with the Jenkins codebase or the code for any of the relevant plugins. However, the quicker a solution can be implemented, the happier I will be :). Thanks! After updating to EnvInject 1.20, the Perforce password is still being exposed (P4PASSWD variable) on the Injected Environment Variables page available on the left menu on each build. I suspect that this may require changes to both the EnvInject plugin and the Perforce plugin. -- 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-12182) Publisher - Code Analysis - NullPointerException
[ https://issues.jenkins-ci.org/browse/JENKINS-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158978#comment-158978 ] Marcin Drozdowski commented on JENKINS-12182: - I've made test again. I made it on new environment (just downloaded): 1) jenkins.war (1.451) http://mirrors.jenkins-ci.org/war/latest/jenkins.war 2) apache-tomcat-6.0.35.zip http://www.idg.pl/mirrors/apache/tomcat/tomcat-6/v6.0.35/bin/apache-tomcat-6.0.35.zip 3) jdk-6u30-windows-i586.exe http://download.oracle.com/otn-pub/java/jdk/6u30-b12/jdk-6u30-windows-i586.exe Than I installed https://wiki.jenkins-ci.org/display/JENKINS/Analysis+Collector+Plugin (1.19), restart Jenkins and still everything was ok, but after install https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin (0.8) again the radio Health priorities (section: Publish combined analysis results) wasn't checked. After uninstalling Flexible Publish Plugin everything back to normal, so for sure Flexible is causing problems. Thanks for help. Publisher - Code Analysis - NullPointerException Key: JENKINS-12182 URL: https://issues.jenkins-ci.org/browse/JENKINS-12182 Project: Jenkins Issue Type: Bug Components: analysis-core Affects Versions: current Environment: - Static Code Analysis Plug-ins (id: analysis-core, wersja: 1.36) - Static Analysis Collector Plug-in 1.19 - Jenkins 1.444 Reporter: Marcin Drozdowski Assignee: Ulli Hafner Labels: jenkins, plugin Attachments: bug_analysis_core_nullpointerexception.jpg, bug_analysis_core_nullpointerexception.jpg, config_correct.xml, config_wrong.xml, installed.html, installed2.html Again in latest version there is a bug during publishing with analysis-core plugin. Cause: In section Post-build Actions of job configuration (type: maven), when Publish combined analysis results checked, the value of Health priorities (e.g. All priorities) is not remembered after save action (probably only in a form, no in stored a job configuration - there is ok). To reproduce (changes in job configuration): - check Post-build Actions - Publish combined analysis results - use advanced settings and select Health priorities - All priorities - use save action - build (should be BUILD SUCCESSFUL, config_correct.xml) - edit configuration again, there should be any value selected in path: Post-build Actions - Publish combined analysis results - Health priorities (bug_analysis_core_nullpointerexception.jpg) - use save action - build (should be FAILURE, config_wrong.xml) ERROR: Publisher hudson.plugins.analysis.collector.AnalysisPublisher aborted due to exception java.lang.NullPointerException: Name is null at java.lang.Enum.valueOf(Enum.java:195) at hudson.plugins.analysis.util.model.Priority.valueOf(Priority.java:18) at hudson.plugins.analysis.core.HealthAwarePublisher.getMinimumPriority(HealthAwarePublisher.java:618) at hudson.plugins.analysis.core.AbstractHealthDescriptor.init(AbstractHealthDescriptor.java:36) at hudson.plugins.analysis.collector.AnalysisHealthDescriptor.init(AnalysisHealthDescriptor.java:25) at hudson.plugins.analysis.collector.AnalysisResultAction.init(AnalysisResultAction.java:31) at hudson.plugins.analysis.collector.AnalysisPublisher.perform(AnalysisPublisher.java:256) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:1014) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) at hudson.model.Run.run(Run.java:1429) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) -- 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-12746) envinject strips off \ each time config page is opened
[ https://issues.jenkins-ci.org/browse/JENKINS-12746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158979#comment-158979 ] SCM/JIRA link daemon commented on JENKINS-12746: Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/service/PropertiesLoader.java http://jenkins-ci.org/commit/envinject-plugin/b183fac8743092f6b49e7313ae6353c35ee6ce82 Log: Fix JENKINS-12746 envinject strips off \ each time config page is opened Key: JENKINS-12746 URL: https://issues.jenkins-ci.org/browse/JENKINS-12746 Project: Jenkins Issue Type: Bug Components: envinject Environment: envinject 1.20 Jenkins 1.424.1 Windows XP Reporter: Roger Myung Assignee: gbois Priority: Critical I have previously used envinject versions 1.13 and 1.17. envinject always had problems with UNC paths in Windows. (ex. MY_SHARED_FOLDER=\\MYCOMPUTER\Shared) I previously was able to escape these directories by using double slashes (MY_SHARED_FOLDER=MYCOMPUTER\Shared). However, one of the updates between 1.17 and 1.20 introduced functionality that updates the the Properties Content each time the config page is saved. So after I set my value to , and save. If I load the page again, the value is set to \\. If I save and load again, this becomes \. This is a very serious issue that forced me to downgrade the plugin even though I really want the Mask Password fix. -- 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-12746) envinject strips off \ each time config page is opened
[ https://issues.jenkins-ci.org/browse/JENKINS-12746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-12746. - Resolution: Fixed envinject strips off \ each time config page is opened Key: JENKINS-12746 URL: https://issues.jenkins-ci.org/browse/JENKINS-12746 Project: Jenkins Issue Type: Bug Components: envinject Environment: envinject 1.20 Jenkins 1.424.1 Windows XP Reporter: Roger Myung Assignee: gbois Priority: Critical I have previously used envinject versions 1.13 and 1.17. envinject always had problems with UNC paths in Windows. (ex. MY_SHARED_FOLDER=\\MYCOMPUTER\Shared) I previously was able to escape these directories by using double slashes (MY_SHARED_FOLDER=MYCOMPUTER\Shared). However, one of the updates between 1.17 and 1.20 introduced functionality that updates the the Properties Content each time the config page is saved. So after I set my value to , and save. If I load the page again, the value is set to \\. If I save and load again, this becomes \. This is a very serious issue that forced me to downgrade the plugin even though I really want the Mask Password fix. -- 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-12753) Instant update of plugins doesn't work in nfs directory
Alex Lehmann created JENKINS-12753: -- Summary: Instant update of plugins doesn't work in nfs directory Key: JENKINS-12753 URL: https://issues.jenkins-ci.org/browse/JENKINS-12753 Project: Jenkins Issue Type: Bug Components: plugin Environment: linux, nfs, jenkins 1.450, any plugin Reporter: Alex Lehmann Priority: Minor Got the question from the irc channel, this was initially discussed on the fosdem jenkins booth. Updating plugins doesn't work when the jenkins home directory is located on nfs, the failure looks like this Caused by: java.io.IOException: Unable to delete /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/.nfs000e897d0096 The .nfs files appear when deleting a file on nfs that is still open, in this case the jar files in the lib directory are still open and cannot be deleted. -- 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-12754) selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesn't
Michael Higgins created JENKINS-12754: - Summary: selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesn't Key: JENKINS-12754 URL: https://issues.jenkins-ci.org/browse/JENKINS-12754 Project: Jenkins Issue Type: Bug Components: selenium Affects Versions: current Environment: ubuntu 1004... Reporter: Michael Higgins Assignee: Kohsuke Kawaguchi This code, driver = Selenium::WebDriver.for(:remote, :url = 'http://slave-tb2.puppetlabs.lan:/wd/hub/', :desired_capabilities = :chrome) Should work to start a webdriver session with chrome... but doesn't. Works as Jenkins user from jenkins. However, driver = Selenium::WebDriver.for :chrome ... works just fine. I raise this because it works as it should with :remote :firefox. -- 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-11894) All tests {test Methods} of TestNG, belonging to the same class are shown as FAILURE, if just one of the test is a failure
[
https://issues.jenkins-ci.org/browse/JENKINS-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158981#comment-158981
]
SCM/JIRA link daemon commented on JENKINS-11894:
Code changed in jenkins
User: Bruno P. Kinoshita
Path:
src/main/java/hudson/plugins/testlink/result/JUnitCaseNameResultSeeker.java
src/main/java/hudson/plugins/testlink/result/Report.java
src/test/java/hudson/plugins/testlink/TestLinkSiteFake.java
src/test/java/hudson/plugins/testlink/result/TestJUnitCaseNameResultSeeker.java
http://jenkins-ci.org/commit/testlink-plugin/90cbcc2c1c52900512a2349682d4bc88303cf670
Log:
JENKINS-11894 Updating tests and planning seek and update strategy to reduce
memory consumption
All tests {test Methods} of TestNG, belonging to the same class are shown as
FAILURE, if just one of the test is a failure
-
Key: JENKINS-11894
URL: https://issues.jenkins-ci.org/browse/JENKINS-11894
Project: Jenkins
Issue Type: Bug
Components: testlink
Environment: Jenkins Version 1.440 {Testlink Plugin - Version 3.0.2}
Testlink Version 1.9.3 (Prague)
Reporter: Venugopal Shenoy
Assignee: Bruno P. Kinoshita
Priority: Critical
Labels: plugin
Attachments: testng-results.xml
Create one TestNG test class with several test methods {say 3 methods}. One
of the test is deliberately failed {using assertTrue(false);}. All the
tests are shown as failure in Testlink, when the testng xml test results are
pushed to testlink using the Jenkins-Testlink plugin. {TestNG XML Results
file is attached}
--
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-12754) selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesn't
[ https://issues.jenkins-ci.org/browse/JENKINS-12754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Lavoie reassigned JENKINS-12754: Assignee: Richard Lavoie (was: Kohsuke Kawaguchi) selenium-grid .for( :remote, :desired_capabilities = :chrome ) should work, but doesn't Key: JENKINS-12754 URL: https://issues.jenkins-ci.org/browse/JENKINS-12754 Project: Jenkins Issue Type: Bug Components: selenium Affects Versions: current Environment: ubuntu 1004... Reporter: Michael Higgins Assignee: Richard Lavoie Labels: plugin This code, driver = Selenium::WebDriver.for(:remote, :url = 'http://slave-tb2.puppetlabs.lan:/wd/hub/', :desired_capabilities = :chrome) Should work to start a webdriver session with chrome... but doesn't. Works as Jenkins user from jenkins. However, driver = Selenium::WebDriver.for :chrome ... works just fine. I raise this because it works as it should with :remote :firefox. -- 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-12755) P4 Counter text field does not do env variable subsitution
[
https://issues.jenkins-ci.org/browse/JENKINS-12755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158982#comment-158982
]
Rob Petti commented on JENKINS-12755:
-
You can send a pull request on github, or even attach it here, whichever is
easiest for you. :)
P4 Counter text field does not do env variable subsitution
--
Key: JENKINS-12755
URL: https://issues.jenkins-ci.org/browse/JENKINS-12755
Project: Jenkins
Issue Type: Bug
Components: perforce
Affects Versions: current
Environment: RH 6
Reporter: Andy Tang
Priority: Minor
Currently the P4 counter text field does not expand env variables when run.
Steps to reproduce:
1) Setup a build job
2) Enable Perforce plugin
3) In the P4 Counter text field, enter a counter name with env varaible,
example: counter_${JOB_NAME}
4) Start the build
Result:
The perforce plugin saves the synced chagnelist to counter_${JOB_NAME}
instead of substituting it when creating a counter name. Env substitution
would be useful in here as I can set this once and use it in different jobs.
I have actually re-compiled the latest 1.3.8-snapshot with changes to support
env variables substitution. It was a one line change...what would be best
method to publish my work? (Sorry this is my first time contributing :)
--
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-12737) Build succeeds but console ends with FATAL: null and a stacktrace
[
https://issues.jenkins-ci.org/browse/JENKINS-12737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen updated JENKINS-12737:
--
Attachment: standardize_jenkins_builds.php
Some more info in case it helps. I think I didn't start seeing these errors
until I started using the attached PHP script to maintain our many config.xml
files (we have many similar but separate jobs).
Build succeeds but console ends with FATAL: null and a stacktrace
---
Key: JENKINS-12737
URL: https://issues.jenkins-ci.org/browse/JENKINS-12737
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: Ubuntu 10.04.3 LTS server. Using jenkins 1.450 deb
package from http://pkg.jenkins-ci.org/debian. Plugins: ant 1.1, javadoc 1.0,
Dependency Graph Viewer Plugin 0.2, Jenkins build timeout plugin 1.8, Jenkins
Subversion Plug-in 1.37, Jenkins Parameterized Trigger plugin 2.13, Maven
Integration plugin 1.450, Jenkins GIT plugin 1.1.15, Hudson Xvnc plugin 1.10,
Jenkins instant-messaging plugin 1.21, Jenkins Jabber notifier plugin 1.22,
github-api 1.16, Build Pipeline Plugin 1.2.3, Jenkins Translation Assistance
plugin 1.8, GitHub plugin 1.0, Jenkins SSH Slaves plugin 0.21.
Reporter: Adam Monsen
Priority: Trivial
Attachments: standardize_jenkins_builds.php
After the build completes (successfully: all test pass, success exit code
from my scripts, etc), I see FATAL: null and a stacktrace at the end of the
console output:
{code}
PHPUnit 3.5.15 by Sebastian Bergmann.
.I...
Time: 4 seconds, Memory: 115.50Mb
OK, but incomplete or skipped tests!
Tests: 25, Assertions: 49, Incomplete: 1.
Terminating xvnc.
$ vncserver -kill :10
Killing Xvnc4 process ID 28139
Recording test results
Pushing tag ci-254 to repo origin
FATAL: null
java.lang.NullPointerException
at hudson.model.Result.isBetterOrEqualTo(Result.java:115)
at hudson.tasks.BuildTrigger$2.shouldTriggerBuild(BuildTrigger.java:234)
at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:212)
at
hudson.model.AbstractBuild$AbstractRunner.cleanUp(AbstractBuild.java:640)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:173)
at hudson.model.Run.run(Run.java:1453)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
{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-12737) Build succeeds but console ends with FATAL: null and a stacktrace
[
https://issues.jenkins-ci.org/browse/JENKINS-12737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158983#comment-158983
]
Adam Monsen edited comment on JENKINS-12737 at 2/14/12 3:46 AM:
Some more info in case it helps. I think I didn't start seeing these errors
until I started using the attached PHP script
({{standardize_jenkins_builds.php}}) to maintain our many config.xml files (we
have many similar but separate jobs).
was (Author: amonsen):
Some more info in case it helps. I think I didn't start seeing these errors
until I started using the attached PHP script to maintain our many config.xml
files (we have many similar but separate jobs).
Build succeeds but console ends with FATAL: null and a stacktrace
---
Key: JENKINS-12737
URL: https://issues.jenkins-ci.org/browse/JENKINS-12737
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: Ubuntu 10.04.3 LTS server. Using jenkins 1.450 deb
package from http://pkg.jenkins-ci.org/debian. Plugins: ant 1.1, javadoc 1.0,
Dependency Graph Viewer Plugin 0.2, Jenkins build timeout plugin 1.8, Jenkins
Subversion Plug-in 1.37, Jenkins Parameterized Trigger plugin 2.13, Maven
Integration plugin 1.450, Jenkins GIT plugin 1.1.15, Hudson Xvnc plugin 1.10,
Jenkins instant-messaging plugin 1.21, Jenkins Jabber notifier plugin 1.22,
github-api 1.16, Build Pipeline Plugin 1.2.3, Jenkins Translation Assistance
plugin 1.8, GitHub plugin 1.0, Jenkins SSH Slaves plugin 0.21.
Reporter: Adam Monsen
Priority: Trivial
Attachments: standardize_jenkins_builds.php
After the build completes (successfully: all test pass, success exit code
from my scripts, etc), I see FATAL: null and a stacktrace at the end of the
console output:
{code}
PHPUnit 3.5.15 by Sebastian Bergmann.
.I...
Time: 4 seconds, Memory: 115.50Mb
OK, but incomplete or skipped tests!
Tests: 25, Assertions: 49, Incomplete: 1.
Terminating xvnc.
$ vncserver -kill :10
Killing Xvnc4 process ID 28139
Recording test results
Pushing tag ci-254 to repo origin
FATAL: null
java.lang.NullPointerException
at hudson.model.Result.isBetterOrEqualTo(Result.java:115)
at hudson.tasks.BuildTrigger$2.shouldTriggerBuild(BuildTrigger.java:234)
at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:212)
at
hudson.model.AbstractBuild$AbstractRunner.cleanUp(AbstractBuild.java:640)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:173)
at hudson.model.Run.run(Run.java:1453)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
{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-12737) Build succeeds but console ends with FATAL: null and a stacktrace
[
https://issues.jenkins-ci.org/browse/JENKINS-12737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen resolved JENKINS-12737.
---
Assignee: Adam Monsen
Resolution: Not A Defect
D'oh! User error. I did indeed corrupt some config.xml files with my script.
Somehow I closed the {{publishers}} element far too soon, lopping off a whole
bunch of settings and confusing Jenkins. I suppose XML validation would help,
but that's another story. Chalk this one up to PEBKAC.
Build succeeds but console ends with FATAL: null and a stacktrace
---
Key: JENKINS-12737
URL: https://issues.jenkins-ci.org/browse/JENKINS-12737
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: Ubuntu 10.04.3 LTS server. Using jenkins 1.450 deb
package from http://pkg.jenkins-ci.org/debian. Plugins: ant 1.1, javadoc 1.0,
Dependency Graph Viewer Plugin 0.2, Jenkins build timeout plugin 1.8, Jenkins
Subversion Plug-in 1.37, Jenkins Parameterized Trigger plugin 2.13, Maven
Integration plugin 1.450, Jenkins GIT plugin 1.1.15, Hudson Xvnc plugin 1.10,
Jenkins instant-messaging plugin 1.21, Jenkins Jabber notifier plugin 1.22,
github-api 1.16, Build Pipeline Plugin 1.2.3, Jenkins Translation Assistance
plugin 1.8, GitHub plugin 1.0, Jenkins SSH Slaves plugin 0.21.
Reporter: Adam Monsen
Assignee: Adam Monsen
Priority: Trivial
Attachments: standardize_jenkins_builds.php
After the build completes (successfully: all test pass, success exit code
from my scripts, etc), I see FATAL: null and a stacktrace at the end of the
console output:
{code}
PHPUnit 3.5.15 by Sebastian Bergmann.
.I...
Time: 4 seconds, Memory: 115.50Mb
OK, but incomplete or skipped tests!
Tests: 25, Assertions: 49, Incomplete: 1.
Terminating xvnc.
$ vncserver -kill :10
Killing Xvnc4 process ID 28139
Recording test results
Pushing tag ci-254 to repo origin
FATAL: null
java.lang.NullPointerException
at hudson.model.Result.isBetterOrEqualTo(Result.java:115)
at hudson.tasks.BuildTrigger$2.shouldTriggerBuild(BuildTrigger.java:234)
at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:212)
at
hudson.model.AbstractBuild$AbstractRunner.cleanUp(AbstractBuild.java:640)
at hudson.model.Build$RunnerImpl.cleanUp(Build.java:173)
at hudson.model.Run.run(Run.java:1453)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
{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-12750) Scriptler 2.0 breaks cc.xml-View for Anonymous User having READ perm on Overall and Job
[ https://issues.jenkins-ci.org/browse/JENKINS-12750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158986#comment-158986 ] domi commented on JENKINS-12750: unfortunately downgrade will most likely not work - the internal structure was changed quite a bit and therefore the format of the scriptler.xml changed too. ...Only upgrade is supported - sorry. Can you please explane what cc.xml is? Where does it come from? How can I reproduce the issue? Scriptler 2.0 breaks cc.xml-View for Anonymous User having READ perm on Overall and Job --- Key: JENKINS-12750 URL: https://issues.jenkins-ci.org/browse/JENKINS-12750 Project: Jenkins Issue Type: Bug Components: scriptler Affects Versions: current Environment: executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator/ hudson.diyChunkingtrue java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version50.0 java.endorsed.dirs/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-6-sun-1.6.0.26/jre java.io.tmpdir/tmp java.library.path /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64/server:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.6.0_26-b03 java.specification.name Java Platform API Specification java.specification.vendor Sun Microsystems Inc. java.specification.version1.6 java.vendor Sun Microsystems Inc. java.vendor.url http://java.sun.com/ java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi java.version 1.6.0_26 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.nameJava Virtual Machine Specification java.vm.specification.vendor Sun Microsystems Inc. java.vm.specification.version 1.0 java.vm.vendorSun Microsystems Inc. java.vm.version 20.1-b02 javamelody.analytics-id UA-1335263-7 javamelody.http-transform-pattern /\d+/|/site/.+|avadoc/.+|/ws/.+|obertura/.+|estReport/.+|iolations/file/.+|/user/.+|/static/\w+/ javamelody.no-databasetrue javamelody.storage-directory //var/lib/jenkins/monitoring javamelody.system-actions-enabled true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib line.separator os.arch amd64 os.name Linux os.version2.6.32-37-server path.separator: pid 21367 sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/resources.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/rt.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/jsse.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/jce.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/charsets.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/classes sun.boot.library.path /usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/amd64 sun.cpu.endianlittle sun.cpu.isalist sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/run/jenkins/war --httpPort=8081 --ajp13Port=-1 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.levelunknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistentfalse user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Europe/Berlin Reporter: ctrabold Assignee: domi Labels: plugin After upgrading Jenkins to Scriptler 2.0 on Jenkins 1.450 calling cc.xml throws an 500 error: https://gist.github.com/1817603 The error appears when calling the URL as an *anonymous user* having READ permissions on Overall and Job. So I think it is somehow related with https://github.com/jenkinsci/scriptler-plugin/pull/2 Downgrading to Scriptler 1.5 fixed the problem. -- 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-12738) Dry Plugin reports code duplicates twice
[ https://issues.jenkins-ci.org/browse/JENKINS-12738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158987#comment-158987 ] Kumar n commented on JENKINS-12738: --- Thanks for the comments. I have attached extracted xml for your reference, where it shows the lines for duplicate code and which are not repeated. that is, there are no multiple warnings. the lines in the attached xml show the duplicated code for the warnings attached in my previous message(for the file job.cpp). Please have a look. Thanks, Santosh. Dry Plugin reports code duplicates twice Key: JENKINS-12738 URL: https://issues.jenkins-ci.org/browse/JENKINS-12738 Project: Jenkins Issue Type: Bug Components: dry Environment: Win-7 Reporter: Kumar n Assignee: Ulli Hafner Labels: plugin Attachments: duplicate.PNG I have used CPD to detect duplicate codes in my project and Dry plugin is used. The plugin is reporting the duplicate codes , but it reports twice for a duplicate code-snippet. I have attached the screenshot of our files reported. Please let me know is this the expected behaviour or it needs any correction. But I feel this is somewhat not an expected behavior and needs your attention. Thanks, Santosh -- 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
