date:20130225
















































Jesse Glick
 resolved  JENKINS-16949 as Fixed


http://jenkins-ci.org/changelog is not updating
















A major changelog corruption was recently fixed. Not sure it is 100% correct now, but better anyway.





Change By:


Jesse Glick
(26/Feb/13 4:06 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-12542) Upgrade xstream to 1.4.2

SCM/JIRA link daemon
commented on JENKINS-12542

Upgrade xstream to 1.4.2

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/pom.xml
core/src/main/java/hudson/util/RobustReflectionConverter.java
core/src/main/java/hudson/util/StringConverter2.java
core/src/main/java/hudson/util/XStream2.java
core/src/main/java/hudson/util/xstream/MapperDelegate.java
core/src/test/java/hudson/util/CopyOnWriteMapTest.java
http://jenkins-ci.org/commit/jenkins/319372b88749b683649549ea52730dac2fc0a8aa
Log:
[FIXED JENKINS-12542] upgraded to XStream 1.4.4

There are several incompatibilities in XStream 1.4 that resulted in our
changing the core, but according to the text search on all the public
plugins, none of these changes affect the 600+ plugins we have today.

However, it is still possible that there are some parts of XStream 1.3
that plugins depend on but the core doesn't depend on — we won't be
able to tell those problems at this point.

–
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-12542) Upgrade xstream to 1.4.2
















































SCM/JIRA link daemon
 resolved  JENKINS-12542 as Fixed


Upgrade xstream to 1.4.2
















Change By:


SCM/JIRA link daemon
(26/Feb/13 3:24 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs

2013-02-25 Thread jpsch...@mtu.net (JIRA)















































jpschewe
 commented on  JENKINS-16923


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs















I upgraded all plugins and the core at the same time and now I see all of my 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-9259) Include promotion status in the JSON/XML for a build

2013-02-25 Thread zhh...@gmail.com (JIRA)













































  
Hua Zhang
 edited a comment on  JENKINS-9259


Include promotion status in the JSON/XML for a build
















One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine. 

I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks: 
  job/[jobname]/promotion/latest/[PromotionName]/api/json
and eventually information of every promoted build:
  job/[jobname]/[PromotionName]/promotion/[PromotionName]/promotionBuild/num/api/json

But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get.

It would be nice if the following information could be exposed through remote access api:
a) promotion status for each build, and/or 
b) a summary/history of all promotion builds with reference to the being promoted build number.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [JIRA] (JENKINS-16940) Git publisher fails with "Invalid id: origin/master" when trying to publish changes

2013-02-25 Thread nathan.oakes

This is blocking us as well.

git --version
git version 1.7.0.4
Fetching upstream changes from cloudforge
Cleaning workspace
Resetting working tree
Commencing build of Revision bdcbf15cb22058e5fdbb0e12ffeb9db8a15cc394
(cloudforge/develop)
Merging Revision bdcbf15cb22058e5fdbb0e12ffeb9db8a15cc394
(cloudforge/develop) onto master
FATAL: Invalid id: cloudforge/master
java.lang.IllegalArgumentException: Invalid id: cloudforge/master

Please let me know if there is anything I can provide to help.



--
View this message in context: 
http://jenkins.361315.n4.nabble.com/JIRA-JENKINS-16940-Git-publisher-fails-with-Invalid-id-origin-master-when-trying-to-publish-changes-tp4656853p4657102.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16632) Jclouds BlobStore writes key to console log when blob store returns 401 error.















































SCM/JIRA link daemon
 commented on  JENKINS-16632


Jclouds BlobStore writes key to console log when blob store returns 401 error.















Code changed in jenkins
User: Andrew Bayer
Path:
 src/main/java/jenkins/plugins/jclouds/blobstore/BlobStorePublisher.java
http://jenkins-ci.org/commit/jclouds-plugin/d4e47c8cca68011bbff4b5b7e463a5a8ac8cd05d
Log:
  Merge pull request #36 from cboylan/fix-JENKINS-16632

[Fix JENKINS-16632] Don't print auth stack traces.


Compare: https://github.com/jenkinsci/jclouds-plugin/compare/01991c65a1f3...d4e47c8cca68

– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16632) Jclouds BlobStore writes key to console log when blob store returns 401 error.















































SCM/JIRA link daemon
 commented on  JENKINS-16632


Jclouds BlobStore writes key to console log when blob store returns 401 error.















Code changed in jenkins
User: Clark Boylan
Path:
 src/main/java/jenkins/plugins/jclouds/blobstore/BlobStorePublisher.java
http://jenkins-ci.org/commit/jclouds-plugin/8b55b2f580e6f0a3ab89c7f5f265952d11e27a41
Log:
  [Fix JENKINS-16632] Don't print auth stack traces.

Really fix JENKINS-16632. We cannot print the AuthorizationException
stack trace because it contains private auth info and printing the stack
trace writes it to the Jenkins build console log. Instead catch
AuthorizationExceptions then create a new RuntimeException whose message
can be printed. Print the RuntimeException stack trace and a helpful
message that authorization failed.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-9259) Include promotion status in the JSON/XML for a build

2013-02-25 Thread zhh...@gmail.com (JIRA)















































Hua Zhang
 commented on  JENKINS-9259


Include promotion status in the JSON/XML for a build















One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine. 

I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks: 
  job/[jobname]/promotion/latest/[PromotionName]/api/json
and eventually information of every promoted build:
  job/[jobname]/[PromotionName]/promotion/[PromotionName]/promotionBuild/num/api/json

But the response does not contain the any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get.

It would be nice if the following information could be exposed through remote access api:
a) promotion status each build, and/or 
b) a summary/history of all promotion builds with reference to the being promoted build number.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-11972) Cannot create job with promoted build plugin automatically using jenkins API

2013-02-25 Thread zhh...@gmail.com (JIRA)















































Hua Zhang
 commented on  JENKINS-11972


Cannot create job with promoted build plugin automatically using jenkins API















We work around this by using CLI copy-job. The copy-job command does copy all promotion configurations. 
I suspect the sshd command would do the same, but I have not tested this.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16957) Tracker field validations not working in CollabNet plugin

2013-02-25 Thread jmcna...@collab.net (JIRA)















































John McNally
 created  JENKINS-16957


Tracker field validations not working in CollabNet plugin















Issue Type:


Bug



Affects Versions:


current



Assignee:


John McNally



Components:


collabnet



Created:


25/Feb/13 10:17 PM



Description:


The tracker field is always showing the error 
"The tracker is required."
even when a valid tracker is entered.
And the assignee field does not validate at all. 




Project:


Jenkins



Priority:


Minor



Reporter:


John McNally

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16956) Authentication associated with a build

Jesse Glick
created JENKINS-16956

Authentication associated with a build

Issue Type:

New Feature

Assignee:

Unassigned

Components:

core

Created:

25/Feb/13 10:04 PM

Description:

Various build steps (or other code run during builds) ought to be checking permissions. For example, you should only be able to trigger a downstream build if "you" would otherwise have permission to schedule that job manually. Similarly for accessing artifacts, running on secure slave nodes, and so on.

Unfortunately in Jenkins currently all builds run in SYSTEM, i.e. effectively having all permissions, and it is up to each build step to do its own checks. Worse, there is no clear authentication to associate with the build. If it was started manually by a particular user, you could use that authentication, but other causes do not lead to a clear user name.

There should be some (probably extensible) system of associating an Authentication with a given Run, either based on its Cause or something else such as the last User to configure the Job.

Project:

Jenkins

Labels:

security
permissions

Priority:

Major

Reporter:

Jesse Glick

[JIRA] (JENKINS-3939) Downstream build failures not assigned to player

2013-02-25 Thread john.arme...@sage.com (JIRA)















































John Armenia
 commented on  JENKINS-3939


Downstream build failures not assigned to player















We are in the same boat as Grant.  All our projects are broken down into sub projects and only the top level project give credit for the commit.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16955) Strange Behaviors since installing

2013-02-25 Thread qhart...@gmail.com (JIRA)

Quentin Hartman
created JENKINS-16955

Strange Behaviors since installing

Issue Type:

Bug

Assignee:

Nicolas De Loof

Components:

build-flow

Created:

25/Feb/13 9:22 PM

Description:

I'm running Jenkins 1.502, and ever since installing Build-Flow, I've noticed strange behavior in the UI. If I try to launch a job from the main dashboard via the "build now" button in the box that pops up when hovering over the job, I get a screen with the warning:

You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.

The build still executes, but this should not happen. Additionally, our build history is not saving consistently any more, both on build-flow jobs, and others.

I see this behavior when either 0.7 or 0.8 of the build-flow plugin is installed. It also seems to happen whether or not the plugin is enabled.

Project:

Jenkins

Priority:

Major

Reporter:

Quentin Hartman

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs
















































Ulli Hafner
 resolved  JENKINS-16923 as Duplicate


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs
















Change By:


Ulli Hafner
(25/Feb/13 9:18 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs















































Ulli Hafner
 commented on  JENKINS-16923


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs















Ok, thanks. Then this really looks like JENKINS-12124.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs

2013-02-25 Thread jpsch...@mtu.net (JIRA)















































jpschewe
 commented on  JENKINS-16923


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs















I only upgraded the core, not the plugins. I didn't try this again as I didn't have time to have a broken Jenkins for long, so I just reverted.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16780) release build fails to deploy new SNAPSHOT pom artifact with 409 error

2013-02-25 Thread kcs_si...@hotmail.com (JIRA)















































Kc Singh
 started work on  JENKINS-16780


release build fails to deploy new SNAPSHOT pom artifact with 409 error
















Change By:


Kc Singh
(25/Feb/13 9:02 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16780) release build fails to deploy new SNAPSHOT pom artifact with 409 error

2013-02-25 Thread kcs_si...@hotmail.com (JIRA)















































Kc Singh
 stopped work on  JENKINS-16780


release build fails to deploy new SNAPSHOT pom artifact with 409 error
















Change By:


Kc Singh
(25/Feb/13 9:02 PM)




Status:


In Progress
Open



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16954) Usability problem finding cause of build failure via web

2013-02-25 Thread bel...@alum.mit.edu (JIRA)

Christopher Beland
created JENKINS-16954

Usability problem finding cause of build failure via web

Issue Type:

Bug

Affects Versions:

current

Assignee:

jieryn

Components:

job-log-logger

Created:

25/Feb/13 9:00 PM

Description:

A recent checkin caused a build failure, so I went to a URL like:

http://jenkins.example.com:8080/job/ProjectName/253/

which is what got emailed out.

That page reports: Jenkins ver. 1.467

My goal in going to this page is to find the output from the actual build job, so I can diagnose and fix the failure. We have two platforms for ProjectName, i686 and x86_64.

The correct way to do this is to click on i686, then either "Console Output" or "[raw]" in the menu on the left. This is not intuitive, and failed several times to find this and had to email a co-worker for help.

I had tried clicking Console Output first; that log is not useful.

That Console Output page has i686 links in the body text; but that brings me to the Jenkins configuration page for that architecture:
http://jenkins.example.com:8080/job/ProjectName/ARCH=i686/

I then tried clicking "i686" from the first page, but the resulting page was obviously not helpful. It was not intuitive that the "Console Output" link on the left would take me anywhere different from this page than it did from the previous page.

Perhaps universally linking to the sub-logs from that universal menu would be the easiest way to solve the problem. Better direct linking from the first page might also help, but that's not necessarily the starting point that everyone who uses Jenkins would be coming from?

I don't know if the component I have chosen for this ticket is correct. "Unknown" is not an option, so I had to choose somewhat randomly.

Project:

Jenkins

Priority:

Minor

Reporter:

Christopher Beland

[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy

2013-02-25 Thread s.chagn...@lectra.com (JIRA)













































  
Sylvain C.
 edited a comment on  JENKINS-16868


Icons are not displayed with a reverse proxy
















The plugin uses getRootUrlFromRequest() ( http://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getRootUrl() ) for getting image base url but I read in jenkins api documentation this method is not compatible with reverse proxy whereas I believe getRootUrl() ( http://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getRootUrlFromRequest() ) works with a reverse proxy. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy

2013-02-25 Thread s.chagn...@lectra.com (JIRA)















































Sylvain C.
 commented on  JENKINS-16868


Icons are not displayed with a reverse proxy















The plugin uses getRootUrlFromRequest() (http://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getRootUrl()) for getting image base url but I read in jenkins api documentation this method is not compatible with reverse proxy whereas I believe getRootUrl() (http://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getRootUrlFromRequest()) works with a reverse proxy. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16953) Unable to run Jenksin with Java for ARM hard float

2013-02-25 Thread wouter....@gmail.com (JIRA)















































Wouter Oet
 commented on  JENKINS-16953


Unable to run Jenksin with Java for ARM hard float















I might have spoken to soon. It does work with JDK 8 for ARM. 

However there is still a bug. When Jenkins is installed in the way I described it also installs the following packages: gcj-4.7-base gcj-4.7-jre gcj-4.7-jre-headless gcj-4.7-jre-lib gcj-jre gcj-jre-headless libgcj13 libgcj13-awt. I didn't notice them when I installed Jenkins thus thinking I only had one Java version which failed. But apparently doesn't gcj provide all the classes which Jenkins need. 

So I still would move to all standard classes and fix the dependencies. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs













































  
Ulli Hafner
 edited a comment on  JENKINS-16923


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs
















Did you also upgrade any plug-ins? This looks like a class loading problem in core. 

Is this error always reproducible, or happens just sometimes on startup? 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs

2013-02-25 Thread glen.ditchfi...@investorsgroup.com (JIRA)















































Ulli Hafner
 commented on  JENKINS-16923


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs















Did you also upgrade any plug-ins? This looks like a class loading problem in core. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16952) Log messages not sent to /log/all unless in hudson.* or jenkins.* namespaces

2013-02-25 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-16952


Log messages not sent to /log/all unless in hudson.* or jenkins.* namespaces















Integrated in  jenkins_main_trunk #2299
 [FIXED JENKINS-16952] Not all log messages were being captured at /log/all. (Revision 3a0126f780bbd133d50615354a61e20364eb1fdf)

 Result = SUCCESS
Jesse Glick : 3a0126f780bbd133d50615354a61e20364eb1fdf
Files : 

	core/src/main/java/hudson/WebAppMain.java
	changelog.html





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-3951) Hudson does not Undeploy correctly















































Glen Ditchfield
 updated  JENKINS-3951


Hudson does not Undeploy correctly
















Change By:


Glen Ditchfield
(25/Feb/13 8:00 PM)




Summary:


Hudson does not
 Undeply correct
 Undeploy correctly





Component/s:


other





Component/s:


deploy



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16953) Unable to run Jenksin with Java for ARM hard float

2013-02-25 Thread wouter....@gmail.com (JIRA)















































Wouter Oet
 created  JENKINS-16953


Unable to run Jenksin with Java for ARM hard float















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


25/Feb/13 7:46 PM



Description:


You're unable to run Jenkins on the raspberry pi with the new Java JDK 8 for ARM (http://jdk8.java.net/fxarmpreview/). Although the JDK is still in 'early access' it shows that Jenkins is still using non-standard Java classes such as sun.security.util.DerValue.

Jenkins was installed by adding the following line to /etc/apt/sources.list:
deb http://pkg.jenkins-ci.org/debian binary/


	sudo apt-get update
	sudo apt-get install jenkins



In /var/log/jenkins/jenkins.log appears the following stacktrace:

Running from: /usr/share/jenkins/jenkins.war
25 Feb 2013 18:47:34 winstone.Logger logInternal
INFO: Beginning extraction from war file
25 Feb 2013 18:48:33 hudson.WebAppMain contextInitialized
SEVERE: Failed to initialize Jenkins
java.lang.ExceptionInInitializerError
   at java.lang.Class.initializeClass(libgcj.so.13)
   at hudson.WebAppMain.installLogger(WebAppMain.java:253)
   at hudson.WebAppMain.contextInitialized(WebAppMain.java:104)
   at winstone.WebAppConfiguration.(WebAppConfiguration.java:876)
   at winstone.HostConfiguration.initWebApp(HostConfiguration.java:129)
   at winstone.HostConfiguration.(HostConfiguration.java:71)
   at winstone.HostGroup.initHost(HostGroup.java:87)
   at winstone.HostGroup.(HostGroup.java:47)
   at winstone.Launcher.(Launcher.java:177)
   at winstone.Launcher.main(Launcher.java:384)
   at java.lang.reflect.Method.invoke(libgcj.so.13)
   at Main._main(Main.java:273)
   at Main.main(Main.java:98)
Caused by: java.lang.NullPointerException
   at com.thoughtworks.xstream.core.JVM.isOpenJDK(JVM.java:72)
   at com.thoughtworks.xstream.core.JVM.canUseSun14ReflectionProvider(JVM.java:198)
   at com.thoughtworks.xstream.core.JVM.bestReflectionProvider(JVM.java:175)
   at com.thoughtworks.xstream.XStream.(XStream.java:431)
   at com.thoughtworks.xstream.XStream.(XStream.java:385)
   at com.thoughtworks.xstream.XStream.(XStream.java:323)
   at hudson.util.XStream2.(XStream2.java:79)
   at jenkins.model.Jenkins.(Jenkins.java:3798)
   at java.lang.Class.initializeClass(libgcj.so.13)
   at hudson.WebAppMain.installLogger(WebAppMain.java:253)
   at hudson.WebAppMain.contextInitialized(WebAppMain.java:104)
   at winstone.WebAppConfiguration.(WebAppConfiguration.java:876)
   at winstone.HostConfiguration.initWebApp(HostConfiguration.java:129)
   at winstone.HostConfiguration.(HostConfiguration.java:71)
25 Feb 2013 18:48:36 winstone.Logger logInternal
SEVERE: Error during context startup for webapp webapp
java.lang.ExceptionInInitializerError
   at java.lang.Class.initializeClass(libgcj.so.13)
   at hudson.WebAppMain.installLogger(WebAppMain.java:253)
   at hudson.WebAppMain.contextInitialized(WebAppMain.java:104)
   at winstone.WebAppConfiguration.(WebAppConfiguration.java:876)
   at winstone.HostConfiguration.initWebApp(HostConfiguration.java:129)
   at winstone.HostConfiguration.(HostConfiguration.java:71)
   at winstone.HostGroup.initHost(HostGroup.java:87)
   at winstone.HostGroup.(HostGroup.java:47)
   at winstone.Launcher.(Launcher.java:177)
   at winstone.Launcher.main(Launcher.java:384)
   at java.lang.reflect.Method.invoke(libgcj.so.13)
   at Main._main(Main.java:273)
   at Main.main(Main.java:98)
Caused by: java.lang.NullPointerException
   at com.thoughtworks.xstream.core.JVM.isOpenJDK(JVM.java:72)
   at com.thoughtworks.xstream.core.JVM.canUseSun14ReflectionProvider(JVM.java:198)
   at com.thoughtworks.xstream.core.JVM.bestReflectionProvider(JVM.java:175)
   at com.thoughtworks.xstream.XStream.(XStream.java:431)
   at com.thoughtworks.xstream.XStream.(XStream.java:385)
   at com.thoughtworks.xstream.XStream.(XStream.java:323)
   at hudson.util.XStream2.(XStream2.java:79)
   at jenkins.model.Jenkins.(Jenkins.java:3798)
   at java.lang.Class.initializeClass(libgcj.so.13)
   at hudson.WebAppMain.installLogger(WebAppMain.java:253)
   at hudson.WebAppMain.conte

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs
















































Jesse Glick
 assigned  JENKINS-16923 to Ulli Hafner



Upgrade from 1.480.2 to 1.480.3 lost most of my jobs
















Change By:


Jesse Glick
(25/Feb/13 7:37 PM)




Assignee:


Ulli Hafner



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs

2013-02-25 Thread glen.ditchfi...@investorsgroup.com (JIRA)















































Jesse Glick
 updated  JENKINS-16923


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs
















Change By:


Jesse Glick
(25/Feb/13 7:37 PM)




Component/s:


analysis-core





Component/s:


core



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs

2013-02-25 Thread jpsch...@mtu.net (JIRA)















































jpschewe
 commented on  JENKINS-16923


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs















Yep, I went back farther in the log. This is the first non-info message after restarting with 1.480.3.

EVERE: Failed Loading job geodesy-cpp
java.lang.NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at hudson.plugins.warnings.WarningsPublisher.getProjectActions(WarningsPublisher.java:252)
at hudson.model.Project.createTransientActions(Project.java:213)
at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:658)
at hudson.model.AbstractProject.onLoad(AbstractProject.java:292)
at hudson.model.Project.onLoad(Project.java:88)
at hudson.model.Items.load(Items.java:209)
at jenkins.model.Jenkins$17.run(Jenkins.java:2516)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:882)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException: hudson.plugins.analysis.core.AbstractProjectAction
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
... 26 more
Feb 20, 2013 10:04:43 PM jenkins.InitReactorRunner$1 onTaskFailed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-3951) Hudson does not Undeply correct

Glen Ditchfield
reopened JENKINS-3951

Hudson does not Undeply correct

Windows 7 Professional 32-bit / Tomcat 7.0.37 / Jenkins 1.480.3
Windows Server 2003 x64 / Tomcat 7.0.11 / Jenkins 1.480.1, 1.480.2

I would like to upgrade Jenkins by undeploying and redeploying through the Tomcat Web Application Manager, but "undeploy" fails. The Manager cannot delete ...\webapps\jenkins\WEB-INF\lib\winp.dll (and sometimes some other files). I have to stop Tomcat, which disrupts other applications, and hand-delete the files.

I have tried adding a context file with antiJARLocking="true" to conf/Catalina/localhost, but that doesn't quite work for me.

When Tomcat undeploys Jenkins, it deletes the context file.
If I put the context file in .../localhost before deploying Jenkins, deploying fails.
If I put the context file in .../localhost after deploying Jenkins, I have to restart Tomcat for antiJARLocking to take effect.

Apache advises against adding context settings to server.xml.

Change By:

Glen Ditchfield
(25/Feb/13 7:23 PM)

Resolution:

Cannot Reproduce

Status:

Resolved
Reopened

[JIRA] (JENKINS-16952) Log messages not sent to /log/all unless in hudson.* or jenkins.* namespaces















































SCM/JIRA link daemon
 commented on  JENKINS-16952


Log messages not sent to /log/all unless in hudson.* or jenkins.* namespaces















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/WebAppMain.java
http://jenkins-ci.org/commit/jenkins/3a0126f780bbd133d50615354a61e20364eb1fdf
Log:
  [FIXED JENKINS-16952] Not all log messages were being captured at /log/all.



– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16952) Log messages not sent to /log/all unless in hudson.* or jenkins.* namespaces
















































SCM/JIRA link daemon
 resolved  JENKINS-16952 as Fixed


Log messages not sent to /log/all unless in hudson.* or jenkins.* namespaces
















Change By:


SCM/JIRA link daemon
(25/Feb/13 7:13 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16952) Log messages not sent to /log/all unless in hudson.* or jenkins.* namespaces















































Jesse Glick
 created  JENKINS-16952


Log messages not sent to /log/all unless in hudson.* or jenkins.* namespaces















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


25/Feb/13 7:04 PM



Description:


WebAppMain.installLogger only registers log handlers on a couple of top-level namespaces. Records logged under other names appear e.g. in stderr but not in /log/all.

That is fine for core, but very bad for plugins which do their own logging, as these may be in all sorts of package hierarchies. For example, org.jenkinsci for plugins created from archetype. You can even see this with the SSHD plugin which logs something at startup that is lost from the web UI.

The handler should I think be registered at the namespace root. If there is a need to specifically exclude messages from certain kinds of classes, such as those in an app server hosting Jenkins, then these should be blacklisted (e.g. by skipping just those records whose source class name can be defined in a class loader which is an ancestor of that used to load Jenkins.class).




Project:


Jenkins



Labels:


logging




Priority:


Major



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-14089) JUnit report - Quarantine intermittent tests

2013-02-25 Thread samuel.n...@taitradio.com (JIRA)















































samuel nobs
 commented on  JENKINS-14089


JUnit report - Quarantine intermittent tests















i don't know anything about getting a plugin hosted, but should be easy enough to find out. my biggest problem right now is to get approval to spend time on writing the plugin during work hours...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16881) Missing XML Declaration in Node's config.xml

2013-02-25 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-16881


Missing XML Declaration in Node's config.xml















Integrated in  jenkins_main_trunk #2297
 [FIXED JENKINS-16881] Introduced XStream2.toXMLUTF8. (Revision b14a7a36e47934375c768d3d317403b01a6982ea)

 Result = SUCCESS
Jesse Glick : b14a7a36e47934375c768d3d317403b01a6982ea
Files : 

	core/src/main/java/hudson/model/View.java
	changelog.html
	core/src/main/java/hudson/util/XStream2.java
	core/src/main/java/hudson/model/Computer.java
	core/src/test/java/hudson/util/XStream2EncodingTest.java





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16950) Can't remove sort of phases in multijob project















































Vlad Beffa
 commented on  JENKINS-16950


Can't remove sort of phases in multijob project















Only by deleting all of my browser cookies was I able to reset the order. Even when I individually removed the cookies associated with the URL of the Jenkins server, the order was not reset. I am using Firefox 18.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16437) Extract MailAddressResolvers to dedicated plugins

2013-02-25 Thread julian.k...@kleientertainment.com (JIRA)















































Jesse Glick
 commented on  JENKINS-16437


Extract MailAddressResolvers to dedicated plugins 















I have to agree with @kutzi that having published plugins known to cause abysmal performance problems is not a good idea. Lots of people will just blindly install stuff and not read the warnings. Better to unconditionally delete bad code.

If there is a real use case for mail address resolvers that infer information from build records, then they should be written carefully to have reasonable performance. For example:


	require the user to specify a sample job or jobs, rather than searching every job in the Jenkins installation
	inspect only up to some maximum number of build records per job (with lazy loading this is especially critical)
	cache information obtained from such searches, e.g. using the Database plugin, so you have only a one-time hit





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16951) Violations plugin don't report score to ci-game plugin for gendarme

2013-02-25 Thread imakow...@gmail.com (JIRA)















































Ireneusz Makowski
 created  JENKINS-16951


Violations plugin don't report score to ci-game plugin for gendarme















Issue Type:


Bug



Assignee:


redsolo



Components:


ci-game, violations



Created:


25/Feb/13 5:22 PM



Description:


When user fixes a rule violation reported by gendarme score is not calculated for ci-game. FxCop works fine




Environment:


Jenkins 1.502 

Latest version of violations plugin and ci-game




Project:


Jenkins



Priority:


Major



Reporter:


Ireneusz Makowski

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-12983) Redundat syncs when using matrix jobs















































Julian Kwan
 commented on  JENKINS-12983


Redundat syncs when using matrix jobs















As an additional note, if there are numerous projects configured to use a Matrix build then the master machine can be really hobbled as it tries to simultaneously sync all the projects that exist. This sync phase does not get queued because it doesn't require an executor to run, it's just the master preparing itself to tell the slaves to do something.

As a result, the master machine ends up crawling as the disk usage goes through the roof from many (large) projects syncing at once.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16881) Missing XML Declaration in Node's config.xml















































SCM/JIRA link daemon
 commented on  JENKINS-16881


Missing XML Declaration in Node's config.xml















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/View.java
 core/src/main/java/hudson/util/XStream2.java
 core/src/test/java/hudson/util/XStream2EncodingTest.java
http://jenkins-ci.org/commit/jenkins/b14a7a36e47934375c768d3d317403b01a6982ea
Log:
  [FIXED JENKINS-16881] Introduced XStream2.toXMLUTF8.



– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16881) Missing XML Declaration in Node's config.xml
















































SCM/JIRA link daemon
 resolved  JENKINS-16881 as Fixed


Missing XML Declaration in Node's config.xml
















Change By:


SCM/JIRA link daemon
(25/Feb/13 5:14 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16314) cvs plugin removes sticky branch tag

2013-02-25 Thread aandru...@andrulis.com.br (JIRA)















































Adriano Andrulis
 commented on  JENKINS-16314


cvs plugin removes sticky branch tag















Hi Michael, while debugging the code I found the problem is in the cleanout method on the FileCallable inner class on the AbstractCVS.java line 695. 
It call entry.setDate(null) that also removes the tag entry as it's stated on its javadoc "Set the sticky date information. Note that setting this will remove any tag information that is currently set."

private void cleanup(File directory, AdminHandler adminHandler) throws IOException {
for (File file : adminHandler.getAllFiles(directory)) {
Entry entry = adminHandler.getEntry(file);
String savedTag = entry.getTag();
entry.setDate(null); 

adminHandler.setEntry(file, entry);
}

I hope that helps your analysis. 
As a quick fix I've changed my AbstractCVS code as below but I'm not fully sure of the consequences.
 entry.setDate(null); 
to
String savedTag = entry.getTag();
entry.setDate(null);
if(savedTag != null) {
	entry.setTag(savedTag);
}




Thanks and Regards.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16946) Ratio percentgraph is wrong, bad alignment, length random

2013-02-25 Thread kettle-...@syntron.com (JIRA)















































Marcel L
 reopened  JENKINS-16946


Ratio percentgraph is wrong, bad alignment, length random
















Could oyu please double check ? 





Change By:


Marcel L
(25/Feb/13 4:38 PM)




Resolution:


Not A Defect





Status:


Closed
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16950) Can't remove sort of phases in multijob project















































Vlad Beffa
 commented on  JENKINS-16950


Can't remove sort of phases in multijob project















I was able to work around this by renaming the job to a new name and then renaming it back. This removed the sort, but there should still be a way to do this without having to rename the job.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16950) Can't remove sort of phases in multijob project















































Vlad Beffa
 commented on  JENKINS-16950


Can't remove sort of phases in multijob project















Actually I spoke too soon, renaming does not remove the sort. When the job is viewed from its view, it keeps the sort. If it is viewed in the global (all) view, the original default sort is applied.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16858) No build phases after update to 1.8

2013-02-25 Thread davew...@cisco.com (JIRA)















































David Watson
 updated  JENKINS-16858


No build phases after update to 1.8
















Change By:


David Watson
(25/Feb/13 4:26 PM)




Priority:


Major
Critical



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-12330) Occasionally,collecting findbugs analysis files will take very long time, event two more hours.

2013-02-25 Thread mi...@mikey.com (JIRA)















































michael pechner
 commented on  JENKINS-12330


Occasionally,collecting findbugs analysis files will take very long time, event two more hours.















We did a reset and the data is gone.
Let me look at our setup.

We have findbugs configured outside of Jenkins.  It is in our ant files.  Maybe you are finding an old Jar file we already have on the system, or we have some old something the Jenkins findbugs is finding.

I'll look at things on my side.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16858) No build phases after update to 1.8

2013-02-25 Thread davew...@cisco.com (JIRA)















































David Watson
 commented on  JENKINS-16858


No build phases after update to 1.8















I also found out the hard way that when you update from multi-job plugin 1.7 -> 1.8 all the jobs disapear !! Whats worse, is that even if you try to add the jobs back in again you get a great big error 500 black screen of death !!! I was not as fortunate, as when I reverted back to 1.7 none of my jobs were available, so I had to manually put all the jobs back 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16950) Can't remove sort of phases in multijob project

2013-02-25 Thread michael.dec...@crx-services.com (JIRA)















































Vlad Beffa
 created  JENKINS-16950


Can't remove sort of phases in multijob project















Issue Type:


Bug



Assignee:


Unassigned


Components:


jenkins-multijob-plugin



Created:


25/Feb/13 4:22 PM



Description:


If you view a multiphase job and click on one of its columns (such as the Job column), the default sort (which is the order of the job phases) is removed, and there's no way to get it back. Perhaps there is but I can't find it. I even tried removing my cookies, and it still remembered the new sort. The sorting by columns makes little sense here, and the resulting table is confusing when the sort is applied.




Project:


Jenkins



Priority:


Major



Reporter:


Vlad Beffa

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16861) Add support for the Claim Plugin

2013-02-25 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-16861


Add support for the Claim Plugin















I think that in the future I'll make two extension points available

1) Recipient list, which can override the other recipient categories similar to how the triggers can override other triggers. This would make it so that the Claim plugin could implement their own recipient category if they wanted to.
2) I am already working on making the triggers into a better model of the extension point mechanism so that other plugins or code could cause triggers to occur.

I am also adding a ScriptTrigger and PreBuildScriptTrigger so that you could script your own triggers. Would these meet your needs? Basically the idea would be to empower other plugins to implement features like this so that the dependencies of email-ext don't grow exponentially with each plugin that people would like to have support for.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-12875) "No valid crumb was included in the request" errors all around













































  
Michael Decker
 edited a comment on  JENKINS-12875


"No valid crumb was included in the request" errors all around
















I've same issue, if I try to disable a project (use Jenkins v1.502):
   http://rhodan:8080/jenkins/job/myproject_3562/disable

It looks like, I would have the same issue, if I would try to enable it, if it is disabled: JENKINS-14501

I tried to added these line to /opt/tomcat/bin/catalina.sh, but it didn't solve the issue:
   — SNIP —
JAVA_OPTS="$JAVA_OPTS -Dhudson.security.csrf.requestfield=crumb"
   — SNAP —



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16949) http://jenkins-ci.org/changelog is not updating

2013-02-25 Thread richard_tay...@scee.net (JIRA)















































Richard Taylor
 created  JENKINS-16949


http://jenkins-ci.org/changelog is not updating















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


25/Feb/13 4:03 PM



Description:


Apologies for adding this to core but I can not find links for web admins.

http://jenkins-ci.org/changelog is not updating.

We are using Jenkins in a production environment and the automated changelog , voting and assiciated issues system is essential in helping us update to a stable version. Without it we are unable to know if it's safe to update.

Many thanks




Project:


Jenkins



Priority:


Major



Reporter:


Richard Taylor

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-12875) "No valid crumb was included in the request" errors all around

2013-02-25 Thread michael.dec...@crx-services.com (JIRA)















































Michael Decker
 commented on  JENKINS-12875


"No valid crumb was included in the request" errors all around















I've same issue, if I try to disable a project (use Jenkins v1.502):
   http://rhodan:8080/jenkins/job/myproject_3562/disable

It looks like, I would have the same issue, if I would try to enable it, if it is disabled: JENKINS-14501



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-15156) Builds disappear from build history after completion
















































Jesse Glick
 assigned  JENKINS-15156 to Unassigned



Builds disappear from build history after completion
















Change By:


Jesse Glick
(25/Feb/13 3:48 PM)




Assignee:


Jesse Glick



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-15156) Builds disappear from build history after completion















































Jesse Glick
 updated  JENKINS-15156


Builds disappear from build history after completion
















Change By:


Jesse Glick
(25/Feb/13 3:47 PM)




Status:


Reopened
Open



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-14814) "Ping-pong" builds store excessively large CauseAction















































Jesse Glick
 commented on  JENKINS-14814


"Ping-pong" builds store excessively large CauseAction















Should be in 1.479, but you might be hitting JENKINS-15747.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16923) Upgrade from 1.480.2 to 1.480.3 lost most of my jobs















































Jesse Glick
 commented on  JENKINS-16923


Upgrade from 1.480.2 to 1.480.3 lost most of my jobs















The mentioned error looks like a symptom, not the cause; maybe there is something earlier in your log? Could be a plugin-specific issue, especially if some jobs loaded while others did not.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

2013-02-25 Thread pedro.r...@mog-solutions.com (JIRA)















































pedro reis
 reopened  JENKINS-15156


Builds disappear from build history after completion
















Still disappearing at 1.502 (at least for failed builds)





Change By:


pedro reis
(25/Feb/13 3:20 PM)




Resolution:


Fixed





Status:


Resolved
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

2013-02-25 Thread pedro.r...@mog-solutions.com (JIRA)















































pedro reis
 commented on  JENKINS-15156


Builds disappear from build history after completion















Sorry, but failed builds still disappear on Jenkins v1.502...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16929) GNU make + GCC parser can't handle UTF-8















































Ulli Hafner
 commented on  JENKINS-16929


GNU make + GCC parser can't handle UTF-8















Yes, that is correct: what Jenkins serves is UTF-8. But I'm reading the raw output of the build! And that output seems to be build related. 

I think that I can try to switch to UTF-8 for the console log and see if others complain about 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32

2013-02-25 Thread nickolay.rumyant...@emc.com (JIRA)















































Nickolay Rumyantsev
 commented on  JENKINS-15466


Fatal Error No Class Definition found for Kernel32















it looks like the error is occured when Jenkins attempts to delete file on Windows 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16929) GNU make + GCC parser can't handle UTF-8

2013-02-25 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 commented on  JENKINS-16929


GNU make + GCC parser can't handle UTF-8















I would imagine it's globally set somewhere near the Winstone level. Everything that Jenkins serves is marked as UTF-8, including your plugin's output.
At minimum the default should be UTF-8, without having to go through every job config and set it 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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16948) JaCoCo - Support for changing build status

2013-02-25 Thread tommy...@visma.com (JIRA)















































Tommy Bø
 updated  JENKINS-16948


JaCoCo - Support for changing build status
















Change By:


Tommy Bø
(25/Feb/13 1:59 PM)




Summary:


JaCoCo -
Support for changing build status



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16946) Ratio percentgraph is wrong, bad alignment, length random

2013-02-25 Thread kettle-...@syntron.com (JIRA)















































Marcel L
 commented on  JENKINS-16946


Ratio percentgraph is wrong, bad alignment, length random















Hi Ogi,

could you please explain ?

Let's take the first bar in  Overall coverage summary , instruction. 

In the example we have M 19K, C 7K  gives coverage 26%. Fine. Why is the bar completly red ?

Second, why is the alignment broken ? The red bar has a different offset in a column (take the instruction col on the Coverage Breadown by package as example). I have plenty more examples of bad alignment)
I understand your point with the length . This is fine if it looks like here: 

http://www.eclemma.org/jacoco/trunk/coverage/org.jacoco.agent/org.jacoco.agent/AgentJar.html



Cheers,

Marcel



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16948) Support for changing build status

2013-02-25 Thread tommy...@visma.com (JIRA)















































Tommy Bø
 created  JENKINS-16948


Support for changing build status















Issue Type:


New Feature



Affects Versions:


current



Assignee:


Ognjen Bubalo



Components:


jacoco



Created:


25/Feb/13 1:58 PM



Description:


Add option to change build-status if coverage is insufficient. When releasing continuously we need to break builds that does not meet the requirements regarding code quality and code coverage. It is possible to handle this directly through the JaCoCo-maven-plugin, but I prefer to break the build as a post-build step after evaluating the aggregated result of a multi-module build.




Environment:


Jenkins JaCoCo plugin/1.0.12




Project:


Jenkins



Labels:


coverage
jacoco




Priority:


Minor



Reporter:


Tommy Bø

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16947) Dashboard as default view has broken configuration link

2013-02-25 Thread lgreg...@nyiso.com (JIRA)















































Larry Gregory
 created  JENKINS-16947


Dashboard as default view has broken configuration link















Issue Type:


Bug



Affects Versions:


current



Assignee:


Peter Hayes



Components:


dashboard-view



Created:


25/Feb/13 1:54 PM



Description:


When a Dashboard View is set as the default view, the north 'configure' link routes to the Jenkins "Configure System" page, instead of the Dashboard View's configuration.  The "Edit View" link on the west sidebar works correctly.




Environment:


Jenkins v1.502, Dashboard View v2.4




Project:


Jenkins



Labels:


plugin
configuration




Priority:


Minor



Reporter:


Larry Gregory

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-14508) Default pre-send script in Jenkins Configuration

2013-02-25 Thread m...@nordicsemi.no (JIRA)















































Markus Hjerto
 commented on  JENKINS-14508


Default pre-send script in Jenkins Configuration















That is how at least I'd like it. All the other fields have a global config level DEFAULT option, but the pre-sim script does not. Adding ${DEFAULT_PRE-SEND_SCRIPT} in the pre-sim script field in a job (it should maybe be there by default), should execute a pre-sim script defined globally. It would make it much easier to run the same script on all the jobs.

An alternative could be to adds support for ${SCRIPT, script="my-default-script.groovy"}, which is fetched from the email-templates directory.

Or even better - both. Let the pre-sim script behave like all the other fields.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16861) Add support for the Claim Plugin

2013-02-25 Thread m...@nordicsemi.no (JIRA)















































Markus Hjerto
 commented on  JENKINS-16861


Add support for the Claim Plugin















Thank you again. After a lot of trial and errors, the UserProperty problem was resolved: The class exists on the Jenkins production server, not on my simple test server. I guess it is because my test server only has the AD plugin installed but it does not use it. It uses Jenkins's own user database. Also, then "last line" trick did the trick.

But I've realized, now that this works, that I have to do this as a pre-mail script. I'd like to replace the default recipients and I'd like it not to email the Culprits and Committers if the job is claimed. So I have to edit the complete recipients list just before the mail is sent, which is a pre-send script. I'll guess I'll have to do some scripting to distribute the pre-send script to all the jobs until we can add global pre-mail scripts (JENKINS-14508).

Here's what I ended up with, for future googlers. I kept the array in case I'd like to add more recipients from other sources later.


def committers = []

build.actions.each { action ->
if(action.class.name == "hudson.plugins.claim.ClaimBuildAction" && action.isClaimed()) {
  hudson.model.User user = hudson.model.User.get(action.getClaimedBy());  
  address = user.getProperty(hudson.tasks.Mailer.UserProperty.class).address  
  committers[0]=address
}
}

// here comes the last line, it MUST be the last line for this to work!!
committers.unique().join(',')


I'd still like a built-in support for the Claim plugin, which was the initial request, so I'd prefer to leave this as open. But I'll accept a Won't Fix if you prefer that such things are resolved using the (excellent) scripting features.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16946) Ratio percentgraph is wrong, bad alignment, length random

2013-02-25 Thread ognjen.bub...@gmail.com (JIRA)
















































Ognjen Bubalo
 closed  JENKINS-16946 as Not A Defect


Ratio percentgraph is wrong, bad alignment, length random
















Change By:


Ognjen Bubalo
(25/Feb/13 1:04 PM)




Status:


Open
Closed





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16946) Ratio percentgraph is wrong, bad alignment, length random

2013-02-25 Thread ognjen.bub...@gmail.com (JIRA)















































Ognjen Bubalo
 commented on  JENKINS-16946


Ratio percentgraph is wrong, bad alignment, length random















Hi,

This is not a bug.

Check this thread: https://groups.google.com/d/topic/jenkins-jacoco-plugin-mailing-list/016MPoIIr2c/discussion

Cheers,
Ogi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16946) Ratio percentgraph is wrong, bad alignment, length random

2013-02-25 Thread kettle-...@syntron.com (JIRA)

Marcel L
created JENKINS-16946

Ratio percentgraph is wrong, bad alignment, length random

Issue Type:

Bug

Affects Versions:

current

Assignee:

Ognjen Bubalo

Attachments:

Auswahl_001.png

Components:

jacoco

Created:

25/Feb/13 12:54 PM

Description:

The percentage bars seem to be totally off.

The ratio red/green doesn't match with the percentage
Alignment is broken
The length of the bars seem random to me

Suggestion. Move the percentage text up to the M: C: lines. This might fix the alignment issue.

The length (length red + length green) of the Red/green bar should be equal in length for all bars. The red/green ratio should reflect the percentage of the coverage.

Have a look at the attached screenshot (taken from Firefox 19 , Chrome shows very similar results)

Environment:

jenkins 1.502 and jacoco plugin 1.0.12

Project:

Jenkins

Priority:

Major

Reporter:

Marcel L

[JIRA] (JENKINS-16929) GNU make + GCC parser can't handle UTF-8















































Ulli Hafner
 commented on  JENKINS-16929


GNU make + GCC parser can't handle UTF-8















Hmm, I'm reading the actual file that is used to render the console log. This file seems to have no UTF-8 encoding header. Maybe that output depends on your build tool and can handle different encodings. 

So I would prefer not to change the current behavior: you just need to set the encoding entry in the job configuration of the warnings plugin (the second last entry in the advanced section).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16929) GNU make + GCC parser can't handle UTF-8

2013-02-25 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 commented on  JENKINS-16929


GNU make + GCC parser can't handle UTF-8















All Jenkins content is served with charset=UTF-8 in the Content-Type, so I guess that's a yes.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16282) JClouds fails to reconnect to slaves after Jenkins restart

2013-02-25 Thread antonio.pu...@altobridge.com (JIRA)















































Antonio Puche
 updated  JENKINS-16282


JClouds fails to reconnect to slaves after Jenkins restart
















Change By:


Antonio Puche
(25/Feb/13 12:41 PM)




Assignee:


Antonio Puche
abayer



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16282) JClouds fails to reconnect to slaves after Jenkins restart

2013-02-25 Thread antonio.pu...@altobridge.com (JIRA)
















































Antonio Puche
 assigned  JENKINS-16282 to Antonio Puche



JClouds fails to reconnect to slaves after Jenkins restart
















Change By:


Antonio Puche
(25/Feb/13 12:40 PM)




Assignee:


abayer
Antonio Puche



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16929) GNU make + GCC parser can't handle UTF-8















































Ulli Hafner
 commented on  JENKINS-16929


GNU make + GCC parser can't handle UTF-8















The option is in the advanced section of the warnings publisher.

Is the console always shown in UTF-8? Then I will always set the encoding to UTF-8 for the console (and ignore the setting in the configuration).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16945) I can't check hardware ID or Image ID from template creation

2013-02-25 Thread antonio.pu...@altobridge.com (JIRA)

Antonio Puche
created JENKINS-16945

I can't check hardware ID or Image ID from template creation

Issue Type:

Bug

Affects Versions:

current

Assignee:

abayer

Components:

jclouds

Created:

25/Feb/13 12:32 PM

Description:

I am configuring JClouds plugin into my Jenkins Server.
I'm trying to use the images I have in the OpenStack cloud from Jenkins.
To do that I configured the plugin as follows:

Profile: JCloud-OpenStack
Provider Name: Nova
End Point UR: http://172.16.4.11:5000/v2.0
Max. No. of Instances: 60
Retention Time: 30
Identity: my_username
Credential: my_password
RSA Private Key : my_rsa_private_key
Public Key: my_rsa_public_key

Once is configured I test the connection and it says:
Connection succeeded!

The problem comes up when I try to add an instance template.
I click on "Specify Hardware ID" and in the menu there is only one option: "None specified". There is no other option to select. It's just empty.
Comment: In this menu is where I'm expecting to see a list of of "flavors" as I will see if i execute "nova flavor-list" from the command line.

When I click on "Specify Image ID" then I specify the name of the image I have already defined in the cloud but when i click on "Check Image Id" it says "Invalid Image Id, please check the value and try again."
Comment: Here I took a name of an image from one of the names I retrieve when I execute from the command line the command "nova image-list".

Environment:

Ubuntu 12.04

Project:

Jenkins

Labels:

configuration
plugin
jenkins

Priority:

Major

Reporter:

Antonio Puche

[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy

2013-02-25 Thread tomas.westl...@sonymobile.com (JIRA)















































Tomas Westling
 commented on  JENKINS-16868


Icons are not displayed with a reverse proxy















Ok, I hoped the slashes would have something to do with it but it seems to be 2 different problems then.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16314) cvs plugin removes sticky branch tag

2013-02-25 Thread aandru...@andrulis.com.br (JIRA)















































Adriano Andrulis
 commented on  JENKINS-16314


cvs plugin removes sticky branch tag















Hi Michael, following is the xml for the job mentioned by James. Thanks for looking at.



"maven-plugin@1.499">
  
  server branch build
  false
  
"jenkinswalldisplay@0.6.15"/>
  
  "hudson.scm.CVSSCM" plugin="cvs@2.8">
true
"hudson.scm.browsers.ViewCVS">
  https://viewvc/cgi-bin/viewvc.cgi/server/?root=root


  
:pserver:builder@pserver:/cvsroot-root

  

  

Component/services/server
  

"hudson.scm.CvsRepositoryLocation$BranchRepositoryLocation">
  BRANCH
  RC_repServer2_6
  false

  

-1

  

  

B5SEyM3MM3X7KWpcw=
true
  

false
false
true
true
false
true
  
  dev02
  false
  false
  false
  false
  sun_jdk_7
  "vector">

  # every 10 mins
*/10 * * * *
  false

  
  false
  
com.components.server
server
  
  -U -DskipITs=false clean install -e
  -Xmx512M -Dm3plugin.lib=/space/jenkins_slave/main/workspace/artifactory-plugin/2.1.3
  true
  false
  true
  false
  false
  false
  false
  -1
  false
  false
  "jenkins.mvn.DefaultSettingsProvider"/>
  "jenkins.mvn.DefaultGlobalSettingsProvider"/>
  

  d...@mail.com
  false
  true
  true

  
  
  
"m2release@0.9.1">
  
  
  IS_M2RELEASEBUILD
  -Dresume=false release:prepare release:perform -Dmaven.scm.provider.cvs.implementation=cvs_native -X
  -X -Dresume=false -DdryRun=true release:prepare -Dmaven.scm.provider.cvs.implementation=cvs_native -e
  false
  false
  false

"artifactory@2.1.3">
  
http://artifactory/artifactory
http://artifactory/artifactory
repository
  

  
  

  

  
  
  
SUCCESS
0
BLUE
  





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-16929) GNU make + GCC parser can't handle UTF-8

2013-02-25 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 commented on  JENKINS-16929


GNU make + GCC parser can't handle UTF-8















Parsing from console log.
In "Console output" (and the raw view) they display correctly as ‘ and ’.
The project configuration has no encoding options that I can see.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-14185) Provide global configuration of settings















































Ulli Hafner
 updated  JENKINS-14185


Provide global configuration of settings
















Change By:


Ulli Hafner
(25/Feb/13 10:52 AM)




Summary:


Provide global configuration
 for trend graphs
 of settings





Description:


My actual requirements are pretty simple:   * All jobs on Continuous Integration can be easily configured to use the same trending settings   * All jobs on Public Dashboard can be easily configured to use the same trending settings (we use the build-publisher plugin to push some of our jobs from CI to the dashboard)   * Make this possible for PMD and my own custom (AppScan) subclass of the hudson.plugins.analysis.core.PluginDescriptor (these are the only two analysis-core plugins we use at this time)   * Possible (lower priority) requirement - in some cases we may want to have custom settings for some jobsYour suggestion to have a global configuration would be perfect for what I really need at this time. If the "*.txt" file doesn't exist, it could fall back on the global configuration. Because I have created my own PluginDescriptor, it would be nice if the global configuration could apply across all extensions, or else make it very easy for me to hook into that global config.
This feature makes not only sense for graphs but also for all other aspects of the plug-ins.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] (JENKINS-12330) Occasionally,collecting findbugs analysis files will take very long time, event two more hours.