[JIRA] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

2016-03-03 Thread anandparaj...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 AN2D commented on  JENKINS-28652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary  
 
 
 
 
 
 
 
 
 
 
Confirmed that Jacoco plugin version: 2.0.1 worked with the 0.7.6 version of jacocoagent.jar & jacocoant.jar. Thanks centic 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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/d/optout.


[JIRA] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary

2016-02-23 Thread anandparaj...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 AN2D commented on  JENKINS-28652 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary  
 
 
 
 
 
 
 
 
 
 
Current Jenkins version: 1.648 Jacoco plugin version: 2.0.1 OS - Windows 7 
Jacoco plugin shows 0% for all projects. Logs below. 
This was working fine in our previous Jenkins instance in Linux which was using Jacoco plugin 1.0.19. 

 

[JaCoCo plugin] Collecting JaCoCo coverage data...
[JaCoCo plugin] Project\build\instrumented\jacoco.exec;Project\build\instrumented\classes;Project\au\com; locations are configured
[JaCoCo plugin] Number of found exec files for pattern Project\build\instrumented\jacoco.exec: 1
[JaCoCo plugin] Saving matched execfiles:  C:\Program Files (x86)\Jenkins\workspace\Project\Project\build\instrumented\jacoco.exec
[JaCoCo plugin] Saving matched class directories for class-pattern: Project\build\instrumented\classes:  C:\Program Files (x86)\Jenkins\workspace\Project\Project\build\instrumented\classes
[JaCoCo plugin] Saving matched source directories for source-pattern: Project\au\com:  C:\Program Files (x86)\Jenkins\workspace\Project\Project\au\com
[JaCoCo plugin] Loading inclusions files..
[JaCoCo plugin] inclusions: []
[JaCoCo plugin] exclusions: []
[JaCoCo plugin] Thresholds: JacocoHealthReportThresholds [minClass=0, maxClass=0, minMethod=0, maxMethod=0, minLine=0, maxLine=0, minBranch=0, maxBranch=0, minInstruction=0, maxInstruction=0, minComplexity=0, maxComplexity=0]
[JaCoCo plugin] Publishing the results..
[JaCoCo plugin] Loading packages..
[JaCoCo plugin] Done.
[JaCoCo plugin] Overall coverage: class: 0, method: 0, line: 0, branch: 0, instruction: 0
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 

[JIRA] [core] (JENKINS-33118) Upgrade to 2.0-alpha-1 fails

2016-02-23 Thread anandparaj...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 AN2D created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33118 
 
 
 
  Upgrade to 2.0-alpha-1 fails  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 24/Feb/16 3:49 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 AN2D 
 
 
 
 
 
 
 
 
 
 
OS - Windows 7 Current version : 1.648 Jenkins suggested an upgrade was available (2.0.1) Attempt to upgrade fails due to exception below http://updates.jenkins-ci.org/download/war/2.0-alpha-1 return 404 

 

hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/war/2.0-alpha-1/jenkins.war (redirected to: http://mirrors.jenkins-ci.org/war/2.0-alpha-1/jenkins.war)
	at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:821)
	at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1183)
	at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1161)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/war/2.0-alpha-1/jenkins.war
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
	at java.lang.reflect.Constructor.newInstance(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown 

[JIRA] [schedule-build-plugin] (JENKINS-30623) Job does not start based on Scheduler / Cron configuration

2015-09-23 Thread anandparaj...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 AN2D created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30623 
 
 
 
  Job does not start based on Scheduler / Cron configuration  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Andreas K 
 
 
 

Components:
 

 schedule-build-plugin, schedule-failed-builds-plugin 
 
 
 

Created:
 

 24/Sep/15 1:14 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.628  Windows XP - 2002  Service Pack 3 
 
 
 

Labels:
 

 jenkins schedule cron 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 AN2D 
 
 
 
 
 
 
 
 
 
 
How to reproduce 
 

Create a free style project
 

Source Code Management - None
 

Build Triggers - periodically - H/5 * * * * (The description below the input field indicates that it understands the cron syntax and matches by expectation)
   

[JIRA] [schedule-build-plugin] (JENKINS-30623) Job does not start based on Scheduler / Cron configuration

2015-09-23 Thread anandparaj...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 AN2D updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30623 
 
 
 
  Job does not start based on Scheduler / Cron configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 AN2D 
 
 
 
 
 
 
 
 
 
 *How to reproduce** Create a free style project* Source Code Management - None* Build Triggers - periodically - H/5 * * * *(The description below the input field indicates that it understands the cron syntax and matches by expectation)* Build - Execute Windows Batch command - dir* Save*Expectation* - Job kicks off every 5 minutes*Observed* - Job never kicks off.*Extra Info*The JOB only ever kicks off as expected (in next 5 min) only one time after Jenkins is restarted. Then onwards, it never kicks off. Going back to the configuration page, I see the following description under the cron configuration which indicates there is an issue. The time value it displays is not as expected._"Would last have run at Thursday, 24 September 2015 11:05:11 AM EST; would next run at Thursday, 24 September 2015 11:05:11 AM EST."_Changing the cron config to something like H/10 * * * * updates the description correctly to match expected behaviour - except it does not kick off the job.  Retuning back to the configuration page at a later time shows incorrect looking description. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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/d/optout.


[JIRA] [external-monitor-job] (JENKINS-24837) Viewing In Progress Status for external-monitor-job

2014-09-25 Thread anandparaj...@gmail.com (JIRA)














































AN2D
 commented on  JENKINS-24837


Viewing In Progress Status for external-monitor-job















Hi,

If someone could confirm whether the behaviour I am seeing is expected or something that could be fixed, it would be great.

Thanks



























This message is automatically generated by JIRA.
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/d/optout.


[JIRA] [external-monitor-job] (JENKINS-24837) Viewing In Progress Status for external-monitor-job

2014-09-23 Thread anandparaj...@gmail.com (JIRA)














































Anand Juli
 created  JENKINS-24837


Viewing In Progress Status for external-monitor-job















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


external-monitor-job



Created:


24/Sep/14 5:21 AM



Description:


Not sure if this is a bug but what I was looking for is to be able to know from Jenkins Dashboard that a job I am monitoring has 'started'. In other, I want to know that the job is 'In Progress'. 

On Jenkins dashboard, I can see that a new build gets registered straight away after the external job completes but there was no indication that the job was 'running'.

I am using Jenkins 1.581 (localhost) in a MAC and the process being monitored in a java process running locally as well. 




Project:


Jenkins



Priority:


Minor



Reporter:


Anand Juli

























This message is automatically generated by JIRA.
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/d/optout.