[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)

2014-02-25 Thread flavio.do...@gmail.com (JIRA)














































Flavio Donzé
 commented on  JENKINS-20196


Failed to connect to URL (status = 404)















"Multiple SCMs plugin" version 0.3

I do have some old credentials in the "manage jenkins" area, but I'm not using them in 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] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)

2014-02-24 Thread flavio.do...@gmail.com (JIRA)














































Flavio Donzé
 commented on  JENKINS-20196


Failed to connect to URL (status = 404)















I just updated to "GIT plugin" 2.0.3 and "GIT client plugin" 1.6.3.

Getting the following output:
Cloning repository https://username:passw...@bitbucket.org/scodi/tools.git
Fetching upstream changes from https://usern...@bitbucket.org/scodi/tools.git
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "git fetch --tags --progress https://usern...@bitbucket.org/scodi/tools.git +refs/heads/:refs/remotes/origin/" returned status code 128:
stdout: 
stderr: fatal: Authentication failed for 'https://usern...@bitbucket.org/scodi/tools.git/'

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1173)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1043)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:74)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:207)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:358)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:847)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880)
	at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560)
	at hudson.model.Run.execute(Run.java:1670)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
ERROR: null



























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-15857) Parse Exception with Java7 and Emma 2.2.0

2013-01-04 Thread flavio.do...@gmail.com (JIRA)














































Flavio Donzé
 updated  JENKINS-15857


Parse Exception with Java7 and Emma 2.2.0
















Change By:


Flavio Donzé
(04/Jan/13 12:10 PM)




Component/s:


emmacoveragecolumn





Component/s:


emma



























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-15857) Parse Exception with Java7 and Emma 2.2.0

2012-11-19 Thread flavio.do...@gmail.com (JIRA)














































Flavio Donzé
 commented on  JENKINS-15857


Parse Exception with Java7 and Emma 2.2.0















Link to forum post:
http://www.eclipse.org/forums/index.php?t=rview&goto=986116

Link to issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=368042




























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-15857) Parse Exception with Java7 and Emma 2.2.0

2012-11-19 Thread flavio.do...@gmail.com (JIRA)














































Flavio Donzé
 created  JENKINS-15857


Parse Exception with Java7 and Emma 2.2.0















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Attachments:


coverage_report.zip



Components:


emma



Created:


19/Nov/12 8:42 AM



Description:


We are using Jenkins and Buckminster to build our product, about half a year ago we updated to java7 since then emma did not work anymore. Because the buckminster emma extension was outdated, used emma (1.4.x).
After I reported in the forum, buckminster updated emma to version 2.2.0.
I now get the following exception even though the xml looks fine (to me).
Maybe this is caused by the update to java7 or emma 2.2.0.
Attached is the coverage report.


Emma: looking for coverage reports in the provided path: output/coverage_report.xml
Emma: found 1 report files: 
  C:\Data\Jenkins\workspace\workspace\scodi.server.integration\output\coverage_report.xml
Emma: stored 1 report files in the build folder: C:\Data\Jenkins\workspace\jobs\scodi.server.integration\builds\2012-11-19_09-05-45\emma
ERROR: Publisher hudson.plugins.emma.EmmaPublisher aborted due to exception
hudson.util.IOException2: Failed to parse C:\Data\Jenkins\workspace\workspace\scodi.server.integration\output\coverage_report.xml
	at hudson.plugins.emma.EmmaBuildAction.load(EmmaBuildAction.java:243)
	at hudson.plugins.emma.EmmaPublisher.perform(EmmaPublisher.java:150)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
	at hudson.model.Run.execute(Run.java:1541)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Caused by: org.xmlpull.v1.XmlPullParserException: expected START_TAG or END_TAG not END_DOCUMENT (position: END_DOCUMENT seen .. @1:5408806) 
	at org.xmlpull.mxp1.MXParser.nextTag(MXParser.java:1083)
	at hudson.plugins.emma.EmmaBuildAction.loadRatios(EmmaBuildAction.java:269)
	at hudson.plugins.emma.EmmaBuildAction.load(EmmaBuildAction.java:241)
	... 10 more




Environment:


Java7,buckminster4.2,Jenkins1.491




Project:


Jenkins



Priority:


Major



Reporter:


Flavio Donzé

























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