[JIRA] (JENKINS-12774) SCM sync configuration plugin crashes jenkins
[ https://issues.jenkins-ci.org/browse/JENKINS-12774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159082#comment-159082 ] Martin Hans commented on JENKINS-12774: --- I use the latest jenkins, version 1.451. The log output is as follows: Feb 15, 2012 9:16:08 AM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness initializeRepository INFO: SCM repository initialization done. Feb 15, 2012 9:16:08 AM hudson.plugins.scm_sync_configuration.SCMManipulator FINE: Checkouted SCM files into [/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration] ! Feb 15, 2012 9:16:07 AM hudson.plugins.scm_sync_configuration.SCMManipulator FINE: Checkouting SCM files into [/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration] ... Feb 15, 2012 9:16:07 AM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness initializeRepository INFO: Initializing SCM repository for scm-sync-configuration plugin ... Feb 15, 2012 9:16:07 AM hudson.plugins.scm_sync_configuration.scms.SCM getConfiguredRepository INFO: Populating credentials data into SCM repository object ... Feb 15, 2012 9:16:07 AM hudson.plugins.scm_sync_configuration.scms.SCM getConfiguredRepository INFO: Populating host data into SCM repository object ... Feb 15, 2012 9:16:07 AM hudson.plugins.scm_sync_configuration.scms.SCM getConfiguredRepository INFO: Creating SCM repository object for url : scm:svn:svn+ssh://linuxsrv01/usr/local/svnroot/trunk/jenkins-config/ Feb 15, 2012 9:16:07 AM hudson.plugins.scm_sync_configuration.scms.SCM FINE: Extracted realm from svn+ssh://linuxsrv01/usr/local/svnroot/trunk/jenkins-config/ is [svn+ssh://linuxsrv01] Feb 15, 2012 9:16:07 AM hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM extractScmCredentials INFO: Extracting SVN Credentials for url : svn+ssh://linuxsrv01/usr/local/svnroot/trunk/jenkins-config/ Feb 15, 2012 9:16:07 AM hudson.plugins.scm_sync_configuration.SCMManipulator scmConfigurationSettledUp INFO: Creating scmRepository connection data .. But it looks like it contains only the log entries since the latest start of jenkins. How can I get the log from the PREVIOUS session of jenkins which might possibly contain some information about the crash? SCM sync configuration plugin crashes jenkins - Key: JENKINS-12774 URL: https://issues.jenkins-ci.org/browse/JENKINS-12774 Project: Jenkins Issue Type: Bug Components: scm-sync-configuration Affects Versions: current Environment: SCM sync plugin verion 0.0.4 Reporter: Martin Hans Assignee: fcamblor Priority: Critical Whenever I have the SCM sync plugin installed, jenkins crashes a couple of minutes after starting up. If I disable the plugin, jenkins keeps running. What information should I provide to help debug this issue? -- 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-12330) Occasionally,collecting findbugs analysis files will take very long time, event two more hours.
[ https://issues.jenkins-ci.org/browse/JENKINS-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159084#comment-159084 ] roger four commented on JENKINS-12330: -- About 14,000 more warnings Occasionally,collecting findbugs analysis files will take very long time, event two more hours. --- Key: JENKINS-12330 URL: https://issues.jenkins-ci.org/browse/JENKINS-12330 Project: Jenkins Issue Type: Bug Components: findbugs Affects Versions: current Environment: ubuntu 10.04 LTS Reporter: roger four Assignee: Ulli Hafner Labels: plugin Occasionally,I found findbugs will take very long time to analysis files.Some time it will take two more hours. Just stop at: [FINDBUGS] Collecting findbugs analysis files... And I had to kill the process. It bothers me very much.Pls help me. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12613) Plugin status is shown even though now thresholds are defined
[
https://issues.jenkins-ci.org/browse/JENKINS-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159087#comment-159087
]
SCM/JIRA link daemon commented on JENKINS-12613:
Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/analysis/core/HealthAwareReporter.java
http://jenkins-ci.org/commit/analysis-core-plugin/66906e68149a4459e588b60e1b79fc5ffe500707
Log:
[FIXED JENKINS-12613] Don't set build status unless thresholds are
defined.
Compare:
https://github.com/jenkinsci/analysis-core-plugin/compare/0327725...66906e6
Plugin status is shown even though now thresholds are defined
-
Key: JENKINS-12613
URL: https://issues.jenkins-ci.org/browse/JENKINS-12613
Project: Jenkins
Issue Type: Bug
Components: analysis-core
Reporter: Ulli Hafner
Assignee: Ulli Hafner
In Maven jobs the following result summary is shown, when there is no
threshold defined.
{noformat}
Plug-in Result:Success (Reference build: #28)
New highscore: only successful builds since yesterday!
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12613) Plugin status is shown even though now thresholds are defined
[
https://issues.jenkins-ci.org/browse/JENKINS-12613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159093#comment-159093
]
dogfood commented on JENKINS-12613:
---
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[plugins_analysis-core
#10407|http://ci.jenkins-ci.org/job/plugins_analysis-core/10407/]
[FIXED JENKINS-12613] Don't set build status unless thresholds are
(Revision 66906e68149a4459e588b60e1b79fc5ffe500707)
Result = SUCCESS
Ulli Hafner :
Files :
* src/main/java/hudson/plugins/analysis/core/HealthAwareReporter.java
Plugin status is shown even though now thresholds are defined
-
Key: JENKINS-12613
URL: https://issues.jenkins-ci.org/browse/JENKINS-12613
Project: Jenkins
Issue Type: Bug
Components: analysis-core
Reporter: Ulli Hafner
Assignee: Ulli Hafner
In Maven jobs the following result summary is shown, when there is no
threshold defined.
{noformat}
Plug-in Result:Success (Reference build: #28)
New highscore: only successful builds since yesterday!
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11718) Initial job build should ignore 'new warnings' threshold
[ https://issues.jenkins-ci.org/browse/JENKINS-11718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159092#comment-159092 ] dogfood commented on JENKINS-11718: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_analysis-core #10407|http://ci.jenkins-ci.org/job/plugins_analysis-core/10407/] [FIXED JENKINS-11718] Don't evaluate new warnings when there is (Revision 3fd140495752b3a7e2e04f87d7d76aab37e8a7ea) Result = SUCCESS Ulli Hafner : Files : * src/main/java/hudson/plugins/analysis/core/BuildResultEvaluator.java * src/main/java/hudson/plugins/analysis/core/BuildResult.java * src/main/java/hudson/plugins/analysis/core/ParserResult.java Initial job build should ignore 'new warnings' threshold Key: JENKINS-11718 URL: https://issues.jenkins-ci.org/browse/JENKINS-11718 Project: Jenkins Issue Type: Improvement Components: analysis-core Reporter: kutzi Assignee: Ulli Hafner Priority: Minor When I import a project with existing warnings - e.g. compiler errors and have the new compiler warnings threshold set to e.g. 1, my initial build will be unstable/failed and I never have the chance to get it stable. Would be nice if the 'new warnings' thresholds could be ignored for the 1st 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-11758) Real 'Use delta for new warnings' value is not shown in UI
[ https://issues.jenkins-ci.org/browse/JENKINS-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159096#comment-159096 ] dogfood commented on JENKINS-11758: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_analysis-core #10407|http://ci.jenkins-ci.org/job/plugins_analysis-core/10407/] [FIXED JENKINS-11758] Added useDeltaValues to public API of reporter. (Revision 99c666e5e9f0bd7a9ee85994b56381c984a3c027) Result = SUCCESS Ulli Hafner : Files : * src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java * src/main/java/hudson/plugins/analysis/core/HealthAwareReporter.java Real 'Use delta for new warnings' value is not shown in UI -- Key: JENKINS-11758 URL: https://issues.jenkins-ci.org/browse/JENKINS-11758 Project: Jenkins Issue Type: Bug Components: checkstyle, findbugs Environment: FindBugs plugin 4.30, Checkstyle plugin 3.21 Reporter: kutzi Assignee: Ulli Hafner The Use delta for new warnings checkbox is always shown disabled when opening the config page. Changes to it seem to be persisted, though. However this is still bad, as all other unrelated changes to the config will disable the setting, again. -- 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-12142) Task plugin logs each time it doesn't have to do anything
[
https://issues.jenkins-ci.org/browse/JENKINS-12142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159097#comment-159097
]
dogfood commented on JENKINS-12142:
---
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[plugins_analysis-core
#10407|http://ci.jenkins-ci.org/job/plugins_analysis-core/10407/]
[FIXED JENKINS-12142] Removed logging statement if reporter already has
(Revision c7639199cbb31009bd68e98c0a909f3001dbd789)
Result = SUCCESS
Ulli Hafner :
Files :
* src/main/java/hudson/plugins/analysis/core/HealthAwareReporter.java
Task plugin logs each time it doesn't have to do anything
-
Key: JENKINS-12142
URL: https://issues.jenkins-ci.org/browse/JENKINS-12142
Project: Jenkins
Issue Type: Improvement
Components: tasks-plugin
Environment: Task Scanner Plugin 4.24
Reporter: kutzi
Assignee: Ulli Hafner
Priority: Minor
The plugin logs - for my taste - a little bit too verbose that it doesn't
have do anything:
10:10:49 [INFO] [clean:clean {execution: default-clean}]
10:10:49 [INFO] Deleting xyz
10:15:37 [TASKS] Scanning folder 'xyz' for files matching the pattern
'**/*.java'
[TASKS] Found 0 files to scan for tasks 10:15:37 Found 0 open tasks.
10:15:37 [TASKS] Using set difference to compute new warnings 10:15:37
[TASKS] Not changing build status, since no threshold has been exceeded
10:15:37[INFO] Preparing source:jar
10:15:39 [INFO] [buildnumber:create {execution: default-execution-id}]
...
10:15:39 [TASKS] Skipping maven reporter: there is already a result available.
10:15:40 [JENKINS] Archiving disabled - not archiving xyz
10:15:40 [INFO] [source:jar {execution: default-cli}]
10:15:40 [TASKS] Skipping maven reporter: there is already a result available.
10:15:40 [INFO] [architecture-rules:check-rules {execution: default}]
10:15:40 [TASKS] Skipping maven reporter: there is already a result available.
10:15:40 [INFO] [buildnumber:create {execution: default-execution-id}]
10:15:40 [TASKS] Skipping maven reporter: there is already a result available.
10:15:40 [debug] execute contextualize
I.e. it seems to log for each mojo execution - after the 1st - on each module
that it doesn't have to do anything anymore.
Could you remove these please as they IMHO only unnecessary inflate the build
console?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8185) Exception in WarningsPlugin
[ https://issues.jenkins-ci.org/browse/JENKINS-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-8185. -- Resolution: Fixed Fixed in flexible-publisher plug-in, see JENKINS-12692. Exception in WarningsPlugin --- Key: JENKINS-8185 URL: https://issues.jenkins-ci.org/browse/JENKINS-8185 Project: Jenkins Issue Type: Bug Components: template-project Affects Versions: current Environment: Linux, Hudson v1.386, Warnings plugin v3.11 Reporter: ingmartinlopez Assignee: huybrechts Builds are finishing with a failure result, and the following exception is being shown: [WARNINGS] Parsing warnings in console log... ERROR: Publisher hudson.plugins.warnings.WarningsPublisher 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:522) at hudson.plugins.analysis.core.AbstractHealthDescriptor.init(AbstractHealthDescriptor.java:36) at hudson.plugins.warnings.WarningsHealthDescriptor.init(WarningsHealthDescriptor.java:25) at hudson.plugins.warnings.WarningsResultAction.init(WarningsResultAction.java:31) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:202) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:280) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:603) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:582) at hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:651) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:529) at hudson.model.Run.run(Run.java:1349) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:349) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:139) If I disable the warnings publisher from the job configuration, the build ends successfully. Here is the config section of the warnings plugin of the job: hudson.plugins.warnings.WarningsPublisher pluginName[WARNINGS] /pluginName defaultEncoding/defaultEncoding canRunOnFailedfalse/canRunOnFailed useDeltaValuesfalse/useDeltaValues thresholds unstableTotalHigh/unstableTotalHigh unstableTotalNormal/unstableTotalNormal unstableTotalLow/unstableTotalLow unstableNewHigh/unstableNewHigh unstableNewNormal/unstableNewNormal unstableNewLow/unstableNewLow failedTotalHigh/failedTotalHigh failedTotalNormal/failedTotalNormal failedTotalLow/failedTotalLow failedNewHigh/failedNewHigh failedNewNormal/failedNewNormal failedNewLow/failedNewLow /thresholds pattern/pattern parserNames stringJava Compiler/string /parserNames ignoreConsolefalse/ignoreConsole /hudson.plugins.warnings.WarningsPublisher -- 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-12735) No upstream or downstream resolution with Maven version ranges
[ https://issues.jenkins-ci.org/browse/JENKINS-12735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159101#comment-159101 ] Alex Koon commented on JENKINS-12735: - I have submitted a pull request for this now - #374. No upstream or downstream resolution with Maven version ranges -- Key: JENKINS-12735 URL: https://issues.jenkins-ci.org/browse/JENKINS-12735 Project: Jenkins Issue Type: Bug Components: maven Affects Versions: current Reporter: Alex Koon This is essentially reopening JENKINS-2787 (https://issues.jenkins-ci.org/browse/JENKINS-2787). We are in an environment where we do have version ranges and ignoring the arguments for or against version ranges, we like to resolve this issue. I have looked at the patch provided in JENKINS-2787 and have integrated this into the latest 1.450 of jenkins and running this in our CI environment. What would be required to submit this latest patch to Jenkins and have this promoted? -- 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-12776) Add git commit date and author to build environmentg
Brian Preuß created JENKINS-12776: - Summary: Add git commit date and author to build environmentg Key: JENKINS-12776 URL: https://issues.jenkins-ci.org/browse/JENKINS-12776 Project: Jenkins Issue Type: Improvement Components: git Reporter: Brian Preuß Assignee: abayer Please add the git commit date and author to the build environment (GIT_COMMIT as sha hash and GIT_BRANCH as branch are already there) -- 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-12777) Publish N'SIQ Collector is not visible for Multi configuration jobs
Prashanth K created JENKINS-12777: - Summary: Publish N'SIQ Collector is not visible for Multi configuration jobs Key: JENKINS-12777 URL: https://issues.jenkins-ci.org/browse/JENKINS-12777 Project: Jenkins Issue Type: Improvement Components: nsiqcollector Affects Versions: current Reporter: Prashanth K Assignee: junoyoon When trying to configure NSIQ collector plugin for multiconfiguration projects, the option is not available although the plugin is installed. The same is available under Free style project. Is there any special configuration needed to enable this option in Multi configuration projects. -- 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-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159102#comment-159102 ] Roland Zwaga commented on JENKINS-11381: Is there some sort of ETA for this fix? I have quite a few projects that can no longer be built by Jenkins. I understand OS work is mostly done in people's spare time, but a rough estimate of when this can be fixed would be really appreciated. Thanks a lot in advance. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- 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-12632) Subversion plugin update fails
[ https://issues.jenkins-ci.org/browse/JENKINS-12632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] C. S. updated JENKINS-12632: Component/s: cvs Subversion plugin update fails -- Key: JENKINS-12632 URL: https://issues.jenkins-ci.org/browse/JENKINS-12632 Project: Jenkins Issue Type: Bug Components: cvs, plugin, subversion, update-center Environment: Jenkins 1.450 CentOS 6.2 (2.6.32-220.4.1.el6.centos.plus.x86_64) java version 1.6.0_29 Java(TM) SE Runtime Environment (build 1.6.0_29-b11) Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode) Reporter: Paul Milliken Labels: jenkins, plugin I'm encountering an issue similar to JENKINS-12514 with Jenkins 1.450. Update manager reports that I'm running subversion plugin 1.34 and 1.37 is available. In my plugins folder I can see: -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.jpi I tell Jenkins to install 1.37. Once it's downloaded I can see: -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak -rw-rw-r--. 1 jenkins jenkins 2103308 Feb 2 15:43 subversion.jpi Checking the manifests: [jenkins@ plugins]$ unzip -p subversion.bak META-INF/MANIFEST.MF | grep Plugin-Version Plugin-Version: 1.34 [jenkins@ plugins]$ unzip -p subversion.jpi META-INF/MANIFEST.MF | grep Plugin-Version Plugin-Version: 1.37 Restart jenkins to apply the changes. At this point, the present files are: -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.bak -rw-rw-r--. 1 jenkins jenkins 2105983 Feb 2 15:20 subversion.jpi and the manifests: [jenkins@ plugins]$ unzip -p subversion.bak META-INF/MANIFEST.MF | grep Plugin-Version Plugin-Version: 1.34 [jenkins@ plugins]$ unzip -p subversion.jpi META-INF/MANIFEST.MF | grep Plugin-Version Plugin-Version: 1.34 And update manager still reports 1.34 with 1.37 available. -- 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-12778) Extend touchstone functionality to allow for multiple touchstones
Thorsten Möllers created JENKINS-12778: -- Summary: Extend touchstone functionality to allow for multiple touchstones Key: JENKINS-12778 URL: https://issues.jenkins-ci.org/browse/JENKINS-12778 Project: Jenkins Issue Type: New Feature Components: matrix Reporter: Thorsten Möllers Since I have to support a constantly/rapidly changing set of branches, each supporting a couple of platforms, I want to be able to have only one matrix per branch job to do all builds/tests per branch. To achieve this efficiently, I need to be able to configure the matrix job to 1. build main targets for all supported platforms 2. If 1 succeeds, run unit test for all supported platforms 3. If 2 succeeds, build additional test tools for more extensive tests3 4. If 3 succeeds, run tests for all supported platforms For this I need to be able to define different touchstones for each of the steps. -- 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:comment-tabpanelfocusedCommentId=159104#comment-159104 ] SCM/JIRA link daemon commented on JENKINS-7733: --- Code changed in jenkins User: Seiji Sogabe Path: core/src/main/java/hudson/model/MyViewsProperty.java core/src/main/java/hudson/model/TreeView.java core/src/main/java/hudson/model/View.java core/src/main/java/hudson/model/ViewGroup.java core/src/main/resources/lib/hudson/editableDescription.jelly http://jenkins-ci.org/commit/jenkins/875b3f628b9127661a3b84945df30bcaf66f3534 Log: [FIXED JENKINS-7733] reimplementation of JENKINS-7733. 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 Assignee: sogabe 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-12693) urltrigger cannot start: claims bad major version at offset=6
[
https://issues.jenkins-ci.org/browse/JENKINS-12693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159105#comment-159105
]
torbent commented on JENKINS-12693:
---
OK. Are we at a point where this issue should be closed as won't fix?
urltrigger cannot start: claims bad major version at offset=6
---
Key: JENKINS-12693
URL: https://issues.jenkins-ci.org/browse/JENKINS-12693
Project: Jenkins
Issue Type: Bug
Components: urltrigger
Environment: Jenkins 1.445, urltrigger 0.10
Reporter: torbent
Assignee: gbois
Attachments: 2012-02-09-urltrigger-major-version.txt.txt
The urltrigger plugin refuses to start, gives a stacktrace where this seems
to be the interesting part:
{quote}Caused by: java.lang.UnsupportedClassVersionError:
(com/sun/jersey/api/client/config/ClientConfig) bad major version at offset=6
{quote}
Full log attached. I'm not able to test newer releases at the moment, because
Jenkins 1.446 does not work for me and the latest urltrigger is built as a
.jpi which Jenkins doesn't support until 1.448.
--
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-4960) Use same SCM checkout for all matrix entries
[ https://issues.jenkins-ci.org/browse/JENKINS-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159106#comment-159106 ] Thorsten Möllers commented on JENKINS-4960: --- I updated the patch (patch.diff from January 11th 2010) to current version of Jenkins and created a pull request accordingly: https://github.com/jenkinsci/jenkins/pull/375/commits I need this feature badly, since I have to support a huge repository with a rapidly changing set of branches for a fast growing number of platforms. Use same SCM checkout for all matrix entries Key: JENKINS-4960 URL: https://issues.jenkins-ci.org/browse/JENKINS-4960 Project: Jenkins Issue Type: Improvement Components: matrix Affects Versions: current Environment: Platform: All, OS: All Reporter: asolsson Priority: Critical Attachments: matrix_update.diff, patch.diff, useSameScmCheckout.diff I've implemented an enhancement to the matrix project to avoid a SCM checkout for each target in the matrix. This can be useful if checkout takes a long time and if the build step can build concurrent builds from the same SCM area. It's implemented as a option when setting up the Matrix project, if not used/checked the Matrix project will work as usual. -- 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-12781) Jenkins hangs after printing Recording test results
[ https://issues.jenkins-ci.org/browse/JENKINS-12781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159110#comment-159110 ] Matti Linnanvuori commented on JENKINS-12781: - I stopped the job and Jenkins wrote the following to Console Output: ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:127) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:747) at hudson.FilePath.act(FilePath.java:740) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:83) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:122) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:134) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:668) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:646) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:615) at hudson.model.Run.run(Run.java:1401) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Jenkins hangs after printing Recording test results --- Key: JENKINS-12781 URL: https://issues.jenkins-ci.org/browse/JENKINS-12781 Project: Jenkins Issue Type: Bug Components: junit Environment: Debian GNU/Linux 6.0 Linux 2.6.32-5-xen-amd64 Reporter: Matti Linnanvuori Jenkins hangs after printing Recording test results. It has been in that state almost an hour now. Jenkins version 1.430 Full thread dump OpenJDK 64-Bit Server VM (14.0-b16 mixed mode): pool-25-thread-7394 prio=10 tid=0x7f8c588fd800 nid=0x1a85 waiting on condition [0x7f8c7084f000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for 0x7f8c996391f0 (a java.util.concurrent.SynchronousQueue$TransferStack) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:453) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:352) at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:903) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) pool-25-thread-7393 prio=10 tid=0x7f8c588fc000 nid=0x1a84 waiting on condition [0x7f8c7064d000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for 0x7f8c996391f0 (a java.util.concurrent.SynchronousQueue$TransferStack) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:453) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:352) at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:903) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1043) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1103) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) pool-25-thread-7392 prio=10 tid=0x7f8c587e6000 nid=0x1a83 waiting on condition [0x7f8c726c2000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for 0x7f8c996391f0 (a java.util.concurrent.SynchronousQueue$TransferStack) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:453) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:352) at
Re: [JIRA] (JENKINS-12758) Jenkins looses build data on restart
I have the same issue, after upgrading to 1.451 windows package , I lost All my Job data. For me a 404 error reported at start up and as per one suggestion I restarted using diff port 12080 and its started up fine but none of the jobs are restarted. Can you please le t me know how to Reload data manually - Thanks, Jagan Kalluri -- View this message in context: http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-12758-Jenkins-looses-build-data-on-restart-tp4387048p4390606.html Sent from the Jenkins issues mailing list archive at Nabble.com.
[JIRA] (JENKINS-12720) CC_BASELINE doesn't update value
[ https://issues.jenkins-ci.org/browse/JENKINS-12720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159122#comment-159122 ] Tim Collier commented on JENKINS-12720: --- I am re-running the build after removing the parameter from the predefined parameters and just passing it as part of the current build parameters It might be that predefined are eveluated once upon setup and current passes the current value. It's a guess, but might make sense. CC_BASELINE doesn't update value Key: JENKINS-12720 URL: https://issues.jenkins-ci.org/browse/JENKINS-12720 Project: Jenkins Issue Type: Bug Components: clearcase-ucm Affects Versions: current Reporter: Christian Wolfgang Assignee: Christian Wolfgang I am triggering a downstream job and passing CC_BASELINE as a parameter. Each time the parent view updates and builds properly from the polling log - Started on Feb 10, 2012 4:36:22 PM [CCUCM] Getting baselines for : [CCUCM] * Stream: ECLPS_Feb12_Int@\ECLPS_PVOB [CCUCM] * Component: eclps_src@\ECLPS_PVOB [CCUCM] * Promotion level: ANY [CCUCM] polling streams: self The last baseline: baseline:BUILDBOX_2012_02_10_13_19_01@\ECLPS_PVOB: * Shortname: BUILDBOX_2012_02_10_13_19_01 * PVOB : \ECLPS_PVOB * Type : Baseline * Level: BUILT * Component: component:eclps_src@\ECLPS_PVOB * Stream : stream:ECLPS_Feb12_Int@\ECLPS_PVOB * Date : Fri Feb 10 13:19:02 EST 2012 The found baseline: baseline:BUILDBOX_2012_02_10_16_19_01@\ECLPS_PVOB: * Shortname: BUILDBOX_2012_02_10_16_19_01 * PVOB : \ECLPS_PVOB * Type : Baseline * Level: BUILT * Component: component:eclps_src@\ECLPS_PVOB * Stream : stream:ECLPS_Feb12_Int@\ECLPS_PVOB * Date : Fri Feb 10 16:19:03 EST 2012 but the value passed in CC_BASELINE is baseline:BUILDBOX_2012_02_07_14_19_00@\ECLPS_PVOB That baseline seems to have been the baseline first built by the parent stream. Is CC_BASELINE updating for other people? Tim -- 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-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159124#comment-159124 ] kutzi commented on JENKINS-11381: - Why not allow usage of the command line client, instead of just SVNKit? At least this way, you're not always dependent on a particular downstream product? In that case you're dependent on having the user installed the 'right' version of the native svn client. I'm not sure if that is the better alternative. Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- 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:all-tabpanel
]
Alex Lehmann reassigned JENKINS-12582:
--
Assignee: Alex Lehmann
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
Assignee: Alex Lehmann
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-12785) Groovy script console SCMTrigger example causes invalid configurationw
Wesley Hartford created JENKINS-12785:
-
Summary: Groovy script console SCMTrigger example causes invalid
configurationw
Key: JENKINS-12785
URL: https://issues.jenkins-ci.org/browse/JENKINS-12785
Project: Jenkins
Issue Type: Bug
Components: other
Reporter: Wesley Hartford
The wiki page at
[https://wiki.jenkins-ci.org/display/JENKINS/Change+SCMTrigger+for+each+project+to+disable+during+the+night+and+the+week-end]
has an sample script which modifies the SCM trigger schedule. The script does
not set the _job_ field of the newly created trigger. I recently used a
modified version of this script and encountered many NullPointerExceptions. I
would recommend changing the sample to the following:
{code:java}
import hudson.model.*
import hudson.triggers.*
TriggerDescriptor SCM_TRIGGER_DESCRIPTOR =
Hudson.instance.getDescriptorOrDie(SCMTrigger.class)
assert SCM_TRIGGER_DESCRIPTOR != null;
for(item in Hudson.instance.items)
{
println(Working on project $item.name)
def trigger = item.getTriggers().get(SCM_TRIGGER_DESCRIPTOR)
if(trigger != null trigger instanceof SCMTrigger)
{
print( $trigger.spec)
String[] parts = trigger.spec.split( );
//Do wanted modifs
if(parts[1] == * )
{
parts[1] = 7-21
}
if(parts[4] == *)
{
parts[4] = 1-5
}
//end modifs
StringBuilder newSpec = new StringBuilder();
for(p in parts)
{
newSpec.append(p+ );
}
println( = $newSpec);
def newTrigger = new SCMTrigger(newSpec.toString())
newTrigger.job = item
item.removeTrigger(SCM_TRIGGER_DESCRIPTOR)
item.addTrigger(newTrigger)
}
else
{
println Nothing to do
}
}
{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-12720) CC_BASELINE doesn't update value
[ https://issues.jenkins-ci.org/browse/JENKINS-12720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159126#comment-159126 ] Tim Collier commented on JENKINS-12720: --- that didn't work either as the CC_BASELINE value is not a parameter to the current build but a value set by the current build any ideas? CC_BASELINE doesn't update value Key: JENKINS-12720 URL: https://issues.jenkins-ci.org/browse/JENKINS-12720 Project: Jenkins Issue Type: Bug Components: clearcase-ucm Affects Versions: current Reporter: Christian Wolfgang Assignee: Christian Wolfgang I am triggering a downstream job and passing CC_BASELINE as a parameter. Each time the parent view updates and builds properly from the polling log - Started on Feb 10, 2012 4:36:22 PM [CCUCM] Getting baselines for : [CCUCM] * Stream: ECLPS_Feb12_Int@\ECLPS_PVOB [CCUCM] * Component: eclps_src@\ECLPS_PVOB [CCUCM] * Promotion level: ANY [CCUCM] polling streams: self The last baseline: baseline:BUILDBOX_2012_02_10_13_19_01@\ECLPS_PVOB: * Shortname: BUILDBOX_2012_02_10_13_19_01 * PVOB : \ECLPS_PVOB * Type : Baseline * Level: BUILT * Component: component:eclps_src@\ECLPS_PVOB * Stream : stream:ECLPS_Feb12_Int@\ECLPS_PVOB * Date : Fri Feb 10 13:19:02 EST 2012 The found baseline: baseline:BUILDBOX_2012_02_10_16_19_01@\ECLPS_PVOB: * Shortname: BUILDBOX_2012_02_10_16_19_01 * PVOB : \ECLPS_PVOB * Type : Baseline * Level: BUILT * Component: component:eclps_src@\ECLPS_PVOB * Stream : stream:ECLPS_Feb12_Int@\ECLPS_PVOB * Date : Fri Feb 10 16:19:03 EST 2012 but the value passed in CC_BASELINE is baseline:BUILDBOX_2012_02_07_14_19_00@\ECLPS_PVOB That baseline seems to have been the baseline first built by the parent stream. Is CC_BASELINE updating for other people? Tim -- 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-12786) Rake do not handle gemsets correctly
Gabor Garami created JENKINS-12786: -- Summary: Rake do not handle gemsets correctly Key: JENKINS-12786 URL: https://issues.jenkins-ci.org/browse/JENKINS-12786 Project: Jenkins Issue Type: Bug Components: rake Affects Versions: current Environment: openSUSE 11.4 Jenkins 1.4.50 from RPM rvm stable rake current version Reporter: Gabor Garami Assignee: david_calavera A problem about executing project tasks in specific gemset is still appears. It is described here https://github.com/jenkinsci/rake-plugin/pull/4 I installed rvm as its website instructs under /var/lib/jenkins (the default home directory of jenkins) and from configure I specified the rvm's home directory After it I selected the gemset what I created for the specific project for all two rake tasks. but under building, Jenkins builds project to global gemset, not the selected gemset. Actual log output: [rhcp] $ /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p0@global/bin/rake --rakefile ./Rakefile.bootstrap bundler:install Expected log output: [rhcp] $ /var/lib/jenkins/.rvm/gems/ruby-1.9.3-p0@rhcp/bin/rake --rakefile ./Rakefile.bootstrap bundler:install It not just uses wrong rake, but it seems do not uses the selected (currently: rhcp) gemset. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page
Joshua Davis created JENKINS-12787:
--
Summary: LOADING overlay does not go away on the Configure System
page
Key: JENKINS-12787
URL: https://issues.jenkins-ci.org/browse/JENKINS-12787
Project: Jenkins
Issue Type: Bug
Components: gui
Affects Versions: current
Environment: Jenkins
Reporter: Joshua Davis
After navigating to Manage-Configure System, the LOADING overlay never goes
away. It is impossible to save any configuration changes.
EXPECTED:
* You can save your global configuration.
Here is the stack trace from Chrome's JS console:
{code}
Uncaught TypeError: Object #Object has no method 'findMatchingInput'
(anonymous function)
e.targetUrl hudson-behavior.js:338
registerValidator hudson-behavior.js:343
apply behavior.js:73
(anonymous function) behavior.js:79
Behaviour.applySubtree behavior.js:68
Behaviour.applybehavior.js:54
(anonymous function)behavior.js:49
window.onload
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page
[
https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159128#comment-159128
]
Joshua Davis commented on JENKINS-12787:
Chrome seems to think this closure in hudson-behavior.js is throwing the
exception:
{code}
function registerValidator(e) {
e.targetElement = findFollowingTR(e,
validation-error-area).firstChild.nextSibling;
e.targetUrl = function() {
return eval(this.getAttribute(checkUrl)); // -- Dies here
};
var method = e.getAttribute(checkMethod);
if (!method) method = get;
var url = e.targetUrl();
{code}
LOADING overlay does not go away on the Configure System page
-
Key: JENKINS-12787
URL: https://issues.jenkins-ci.org/browse/JENKINS-12787
Project: Jenkins
Issue Type: Bug
Components: gui
Affects Versions: current
Environment: Jenkins
Reporter: Joshua Davis
Labels: gui, jenkins
After navigating to Manage-Configure System, the LOADING overlay never goes
away. It is impossible to save any configuration changes.
EXPECTED:
* You can save your global configuration.
Here is the stack trace from Chrome's JS console:
{code}
Uncaught TypeError: Object #Object has no method 'findMatchingInput'
(anonymous function)
e.targetUrl hudson-behavior.js:338
registerValidator hudson-behavior.js:343
apply behavior.js:73
(anonymous function) behavior.js:79
Behaviour.applySubtree behavior.js:68
Behaviour.applybehavior.js:54
(anonymous function)behavior.js:49
window.onload
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12628) Executable file permission not set anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clarke reassigned JENKINS-12628: Assignee: Michael Clarke Executable file permission not set anymore -- Key: JENKINS-12628 URL: https://issues.jenkins-ci.org/browse/JENKINS-12628 Project: Jenkins Issue Type: Bug Components: cvs Environment: CentOS release 5.7 (affected system, Slave), Windows Server 2003 (Master) Reporter: Marco Borm Assignee: Michael Clarke Fix For: current Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the fact that our compile scripts don't have executable permission bit set anymore. The bit is correctly set on the affected files on cvs server side. cvs plugin 1.6: -rwxrwx--- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release cvs plugin 2.0: -rw-rw-r-- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12628) Executable file permission not set anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12628 started by Michael Clarke. Executable file permission not set anymore -- Key: JENKINS-12628 URL: https://issues.jenkins-ci.org/browse/JENKINS-12628 Project: Jenkins Issue Type: Bug Components: cvs Environment: CentOS release 5.7 (affected system, Slave), Windows Server 2003 (Master) Reporter: Marco Borm Assignee: Michael Clarke Fix For: current Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the fact that our compile scripts don't have executable permission bit set anymore. The bit is correctly set on the affected files on cvs server side. cvs plugin 1.6: -rwxrwx--- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release cvs plugin 2.0: -rw-rw-r-- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12628) Executable file permission not set anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159130#comment-159130 ] SCM/JIRA link daemon commented on JENKINS-12628: Code changed in jenkins User: Michael Clarke Path: pom.xml http://jenkins-ci.org/commit/cvs-plugin/50d22a4953688f2ead47eba4f3608de63fef5a2c Log: [FIXED JENKINS-12628] - Upgrading to CVS client with permission support [FIXED JENKINS-12599] - Upgrading to CVS client with ext support Executable file permission not set anymore -- Key: JENKINS-12628 URL: https://issues.jenkins-ci.org/browse/JENKINS-12628 Project: Jenkins Issue Type: Bug Components: cvs Environment: CentOS release 5.7 (affected system, Slave), Windows Server 2003 (Master) Reporter: Marco Borm Assignee: Michael Clarke Fix For: current Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the fact that our compile scripts don't have executable permission bit set anymore. The bit is correctly set on the affected files on cvs server side. cvs plugin 1.6: -rwxrwx--- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release cvs plugin 2.0: -rw-rw-r-- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12599) IllegalArgumentException after Upgrade to 2.0
[ https://issues.jenkins-ci.org/browse/JENKINS-12599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159131#comment-159131 ] SCM/JIRA link daemon commented on JENKINS-12599: Code changed in jenkins User: Michael Clarke Path: pom.xml http://jenkins-ci.org/commit/cvs-plugin/50d22a4953688f2ead47eba4f3608de63fef5a2c Log: [FIXED JENKINS-12628] - Upgrading to CVS client with permission support [FIXED JENKINS-12599] - Upgrading to CVS client with ext support IllegalArgumentException after Upgrade to 2.0 - Key: JENKINS-12599 URL: https://issues.jenkins-ci.org/browse/JENKINS-12599 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Ulli Hafner Assignee: Michael Clarke Priority: Blocker 12:00:14 Started by user hafner 12:00:14 Building on master 12:00:14 FATAL: Unrecognized CVS Root: :ext:haf...@fipsfspm.faktorzehn.de:/projekte/cvs.com.f10.ips4fspm 12:00:14 java.lang.IllegalArgumentException: Unrecognized CVS Root: :ext:haf...@fipsfspm.faktorzehn.de:/projekte/cvs.com.f10.ips4fspm 12:00:14 at org.netbeans.lib.cvsclient.connection.ConnectionFactory.getConnection(ConnectionFactory.java:117) 12:00:14 at hudson.scm.CVSSCM.getCvsClient(CVSSCM.java:570) 12:00:14 at hudson.scm.CVSSCM.checkout(CVSSCM.java:702) 12:00:14 at hudson.model.AbstractProject.checkout(AbstractProject.java:1193) 12:00:14 at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:555) 12:00:14 at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:443) 12:00:14 at hudson.model.Run.run(Run.java:1376) 12:00:14 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 12:00:14 at hudson.model.ResourceController.execute(ResourceController.java:88) 12:00:14 at hudson.model.Executor.run(Executor.java:175) -- 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=159132#comment-159132
]
dogfood commented on JENKINS-12582:
---
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_cvs
#9|http://ci.jenkins-ci.org/job/plugins_cvs/9/]
Result = SUCCESS
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
Assignee: Alex Lehmann
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-12628) Executable file permission not set anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159133#comment-159133 ] dogfood commented on JENKINS-12628: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_cvs #9|http://ci.jenkins-ci.org/job/plugins_cvs/9/] [FIXED JENKINS-12628] - Upgrading to CVS client with permission support (Revision 50d22a4953688f2ead47eba4f3608de63fef5a2c) Result = SUCCESS michael.m.clarke : Files : * pom.xml Executable file permission not set anymore -- Key: JENKINS-12628 URL: https://issues.jenkins-ci.org/browse/JENKINS-12628 Project: Jenkins Issue Type: Bug Components: cvs Environment: CentOS release 5.7 (affected system, Slave), Windows Server 2003 (Master) Reporter: Marco Borm Assignee: Michael Clarke Fix For: current Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the fact that our compile scripts don't have executable permission bit set anymore. The bit is correctly set on the affected files on cvs server side. cvs plugin 1.6: -rwxrwx--- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release cvs plugin 2.0: -rw-rw-r-- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12788) Missing variables when executing EnvInject script
[ https://issues.jenkins-ci.org/browse/JENKINS-12788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hartling updated JENKINS-12788: --- Attachment: config.xml Job configuration with Git enabled. Missing variables when executing EnvInject script - Key: JENKINS-12788 URL: https://issues.jenkins-ci.org/browse/JENKINS-12788 Project: Jenkins Issue Type: Bug Components: envinject Affects Versions: current Environment: Jenkins 1.450 on Ubuntu 10.04 EnvInject 1.20 or 1.22 Reporter: Patrick Hartling Assignee: gbois Labels: git, plugin, windows Attachments: config.xml, config.xml Not all the Jenkins environment variables and build variables are being made available to the EnvInject script. When testing with version 1.19, we had JOB_NAME, EXECUTOR_NUMBER, and GIT_BRANCH to name a few. With 1.20 and 1.22, we still have JOB_NAME, but EXECUTOR_NUMBER and GIT_BRANCH are not available. I have attached a config.xml for use on a Windows slave. The same issue exists on a Linux slave. The Git repository referenced in the config.xml could be anything. The repository referenced is just there so that there is some Git-related piece in the job. -- 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-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clarke reassigned JENKINS-12573: Assignee: Michael Clarke CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- 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-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12573 started by Michael Clarke. CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- 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-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159136#comment-159136 ] SCM/JIRA link daemon commented on JENKINS-12573: Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/CVSSCM.java http://jenkins-ci.org/commit/cvs-plugin/3bbeea490c27f333078224b7a17ac05b43ee431c Log: [FIXED JENKINS-12573] Switch to RFC 1123 compliant date as per CVS spec CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- 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-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12573. Resolution: Fixed CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- 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-12573) CVS plugin version 2.0 checkout failed: Can't parse date/time
[ https://issues.jenkins-ci.org/browse/JENKINS-12573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159137#comment-159137 ] dogfood commented on JENKINS-12573: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_cvs #10|http://ci.jenkins-ci.org/job/plugins_cvs/10/] [FIXED JENKINS-12573] Switch to RFC 1123 compliant date as per CVS spec (Revision 3bbeea490c27f333078224b7a17ac05b43ee431c) Result = SUCCESS michael.m.clarke : Files : * src/main/java/hudson/scm/CVSSCM.java CVS plugin version 2.0 checkout failed: Can't parse date/time - Key: JENKINS-12573 URL: https://issues.jenkins-ci.org/browse/JENKINS-12573 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins ver. 1.424.2 Jenkins CVS Plug-in 2.0 Reporter: Eric Co Assignee: Michael Clarke After I upgraded the CVS plugin 2.0, got the following error: cvs checkout -P -D 2012-01-30 16:37:44HKT -d abc abc cvs [checkout aborted]: Can't parse date/time: 2012-01-30 16:37:44HKT -- 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-12789) Clarify help text and names for things
francis Upton created JENKINS-12789: --- Summary: Clarify help text and names for things Key: JENKINS-12789 URL: https://issues.jenkins-ci.org/browse/JENKINS-12789 Project: Jenkins Issue Type: Improvement Components: ec2 Reporter: francis Upton Assignee: francis Upton 1) From JENKINS-8615: To me, EC2 RSA Private Key means the private part of the X.509 certificate you use to sign requests to AWS APIs, but what the hudson-ec2 plugin wants is a EC2 key pair. I think this could easily be clarified. 2) Hudson - Jenkins in the desciptions. 3) Clarify help on the user name 4) Move the Root command prefix out of the advanced properties since it's used most of the time now. 5) Various other wording changes -- 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-12789) Clarify help text and names for things
[ https://issues.jenkins-ci.org/browse/JENKINS-12789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12789. Resolution: Fixed Clarify help text and names for things -- Key: JENKINS-12789 URL: https://issues.jenkins-ci.org/browse/JENKINS-12789 Project: Jenkins Issue Type: Improvement Components: ec2 Reporter: francis Upton Assignee: francis Upton 1) From JENKINS-8615: To me, EC2 RSA Private Key means the private part of the X.509 certificate you use to sign requests to AWS APIs, but what the hudson-ec2 plugin wants is a EC2 key pair. I think this could easily be clarified. 2) Hudson - Jenkins in the desciptions. 3) Clarify help on the user name 4) Move the Root command prefix out of the advanced properties since it's used most of the time now. 5) Various other wording changes -- 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-12789) Clarify help text and names for things
[ https://issues.jenkins-ci.org/browse/JENKINS-12789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159138#comment-159138 ] SCM/JIRA link daemon commented on JENKINS-12789: Code changed in jenkins User: Francis Upton IV Path: src/main/resources/hudson/plugins/ec2/AmazonEC2Cloud/config-entries.jelly src/main/resources/hudson/plugins/ec2/AmazonEC2Cloud/help-region.html src/main/resources/hudson/plugins/ec2/EC2Cloud/help-accessId.html src/main/resources/hudson/plugins/ec2/EC2Cloud/help-instanceCapStr.html src/main/resources/hudson/plugins/ec2/EC2Cloud/help-privateKey.html src/main/resources/hudson/plugins/ec2/EC2Cloud/help-remoteAdmin.html src/main/resources/hudson/plugins/ec2/EC2Cloud/help-rootCommandPrefix.html src/main/resources/hudson/plugins/ec2/EC2Slave/help-initScript.html src/main/resources/hudson/plugins/ec2/EC2Slave/help-remoteAdmin.html src/main/resources/hudson/plugins/ec2/EC2Slave/help-rootCommandPrefix.html src/main/resources/hudson/plugins/ec2/EC2Slave/help-type.html src/main/resources/hudson/plugins/ec2/Eucalyptus/config-entries.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/main/resources/hudson/plugins/ec2/ebs/ZPoolExpandNotice/index.jelly src/main/resources/hudson/plugins/ec2/ebs/ZPoolExpandNotice/message.jelly src/main/resources/index.jelly http://jenkins-ci.org/commit/ec2-plugin/d03fd0721824a24092f176e8be1c39a4ae7d624c Log: [FIXED JENKINS-12789] Clarification and updating of help Clarify help text and names for things -- Key: JENKINS-12789 URL: https://issues.jenkins-ci.org/browse/JENKINS-12789 Project: Jenkins Issue Type: Improvement Components: ec2 Reporter: francis Upton Assignee: francis Upton 1) From JENKINS-8615: To me, EC2 RSA Private Key means the private part of the X.509 certificate you use to sign requests to AWS APIs, but what the hudson-ec2 plugin wants is a EC2 key pair. I think this could easily be clarified. 2) Hudson - Jenkins in the desciptions. 3) Clarify help on the user name 4) Move the Root command prefix out of the advanced properties since it's used most of the time now. 5) Various other wording changes -- 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-8615) EC2 RSA Private Key option confusingly named
[ https://issues.jenkins-ci.org/browse/JENKINS-8615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton resolved JENKINS-8615. Assignee: francis Upton (was: Kohsuke Kawaguchi) Resolution: Duplicate Subsumbed by JENKINS-12789 EC2 RSA Private Key option confusingly named -- Key: JENKINS-8615 URL: https://issues.jenkins-ci.org/browse/JENKINS-8615 Project: Jenkins Issue Type: Bug Components: ec2 Reporter: mwhudson Assignee: francis Upton Priority: Trivial To me, EC2 RSA Private Key means the private part of the X.509 certificate you use to sign requests to AWS APIs, but what the hudson-ec2 plugin wants is a EC2 key pair. I think this could easily be clarified. -- 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-7883) Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances
[ https://issues.jenkins-ci.org/browse/JENKINS-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159143#comment-159143 ] francis Upton commented on JENKINS-7883: Will fix this to count only the running or pending instances as active against the count, all other will be ignored. It was deliberate to use the EC2 instance counts to manage this, and I think it's a good idea to continue that way (as opposed to having a separate Jenkins count), so that won't be changed. Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances Key: JENKINS-7883 URL: https://issues.jenkins-ci.org/browse/JENKINS-7883 Project: Jenkins Issue Type: Bug Components: ec2 Affects Versions: current Environment: ubuntu amd64 e.g. alestic ami-da0cf8b3 ec2 plugin v 1.9 Reporter: truher Assignee: Kohsuke Kawaguchi Priority: Blocker i can manually create slaves, but they are never created automatically. -- 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-7883) Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances
[ https://issues.jenkins-ci.org/browse/JENKINS-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-7883. --- Resolution: Fixed Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances Key: JENKINS-7883 URL: https://issues.jenkins-ci.org/browse/JENKINS-7883 Project: Jenkins Issue Type: Bug Components: ec2 Affects Versions: current Environment: ubuntu amd64 e.g. alestic ami-da0cf8b3 ec2 plugin v 1.9 Reporter: truher Assignee: Kohsuke Kawaguchi Priority: Blocker i can manually create slaves, but they are never created automatically. -- 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-7883) Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances
[ https://issues.jenkins-ci.org/browse/JENKINS-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159145#comment-159145 ] dogfood commented on JENKINS-7883: -- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_ec2 #58|http://ci.jenkins-ci.org/job/plugins_ec2/58/] [FIXED JENKINS-7883] Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances (Revision fb48500653bf851b59022b61ed3eb86ac60ab07f) Result = SUCCESS francisu : Files : * src/main/java/hudson/plugins/ec2/EC2Cloud.java Stopped (as opposed to terminated) slaves are counted against the active instance count for the purpose of launching; can prevent launching of instances Key: JENKINS-7883 URL: https://issues.jenkins-ci.org/browse/JENKINS-7883 Project: Jenkins Issue Type: Bug Components: ec2 Affects Versions: current Environment: ubuntu amd64 e.g. alestic ami-da0cf8b3 ec2 plugin v 1.9 Reporter: truher Assignee: francis Upton Priority: Blocker i can manually create slaves, but they are never created automatically. -- 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-12763) Excessive lock contention when using mercurial cache with multiple repos and slaves
[ https://issues.jenkins-ci.org/browse/JENKINS-12763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Santiago reassigned JENKINS-12763: Assignee: David Santiago (was: Kohsuke Kawaguchi) Excessive lock contention when using mercurial cache with multiple repos and slaves --- Key: JENKINS-12763 URL: https://issues.jenkins-ci.org/browse/JENKINS-12763 Project: Jenkins Issue Type: Improvement Components: mercurial Affects Versions: current Reporter: David Santiago Assignee: David Santiago Labels: lock, mercurial, threads The current implementation of the mercurial plugin uses a too aggressive locking approach for managing its cache across master and build slaves. By aggressive I mean that whenever a build starts for a given repository on any given build slave, it will block any subsequent build of any other jobs which share the same repository while it updates the cache in both the master and the slave used for the build, and also creates its working directory. With multiple jobs which share repositories (through different branches, for instance), lock contention ramps up. This is not necessary, as a different locking mechanism can be used to allow concurrent builds of jobs which share the same repository but run in different slaves. It can be achieved by using different locks for controlling the updates of master and slave nodes caches. This way, we reduce lock contention and increase cache update performance. A pull request has been created for this: https://github.com/jenkinsci/mercurial-plugin/pull/21 -- 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-12791) within build step, missing option to not run further build steps if triggered builds fail or are unstable
Dieter Schüle created JENKINS-12791: --- Summary: within build step, missing option to not run further build steps if triggered builds fail or are unstable Key: JENKINS-12791 URL: https://issues.jenkins-ci.org/browse/JENKINS-12791 Project: Jenkins Issue Type: New Feature Components: parameterized-trigger Reporter: Dieter Schüle Assignee: huybrechts When used as post build step, there is an option to not run further build steps if triggered builds fail or are unstable. This option should also be available when used as build step. -- 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-12481) Dependency Graph plug in does not know about Trigger/call builds on other projects build steps
[ https://issues.jenkins-ci.org/browse/JENKINS-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159125#comment-159125 ] Dieter Schüle edited comment on JENKINS-12481 at 2/15/12 11:53 PM: --- works here was (Author: jenuser7): same issue here Dependency Graph plug in does not know about Trigger/call builds on other projects build steps Key: JENKINS-12481 URL: https://issues.jenkins-ci.org/browse/JENKINS-12481 Project: Jenkins Issue Type: Bug Components: depgraph-view Reporter: giuliano carlini Assignee: wolfs Many/most of our job dependencies are expressed as build steps, rather than with Build after other projects are built/Build other projects. Dependency view does not know about these dependencies. -- 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-12481) Dependency Graph plug in does not know about Trigger/call builds on other projects build steps
[ https://issues.jenkins-ci.org/browse/JENKINS-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159125#comment-159125 ] Dieter Schüle edited comment on JENKINS-12481 at 2/15/12 11:54 PM: --- works here guess works since version 2.13 (Feb 9, 2012) of paramerized trigger plugin, see version comment: •Builds triggered as build steps will now appear as downstream builds. (issue #11082, issue #9263, issue #5184) was (Author: jenuser7): works here Dependency Graph plug in does not know about Trigger/call builds on other projects build steps Key: JENKINS-12481 URL: https://issues.jenkins-ci.org/browse/JENKINS-12481 Project: Jenkins Issue Type: Bug Components: depgraph-view Reporter: giuliano carlini Assignee: wolfs Many/most of our job dependencies are expressed as build steps, rather than with Build after other projects are built/Build other projects. Dependency view does not know about these dependencies. -- 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-8946) Option to set Zone as well as region for instance creation
[ https://issues.jenkins-ci.org/browse/JENKINS-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] francis Upton reassigned JENKINS-8946: -- Assignee: francis Upton (was: Kohsuke Kawaguchi) Option to set Zone as well as region for instance creation -- Key: JENKINS-8946 URL: https://issues.jenkins-ci.org/browse/JENKINS-8946 Project: Jenkins Issue Type: New Feature Components: ec2 Reporter: william selwood Assignee: francis Upton Instances in the same zone have much better performance when communicating between each other. It would be useful to be able to set the zone you wish an instance to start in as well as the region. At least they end up on the right side of the world at the moment but same server farm would be even more useful. region: eu-west zone: eu-west-1b for instance -- 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-8946) Option to set Zone as well as region for instance creation
[ https://issues.jenkins-ci.org/browse/JENKINS-8946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-8946 started by francis Upton. Option to set Zone as well as region for instance creation -- Key: JENKINS-8946 URL: https://issues.jenkins-ci.org/browse/JENKINS-8946 Project: Jenkins Issue Type: New Feature Components: ec2 Reporter: william selwood Assignee: francis Upton Instances in the same zone have much better performance when communicating between each other. It would be useful to be able to set the zone you wish an instance to start in as well as the region. At least they end up on the right side of the world at the moment but same server farm would be even more useful. region: eu-west zone: eu-west-1b for instance -- 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-12598) In 2.0 update you need to specify branch for every module
[ https://issues.jenkins-ci.org/browse/JENKINS-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G updated JENKINS-12598: - Attachment: Jenkins_CvsPluginModules.png In 2.0 update you need to specify branch for every module - Key: JENKINS-12598 URL: https://issues.jenkins-ci.org/browse/JENKINS-12598 Project: Jenkins Issue Type: Improvement Components: cvs Reporter: Ulli Hafner Priority: Critical Attachments: Jenkins_CvsPluginModules.png After an upgrade to the new 2.0 version of the cvs plug-in we now need to specify the Module location (trunk, branch) for each module. This is quite cumbersome if you have a lot of modules. In the 1.x plug-in releases you are able to select a given branch for all modules in one text field. While I think the new feature has a lot of use cases (i.e., having trunk and branches mixed), the usability could be improved here. My requirement is to select/change the branch (or trunk) for all modules in a simple way. A non-Ajax suggestion would be to have a default entry in the Selection, i.e. Trunk, Branch, Tag, Default. And you can define the default behavior at the top of the cvs configuration. -- 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-12792) Violation Plugin display [no report] for FxCop
Arun Mariappan Karunanithi created JENKINS-12792: Summary: Violation Plugin display [no report] for FxCop Key: JENKINS-12792 URL: https://issues.jenkins-ci.org/browse/JENKINS-12792 Project: Jenkins Issue Type: Bug Components: violations Affects Versions: current Reporter: Arun Mariappan Karunanithi Assignee: peterkittreilly Priority: Minor Attachments: jenkins-violation.png I am using the FxCop 1.36 command line to generate the Violation report. When there are no Violation in the specified .dll then the FxCop return No messages written and no output file written. So the violation plug-in displays as Fxcop No reports in the violation graph. It's not an big issue but the Build Icon changed to Thunder Icon.(Check the attachment) -- 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-12793) Why Post Steps and Post-build Actions are executed after builded finished
dzy dzy created JENKINS-12793: - Summary: Why Post Steps and Post-build Actions are executed after builded finished Key: JENKINS-12793 URL: https://issues.jenkins-ci.org/browse/JENKINS-12793 Project: Jenkins Issue Type: Bug Components: analysis-core Environment: Windows Reporter: dzy dzy Assignee: Ulli Hafner Priority: Critical Attachments: 11.jpg My question is that The log file is in whole or in part when executed post step or Post-build Actions. How to get the build result. I want to get the build result,but there are no any plugins to get the result.So I did below this: 1 In my opinion,the post step are executed after the build finished. So I cofigured the job and selected Run regardless of build result at post step ,at the same time there is one bat at execute windows at batch command. The bat is used to query the two files build.xml and log. But I can not find the string resultFAILURE/result in the build.xml and Finished: FAILURE in the file log. When the build finished,I queried these 2 files on the disk,the strings are exists in the two file. 2 I installed one plugin Post build task below Post-build Actions,I put the string FAILURE into the Log text. but the Script did not executed. -- 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-12793) Why Post Steps and Post-build Actions are executed after builded finished
[ https://issues.jenkins-ci.org/browse/JENKINS-12793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159147#comment-159147 ] dzy dzy commented on JENKINS-12793: --- the title is Why Post Steps and Post-build Actions are not executed after the build finished Why Post Steps and Post-build Actions are executed after builded finished -- Key: JENKINS-12793 URL: https://issues.jenkins-ci.org/browse/JENKINS-12793 Project: Jenkins Issue Type: Bug Components: analysis-core Environment: Windows Reporter: dzy dzy Assignee: Ulli Hafner Priority: Critical Attachments: 11.jpg My question is that The log file is in whole or in part when executed post step or Post-build Actions. How to get the build result. I want to get the build result,but there are no any plugins to get the result.So I did below this: 1 In my opinion,the post step are executed after the build finished. So I cofigured the job and selected Run regardless of build result at post step ,at the same time there is one bat at execute windows at batch command. The bat is used to query the two files build.xml and log. But I can not find the string resultFAILURE/result in the build.xml and Finished: FAILURE in the file log. When the build finished,I queried these 2 files on the disk,the strings are exists in the two file. 2 I installed one plugin Post build task below Post-build Actions,I put the string FAILURE into the Log text. but the Script did not executed. -- 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-12793) Why the Post Steps and Post-build Actions are not executed after the build finished
[ https://issues.jenkins-ci.org/browse/JENKINS-12793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159148#comment-159148 ] dzy dzy commented on JENKINS-12793: --- I tested the job which is builded failure. Why the Post Steps and Post-build Actions are not executed after the build finished --- Key: JENKINS-12793 URL: https://issues.jenkins-ci.org/browse/JENKINS-12793 Project: Jenkins Issue Type: Bug Components: analysis-core Environment: Windows Reporter: dzy dzy Assignee: Ulli Hafner Priority: Critical Attachments: 11.jpg My question is that The log file is in whole or in part when executed post step or Post-build Actions. How to get the build result. I want to get the build result,but there are no any plugins to get the result.So I did below this: 1 In my opinion,the post step are executed after the build finished. So I cofigured the job and selected Run regardless of build result at post step ,at the same time there is one bat at execute windows at batch command. The bat is used to query the two files build.xml and log. But I can not find the string resultFAILURE/result in the build.xml and Finished: FAILURE in the file log. When the build finished,I queried these 2 files on the disk,the strings are exists in the two file. 2 I installed one plugin Post build task below Post-build Actions,I put the string FAILURE into the Log text. but the Script did not executed. -- 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-12793) Why the Post Steps and Post-build Actions are not executed after the build finished
[ https://issues.jenkins-ci.org/browse/JENKINS-12793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dzy dzy updated JENKINS-12793: -- Summary: Why the Post Steps and Post-build Actions are not executed after the build finished (was: Why Post Steps and Post-build Actions are executed after builded finished) Why the Post Steps and Post-build Actions are not executed after the build finished --- Key: JENKINS-12793 URL: https://issues.jenkins-ci.org/browse/JENKINS-12793 Project: Jenkins Issue Type: Bug Components: analysis-core Environment: Windows Reporter: dzy dzy Assignee: Ulli Hafner Priority: Critical Attachments: 11.jpg My question is that The log file is in whole or in part when executed post step or Post-build Actions. How to get the build result. I want to get the build result,but there are no any plugins to get the result.So I did below this: 1 In my opinion,the post step are executed after the build finished. So I cofigured the job and selected Run regardless of build result at post step ,at the same time there is one bat at execute windows at batch command. The bat is used to query the two files build.xml and log. But I can not find the string resultFAILURE/result in the build.xml and Finished: FAILURE in the file log. When the build finished,I queried these 2 files on the disk,the strings are exists in the two file. 2 I installed one plugin Post build task below Post-build Actions,I put the string FAILURE into the Log text. but the Script did not executed. -- 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-12794) Occasional crash of plugin
Waldek M created JENKINS-12794: -- Summary: Occasional crash of plugin Key: JENKINS-12794 URL: https://issues.jenkins-ci.org/browse/JENKINS-12794 Project: Jenkins Issue Type: Bug Components: clearcase, cobertura Affects Versions: current Environment: RHEL. Jenkins 1.451 and the latest versions of plugins - clearcase and cobertura Reporter: Waldek M Assignee: Vincent Latombe Priority: Minor Occasionally, the cobertura plugin crashes with the trace as follows. I'm afraid I'm not able to tell whether this is really releated to the cobertura, or clearcase plugins, because both appear on the trace. Publishing Cobertura coverage report... ERROR: Publisher hudson.plugins.cobertura.CoberturaPublisher aborted due to exception java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:226) at hudson.FilePath.init(FilePath.java:214) at hudson.FilePath.child(FilePath.java:926) at hudson.plugins.clearcase.AbstractClearCaseScm.getModuleRoot(AbstractClearCaseScm.java:345) at hudson.scm.SCM.getModuleRoots(SCM.java:543) at hudson.model.AbstractBuild.getModuleRoots(AbstractBuild.java:287) at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:216) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:700) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:675) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:653) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:622) at hudson.model.Run.run(Run.java:1434) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 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
