[JIRA] (JENKINS-14823) Use environment variables in Target definition
Peter S assigned JENKINS-14823 to Dominik Bartholdi Use environment variables in Target definition Change By: Peter S (17/Aug/12 6:59 AM) Assignee: domi Dominik Bartholdi 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
[JIRA] (JENKINS-14817) Allow to dynamically map filenames on job start from Enviroment variables
Peter S assigned JENKINS-14817 to Dominik Bartholdi Allow to dynamically map filenames on job start from Enviroment variables Change By: Peter S (17/Aug/12 6:59 AM) Assignee: domi Dominik Bartholdi 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
[JIRA] (JENKINS-14839) 'Abort the build if it's stuck' does not work when cloud node has start up problmes
Samu Wikstedt created JENKINS-14839 'Abort the build if it's stuck' does not work when cloud node has start up problmes Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 17/Aug/12 7:13 AM Description: When using EC cloud nodes to execute projects, the option 'Abort the build if it's stuck' does not work for it's original purpose: Making sure that in case of major problem(s) during project execution, project will be put to 'failed' state after certain time: Project's time-count will start after cloud node has been started up, if problem is with starting the EC2 -node, time is never run out, meaning: project won't fail -ever. Could the time-count be started immediately when project starts, regardless if project needs to start cloud node? Project: Jenkins Priority: Minor Reporter: Samu Wikstedt 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
SCM/JIRA link daemon commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Code changed in jenkins User: mgraciano Path: src/main/java/hudson/scm/CVSChangeLogSet.java http://jenkins-ci.org/commit/cvs-plugin/acda8d6d6cc9053f770ae765c497a6396b860b9f Log: JENKINS-14711 - No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
SCM/JIRA link daemon commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Code changed in jenkins User: mgraciano Path: src/main/java/hudson/scm/CVSChangeLogSet.java src/test/java/hudson/scm/CVSChangeLogParserTest.java src/test/resources/hudson/scm/changelogCurrentFormat.xml src/test/resources/hudson/scm/changelogRegression14711.xml http://jenkins-ci.org/commit/cvs-plugin/c990be067a84f6dda9a127dada65e47e0b91ec84 Log: Created tests to verify changelog parsing retrocompatibility for JENKINS-14711 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
SCM/JIRA link daemon commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Code changed in jenkins User: mgraciano Path: src/test/java/hudson/scm/CVSChangeLogSetTest.java http://jenkins-ci.org/commit/cvs-plugin/e50ef5e9abf9f196a4c7e487481c5dcfcac094e9 Log: Created tests to avoid regressions as JENKINS-14711 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
SCM/JIRA link daemon commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Code changed in jenkins User: mc1arke Path: src/main/java/hudson/scm/CVSChangeLogSet.java src/test/java/hudson/scm/CVSChangeLogParserTest.java src/test/java/hudson/scm/CVSChangeLogSetTest.java src/test/resources/hudson/scm/changelogCurrentFormat.xml src/test/resources/hudson/scm/changelogRegression14711.xml http://jenkins-ci.org/commit/cvs-plugin/7b2322db8d83efbef17a4dc1bf1f67931d83f0e2 Log: Merge pull request #14 from mgraciano/master Fix for issue JENKINS-14711 Compare: https://github.com/jenkinsci/cvs-plugin/compare/dd3cbc6479a4...7b2322db8d83 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
[JIRA] (JENKINS-14550) "Checksum mismatch while updating" with Subversion Plugin 1.42
Yury Pukhalsky commented on JENKINS-14550 "Checksum mismatch while updating" with Subversion Plugin 1.42 To add to Chris Simmons' observation. I think it's indeed connected with renaming files. I've seen (and see) it only if the files are renamed in SVN. 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
Michael Clarke resolved JENKINS-14711 as Fixed No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Pull request merged, available in next release Change By: Michael Clarke (17/Aug/12 7:24 AM) Status: Open Resolved Assignee: Michael Clarke Resolution: Fixed 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
[JIRA] (JENKINS-14710) net.sf.json.JSONException: JSONObject["cvspassFile"] not found when saving main configuration
Michael Clarke closed JENKINS-14710 as Cannot Reproduce net.sf.json.JSONException: JSONObject["cvspassFile"] not found when saving main configuration This looks like Jenkins is using an old version of the CVS plugin which is no longer supported. Please make sure you have the latest version installed as I'm unable to replicate this issue with on my installation. Change By: Michael Clarke (17/Aug/12 7:32 AM) Status: Open Closed Assignee: Michael Clarke Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-14550) "Checksum mismatch while updating" with Subversion Plugin 1.42
Chris Withers commented on JENKINS-14550 "Checksum mismatch while updating" with Subversion Plugin 1.42 The specific case we had was when the plugin performed an svn update on trunk that involved a revision where a file was added on a branch and then that branch was merged into trunk. Annoyingly, we had this re-occur recently, even though we're now on what purports to be 1.34. Anyone know how we could upgrade to 1.39? 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
[JIRA] (JENKINS-7894) BuildWithParameters - parameter values disappear if user is not logged in
OHTAKE Tomohiro updated JENKINS-7894 BuildWithParameters - parameter values disappear if user is not logged in Change By: OHTAKE Tomohiro (17/Aug/12 7:52 AM) Assignee: huybrechts OHTAKE Tomohiro Component/s: core Component/s: parameterized-trigger 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
[JIRA] (JENKINS-7894) BuildWithParameters - parameter values disappear if user is not logged in
SCM/JIRA link daemon resolved JENKINS-7894 as Fixed BuildWithParameters - parameter values disappear if user is not logged in Change By: SCM/JIRA link daemon (17/Aug/12 8:04 AM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-7894) BuildWithParameters - parameter values disappear if user is not logged in
SCM/JIRA link daemon commented on JENKINS-7894 BuildWithParameters - parameter values disappear if user is not logged in Code changed in jenkins User: OHTAKE Tomohiro Path: changelog.html core/src/main/java/hudson/security/HudsonAuthenticationEntryPoint.java http://jenkins-ci.org/commit/jenkins/74d2607b8de4df3ecf99effcfe71d66fbbce1694 Log: [FIXED JENKINS-7894] Prevent parameter values from disappearing when user is not logged in 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
[JIRA] (JENKINS-14786) Build.xml file missing for every builds using "Publish Klocwork test result report"
Geoffroy Jabouley updated JENKINS-14786 Build.xml file missing for every builds using "Publish Klocwork test result report" Change By: Geoffroy Jabouley (17/Aug/12 8:31 AM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14786) Build.xml file missing for every builds using "Publish Klocwork test result report"
Geoffroy Jabouley updated JENKINS-14786 Build.xml file missing for every builds using "Publish Klocwork test result report" Change By: Geoffroy Jabouley (17/Aug/12 8:31 AM) Priority: Major Critical 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
[JIRA] (JENKINS-14840) default graph values are not saved
evernat created JENKINS-14840 default graph values are not saved Issue Type: Bug Assignee: Ulli Hafner Attachments: analysis.txt, config.xml Components: analysis-collector, analysis-core Created: 17/Aug/12 9:21 AM Description: With a fresh install of Jenkins 1.477, the following plugins are installed: Static Analysis Utilities (1.43), FindBugs Plug-in (4.42), Warnings Plug-in (4.13), Checkstyle Plug-in (3.29), PMD Plug-in (3.29), Task Scanner Plug-in (4.32), Static Analysis Collector Plug-in (1.29). In a maven job, a combined analysis is configured. Then in the default graph configuration (job/test/analysis/configureDefaults/?), whatever values are written they are not saved when clicking the save button. There is no error displayed in the browser or in the logs. The lastModified tome of the analysis.txt file in the job directory is changed when clicking the save button, but the content is always the same (500!200!50!30!PRIORITY!0). Tested with both firefox and chrome. Environment: Windows XP, Java 1.7.0_05, Jenkins 1.477 Project: Jenkins Priority: Major Reporter: evernat 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
[JIRA] (JENKINS-14840) default graph values are not saved
evernat updated JENKINS-14840 default graph values are not saved analysis.txt and config.xml of the test job attached Change By: evernat (17/Aug/12 9:22 AM) Attachment: config.xml Attachment: analysis.txt 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
[JIRA] (JENKINS-13975) Promoted-builds not following jenkins access control policies
Jose Sa commented on JENKINS-13975 Promoted-builds not following jenkins access control policies Regarding "!anonymous" there is actually a special group in Matrix or Project-Matrix Auth Strategy called "authenticated" that matches any logged-in user as a counterpart of "anonymous" (not logged-in). But it seems you are trying to define yet another Auth layer in each Promote Action. Wich makes sense if you want to override or complement the Authorizations in upper levels (Job or Global). 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
[JIRA] (JENKINS-14786) Build.xml file missing for every builds using "Publish Klocwork test result report"
Geoffroy Jabouley updated JENKINS-14786 Build.xml file missing for every builds using "Publish Klocwork test result report" Have to change the priority as i have deactivated Klocwork plug-in because of this issue. Change By: Geoffroy Jabouley (17/Aug/12 9:27 AM) Priority: Major Blocker 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
[JIRA] (JENKINS-14841) Show Configuration history in job and global config and restore from history
cforce created JENKINS-14841 Show Configuration history in job and global config and restore from history Issue Type: New Feature Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 17/Aug/12 9:31 AM Description: Please checkout https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin which already offers showing, diffing and restoring of locallc baclup job configs. Maybe the plugins can make usage of each other. Project: Jenkins Priority: Major Reporter: cforce 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
[JIRA] (JENKINS-14842) Save config version to scm repo
cforce created JENKINS-14842 Save config version to scm repo Issue Type: New Feature Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 17/Aug/12 9:35 AM Description: There is a plugin https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin which can save all cfg changes to scm but it can't show trhe history , diff adn restore like this plugin does. I created a request for this here: https://issues.jenkins-ci.org/browse/JENKINS-14841 It would be cool if both plugins make use of each other or even merge together, either using local file system or optionally scm to version the changes config files. Project: Jenkins Priority: Major Reporter: cforce 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
[JIRA] (JENKINS-14841) Show Configuration history in job and global config and restore from history
cforce commented on JENKINS-14841 Show Configuration history in job and global config and restore from history see also request on other plugin . https://issues.jenkins-ci.org/browse/JENKINS-14842 It would be cool if both plugins make use of each other or even merge together, either using local file system or optionally scm to version the changes config files. 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
[JIRA] (JENKINS-9175) Changing capitalization of promotion deletes promotion
Sylvain Veyrié commented on JENKINS-9175 Changing capitalization of promotion deletes promotion It have not tested this for a while. It works now with non-ascii on 2.6.2, Jenkins 1.476. 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
[JIRA] (JENKINS-14144) Build config history getting spammed
Hugo Koblmueller edited a comment on JENKINS-14144 Build config history getting spammed any update on this issue? we also can reproduce it, and in combination with the "SCM Sync Configuration Plugin" it is also spamming our SVN. 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
[JIRA] (JENKINS-14144) Build config history getting spammed
Hugo Koblmueller commented on JENKINS-14144 Build config history getting spammed any update on this issue, we also can reproduce it, and in combination with the "SCM Sync Configuration Plugin" it is also spamming our SVN. 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
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
Michel Graciano commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Thanks Michael. 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
[JIRA] (JENKINS-11159) Rake Plugin invocation on windows cannot find rake.bat
Rick Beyer commented on JENKINS-11159 Rake Plugin invocation on windows cannot find rake.bat I'm experiencing this same issue but I only have a Windows node. I even tried moving the rake.bat file into the location it thinks it should be in (and looks for it in) and it still gives me the same error. 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
[JIRA] (JENKINS-14806) Multisite polling finds the same baseline
Christian Wolfgang updated JENKINS-14806 Multisite polling finds the same baseline Change By: Christian Wolfgang (17/Aug/12 12:41 PM) Summary: Multisite polling finds the same baseline times 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
[JIRA] (JENKINS-14843) OpenID SSO should use POST to submit details to google apps endpoint
blongden created JENKINS-14843 OpenID SSO should use POST to submit details to google apps endpoint Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: openid Created: 17/Aug/12 12:40 PM Description: When you have more than roughly 33 google accounts (cross domains) able to access your Jenkins installation you hit googles maximum URL length when the browser is instructed to redirect to the OpenID endpoint. According to http://stackoverflow.com/questions/4957435/got-414-request-uri-too-large-from-google-when-authenticating-using-spring-secur the correct thing to do is POST the data from the browser rather than redirect with it all in the query string. I have half an implementation of this here. I will update this if I ever get it working correctly. Project: Jenkins Priority: Major Reporter: blongden 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
[JIRA] (JENKINS-14806) Multisite polling finds the same baseline
Christian Wolfgang resolved JENKINS-14806 as Fixed Multisite polling finds the same baseline Change By: Christian Wolfgang (17/Aug/12 12:41 PM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14728) Buil-flow jobs fail to load the job history if the envinject plugin is installed
Andrei Ababei commented on JENKINS-14728 Buil-flow jobs fail to load the job history if the envinject plugin is installed I updated to the official 1.67 and the bug is fixed (the history is now displayed). The bad news is that the way it was fixed results in another less serious bug (a chart is missing). I will submit another bug for it shortly. 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
[JIRA] (JENKINS-14656) Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually
Christopher Masto commented on JENKINS-14656 Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually I've been struggling with the same problem for the past couple of days. It seems like both plugins are slightly broken; the Build Pipeline doesn't set up the environment exactly the same for its manually-triggered jobs as an auto-triggered downstream build does: for example, the log doesn't always say Started by upstream project "test_upstream" build number 30 (although sometimes it does, and I haven't figured out the difference). Setting a Run Parameter works consistently but only in one of the two pipelines I created. I think Build Pipelines is a bit buggy but I don't understand enough about the internals to make sense of the symptoms. Looking at build.xml from a manually triggered vs automatically triggered build, the manual one seems to have an amalgam of system configuration, the upstream project's configuration, and the downstream one. It looks wrong to me. Regardless, since the downstream job does always have upstream build information available, Copy Artifact ought to be able to use it. It would be nice to have the option to use a standard Run Parameter rather than the special copy parameter that other plugins don't know how to set. 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
[JIRA] (JENKINS-14844) Author no longer shown in change log after upgrading integrity plugin to 1.15
Ryan Stedman created JENKINS-14844 Author no longer shown in change log after upgrading integrity plugin to 1.15 Issue Type: Bug Affects Versions: current Assignee: Cletus D'Souza Components: integrity-plugin Created: 17/Aug/12 1:35 PM Description: I recently upgraded my Jenkins server from 1.475 to 1.477 and upgraded the installed PTC Integrity plugin from 1.14 to 1.15. After this upgrade the change log for my builds are no longer displaying the author of the change, it just displays "unknown". I verified that the "Omit Author in Change Log" setting was unselected in the project configuration. Prior to upgrading Jenkins and the Integrity plugin, the author was being correctly reported in the change log. Environment: Windows Server 2008 R2 Integrity 10 (10.0.0.140), API Version: 4.11.140 Project: Jenkins Labels: plugin Priority: Major Reporter: Ryan Stedman 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
[JIRA] (JENKINS-14845) Default "SUCCESS" status reported when no results are found is wrong
oscar francois
created JENKINS-14845
Default "SUCCESS" status reported when no results are found is wrong
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Bruno P. Kinoshita
Components:
testlink
Created:
17/Aug/12 1:46 PM
Description:
In the console example below:
"Found 0 test result(s).
Updating TestLink test cases.
No emails were triggered.
Finished: SUCCESS"
we can see that when no test results are found, the test link plug-in reports a "SUCCESS" status. I think it's wrong and a "FAILURE" status should be reported instead.
Fix proposal:
Just adding:
if (report.getTestsTotal()==0) {
build.setResult(Result.FAILURE);
}
in src/main/java/hudson/plugins/testlink/TestLinkBuilder.java
at the end of the perform method is sufficient in my case.
Best Regards,
Oscar
Project:
Jenkins
Priority:
Minor
Reporter:
oscar francois
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
[JIRA] (JENKINS-9175) Changing capitalization of promotion deletes promotion
OHTAKE Tomohiro resolved JENKINS-9175 as Fixed Changing capitalization of promotion deletes promotion Thank you for testing. We can close the issue. Change By: OHTAKE Tomohiro (17/Aug/12 1:51 PM) Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14846) Environment variable doesn't get expanded
Florin Hillebrand
created JENKINS-14846
Environment variable doesn't get expanded
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git, multiple-scms
Created:
17/Aug/12 2:06 PM
Description:
Steps to reproduce:
1. Setup MultiSCM with a git repository
2. Specify ${TEST_BRANCH} as branch specifier
3. Define "job is parameterized" and define the string parameter TEST_BRANCH with a valid branch.
Actual results:
Checks out the last build branch
Expected results:
Check out the branch which was specified by TEST_BRANCH
Environment:
jenkins: 1.477 and 1.472
git: 1.1.21 and 1.1.22
multi-scm: 0.2
Project:
Jenkins
Labels:
git
multiple-scms
Priority:
Major
Reporter:
Florin Hillebrand
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
[JIRA] (JENKINS-9175) Changing capitalization of promotion deletes promotion
Sylvain Veyrié edited a comment on JENKINS-9175 Changing capitalization of promotion deletes promotion I have not tested this for a while. It works now with non-ascii on 2.6.2, Jenkins 1.476. 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
[JIRA] (JENKINS-14847) Apply button not taken into account
Frédéric Camblor created JENKINS-14847 Apply button not taken into account Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 17/Aug/12 2:39 PM Description: Starting from 1.466.1, there is a new "apply" button, in plus of "save" button. scm-sync-configuration is not fired when clicking the apply button. Project: Jenkins Priority: Major Reporter: Frédéric Camblor 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
[JIRA] (JENKINS-14848) switch to using User.getCommitByName() for revision information
Daniel Khodaparast created JENKINS-14848 switch to using User.getCommitByName() for revision information Issue Type: Improvement Assignee: Daniel Khodaparast Components: cvs Created: 17/Aug/12 2:52 PM Description: As a result of work done on JENKINS-11759, there is a potential new function in the User model called getCommitByName. Where applicable, switch from doing User.get() requests to User.getCommitByName(). Project: Jenkins Priority: Major Reporter: Daniel Khodaparast 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
[JIRA] (JENKINS-14850) switch to using User.getCommitByName() for revision information
Daniel Khodaparast created JENKINS-14850 switch to using User.getCommitByName() for revision information Issue Type: Improvement Assignee: Daniel Khodaparast Components: subversion Created: 17/Aug/12 2:52 PM Description: As a result of work done on JENKINS-11759, there is a potential new function in the User model called getCommitByName. Where applicable, switch from doing User.get() requests to User.getCommitByName(). Project: Jenkins Priority: Major Reporter: Daniel Khodaparast 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
[JIRA] (JENKINS-14849) switch to using User.getCommitByName() for revision information
Daniel Khodaparast created JENKINS-14849 switch to using User.getCommitByName() for revision information Issue Type: Improvement Assignee: Daniel Khodaparast Components: git Created: 17/Aug/12 2:52 PM Description: As a result of work done on JENKINS-11759, there is a potential new function in the User model called getCommitByName. Where applicable, switch from doing User.get() requests to User.getCommitByName(). Project: Jenkins Priority: Major Reporter: Daniel Khodaparast 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
[JIRA] (JENKINS-14851) switch to using User.getCommitByName() for revision information
Daniel Khodaparast created JENKINS-14851 switch to using User.getCommitByName() for revision information Issue Type: Improvement Assignee: Daniel Khodaparast Components: mercurial Created: 17/Aug/12 2:52 PM Description: As a result of work done on JENKINS-11759, there is a potential new function in the User model called getCommitByName. Where applicable, switch from doing User.get() requests to User.getCommitByName(). Project: Jenkins Priority: Major Reporter: Daniel Khodaparast 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
[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work
T. Houdayer commented on JENKINS-12418 flexible publish - Parametrized trigger does not work cjo9900, do you fix this issue ? If yes, when do you plan to re-add the parameterized trigger into the Flexible plugin list of available publishers ? 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
[JIRA] (JENKINS-14154) Groovy script can not resolve import classes like hudson.scm.SubversionSCM
jglick commented on JENKINS-14154 Groovy script can not resolve import classes like hudson.scm.SubversionSCM FYI - JENKINS-6068 is the issue in this JIRA instance. 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
[JIRA] (JENKINS-14250) E-mail field is not automatically populated when a git plugin creates new user.
Roger Geere commented on JENKINS-14250 E-mail field is not automatically populated when a git plugin creates new user. I have looked at User.java and it does seem that a default Mailer.UserProperty is created when a new User is created. So I believe the test getProperty(Mailer.UserProperty.class)==null) will always fail. 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
[JIRA] (JENKINS-14605) Simple means to obtain logged in user's id
jglick resolved JENKINS-14605 as Not A Defect Simple means to obtain logged in user's id User.current() works for me, e.g. from Groovy console. Also check Jenkins.getAuthentication(). Remember that these methods are generally only meaningful within the dynamic scope of an HTTP request or CLI command. Use the dev mailing list or IRC if you still have issues. Change By: jglick (17/Aug/12 3:29 PM) Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-12418) flexible publish - Parametrized trigger does not work
cjo9900 commented on JENKINS-12418 flexible publish - Parametrized trigger does not work The fix was to add the functionality to the parameterized trigger, as there is no way that the flexible publish can affect the Dependancies that are created. See Pull request for it. https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17 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
[JIRA] (JENKINS-14852) Campfire plugin fails to send notification
Stephen Jones created JENKINS-14852 Campfire plugin fails to send notification Issue Type: Bug Affects Versions: current Assignee: jenslukowski Components: campfire, plugin Created: 17/Aug/12 4:03 PM Description: When I configure a project with the postbuild action of sending a campfire notification I get the following exception in the console log of the build and no notification is sent to campfire. ERROR: Publisher hudson.plugins.campfire.CampfireNotifier aborted due to exception java.lang.NullPointerException at hudson.plugins.campfire.CampfireNotifier.publish(CampfireNotifier.java:48) at hudson.plugins.campfire.CampfireNotifier.perform(CampfireNotifier.java:80) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632) at hudson.model.Run.run(Run.java:1463) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Project: Jenkins Priority: Major Reporter: Stephen Jones 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
[JIRA] (JENKINS-14853) Global setting for slave prerequisites
Slide-O-Mix created JENKINS-14853 Global setting for slave prerequisites Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: slave-prerequisites Created: 17/Aug/12 4:14 PM Description: It would be nice to have a global slave prerequisite configuration. I need to have the same check for all of my jobs and putting the check in for each job would be a hassle. Project: Jenkins Priority: Minor Reporter: Slide-O-Mix 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
[JIRA] (JENKINS-11025) Allow the build to fail on low coverage
SCM/JIRA link daemon commented on JENKINS-11025 Allow the build to fail on low coverage Code changed in jenkins User: Po-Dar Wang Path: src/main/java/hudson/plugins/cobertura/CoberturaBuildAction.java src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java src/main/java/hudson/plugins/cobertura/MavenCoberturaBuildAction.java src/main/java/hudson/plugins/cobertura/MavenCoberturaPublisher.java src/main/java/hudson/plugins/cobertura/renderers/SourceEncoding.java src/main/java/hudson/plugins/cobertura/targets/CoverageTarget.java src/main/java/hudson/plugins/cobertura/targets/CoverageTree.java src/main/java/hudson/plugins/cobertura/targets/CoverageTreeElement.java src/main/resources/hudson/plugins/cobertura/CoberturaPublisher/config.jelly src/main/resources/hudson/plugins/cobertura/CoberturaPublisher/config.properties src/test/java/hudson/plugins/cobertura/CoverageResultTest.java src/test/resources/hudson/plugins/cobertura/coverage-with-lots-of-data.xml http://jenkins-ci.org/commit/cobertura-plugin/1cef2b6890bf3388e7e80f12bbe8588035049403 Log: Fixed bug: JENKINS-14589 Added Features: JENKINS-11025 JENKINS-8326 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
[JIRA] (JENKINS-14589) Inconsistent delete button.
SCM/JIRA link daemon commented on JENKINS-14589 Inconsistent delete button. Code changed in jenkins User: Po-Dar Wang Path: src/main/java/hudson/plugins/cobertura/CoberturaBuildAction.java src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java src/main/java/hudson/plugins/cobertura/MavenCoberturaBuildAction.java src/main/java/hudson/plugins/cobertura/MavenCoberturaPublisher.java src/main/java/hudson/plugins/cobertura/renderers/SourceEncoding.java src/main/java/hudson/plugins/cobertura/targets/CoverageTarget.java src/main/java/hudson/plugins/cobertura/targets/CoverageTree.java src/main/java/hudson/plugins/cobertura/targets/CoverageTreeElement.java src/main/resources/hudson/plugins/cobertura/CoberturaPublisher/config.jelly src/main/resources/hudson/plugins/cobertura/CoberturaPublisher/config.properties src/test/java/hudson/plugins/cobertura/CoverageResultTest.java src/test/resources/hudson/plugins/cobertura/coverage-with-lots-of-data.xml http://jenkins-ci.org/commit/cobertura-plugin/1cef2b6890bf3388e7e80f12bbe8588035049403 Log: Fixed bug: JENKINS-14589 Added Features: JENKINS-11025 JENKINS-8326 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
[JIRA] (JENKINS-8326) Support for ratcheting
SCM/JIRA link daemon commented on JENKINS-8326 Support for ratcheting Code changed in jenkins User: Po-Dar Wang Path: src/main/java/hudson/plugins/cobertura/CoberturaBuildAction.java src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java src/main/java/hudson/plugins/cobertura/MavenCoberturaBuildAction.java src/main/java/hudson/plugins/cobertura/MavenCoberturaPublisher.java src/main/java/hudson/plugins/cobertura/renderers/SourceEncoding.java src/main/java/hudson/plugins/cobertura/targets/CoverageTarget.java src/main/java/hudson/plugins/cobertura/targets/CoverageTree.java src/main/java/hudson/plugins/cobertura/targets/CoverageTreeElement.java src/main/resources/hudson/plugins/cobertura/CoberturaPublisher/config.jelly src/main/resources/hudson/plugins/cobertura/CoberturaPublisher/config.properties src/test/java/hudson/plugins/cobertura/CoverageResultTest.java src/test/resources/hudson/plugins/cobertura/coverage-with-lots-of-data.xml http://jenkins-ci.org/commit/cobertura-plugin/1cef2b6890bf3388e7e80f12bbe8588035049403 Log: Fixed bug: JENKINS-14589 Added Features: JENKINS-11025 JENKINS-8326 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
[JIRA] (JENKINS-14658) Invalid Percentages
SCM/JIRA link daemon commented on JENKINS-14658 Invalid Percentages Code changed in jenkins User: Po-Dar Wang Path: src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java src/main/java/hudson/plugins/cobertura/CoberturaPublisherTarget.java src/main/java/hudson/plugins/cobertura/targets/CoverageTarget.java http://jenkins-ci.org/commit/cobertura-plugin/9f3026f2513d38ee89945e96b66d1e6dbe26ac9c Log: re-implemented decimal support so that plugin maintains backwards compatibility. Also added improvement so that percentages cannot be > 100% or < 0%. Fixed bug JENKINS-14658 and made improvement JENKINS-14659. Signed-off-by: Po-Dar Wang 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
[JIRA] (JENKINS-14659) More accurent percentages in decimals.
SCM/JIRA link daemon commented on JENKINS-14659 More accurent percentages in decimals. Code changed in jenkins User: Po-Dar Wang Path: src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java src/main/java/hudson/plugins/cobertura/CoberturaPublisherTarget.java src/main/java/hudson/plugins/cobertura/targets/CoverageTarget.java http://jenkins-ci.org/commit/cobertura-plugin/9f3026f2513d38ee89945e96b66d1e6dbe26ac9c Log: re-implemented decimal support so that plugin maintains backwards compatibility. Also added improvement so that percentages cannot be > 100% or < 0%. Fixed bug JENKINS-14658 and made improvement JENKINS-14659. Signed-off-by: Po-Dar Wang 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
[JIRA] (JENKINS-14401) Jenkins throws exception iv version colnumn plugin is disabled.
lata kopalle commented on JENKINS-14401 Jenkins throws exception iv version colnumn plugin is disabled. How do we resolve this, do you have a workaround, i don't mind enabling the plugin back, but not sure how to. I just hit this issue, and it's a blocker for us. 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
[JIRA] (JENKINS-14589) Inconsistent delete button.
sogabe resolved JENKINS-14589 as Fixed Inconsistent delete button. merged. fix in 1.6. Change By: sogabe (17/Aug/12 5:09 PM) Status: In Progress Resolved Resolution: Fixed 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
[JIRA] (JENKINS-11025) Allow the build to fail on low coverage
sogabe resolved JENKINS-11025 as Fixed Allow the build to fail on low coverage merged. fix in 1.6. Change By: sogabe (17/Aug/12 5:10 PM) Status: Reopened Resolved Resolution: Fixed 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
[JIRA] (JENKINS-8326) Support for ratcheting
sogabe resolved JENKINS-8326 as Fixed Support for ratcheting merged. fix in 1.6. Change By: sogabe (17/Aug/12 5:12 PM) Status: In Progress Resolved Resolution: Fixed 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
[JIRA] (JENKINS-14854) Icons and login button not showing up if not logged in after server restart
Sebastien Tardif created JENKINS-14854 Icons and login button not showing up if not logged in after server restart Issue Type: Bug Assignee: Unassigned Components: ui-changes Created: 17/Aug/12 5:15 PM Description: Icon and so also button like to login do not shows up before log-in after system restart. GET /static/e46b443e/images/16x16/blue_anime.gif HTTP/1.1 Host: oxgslcrsa01.oaifield.onasgn.com:8080 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0 Accept: image/png,image/;q=0.8,/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip, deflate Connection: keep-alive Referer: http://oxgslcrsa01.oaifield.onasgn.com:8080/view/QA/job/QA_CREATE_NEW_RELEASE_FROM_LATEST_SIT3_AND_DEPLOY/build?token=ken Cookie: JSESSIONID=12EB977E8E88A21AC71D547BFBEF2702 HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 Content-Length: 1180 Date: Fri, 17 Aug 2012 17:13:59 GMT Connection: close X-RBT-Optimized-By: oxgbevwan01 (RiOS 6.5.4) SC Environment: Windows Project: Jenkins Priority: Major Reporter: Sebastien Tardif 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
[JIRA] (JENKINS-14854) Icons and login button not showing up if not logged in after server restart
Sebastien Tardif commented on JENKINS-14854 Icons and login button not showing up if not logged in after server restart Happens on Jenkins ver. 1.477 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
[JIRA] (JENKINS-14854) Icons and login button not showing up if not logged in after server restart
Sebastien Tardif updated JENKINS-14854 Icons and login button not showing up if not logged in after server restart Change By: Sebastien Tardif (17/Aug/12 5:29 PM) Description: Icon and so also button like to login do not shows up before log-in after system restart.GET /static/e46b443e/images/16x16/blue_anime.gif HTTP/1.1Host: oxgslcrsa01.oaifield.onasgn.com:8080User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0Accept: image/png,image/*;q=0.8,*/*;q=0.5Accept-Language: en-us,en;q=0.5Accept-Encoding: gzip, deflateConnection: keep-aliveReferer: http://oxgslcrsa01.oaifield.onasgn.com:8080/view/QA/job/QA_CREATE_NEW_RELEASE_FROM_LATEST_SIT3_AND_DEPLOY/build?token=kenCookie: JSESSIONID=12EB977E8E88A21AC71D547BFBEF2702HTTP/1.1 500 Internal Server ErrorServer: Apache-Coyote/1.1Content-Type: text/html;charset=utf-8Content-Length: 1180Date: Fri, 17 Aug 2012 17:13:59 GMTConnection: closeX-RBT-Optimized-By: oxgbevwan01 (RiOS 6.5.4) SC SEVERE: Servlet.service() for servlet [Stapler] in context with path [] threw exceptionjava.lang.NullPointerException at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:50) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) 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:63) 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 hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterCh
[JIRA] (JENKINS-14854) Icons and login button not showing up if not logged in after server restart
Sebastien Tardif updated JENKINS-14854 Icons and login button not showing up if not logged in after server restart Change By: Sebastien Tardif (17/Aug/12 5:30 PM) Component/s: greenballs Component/s: ui-changes 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
[JIRA] (JENKINS-14848) switch to using User.getByCommitName() for revision information
Daniel Khodaparast updated JENKINS-14848 switch to using User.getByCommitName() for revision information Change By: Daniel Khodaparast (17/Aug/12 5:52 PM) Summary: switch to using User. getCommitByName getByCommitName () for revision information Description: As a result of work done on JENKINS-11759, there is a potential new function in the User model called getCommitByName getByCommitName . Where applicable, switch from doing User.get() requests to User. getCommitByName getByCommitName (). 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
[JIRA] (JENKINS-14849) switch to using User.getByCommitName() for revision information
Daniel Khodaparast updated JENKINS-14849 switch to using User.getByCommitName() for revision information Change By: Daniel Khodaparast (17/Aug/12 5:52 PM) Summary: switch to using User. getCommitByName getByCommitName () for revision information Description: As a result of work done on JENKINS-11759, there is a potential new function in the User model called getCommitByName getByCommitName . Where applicable, switch from doing User.get() requests to User. getCommitByName getByCommitName (). 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
[JIRA] (JENKINS-14850) switch to using User.getByCommitName() for revision information
Daniel Khodaparast updated JENKINS-14850 switch to using User.getByCommitName() for revision information Change By: Daniel Khodaparast (17/Aug/12 5:52 PM) Summary: switch to using User. getCommitByName getByCommitName () for revision information Description: As a result of work done on JENKINS-11759, there is a potential new function in the User model called getCommitByName getByCommitName . Where applicable, switch from doing User.get() requests to User. getCommitByName getByCommitName (). 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
[JIRA] (JENKINS-14851) switch to using User.getByCommitName() for revision information
Daniel Khodaparast updated JENKINS-14851 switch to using User.getByCommitName() for revision information Change By: Daniel Khodaparast (17/Aug/12 5:53 PM) Summary: switch to using User. getCommitByName getByCommitName () for revision information Description: As a result of work done on JENKINS-11759, there is a potential new function in the User model called getCommitByName getByCommitName . Where applicable, switch from doing User.get() requests to User. getCommitByName getByCommitName (). 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
[JIRA] (JENKINS-8753) ROADMAP: Improve Build Chaining / Workflow
Shai Ben-Hur commented on JENKINS-8753 ROADMAP: Improve Build Chaining / Workflow check out this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Template+Workflows+Plugin 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
[JIRA] (JENKINS-11159) Rake Plugin invocation on windows cannot find rake.bat
Rick Beyer commented on JENKINS-11159 Rake Plugin invocation on windows cannot find rake.bat I was able to work around this issue by downloading the source code and manually creating my own RubyInstallation within Rake.java The RubyInstallation rake object was never being created (was always null). 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
[JIRA] (JENKINS-14539) Incorrectly Using Committer User Full Name in resolving Committer Email Address
rejesi commented on JENKINS-14539 Incorrectly Using Committer User Full Name in resolving Committer Email Address I don't quite understand what you mean by "MailAddressResolver implementation for plugins". May I ask from whom I am to get resolution for this issue? I have noted the plugins in use and believe it is from the Git plugin since you indicate it is not an email-ext issue. But as I am new to Jenkins I do not understand how to present this issue to any of the other plugin owners. I don't even know how it went to email-ext as opposed to Git or Jenkins or all. I would truly appreciate any help or direction in this matter as I don't want it closed until it is fixed. Thanks much 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
[JIRA] (JENKINS-14831) Environment setup fails & unable to build Jenkins
sogabe updated JENKINS-14831 Environment setup fails & unable to build Jenkins removed github from component. Change By: sogabe (17/Aug/12 7:31 PM) Component/s: github 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
[JIRA] (JENKINS-14855) Repo Build Code Changes not Identified When Job Config is Modified
rejesi created JENKINS-14855 Repo Build Code Changes not Identified When Job Config is Modified Issue Type: Bug Assignee: Nicolas De Loof Components: git, repo Created: 17/Aug/12 7:57 PM Description: It seems that every time a build job configuration is modified, the code list changes cannot be identified for the first build after the modification. The Jenkins repo plugin seems to be failing to properly parse and record all the changes that trigger a build. Either that or not all commits are showing up in the log In place of changes, the message 'Failed to determine' is displayed with a link to the log. Looking at the log does not reveal any errors or stack traces. Environment: Linux RHEL server Linux Ubuntu slave agents Linux RHEL slave agents Jenkins 1.472 Repo 1.2.1 Git 1.1.21 Project: Jenkins Labels: plugin configuration jenkins Priority: Major Reporter: rejesi 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
[JIRA] (JENKINS-14539) Incorrectly Using Committer User Full Name in resolving Committer Email Address
Slide-O-Mix commented on JENKINS-14539 Incorrectly Using Committer User Full Name in resolving Committer Email Address When a username only is sent to email-ext, it calls into something provided by the core to resolve that username to an email address. Plugins can implement their own address resolver. It sounds like the git plugin is what is resolving the address. 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
[JIRA] (JENKINS-14856) Slave Registered Remote Controls not identified in Jenkins Selenium Grid
rejesi
created JENKINS-14856
Slave Registered Remote Controls not identified in Jenkins Selenium Grid
Issue Type:
Bug
Affects Versions:
current
Assignee:
Kohsuke Kawaguchi
Components:
selenium
Created:
17/Aug/12 8:20 PM
Description:
I was attempting to rename the newest selenium-server-standalone-*.jar to replace the older one (as per some of the users posts).
When I restarted the Jenkins server, the Selenium Grid page shows that the jenkins.nodeName is null for all of the connected remote contols clients (as shown below)
{seleniumProtocol=Selenium, browserName=*firefox, maxInstances=5, jenkins.nodeName=}
I put everything back the way it was, but this problem still exists, and the process for the hudson.remoting.Launcher of the selenium-server-standalone-*.jar is not running on the agents.
Everything says that it should automatically configure and start when the Jenkins server is restarted.
Environment:
Linux RHEL server
Linux Ubuntu slave agent remote client
Project:
Jenkins
Priority:
Major
Reporter:
rejesi
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
[JIRA] (JENKINS-14539) Incorrectly Using Committer User Full Name in resolving Committer Email Address
rejesi commented on JENKINS-14539 Incorrectly Using Committer User Full Name in resolving Committer Email Address Is there anyway to move this issue over to the git plugin people or do I have to recreate another one. Please excuse my ignorance in this process, I still don't understand how this went to the email-ext plugin issue queue and nowhere else. 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
[JIRA] (JENKINS-14539) Incorrectly Using Committer User Full Name in resolving Committer Email Address
Slide-O-Mix commented on JENKINS-14539 Incorrectly Using Committer User Full Name in resolving Committer Email Address You put email-ext as one of the components. You just need to change the components that the issue deals with. There is an auto-complete box for the components, so find the one that matches that plugin you are using for git. 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
[JIRA] (JENKINS-14857) Android Lint Plugin does nothing
Paul Davis created JENKINS-14857 Android Lint Plugin does nothing Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Components: android-lint Created: 17/Aug/12 10:56 PM Description: The plugin does nothing. It doesn't contribute to the logged output, it doesn't add the link to the menu. The only mention in the Jenkins log is from the install: WARNING: Adding dependent install of analysis-core for plugin android-lint INFO: Attempting to dynamic load /var/lib/jenkins/plugins/android-lint.jpi INFO: Plugin android-lint dynamically installed Environment: Android Lint Plugin version 1.0.1 Static Analysis Utilities 1.43 Jenkins version 1.477 Project: Jenkins Priority: Major Reporter: Paul Davis 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
[JIRA] (JENKINS-14648) Allow to GitHub Plugin to work with Standalone GitHub Enterprise
sogabe resolved JENKINS-14648 as Duplicate Allow to GitHub Plugin to work with Standalone GitHub Enterprise Change By: sogabe (18/Aug/12 12:10 AM) Status: Open Resolved Resolution: Duplicate 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
[JIRA] (JENKINS-13726) Github plugin should work with Guthub enterprise by allowing for overriding the github URL
sogabe commented on JENKINS-13726 Github plugin should work with Guthub enterprise by allowing for overriding the github URL Github plugin uses "configure" -> "Source Code Management" -> "Git" -> "Repository URL" as a github URL. try to configure it. if not, attach log file. 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
[JIRA] (JENKINS-14401) Jenkins throws exception iv version colnumn plugin is disabled.
sogabe commented on JENKINS-14401 Jenkins throws exception iv version colnumn plugin is disabled. try as follows. 1) enable Version Column plugin. 2) make nodes online. 3) then disable the plugin. 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
[JIRA] (JENKINS-14539) Incorrectly Using Committer User Full Name in resolving Committer Email Address
rejesi reopened JENKINS-14539 Incorrectly Using Committer User Full Name in resolving Committer Email Address Changing the component to Git for possible resolution as the issue is not with email-ext Change By: rejesi (18/Aug/12 4:47 AM) Resolution: Not A Defect Status: Closed Reopened Assignee: Slide-O-Mix 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
[JIRA] (JENKINS-14539) Incorrectly Using Committer User Full Name in resolving Committer Email Address
rejesi updated JENKINS-14539 Incorrectly Using Committer User Full Name in resolving Committer Email Address Change By: rejesi (18/Aug/12 4:49 AM) Component/s: email-ext 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
