[JIRA] (JENKINS-9016) Git creates usernames based on 'name' not the email.
Jan Vansteenkiste edited a comment on JENKINS-9016 Git creates usernames based on 'name' not the email. I have created some initial code on this subject. The only question that remains is whether the plugin is the right place for my UserEmailResolver. I also had some troubles getting the tests going and had to add a newer jenkins-core, ui-samples-plugin, jenkins-test-harness and javadoc to the dependencies. https://github.com/vStone/git-plugin/commit/63612268d832edc7a77d0be55e650e31fc5442a9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9016) Git creates usernames based on 'name' not the email.
Jan Vansteenkiste commented on JENKINS-9016 Git creates usernames based on 'name' not the email. I have created some initial code on this subject. The only question that remains is whether the plugin is the right place for my UserEmailResolver. I also had some troubles getting the tests going and had to add a newer jenkins-core, ui-samples-plugin, jenkins-test-harness and javadoc to the dependencies. https://github.com/vStone/git-plugin/commit/63612268d832edc7a77d0be55e650e31fc5442a9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer
commented on JENKINS-15499
HistoryWidget/entry.jelly throws NullPointerException
Looking at the output from an affected job the /job/hudson8462/buildHistory/all output contains a link to the console output which contains //console.
"build-row no-wrap ">"/job/hudson8462//console">
The build number should be between the // so that suggests that ${build} is null in /hudson/widgets/HistoryWidget/entry.jelly
That in turn means that getRenderList() in HistoryWidget.java is returning null values in the list.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15541) "Execute concurrent builds if necessary" checkbox does not allow multiple builds in queue
jchatham created JENKINS-15541 "Execute concurrent builds if necessary" checkbox does not allow multiple builds in queue Issue Type: Improvement Affects Versions: current Assignee: Kohsuke Kawaguchi Components: concurrent-build Created: 16/Oct/12 10:55 PM Description: This is a problem because, if further builds are currently blocked (say, by being out of available executors), jenkins will quietly drop any additional attempts to queue a build - which seems at odds with the stated effect of allowing Jenkins to "schedule and execute multiple builds concurrently" To replicate: Set available executors to one. Create a freestyle build; make it, say, printenv and sleep 30. Add a parameter and check "Execute concurrent builds if necessary" - it seems to me like this should allow unlimited parallel builds with different parameterized values; in practice, only two can exist - the one that's building right now, and one in the queue; attempting to start additional builds beyond that, even with different parameters, simply fails. (My personal use case is a bit more complicated, with builds being blocked by things other than just insufficient available executors. But the underlying problem is the same.) Project: Jenkins Priority: Major Reporter: jchatham This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15165) Using openjdk 6 to build jenkins from code failed
Wade C commented on JENKINS-15165 Using openjdk 6 to build jenkins from code failed Any workaround? I'm seeing the same thing. Apache Maven 3.0.4 (rNON-CANONICAL_2012-01-24_13-02_root; 2012-01-24 05:02:02-0800) Maven home: /opt/maven Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-6-openjdk/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux", version: "3.3.6-1-arch", arch: "i386", family: "unix" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13702) extra columns plugin - would like to see tests run,failed,error,skipped numbers
SCM/JIRA link daemon commented on JENKINS-13702 extra columns plugin - would like to see tests run,failed,error,skipped numbers Code changed in jenkins User: Fred G Path: src/main/java/jenkins/plugins/extracolumns/TestResultColumn.java src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/column.jelly src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/column.properties src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/columnHeader.jelly src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/columnHeader_de.properties src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/column_de.properties src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/config.jelly src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/config.properties src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/config_de.properties src/main/webapp/help-testresult-column.html src/main/webapp/help-testresult-column_de.html http://jenkins-ci.org/commit/extra-columns-plugin/68238105632298a3532fd6aacc9112958a443498 Log: [FIXED JENKINS-15155], [FIXED JENKINS-13702] Test column can now be configured This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15155) Show total number of tests in test column
SCM/JIRA link daemon commented on JENKINS-15155 Show total number of tests in test column Code changed in jenkins User: Fred G Path: src/main/java/jenkins/plugins/extracolumns/TestResultColumn.java src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/column.jelly src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/column.properties src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/columnHeader.jelly src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/columnHeader_de.properties src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/column_de.properties src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/config.jelly src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/config.properties src/main/resources/jenkins/plugins/extracolumns/TestResultColumn/config_de.properties src/main/webapp/help-testresult-column.html src/main/webapp/help-testresult-column_de.html http://jenkins-ci.org/commit/extra-columns-plugin/68238105632298a3532fd6aacc9112958a443498 Log: [FIXED JENKINS-15155], [FIXED JENKINS-13702] Test column can now be configured This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
Wade C commented on JENKINS-15540 Update logging levels in LogRotator - hudson.tasks.LogRotator perform Currently setting up dev environment, going to create pull request. Opened this issue for tracking purposes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15540) Update logging levels in LogRotator - hudson.tasks.LogRotator perform
Wade C created JENKINS-15540 Update logging levels in LogRotator - hudson.tasks.LogRotator perform Issue Type: Patch Affects Versions: current Assignee: Wade C Components: core, logging Created: 16/Oct/12 10:30 PM Description: I noticed a couple of things when looking at the code for perform() in hudson.tasks.LogRotator, related to the way actions are logged. 1. Removals are logged at the same level (FINER) as notices about builds not to be removed (FINER), 2. Artifact removals are not logged at all. I was planning to change this: 1. Log all removals as FINE instead of FINER. 2. Log artifact removes as FINE. Project: Jenkins Priority: Trivial Reporter: Wade C This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13995) Would like the ability to disable hover-over context menus.
marc_swingler commented on JENKINS-13995 Would like the ability to disable hover-over context menus. "I'm just constantly swatting them away like flies." I'll second that comment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14923) Configurable build slave balancing modes
Damien Nozay commented on JENKINS-14923 Configurable build slave balancing modes there is a @Override extension point we could leverage to change the assignGreedily to an assignRoundRobin? I'm not much of a java / jenkins plugin expert though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14923) Configurable build slave balancing modes
Damien Nozay
edited a comment on JENKINS-14923
Configurable build slave balancing modes
I've run into this issue where we got 10 nodes with 10 executors each and the same one gets full before it gets executed elsewhere. somehow the contents of the job can kill the agent (OOM), which means it is very bothersome to greedily fill the same node.
my coworker looked up the code:
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/LoadBalancer.java
LoadBalancer.java
@Override
public Mapping map(Task task, MappingWorksheet ws) {
// build consistent hash for each work chunk
List> hashes = new ArrayList>(ws.works.size());
for (int i=0; i hash = new ConsistentHash(new Hash() {
public String hash(ExecutorChunk node) {
return node.getName();
}
});
for (ExecutorChunk ec : ws.works(i).applicableExecutorChunks())
hash.add(ec,ec.size()*100);
hashes.add(hash);
}
// do a greedy assignment
Mapping m = ws.new Mapping();
assert m.size()==ws.works.size(); // just so that you the reader of the source code don't get confused with the for loop index
if (assignGreedily(m,task,hashes,0)) {
assert m.isCompletelyValid();
return m;
} else
return null;
}
private boolean assignGreedily(Mapping m, Task task, List> hashes, int i) {
if (i==hashes.size()) return true;// fully assigned
String key = task.getFullDisplayName() + (i>0 ? String.valueOf(i) : "");
for (ExecutorChunk ec : hashes.get(i).list(key)) {
// let's attempt this assignment
m.assign(i,ec);
if (m.isPartiallyValid() && assignGreedily(m,task,hashes,i+1))
return true;// successful greedily allocation
// otherwise 'ec' wasn't a good fit for us. try next.
}
// every attempt failed
m.assign(i,null);
return false;
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14923) Configurable build slave balancing modes
Damien Nozay
commented on JENKINS-14923
Configurable build slave balancing modes
I've run into this issue where we got 10 nodes with 10 executors each and the same one gets full before it gets executed elsewhere. somehow the contents of the job can kill the agent (OOM), which means it is very bothersome to greedily fill the same node.
my coworker looked up the code:
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/LoadBalancer.java
@Override
public Mapping map(Task task, MappingWorksheet ws) {
// build consistent hash for each work chunk
List> hashes = new ArrayList>(ws.works.size());
for (int i=0; i
ConsistentHash hash = new ConsistentHash(new Hash() {
public String hash(ExecutorChunk node) {
return node.getName();
}
});
for (ExecutorChunk ec : ws.works.applicableExecutorChunks())
hash.add(ec,ec.size()*100);
hashes.add(hash);
}
// do a greedy assignment
Mapping m = ws.new Mapping();
assert m.size()==ws.works.size(); // just so that you the reader of the source code don't get confused with the for loop index
if (assignGreedily(m,task,hashes,0)) {
assert m.isCompletelyValid();
return m;
} else
return null;
}
private boolean assignGreedily(Mapping m, Task task, List> hashes, int i) {
if (i==hashes.size()) return true;// fully assigned
String key = task.getFullDisplayName() + (i>0 ? String.valueOf : "");
for (ExecutorChunk ec : hashes.get.list(key)) {
// let's attempt this assignment
m.assign(i,ec);
if (m.isPartiallyValid() && assignGreedily(m,task,hashes,i+1))
return true;// successful greedily allocation
// otherwise 'ec' wasn't a good fit for us. try next.
}
// every attempt failed
m.assign(i,null);
return false;
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15150) Content is returned for HEAD requests when using gzip
Michael Clarke commented on JENKINS-15150 Content is returned for HEAD requests when using gzip The above comment shows that Jenkins is being run on Winstone. Is this the same for everyone else with this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10131) Git polling shouldn't need a workspace on a slave.
wgracelee commented on JENKINS-10131 Git polling shouldn't need a workspace on a slave. We're seeing this message in (git) polling log, and we're using git plugin 1.1.23. Polling Log View as plain text This page captures the polling log that triggered this build. Started on Oct 15, 2012 11:24:38 PM Workspace is offline. Scheduling a new build to get a workspace. Done. Took 4 ms Changes found This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization
Grant Limberg edited a comment on JENKINS-15437 ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization Here's the list of plugins I'm currently running as well. name version enabled pinned external-monitor-job 1.1 true true ldap 1.1 true false pam-auth 1.0 true false ant 1.1 true false javadoc 1.0 true false cvs 2.6 true true next-build-number 1.0 false false scp 1.8 false false jython 1.9 true false bugzilla 1.5 false false setenv 1.1 true false cmakebuilder 1.9 false false ftppublisher 1.2 true false locks-and-latches 0.6 false false python 1.2 true false chucknorris 0.4 true false subversion 1.43 true true parameterized-trigger 2.16 true false token-macro 1.5.1 true false maven-plugin 1.486 true true copyartifact 1.24 true false jira 1.35 false false perforce 1.3.17 true false analysis-core 1.48 true false s3 0.3.0-SNAPSHOT (private-04/19/2012 22:11-grant) true false email-ext 2.24.1 true false view-job-filters 1.22 true false publish-over-ssh 1.8 false false translation 1.9 true true shelve-project-plugin 1.3 false false virtualbox 0.6 true false cppcheck 1.10 true false warnings 4.18 true false jenkins-multijob-plugin 1.5 true false redmine 0.10 true false ssh-slaves 0.21 true true xcode-plugin 1.3.1 true false envinject 1.72 true false promoted-builds 2.7 true false scm-sync-configuration 0.0.6 false false greenballs 1.12 true false timestamper 1.3.2 true false clang-scanbuild-plugin 1.3.1 true false ci-game 1.19 true false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15437) ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization
Grant Limberg commented on JENKINS-15437 ERR_CONTENT_DECODING_FAILED on Custom Views with Project-based Matrix Authorization Here's the list of plugins I'm currently running as well. name version enabled pinned -- external-monitor-job 1.1 true true ldap 1.1 true false pam-auth 1.0 true false ant 1.1 true false javadoc 1.0 true false cvs 2.6 true true next-build-number 1.0 false false scp 1.8 false false jython 1.9 true false bugzilla 1.5 false false setenv 1.1 true false cmakebuilder 1.9 false false ftppublisher 1.2 true false locks-and-latches 0.6 false false python 1.2 true false chucknorris 0.4 true false subversion 1.43 true true parameterized-trigger 2.16 true false token-macro 1.5.1 true false maven-plugin 1.486 true true copyartifact 1.24 true false jira 1.35 false false perforce 1.3.17 true false analysis-core 1.48 true false s3 0.3.0-SNAPSHOT (private-04/19/2012 22:11-grant) true false email-ext 2.24.1 true false view-job-filters 1.22 true false publish-over-ssh 1.8 false false translation 1.9 true true shelve-project-plugin 1.3 false false virtualbox 0.6 true false cppcheck 1.10 true false warnings 4.18 true false jenkins-multijob-plugin 1.5 true false redmine 0.10 true false ssh-slaves 0.21 true true xcode-plugin 1.3.1 true false envinject 1.72 true false promoted-builds 2.7 true false scm-sync-configuration 0.0.6 false false greenballs 1.12 true false timestamper 1.3.2 true false clang-scanbuild-plugin 1.3.1 true false ci-game 1.19 true false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11542) Add support for QTestLib XML reports
sahumada commented on JENKINS-11542 Add support for QTestLib XML reports I came up with a basic XSL for the xUnit plugin. How can I contribute it upstream ? I have it under $JENKINS_HOME/userContent/xUnit/QtTest/5.0.0/qttest-to-junit.xsl but I'd like to have it as part of Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Audrey Azra edited a comment on JENKINS-14546 Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated We are facing the same problem (Jenkins LTS 1.466.2 & Nested View 1.9) [using Project-based Matrix Authorization Strategy] Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users; As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME) [Note: This issue was not visible when we were running Jenkins 1.450 / Nested view plugin 1.8] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Audrey Azra edited a comment on JENKINS-14546 Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated We are facing the same problem (Jenkins LTS 1.466.2 & Nested View 1.9) [using Project-based Matrix Authorization Strategy] Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users; As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME) [Note: This issue was not visible when we were running Jenkins 1.450 / Nested view plugin 1.9] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Audrey Azra edited a comment on JENKINS-14546 Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated We are facing the same problem (Jenkins LTS 1.466.2 & Nested View 1.9) [using Project-based Matrix Authorization Strategy] Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users; As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Audrey Azra commented on JENKINS-14546 Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated We are facing the same problem (Jenkins LTS 1.466.2 & Nested View 1.9) Even if View.READ permission is granted, nested views are not visible to regular (non-admin) users; As a workaround, we have emailed the affected users the URL to the view (eg: http://jenkins_server/view/VIEWNAME) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10905) Deleting previous project files regularly fails the build
pjdarton commented on JENKINS-10905 Deleting previous project files regularly fails the build I have a prospective fix for this in JENKINS-15331. However, on Windows XP, I've found that it is possible to workaround the issue by configuring any anti-virus to not scan the workspace, and to ensure that the windows search service is either completely disabled or configured to avoid files in the workspace. In my experience, it's only on Vista & Windows 7 onwards that it's impossible to disable this "malware-like" behavior as it's now too deeply embedded in the OS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15095) Testopia fields witn no value should give an empty environment variable and not value null
Bruno P. Kinoshita resolved JENKINS-15095 as Fixed Testopia fields witn no value should give an empty environment variable and not value null Should be fixed in 1.2 Change By: Bruno P. Kinoshita (16/Oct/12 5:11 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15095) Testopia fields witn no value should give an empty environment variable and not value null
Bruno P. Kinoshita closed JENKINS-15095 as Fixed Testopia fields witn no value should give an empty environment variable and not value null Change By: Bruno P. Kinoshita (16/Oct/12 5:11 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10905) Deleting previous project files regularly fails the build
Paul Espinoza commented on JENKINS-10905 Deleting previous project files regularly fails the build I am also experiencing these occasional checkout failures while trying to delete the files from the last build. The Checkout settings are set to 'Always check out a fresh copy'. This is happening on a Windows XP (version 5.1) node connected to a Linux master Jenkins server. Jenkins version 1.466.2. I have experienced this in 7 of my last 64 builds (which are scheduled to run nightly), so it's happening roughly 10% of the time for me. Triggering the job again works as a temporary work around. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15539) Provide a link to the jacoco.exec
Mickael Istria created JENKINS-15539 Provide a link to the jacoco.exec Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco Created: 16/Oct/12 4:45 PM Description: The most convenient way to work with coverage results is to load them into IDE. EclEmma takes as input the Jacoco.exec files and provides source reports and highlighting directly in Eclipse workspace. It would be nice to provide a link to those jacoco.exec files and to some useful resources on how to consume them efficiently in IDE. Project: Jenkins Priority: Major Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15497) Display link to download TAP attachment
SCM/JIRA link daemon commented on JENKINS-15497 Display link to download TAP attachment Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapResult.java src/main/java/org/tap4j/plugin/model/TapAttachment.java http://jenkins-ci.org/commit/tap-plugin/a4a18a7d5e5570216c725a66d264407ba19c0bd9 Log: JENKINS-15497 Adding a new object to represent a TapAttachment. This new design allows us to send the file-size, file-name and other values found in a map diagnostics This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15484) New permission controlling ability to configure your own User
Jesse Glick commented on JENKINS-15484 New permission controlling ability to configure your own User Introduce permission in core, implied by ADMINISTER, disabled by default, called by User.getACL or User.doConfigSubmit only if enabled; then create a plugin which does nothing but enable the permission. Awkward but may work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15538) Show source highlighting on the whole class
Mickael Istria created JENKINS-15538 Show source highlighting on the whole class Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco Created: 16/Oct/12 4:42 PM Description: When browsing coverage reports in Jenkins, it is not possible to show hightlighting on the whole class. Coverage is only highlighted at method scope. IT would be easier to highlight coverage at the class level rather than at the method level Project: Jenkins Priority: Major Reporter: Mickael Istria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15537) Target ABI field doesn't handle Token Expansion
Christopher Orr commented on JENKINS-15537 Target ABI field doesn't handle Token Expansion Try again with version 2.6 of the plugin; it should work there. Also, I seem to remember testing matrix names with hyphens and they didn't get expanded by Jenkins at runtime (or something like that). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15537) Target ABI field doesn't handle Token Expansion
recampbell assigned JENKINS-15537 to recampbell Target ABI field doesn't handle Token Expansion Change By: recampbell (16/Oct/12 4:23 PM) Assignee: Christopher Orr recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15537) Target ABI field doesn't handle Token Expansion
recampbell updated JENKINS-15537 Target ABI field doesn't handle Token Expansion Change By: recampbell (16/Oct/12 4:13 PM) Attachment: android_token.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15495) Workspace got deleted for custom workspaces after updating to 1.485
Jesse Glick commented on JENKINS-15495 Workspace got deleted for custom workspaces after updating to 1.485 Never put original scripts directly in the workspace. Rather, version the scripts somewhere, either as part of some VCS-controlled project or inlined in the job configuration (which you should back up), and copy them to the workspace as a build step. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15537) Target ABI field doesn't handle Token Expansion
recampbell created JENKINS-15537 Target ABI field doesn't handle Token Expansion Issue Type: Bug Assignee: Christopher Orr Attachments: android_token.png Components: android-emulator Created: 16/Oct/12 4:12 PM Description: When creating a matrix build we have a parameter called "target-abi". However, when Jenkins validates the form it shows an error for this field, even though it doesn't display an error for other parameterized emulator arguments. Furthermore, this setting is not expanded when running from the command line: [android] /opt/android/android-sdk-linux/tools/android create avd -f -a -c 512M -s WVGA800 -n hudson_en-US_160_WVGA_android-16 -t android-16 --abi $target-abi Error: Unable to find a 'userdata.img' file for ABI $target-abi to copy into the AVD folder. Project: Jenkins Priority: Major Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15529) NoClassDefFoundError: com/sun/management/OperatingSystemMXBean
Jesse Glick commented on JENKINS-15529 NoClassDefFoundError: com/sun/management/OperatingSystemMXBean I see, OperatingSystem is the Windows implementation. I do not yet know the identity of the JVM in this case; reporting on behalf of another user. That would certainly be necessary for testing, though a fix can be proposed without that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15343) Unable to use Conditional BuildStep Plugin with Testlink Plugin
SCM/JIRA link daemon resolved JENKINS-15343 as Fixed Unable to use Conditional BuildStep Plugin with Testlink Plugin Change By: SCM/JIRA link daemon (16/Oct/12 3:38 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15343) Unable to use Conditional BuildStep Plugin with Testlink Plugin
SCM/JIRA link daemon commented on JENKINS-15343 Unable to use Conditional BuildStep Plugin with Testlink Plugin Code changed in jenkins User: Bruno P. Kinoshita Path: pom.xml src/main/java/hudson/plugins/testlink/TestLinkBuilderDescriptor.java src/main/java/hudson/plugins/testlink/util/TestLinkHelper.java http://jenkins-ci.org/commit/testlink-plugin/4699a45e6f4e49481b53f6bd661c4932221d99df Log: [FIXED JENKINS-15343] Using BuildStepDescriptor instead of Descriptor. This should make the plugin compatible with other plug-ins, such as Conditional Build Step. The Jenkins parent version has been updated from 1.399 to 1.466, as the BuildStepDescriptor requires at least 1.150 (as per javadocs). And 1.466 is the current version used in the mvn hpi:create task. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15474) Icons appears multiple times in the same line
Pailloncy Michaël resolved JENKINS-15474 as Fixed Icons appears multiple times in the same line fixed in version 0.9 Change By: Pailloncy Michaël (16/Oct/12 3:23 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15490) Analysis parsers don't work with maven 2 jobs
Ulli Hafner commented on JENKINS-15490 Analysis parsers don't work with maven 2 jobs I don't know if that is something that needs to be fixed in core or my plug-in. I would suspect that my plug-in needs to be fixed. Before I can make an estimation I need to look into that bug and try to reproduce it on my machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15333) Unable to see build history after upgrade
josh kehoe commented on JENKINS-15333 Unable to see build history after upgrade Thank you, I'll give that a try. For some reason though, my instance of Jenkins thinks it's on the latest release and is not seeing 1.486 as being available yet. I'll have to update manually. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15343) Unable to use Conditional BuildStep Plugin with Testlink Plugin
Bruno P. Kinoshita edited a comment on JENKINS-15343 Unable to use Conditional BuildStep Plugin with Testlink Plugin You're right indeed. The conditional build step plugin looks for BuildStepDescriptor at [1] and maybe in other places too. I'll change the testlink-plugin code and will run some preliminary tests. Thanks for reporting! [1] https://github.com/jenkinsci/conditional-buildstep-plugin/blob/master/src/main/java/org/jenkinsci/plugins/conditionalbuildstep/lister/DefaultBuilderDescriptorLister.java#L51 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15333) Unable to see build history after upgrade
Richard Mortimer commented on JENKINS-15333 Unable to see build history after upgrade For those who are seeing problems in 1.483 can you check the jenkins.log file to see if any errors are reported there. It is likely that something changed in either Jenkins core or a plugin that stopped older builds from being read from disk. The log contents should help diagnose that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15333) Unable to see build history after upgrade
Richard Mortimer commented on JENKINS-15333 Unable to see build history after upgrade @josh kehoe I suspect that your problen is different to the earlier reported problem. Yours sounds more like JENKINS-15465 and that is fixed in 1.486 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13887) Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build
Mark Warren
commented on JENKINS-13887
Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build
I concur. I'm currently trying to use a shell command prior to the Xcode plugin to set the CFBundleIdentifier value:
defaults write ${WORKSPACE}/Targetname-Info CFBundleIdentifier com.mycompany.mycompany
However, this results in a build error:
The following build commands failed:
ProcessInfoPlistFile /Users/Jenkins/workspace/MyApp/builds/MyApp.app/Info.plist Targetname-Info.plist
(1 failure)
Build step 'XCode' marked build as failure
I'm trying to figure out what is going on there, looks like something is messing up the file somehow.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15333) Unable to see build history after upgrade
josh kehoe commented on JENKINS-15333 Unable to see build history after upgrade This is happening to us too, but randomly. A restart of Jenkins restores the history but after a few days, it disappears again. This started happening after upgrading to 1.485. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15343) Unable to use Conditional BuildStep Plugin with Testlink Plugin
Bruno P. Kinoshita commented on JENKINS-15343 Unable to use Conditional BuildStep Plugin with Testlink Plugin You're right indeed. The conditional build step plugin looks for BuildStepDescriptor at [1] and maybe in other places too. I'll change the testlink-plugin code and will run some preliminary tests. Thanks for reporting! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12635) packaging ipa doesn´t work if run on a slave
Mark Warren commented on JENKINS-12635 packaging ipa doesn´t work if run on a slave I can confirm Leena's modification will indeed allow a slave to build an Xcode project. I had exactly the same issue until I added that option to Build Output Directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15343) Unable to use Conditional BuildStep Plugin with Testlink Plugin
Bruno P. Kinoshita started work on JENKINS-15343 Unable to use Conditional BuildStep Plugin with Testlink Plugin Change By: Bruno P. Kinoshita (16/Oct/12 1:50 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14437) envinject fails to "really" set/override build parameters
WH edited a comment on JENKINS-14437 envinject fails to "really" set/override build parameters Here's a more simple example: Parameterized job with: string parameter "_VERSION" two builders: Inject environment variables: Overwrites paramameter (environment variable) "_VERSION=xy" Execute shell: echo "value = $_VERSION" Actual result: The value of the the environment variable "_VERSION" is the orginal one. It is not "xy"! Expected result: The value is "xy". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15490) Analysis parsers don't work with maven 2 jobs
Justin Ye commented on JENKINS-15490 Analysis parsers don't work with maven 2 jobs thanks, Ulli. Is it a bug of Jenkins or the plugin? How long would it take to fix this issue? I'a afraid we cannot apply the workaround to all of our jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15490) Analysis parsers don't work with maven 2 jobs
Justin Ye edited a comment on JENKINS-15490 Analysis parsers don't work with maven 2 jobs thanks, Ulli. Is it a bug of Jenkins or the plugin? How long would it take to fix this issue? I'm afraid we cannot apply the workaround to all of our jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14437) envinject fails to "really" set/override build parameters
WH
commented on JENKINS-14437
envinject fails to "really" set/override build parameters
Here's a more simple example:
Parameterized job with:
string parameter "_VERSION"
two builders:
Inject environment variables: Overwrites paramameter (environment variable) "_VERSION=xy"
Ant: Is called with property "version=${_VERSION}"
Actual result:
The value of the Ant property "version" is the original value of environment variable "_VERSION". It is not "xy"!
Expected result:
Value is "xy".
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12377) Jenkins fitnesse build aborts after HTTP Timeout is exceeded, but tests continue to run
Mike Guiney commented on JENKINS-12377 Jenkins fitnesse build aborts after HTTP Timeout is exceeded, but tests continue to run Hi, I'm seeing very similar behaviour. I would have expected the FitServer.exe process to eventually finish but I guess its hung for some reason (hence the timeout). Trying to debug now. I'm also using a combination of timeouts i.e. the Http timeout thats part of the fitnesse plugin and a Build Timeout plugin for the job. More testing required I guess... Mike This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15345) Wrong help for dynamic trigger configuration
glundh closed JENKINS-15345 as Fixed Wrong help for dynamic trigger configuration Change By: glundh (16/Oct/12 12:41 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15345) Wrong help for dynamic trigger configuration
glundh resolved JENKINS-15345 as Fixed Wrong help for dynamic trigger configuration Change By: glundh (16/Oct/12 12:39 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15345) Wrong help for dynamic trigger configuration
SCM/JIRA link daemon commented on JENKINS-15345 Wrong help for dynamic trigger configuration Code changed in jenkins User: Gustaf Lundh Path: gerrithudsontrigger/src/main/webapp/trigger/help-DynamicTriggerConfiguration.html http://jenkins-ci.org/commit/gerrit-trigger-plugin/4794647abd18fb4b4e5fbba526fe4a27698a31ff Log: Small error in the help for dynamic trigger configuration. JENKINS-15345: Wrong help for dynamic trigger configuration Change-Id: Icbca38348905aea9123bd42c2a27ee862a776ad9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13006) Allows node labels to be read from a file.
Sergey Irisov commented on JENKINS-13006 Allows node labels to be read from a file. I'm using Parametrized Trigger Plugin and trying to use File Parameter Factory with node variable inside. With Parametrized Build Plugin I configured job with some label parameter. And when job is triggered with params from file, existing nodelabel parameter (with same name as in file) is overwrited but as a string parameter, and job eventually runs on master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15345) Wrong help for dynamic trigger configuration
glundh assigned JENKINS-15345 to glundh Wrong help for dynamic trigger configuration Change By: glundh (16/Oct/12 11:25 AM) Assignee: rsandell glundh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15345) Wrong help for dynamic trigger configuration
glundh started work on JENKINS-15345 Wrong help for dynamic trigger configuration Change By: glundh (16/Oct/12 11:24 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14552) Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked
Roland Asmann commented on JENKINS-14552 Cannot plublish cobertura reports if org.codehaus.mojo:cobertura-maven-plugin is not invoked Any news on this for v1.6 or 1.7 of the plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15536) Allow to remove 'Number of builds' column from 'All' view
Tomasz Bartczak created JENKINS-15536 Allow to remove 'Number of builds' column from 'All' view Issue Type: Bug Assignee: Unassigned Components: project-stats Created: 16/Oct/12 11:10 AM Description: When installing this plugin I didn't intend to modify main view, and so this is needed to configure columns that are shown in 'All' view. I know I can do https://wiki.jenkins-ci.org/display/JENKINS/Editing+or+Replacing+the+All+View but this should be a plugin option whether this column is appended to 'All' or not Project: Jenkins Priority: Minor Reporter: Tomasz Bartczak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result
SCM/JIRA link daemon commented on JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result Code changed in jenkins User: r.baradari Path: src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java http://jenkins-ci.org/commit/cobertura-plugin/2e2f3b0568c4cc4ee235fc98d494a0b085f0bf67 Log: JENKINS-15518 changed anonymous inner FileCallable to nested class because the outer class is not serializable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result
SCM/JIRA link daemon commented on JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java http://jenkins-ci.org/commit/cobertura-plugin/e2777e8d795ae863ef24832bf23ad6b7c2ef490f Log: Merge pull request #10 from rbaradari/fix-15518 JENKINS-15518 changed anonymous inner FileCallable to nested class because the outer class is not serializable Compare: https://github.com/jenkinsci/cobertura-plugin/compare/9e6a61b3048a...e2777e8d795a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result
Ramin Baradari commented on JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result A patch is available for merge in this pull request: https://github.com/jenkinsci/cobertura-plugin/pull/10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15521) Backup plugin can't restore in Ubuntu with Unable to created directory
Richard Mortimer commented on JENKINS-15521 Backup plugin can't restore in Ubuntu with Unable to created directory @James Yin. Your suggestion of a chmod -R is a bit too permissive. After you have done that you have made the entire contents of /var/lib writeable by anyone with login access to your machine. I really would caution against doing that. A better (untested) way would be to do sudo mkdir /var/lib/jenkins_restore sudo chown jenkins /var/lib/jenkins_restore or if that does not work and you really need to change the permissions of /var/lib then just do sudo chmod 777 /var/lib ... perform restore ... sudo chmod 755 /var/lib But certainly you do not need to supply the -R parameter to chmod. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4266) Enable Support for SSL Client Certificates
Christoph Torens commented on JENKINS-4266 Enable Support for SSL Client Certificates unforunately, the link is not working anymore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15521) Backup plugin can't restore in Ubuntu with Unable to created directory
James Yin commented on JENKINS-15521 Backup plugin can't restore in Ubuntu with Unable to created directory This problem is caused by permission limit to Create folder, a workaround is chmod -R 0777 /var/lib, to set all permission to all user. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15199) Slaves turns to "Dead" state after connecting to remote machine
Steven Aerts edited a comment on JENKINS-15199 Slaves turns to "Dead" state after connecting to remote machine We are seeing this problem on jenkins version 1.486. We see exact the same stacktrace as Stewart. We see this only on nodes coupled with matrix jobs. Some of our matrix jobs we are not able to run anymore. Whenever one of those matrix jobs is started its node crashes with this NPE exception. It is unclear for us what the discriminator is which makes a matrix job faulty. Doe anyone have an idea what could cause these matrix jobs to crash. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6965) GT seems to loose it's connection to Gerrit without re-connecting
glundh commented on JENKINS-6965 GT seems to loose it's connection to Gerrit without re-connecting You guys that still see this issue, would you mind building & testing this release? https://github.com/jenkinsci/gerrit-trigger-plugin/commit/9d6e7db02dea2e79ec87a9bb02d8c0cbeaa4fbbd The jsch dependency has been updated, and it has a few fixes which could potentially help solve this issue. Please know that this is a unreleased version of Gerrit-Trigger (do not yet bring it into your 99.999% uptime production system). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15199) Slaves turns to "Dead" state after connecting to remote machine
Steven Aerts edited a comment on JENKINS-15199 Slaves turns to "Dead" state after connecting to remote machine We are seeing this problem on jenkins version 1.486. We see exact the same stacktrace as Stewart. We see this only on nodes coupled with matrix jobs. We have the impression that we are not able to run any matrix job anymore. Whenever a matrix job is started its node crashes with this NPE exception/ Can anyone confirm this behavior on their setup? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15199) Slaves turns to "Dead" state after connecting to remote machine
Steven Aerts commented on JENKINS-15199 Slaves turns to "Dead" state after connecting to remote machine We are seeing this problem on jenkins version 1.486. We see exact the same stacktrace as Stewart. We see this only on nodes coupled with matrix jobs. We have the impression that we are not able to run any matrix job anymore. Whenever a matrix job is started its node crashes with this NPE exception/ Can anyone confirm this behavior on their setup? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15199) Slaves turns to "Dead" state after connecting to remote machine
Steven Aerts updated JENKINS-15199 Slaves turns to "Dead" state after connecting to remote machine Set assignee to Automatic so some of the core developers can take this up. Change By: Steven Aerts (16/Oct/12 7:40 AM) Labels: fail jenkins matrix slave startup Assignee: Carlos André Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15525) ProjectSet parser isn't working
Félix velasco commented on JENKINS-15525 ProjectSet parser isn't working Regarding your points: 1. I thought that colon was mandatory, not optional. That's why I took it out of the optional part 2. My bad, I put the slash in the wrong place (most embarrassingly, since I need that slash in the middle of the remote module name). However, I honestly believe regexp is way too complicated, error-prone and hard to maintain for this job. Just a couple of StringTokenizers, first using commas, then colons for the cvsroot, should be enough. Just my two cents. Anyway, the committed change works perfectly for my psfs. Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15490) Analysis parsers don't work with maven 2 jobs
Ulli Hafner commented on JENKINS-15490 Analysis parsers don't work with maven 2 jobs Ok, I see. Until that is fixed, can you please try as a workaround: switch to the freestyle job type split your job into a maven 2 job that builds your project (and produces the checkstyle results) and a freestyle job that simply parses the results from the first job and visualizes the results This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15490) Analysis parsers don't work with maven 2 jobs
Ulli Hafner updated JENKINS-15490 Analysis parsers don't work with maven 2 jobs Change By: Ulli Hafner (16/Oct/12 7:15 AM) Summary: Analysis parsers don't work with maven 2 projects jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15490) Analysis parsers don't work with maven 2 projects
Ulli Hafner
updated JENKINS-15490
Analysis parsers don't work with maven 2 projects
Change By:
Ulli Hafner
(16/Oct/12 7:15 AM)
Summary:
checkstyle plugin does not
Analysis parsers don't
work
in the latest version of Jenkins
with maven 2 projects
Labels:
IllegalAccessError LogFactoryImpl checkstyle
Environment:
windows XP
maven 2.1
Priority:
Blocker
Minor
Description:
In the latest version(1.485) of Jenkins with only Checkstyle plugin and Static Analysis Utilities/Static Analysis Collector Plug-in installed and no any other configuration change, enabling Publish Checkstyle analysis results
in a maven 2 job type
and use checkstyle:checkstyle as maven goal will get exception as below:{noformat}[INFO] [INFO] Traceorg.apache.commons.logging.LogConfigurationException: java.lang.IllegalAccessError: tried to access class org.apache.commons.logging.impl.LogFactoryImpl$3 from class org.apache.commons.logging.impl.LogFactoryImpl (Caused by java.lang.IllegalAccessError: tried to access class org.apache.commons.logging.impl.LogFactoryImpl$3 from class org.apache.commons.logging.impl.LogFactoryImpl) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:637) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:704) at org.apache.commons.digester.Digester.(Digester.java:304) at hudson.plugins.checkstyle.parser.CheckStyleParser.parse(CheckStyleParser.java:48) at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:53) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:261) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:220) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:169) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:851) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.checkstyle.CheckStyleReporter.perform(CheckStyleReporter.java:120) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:313) at hudson.maven.Maven2Builder.postExecute(Maven2Builder.java:155) at hudson.maven.MavenBuilder$Adapter.postExecute(MavenBuilder.java:310) at hudson.maven.agent.PluginManagerInterceptor$1MojoIntercepterImpl.callPost(PluginManagerInterceptor.java:170) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:183) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.La
