[JIRA] [core] (JENKINS-29372) Help text for Label expression does not appear
Title: Message Title Dave Bacher created an issue Jenkins / JENKINS-29372 Help text for Label _expression_ does not appear Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Jul/15 8:50 PM Environment: Jenkins 1.609.1 Priority: Minor Reporter: Dave Bacher Previous versions of Jenkins show a help button for the Label _expression_ field under Restrict where this job can run in the job configuration page. With Jenkins 1.609.1, I no longer see this help button or text on the job configuration page. The text itself does appear to be present under http://jenkins/descriptor/hudson.model.FreeStyleProject/help/assignedLabelString, but it's not linked on the job configuration page.
[JIRA] [core] (JENKINS-16765) Setting an empty email address in User configuration is not saved
Dave Bacher updated JENKINS-16765 Setting an empty email address in User configuration is not saved Changed type from Bug to Improvement Change By: Dave Bacher (30/Jun/14 6:41 PM) Issue Type: Bug Improvement Description: Iwanttodisableemailstoaparticular(automated)user.Todothis,IthinkIcansettheusersemailaddresstoanemptyvalue.IntheUsersconfiguration,IcansettheemailaddresstoanemptyvalueandpressSave,theSaveappearstosucceed,buttheemptyvalueisnotsaved.OpeningtheUsersconfigurationagainshowsthefullemailaddress(username@domain).IntheUsersconfiguration,ifIsettheaddresstoanemptyvalueandpressApply,Igetanemptyerrorwindow.IntheSystemConfigurationE-mailsection,Ihaveadefaultdomainset.IfIremovethedefaultdomain,Icansettheusersemailaddresstoanemptyvalue. SinceJenkinsdoesnotallowmetosetanemptyemailaddresswhenthedefaultemaildomainisset,IwouldliketheabilitytosomehowdisableJenkinsemailsforaparticularuser. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [coverity] (JENKINS-18315) Cov-commit-defects fails to find defects when the intermediate directory is a relative path
Dave Bacher commented on JENKINS-18315 Cov-commit-defects fails to find defects when the intermediate directory is a relative path My original reason for using a relative directory was to capture the build-log.txt from the intermediate directory as an artifact of the Jenkins build. The workaround to capture build-log.txt is to add a build step that copies build-log.txt from the (temporary) intermediate directory stored in the COVERITY_IDIR env variable into the workspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-18315) Cov-commit-defects fails to find defects when the intermediate directory is a relative path
Dave Bacher created JENKINS-18315 Cov-commit-defects fails to find defects when the intermediate directory is a relative path Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: coverity Created: 12/Jun/13 3:57 PM Description: When I configure a Coverity build with the option for the plugin to perform the Coverity build, analysis and commit AND I configure the intermediate directory to be a relative path (relative to the workspace), the cov-commit-defects step reports that it can not find defects. $ "C:\Program Files\Coverity-6\Prevent\bin\cov-commit-defects" --dir coverity-build --host coverity --port 8080 --stream "My stream trunk" --user jenkins Coverity Defect Commit Client version 6.5.3 on Windows Server 2003, Standard Edition, 32-bit, Service Pack 2 (build 3790) Internal version numbers: 7d3b4ace9c p-davis-push-13307.195 [ERROR] Specified intermediate directory c:/jenkins/coverity-build doesn't contain any usable data One good reason for configuring the intermediate directory relative to the workspace is that it's straightforward for the build_log.txt to be made an artifact of the build (for later examination). Environment: Jenkins 1.517, Coverity plugin 1.2.4 Project: Jenkins Priority: Major Reporter: Dave Bacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-18317) Coverity - Default Defect Filter selects no defects when non-default component map is associated with a stream in Coverity
Dave Bacher created JENKINS-18317 Coverity - Default Defect Filter selects no defects when non-default component map is associated with a stream in Coverity Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: coverity Created: 12/Jun/13 4:35 PM Description: I have a (non-default) component map associated with my stream in Coverity. After selecting this stream for the build results in the Jenkins build's Post-build Coverity configuration, the default Defect Filter associated with this stream does not select any defects (see build output below). If I open the Defect Filters section, I see that none of the components under Component is among in my stream's component map are selected. In addition, the Select All and Select None buttons have no effect on the component selection. Expected result: when adding a Stream for build results in the Coverity plugin, the default Defect Filter should select all components. In addition, the Select All and Select None buttons should (respectively) select all or unselect all of the components in the component map. $ "C:\Program Files\Coverity-6\Prevent\bin\cov-commit-defects" --dir c:\jenkins\coverity\temp-4525474660219577452.tmp --host dust-coverity64 --port 8080 --stream "IP Manager trunk" --user jenkins Coverity Defect Commit Client version 6.5.3 on Windows Server 2003, Standard Edition, 32-bit, Service Pack 2 (build 3790) Internal version numbers: 7d3b4ace9c p-davis-push-13307.195 Connecting to server dust-coverity64:9090 2013-06-11 21:43:20 UTC - Committing 584 file descriptions... |0--25---50--75-100| 2013-06-11 21:43:27 UTC - Committing 2 source files... |0--25---50--75-100| 2013-06-11 21:43:21 UTC - Calculating 584 cross-reference bundles... |0--25---50--75-100| 2013-06-11 21:43:29 UTC - Committing 584 cross-reference bundles... |0--25---50--75-100| 2013-06-11 21:43:31 UTC - Committing 2978 functions... |0--25---50--75-100| 2013-06-11 21:43:35 UTC - Committing 18 defect occurrences... |0--25---50--75-100| 2013-06-11 21:43:36 UTC - Committing 3 output files... |0--25---50--75-100| New snapshot ID 10020 added. Elapsed time: 00:00:17 [Coverity] deleting intermediate directory [Coverity] Found snapshot IDs [10020] [Coverity] Fetching defects for stream IP Manager trunk [Coverity] Found 17 defects [Coverity] No defects matched all filters. Environment: Jenkins 1.517, Coverity plugin 1.2.4 Project: Jenkins Priority: Major Reporter: Dave Bacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [envinject] (JENKINS-18297) Can not set PATH environment variable on master node
Dave Bacher created JENKINS-18297 Can not set PATH environment variable on master node Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 11/Jun/13 4:37 PM Description: The PATH environment variable is not set properly on the master. I have tried configuring the PATH variable in: the Manage Jenkins - Configure System - Global Properties. and in the Node Properties - Environment variables section on the master node Configure screen. With a simple job that is tied to the master node and prints the PATH variable, I see only a default-looking PATH=/sbin:/usr/sbin:/bin:/usr/bin. The job does properly print other environment variables that I have configured on the master. I recently upgraded from 1.498 to 1.517 along with many plugins, including EnvInject 1.78 to 1.87. This was not a problem with my previous installation. Downgrading from EnvInject 1.87 to 1.78 resolved the problem. Environment: Jenkins 1.517, envInject 1.87. Master runs on i686 CentOS 5.8. Slave nodes on various CentOS, Redhat and Windows versions. Project: Jenkins Labels: envinject Priority: Major Reporter: Dave Bacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16765) Setting an empty email address in User configuration is not saved
Dave Bacher created JENKINS-16765 Setting an empty email address in User configuration is not saved Issue Type: Bug Assignee: Unassigned Attachments: Jenkins user error.png Components: core Created: 11/Feb/13 7:21 PM Description: I want to disable emails to a particular (automated) user. To do this, I think I can set the user's email address to an empty value. In the User's configuration, I can set the email address to an empty value and press Save, the Save appears to succeed, but the empty value is not saved. Opening the User's configuration again shows the full email address (username@domain). In the User's configuration, if I set the address to an empty value and press Apply, I get an empty error window. In the System Configuration E-mail section, I have a default domain set. If I remove the default domain, I can set the user's email address to an empty value. Environment: master: CentOS 5.8 Project: Jenkins Labels: email Priority: Major Reporter: Dave Bacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows
Dave Bacher created JENKINS-16176 ShiningPanda PATH update uses wrong separator on Windows Issue Type: Bug Assignee: Unassigned Components: shiningpanda Created: 19/Dec/12 10:37 PM Description: When running ShiningPanda on a Windows slave, the plugin (or virtualenv?) updates the PATH to include the virtualenv directory. 0. Install ShiningPanda plugin (this result is for v1.15) 1. Create a build with a Virtualenv build step 2. Use the Shell or XShell command with a minimal script: set pip.exe install -r pkg_requirements.txt The build fails because the pip command can not be found. The output shows the Path environment variable uses the : (colon) separator for the virtualenv Scripts directory. On Windows, the PATH separator should be ; (semicolon). [1-SMSDK-apps-venv] $ cmd.exe /c call C:\DOCUME~1\builder\LOCALS~1\Temp\shiningpanda4030889806584404855.bat c:\jenkins-dev\workspace\1-SMSDK-apps-venvset ... [edited for relevance] ... Path=c:\jenkins-dev\workspace\1-SMSDK-apps-venv:c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9\Scripts:C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\FLEXlm;C:\Program Files\CollabNet\Subversion Client;c:\cygwin\bin;c:\cygwin\usr\bin;C:\Program Files\Java\jre6\bin PYTHON_EXE=c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9\Scripts\python.exe VIRTUAL_ENV=c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9 WORKSPACE=c:\jenkins-dev\workspace\1-SMSDK-apps-venv c:\jenkins-dev\workspace\1-SMSDK-apps-venvpip.exe install -r pkg_requirements.pip 'pip.exe' is not recognized as an internal or external command, operable program or batch file. Environment: Linux master, Windows XP slave with Python 2.7 Project: Jenkins Priority: Major Reporter: Dave Bacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
