[JIRA] (JENKINS-16076) No email is sent to anyone if there is an invalid email address contained within the email list
rejesi commented on JENKINS-16076 No email is sent to anyone if there is an invalid email address contained within the email list The email being sent actually has the invalid email address included as well as the valid email addresses in the "To:" field. Since it did send email to the invalid user, the verbiage "Error sending to the following INVALID addresses:" is not true to the actual processing The misleading info I am referring to is the line "Error sending to the following VALID addresses:" even though it is blank, it probably shouldn't be displayed unless there were valid emails that had a problem being sent. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16076) No email is sent to anyone if there is an invalid email address contained within the email list
Slide-O-Mix commented on JENKINS-16076 No email is sent to anyone if there is an invalid email address contained within the email list I'm not surprised...I was making some other modifications as well. I'll fix that up and should be doing a release within the next couple of days. Once I fix the HTML issue, I'll post another version here so you aren't completely blocked. When you say it sends to invalid email addresses as well, do you mean you see an email actually being sent to the invalid address, or you believe the log info is misleading? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
Vlad Aginsky updated JENKINS-16081 xUnit plugin fails to recognize regression if total number of tests doesn't go up. Change By: Vlad Aginsky (09/Dec/12 5:11 AM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16076) No email is sent to anyone if there is an invalid email address contained within the email list
rejesi commented on JENKINS-16076 No email is sent to anyone if there is an invalid email address contained within the email list Hi Slide-O-Mix, thanks so much for the quick turn around. The new snapshot plugin no longer throws an exception - it sends email to the invalid email address and valid addresses alike. The messages in the log sown below are not totally accurate: Email was triggered for: Success Sending email for trigger: Success Sending email to: sw@xxx.xx.com unkn...@xxx.xx.com Error sending to the following INVALID addresses: unkn...@qti.qualcomm.com Successfully sent to the following addresses: sw@xxx.xx.com Error sending to the following VALID addresses: Finished: SUCCESS It appears however that a side effect of this change causes the "html" jelly templated emails to get sent showing marked up HTML in the email instead of the way it should be. It was working properly prior to the installation of the snapshot of the modified email-ext plugin.
BODY, TABLE, TD, TH, P { font-family:Verdana,Helvetica,sans serif; font-size:11px; color:black; }
h1 { color:black; }
h2 { color:black; }
h3 { color:black; }
TD.bg1 { color:white; background-color:#C0; font-size:120% }
TD.bg2 { color:white; background-color:#4040FF; font-size:110% }
TD.bg3 { color:white; background-color:#8080FF; } TD.test_passed { color:blue; } TD.test_failed { color:red; } TD.console { font-family:Courier New; } This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
Vlad Aginsky updated JENKINS-16081 xUnit plugin fails to recognize regression if total number of tests doesn't go up. here is simplest set of files to reproduce the problem. Run 38 has all pass. run 40 has one test failed, was reported as "unstable" run 41 has another test failed, was reported as "unstable" by jenkins, while i was expecting to see "broken". Change By: Vlad Aginsky (09/Dec/12 5:09 AM) Attachment: jenkins-play_with_tests-38.xml Attachment: jenkins-play_with_tests-40.xml Attachment: jenkins-play_with_tests-41.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
Vlad Aginsky started work on JENKINS-16081 xUnit plugin fails to recognize regression if total number of tests doesn't go up. Change By: Vlad Aginsky (09/Dec/12 5:09 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
Vlad Aginsky commented on JENKINS-16081 xUnit plugin fails to recognize regression if total number of tests doesn't go up. Example: If there are 5 tests that failed, and on next run another set of 5 tests fails, it will not be able to detect a regression case here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
Vlad Aginsky created JENKINS-16081 xUnit plugin fails to recognize regression if total number of tests doesn't go up. Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 09/Dec/12 4:52 AM Project: Jenkins Priority: Major Reporter: Vlad Aginsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14857) Android Lint Plugin does nothing
David Müller reopened JENKINS-14857 Android Lint Plugin does nothing Please provide a fix for this, this plugin is too useful to keep away from maven users. A suitable maven phase would be the "verify" (See Maven Livecyles). If a goal is really needed, I would suggest "android:emma" Available goals from the android maven plugin are listed here: http://maven-android-plugin-m2site.googlecode.com/svn/plugin-info.html I would be glad to test new plugin versions. Change By: David Müller (09/Dec/12 1:47 AM) Resolution: Won't Fix 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
[JIRA] (JENKINS-3369) Force Promotion button missing
jpollak commented on JENKINS-3369 Force Promotion button missing Where IS the button? I have a few builds which have a Promotions Status page, but I'm clearly missing the button. Where is it supposed to be? I can't find any resources official or not that show where to find it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15380) No history for test cases where name of suite is part of test case name
Samuel Moritz assigned JENKINS-15380 to Unassigned No history for test cases where name of suite is part of test case name Change By: Samuel Moritz (08/Dec/12 11:16 PM) Assignee: Samuel Moritz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15380) No history for test cases where name of suite is part of test case name
Samuel Moritz assigned JENKINS-15380 to Samuel Moritz No history for test cases where name of suite is part of test case name Change By: Samuel Moritz (08/Dec/12 9:56 PM) Assignee: Samuel Moritz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6956) NPE if Buildsnumbers are not configured wrong
Thomas Fürer resolved JENKINS-6956 as Fixed NPE if Buildsnumbers are not configured wrong Change By: Thomas Fürer (08/Dec/12 6:23 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16042) NullPointer when collecting successful results
Scott Armit commented on JENKINS-16042 NullPointer when collecting successful results I also see this with 1.7 version. I have only 1 build step with two jobs. Both jobs complete successfully, but the main job (the multijob, job) fails due to the below exception: FATAL: null java.lang.NullPointerException at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.evaluateResult(MultiJobBuild.java:69) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.isFailure(MultiJobBuild.java:59) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:51) at hudson.model.Run.execute(Run.java:1516) at hudson.model.Run.run(Run.java:1462) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Thanks for any fix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15681) Support for Cloudbees Folders
SCM/JIRA link daemon commented on JENKINS-15681 Support for Cloudbees Folders Code changed in jenkins User: tofuatgit Path: .gitignore pom.xml src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java src/test/java/org/jvnet/hudson/plugins/thinbackup/TestHelper.java src/test/java/org/jvnet/hudson/plugins/thinbackup/backup/TestBackupWithCloudBeesFolder.java src/test/java/org/jvnet/hudson/plugins/thinbackup/backup/TestHudsonBackup.java http://jenkins-ci.org/commit/thin-backup-plugin/85a3c94074a24d7f513bd445c14b34c39be04eae Log: JENKINS-15681: Support for Cloudbees Folders This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15681) Support for Cloudbees Folders
Thomas Fürer resolved JENKINS-15681 as Fixed Support for Cloudbees Folders Change By: Thomas Fürer (08/Dec/12 5:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15681) Support for Cloudbees Folders
Thomas Fürer commented on JENKINS-15681 Support for Cloudbees Folders add cloudbees folder support This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16080) send existing html under workspace directly without template
Slide-O-Mix closed JENKINS-16080 as Not A Defect send existing html under workspace directly without template Change By: Slide-O-Mix (08/Dec/12 3:31 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16080) send existing html under workspace directly without template
Slide-O-Mix resolved JENKINS-16080 as Not A Defect send existing html under workspace directly without template The FILE token can be used to achieve this purpose. Change By: Slide-O-Mix (08/Dec/12 3:31 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16080) send existing html under workspace directly without template
Larry Cai commented on JENKINS-16080 send existing html under workspace directly without template Yes, it works excellent. Thank for the quick response, well done. The problem is solved excellent, please help me to close it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16076) No email is sent to anyone if there is an invalid email address contained within the email list
Slide-O-Mix started work on JENKINS-16076 No email is sent to anyone if there is an invalid email address contained within the email list Change By: Slide-O-Mix (08/Dec/12 2:58 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16080) send existing html under workspace directly without template
Slide-O-Mix
commented on JENKINS-16080
send existing html under workspace directly without template
${FILE, path='path/to/file'} should do the trick. The path to the file is relative to the workspace root.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16080) send existing html under workspace directly without template
Larry Cai edited a comment on JENKINS-16080 send existing html under workspace directly without template Seems like this, and I found it the help for "Content Token Reference" in this plugin I will try it and give updates. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16080) send existing html under workspace directly without template
Larry Cai commented on JENKINS-16080 send existing html under workspace directly without template Seems like this, can you point me the link how to use FILE token in "Default Content" ? I can't find it, I always use template. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12068) Cannot configure projects anymore
evernat resolved JENKINS-12068 as Duplicate Cannot configure projects anymore duplicates JENKINS-12075 Change By: evernat (08/Dec/12 2:24 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
[JIRA] (JENKINS-12054) How to run a command line batch windows ?
evernat commented on JENKINS-12054 How to run a command line batch windows ? You should have a "Save" button at the bottom. Is this issue still a problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16080) send existing html under workspace directly without template
Slide-O-Mix commented on JENKINS-16080 send existing html under workspace directly without template Couldn't you just use the FILE token for 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
[JIRA] (JENKINS-16080) send existing html under workspace directly without template
Larry Cai
created JENKINS-16080
send existing html under workspace directly without template
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
08/Dec/12 1:54 PM
Description:
currently email-ext is used to fill information into template, it is good, but it not only demands on groovy or jelly kinds of script knowledge, but also depends on the API exposed to the plugin.
More flexible way could be to use script to generate the html files directly in building steps.
email.py > sample.template
Currently I will copy it to the template directory and send it as groovy template though it is pure html.
cp sample.template $EMAIL_EXT_PLUGINS/template
${SCRIPT, template="sample.template"}
Will be nice if the email-ext can support to send html file directly, and also the sending html can't be saved easily as well
Environment:
Project:
Jenkins
Priority:
Minor
Reporter:
Larry Cai
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15802) CopyArticat plugin cannot resolve NodeLabel parameter
SCM/JIRA link daemon resolved JENKINS-15802 as Fixed CopyArticat plugin cannot resolve NodeLabel parameter Change By: SCM/JIRA link daemon (08/Dec/12 1:11 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15802) CopyArticat plugin cannot resolve NodeLabel parameter
SCM/JIRA link daemon commented on JENKINS-15802 CopyArticat plugin cannot resolve NodeLabel parameter Code changed in jenkins User: imod Path: src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/LabelParameterValue.java http://jenkins-ci.org/commit/nodelabelparameter-plugin/e8918d5bc0d025a224db89d511cc31790fff13fb Log: [FIXED JENKINS-15802] expose node/label parameter to env This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12218) Performance problems with JUnit reports
Gregory Boissinot updated JENKINS-12218 Performance problems with JUnit reports Change By: Gregory Boissinot (08/Dec/12 12:31 PM) Component/s: dtkit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Niklaus Giger commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space I have this issue frequently on my CI http://ngiger.dyndns.org/jenkins/. I changed my projects to poll only at 3 minutes after the hour. I see the problem mostly when one of my slaves (1 Windows, 1 MacOSx, 1 Debian/Lenny) does some work. If I clean a workspace on one of these slaves. I get very often the PermGen error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Niklaus Giger commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Hi everyone. I need this bug/feature so much that I'm willing to pay 100.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/92/64-bit-javalangoutofmemoryerror-permgen-space). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16079) If EC2 plugin fails to start a stopped slave because it's been manually started, it treats it as dead
Craig Ringer created JENKINS-16079 If EC2 plugin fails to start a stopped slave because it's been manually started, it treats it as dead Issue Type: Bug Affects Versions: current Assignee: Francis Upton Components: ec2 Created: 08/Dec/12 12:04 PM Description: When using the EC2 plugin with EBS-based hosts and an idle timeout after which the instances are stopped, the EC2 plugin treats a manually started host as if it were dead if Jenkins expected it to be stopped. As far as I can tell, if the EC2 plugin's EC2 API call to start the stopped host fails (say, because the host has already been started so an admin can investigate the working tree of a failed build in-situ) it assumes the host is dead. It should instead query the host's state to determine if it's running and if it is, proceed with starting the agent as if it'd successfully started it its self. I'm not asking anybody to make this change for me; this report is here to explain the issue to others who encounter it and as a note to remind me of what I need to do if I get time to address this issue. Environment: Host is Debian 6 with OpenJDK 6 but issue appears host-independent Project: Jenkins Priority: Minor Reporter: Craig Ringer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16078) JNLP slave hangs on start in ~1 of 10 build starts
Serge Tsygankov created JENKINS-16078 JNLP slave hangs on start in ~1 of 10 build starts Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: slave-hang-systemInfo.txt Components: slave-status Created: 08/Dec/12 11:44 AM Description: Slave is started in Nimbula cloud - our own plugin is used to start virtual machine. Plugin is not published yet. But I really don't think trouble is in it. Steps are: 1. Job is started 2. Our plugin is used to start VM to run job 3. VM starts 4. It connects on start to Jnlp url 5. Build process starts And.. sometimes ~1 of 10 starts (rather rare) build process hangs. Console is in such state: Started by timer Building remotely on Nimbula-slave-1110 in workspace /jenkins-slave/workspace/PRODUCTION - Sanity [Throbber non stop here] Node system info is in attachment. I would be very much obliged if you can help to understand possible reasons! Environment: Jenkins 1.492 on Ubunta Jnlp slave on win7 x86 Project: Jenkins Priority: Major Reporter: Serge Tsygankov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16077) ${WORKSPACE} environment var is relative on slaves if jenkins root path isn't explicitly set
Craig Ringer
created JENKINS-16077
${WORKSPACE} environment var is relative on slaves if jenkins root path isn't explicitly set
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
08/Dec/12 10:03 AM
Description:
If a job's UNIX shell script references the environment variable ${WORKSPACE}, it's always an absolute path when the job runs on the master, but it's a relative path when the job runs on a slave - and it's the wrong relative path, because it's relative to the jenkins root, not to the CWD the job script is run in.
I've traced this to the fact that my slaves don't have an explicit jenkins root path set. They do their work in the $HOME of the user Jenkins ssh's in as.
Jenkins should be prepending its cwd to the working path if no explicit root path was configured.
On one of my workers for example, ${WORKSPACE} resolves to:
workspace/pg_master_multiplatform/label_arch/x64/label_os/amazonlinux201209
where it should be :
/home/ec2-user/workspace/pg_master_multiplatform/label_arch/x64/label_os/amazonlinux201209
Environment:
Jenkins is on Java SE 6 on Debian 6 x64. The issue appears on any UNIX slave, but not on the master.
Project:
Jenkins
Priority:
Minor
Reporter:
Craig Ringer
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Willem Verstraeten commented on JENKINS-15829 hg share always recreating working copy on slave (on master it's working fine) I think this is because the mercurial caches on the slave don't have a default path to push and pull from. Igor: could you, on your slave, create a .hg/hgrc file in the /app/agora/hudsonslave/hgcache/D38534FF4534AE3232A1AB292D5BA54825AE752B-AgoraLight that contains the following information: [paths] default=__URL_OF_YOUR_MASTER_REPO__ Does the working copy get recreated every time then, after you remove your workaround? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16075) Lint icon not shown when selecting a particular build
Joris van der Pol commented on JENKINS-16075 Lint icon not shown when selecting a particular build Link for the 48x48 icon: http://xps:8080/static/944d390a/static/944d390a/plugin/android-lint/icons/android-48x48.png Link for the 24x24 icon: http://xps:8080/static/944d390a/plugin/android-lint/icons/android-24x24.png Jenkins version 1.492 Android Lint Plugin version: 2.0.1 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
