[JIRA] [s3-plugin] (JENKINS-26614) S3 plugin should use artifacts build in the job rather than content of the workspace

2015-01-26 Thread christop...@java.net (JIRA) 














































christopheM
 created  JENKINS-26614


S3 plugin should use artifacts build in the job rather than content of the workspace















Issue Type:


Improvement



Assignee:


Michael Watt



Components:


s3-plugin



Created:


26/Jan/15 5:55 PM



Description:


Promotion can occurs many hours/days after a successful build N. In the mean time, other build (N+1, N+2... N+m) can be triggered.
So when promoting build N, as the workspace is used, you will in fact promote the result of build N+m which is not the desired effect

(see for example the plugin https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+CIFS+Plugin which states: The base directory for this fileset is the artifacts directory of the build that is being promoted)





Project:


Jenkins



Priority:


Major



Reporter:


christopheM

























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] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)

2014-09-12 Thread christop...@java.net (JIRA) 














































christopheM
 commented on  JENKINS-24125


Git Polling fails for job restricted to Mac OS X slave (with Windows master)















I had exactly the same issue for months. Since Jan 2013 we were using a OSX restricted job with a windows master; the polling never worked and we had to launch the build manually. The workaround works fine for us too



























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] [mail] (JENKINS-15763) Publisher hudson.tasks.Mailer aborted due to exception

2014-02-13 Thread christop...@java.net (JIRA) 














































christopheM
 commented on  JENKINS-15763


Publisher hudson.tasks.Mailer aborted due to exception















@Alex Earl: 
for me it is ok also. I cannot say since when, certainly more than a couple of months.



























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] [subversion] (JENKINS-13913) after upgrading Subversion Plugin to 1.40 some (not all) project are building again and again

2013-06-14 Thread christop...@java.net (JIRA) 














































christopheM
 updated  JENKINS-13913


after upgrading Subversion Plugin to 1.40 some (not all) project are building again and again
















Change By:


christopheM
(14/Jun/13 7:55 AM)




Description:


I upgraded subversion plugin one or 2 weeks agoThe first time one of our project sources have been updated in SVN, this project is build again and again with the following code change info: {Started on 25 mai 2012 13:50:49 Workspace doesn't contain https://xxx.yyy.com:443/svn/applications/2011/Telefonica/SelfCareApp/trunk/sources. Need a new build Done. Took 0,2 s Changes found}This happens with both modes : - Emulate clean checkout by first deleting unversioned/ignored files - always check up a fresh copy(I even deleted manually the workspace, in both configuration to be sure to avoid any memorizing side-effect of the extracted source code)It also happens on another single project yesterday after its source has been updated.All other projects are currently working correctly (ie only rebuilding when the svn source change).A weird thing is that it is the same user who updated the code in both projects
-
This issue is similar to the
-
 JENKINS-13835
 (#1),
 -issue
 but in our case we have
-
 more than 12 living builds, only two seems impacted for the moment
.
-



























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-15763) Publisher hudson.tasks.Mailer aborted due to exception

2013-01-17 Thread christop...@java.net (JIRA) 














































christopheM
 commented on  JENKINS-15763


Publisher hudson.tasks.Mailer aborted due to exception















I guess its is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-15440



























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-15763) Publisher hudson.tasks.Mailer aborted due to exception

2013-01-17 Thread christop...@java.net (JIRA) 












































  
christopheM
 edited a comment on  JENKINS-15763


Publisher hudson.tasks.Mailer aborted due to exception
















exactly the same issue with :
Win7x64 Jenkins 1.499 after  an upgrade from 1.486


the stack trace is:
ERROR: Publisher hudson.tasks.Mailer aborted due to exception
java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #2185 DESC: lo=106,hi=97,size=125,size2=125
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:418)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:213)
	at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349)
	at hudson.model.Run.onLoad(Run.java:315)
	at hudson.model.RunMap.retrieve(RunMap.java:226)
	at hudson.model.RunMap.retrieve(RunMap.java:59)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:642)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:625)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:213)
	at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349)
	at hudson.model.Run.onLoad(Run.java:315)
	at hudson.model.RunMap.retrieve(RunMap.java:226)
	at hudson.model.RunMap.retrieve(RunMap.java:59)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:642)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:625)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.getById(AbstractLazyLoadRunMap.java:498)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:472)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:213)
	at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349)
	at hudson.model.Run.onLoad(Run.java:315)
	at hudson.model.RunMap.retrieve(RunMap.java:226)
	at hudson.model.RunMap.retrieve(RunMap.java:59)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:642)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:625)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:213)
	at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1523)
	at hudson.model.User.getProjects(User.java:444)
	at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21)
	at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101)
	at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532)
	at hudson.tasks.MailSender.buildCulpritList(MailSender.java:408)
	at hudson.tasks.MailSender.createEmptyMail(MailSender.java:368)
	at hudson.tasks.MailSender.createFailureMail(MailSender.java:227)
	at hudson.tasks.MailSender.getMail(MailSender.java:154)
	at hudson.tasks.MailSender.execute(MailSender.java:100)
	at hudson.tasks.Mailer.perform(Mailer.java:117)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732)
	at hudson.model.Run.execute(Run.java:1568)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)



























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-15763) Publisher hudson.tasks.Mailer aborted due to exception

2013-01-17 Thread christop...@java.net (JIRA) 














































christopheM
 commented on  JENKINS-15763


Publisher hudson.tasks.Mailer aborted due to exception















exactly the same issue with :
Win7x64 Jenkins 1.499 after  an upgrade from 1.486



























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

[JIRA] (JENKINS-13913) after upgrading Subversion Plugin to 1.40 some (not all) project are building again and again

2012-05-25 Thread christop...@java.net (JIRA) 
christopheM created JENKINS-13913:
-

 Summary: after upgrading Subversion Plugin to 1.40 some (not all) 
project are building again and again
 Key: JENKINS-13913
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13913
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
Affects Versions: current
 Environment: Jenkins ver. 1.465
Subversion Plug-in 1.40
windows 7
Reporter: christopheM


I upgraded subversion plugin one or 2 weeks ago

The first time one of our project sources have been updated in SVN, this 
project is build again and again with the following code change info:
 {Started on 25 mai 2012 13:50:49
 Workspace doesn't contain 
https://xxx.yyy.com:443/svn/applications/2011/Telefonica/SelfCareApp/trunk/sources.
 Need a new build
 Done. Took 0,2 s
 Changes found}

This happens with both modes :
 - Emulate clean checkout by first deleting unversioned/ignored files
 - always check up a fresh copy
(I even deleted manually the workspace, in both configuration to be sure to 
avoid any memorizing side-effect of the extracted source code)

It also happens on another single project yesterday after its source has been 
updated.
All other projects are currently working correctly (ie only rebuilding when the 
svn source change).

A weird thing is that it is the same user who updated the code in both projects

This issue is similar to the JENKINS-13835 (#1), but in our case we have more 
than 12 living builds, only two seems impacted for the moment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12918) a job dedicated to copyartifacts from a build specified by a build paramter (ie a run parameter) fails when launched manuallyco

2012-02-27 Thread christop...@java.net (JIRA) 
christopheM created JENKINS-12918:
-

 Summary: a job dedicated to copyartifacts from a build specified 
by a build paramter (ie a run  parameter)  fails when launched manuallyco
 Key: JENKINS-12918
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12918
 Project: Jenkins
  Issue Type: Bug
  Components: copyartifact
 Environment: Jenkins ver. 1.450
copy artifacts plugin v1.21
Reporter: christopheM
Assignee: Alan Harder
 Attachments: config.xml

The tested job is minimalist:

- it defines a Run parameter (named "IFW") to select a build from the job "IFW"
- it defines a "copy artifacts from another project" specified by a "build 
parameter", the parameter name beeing "IFW", and selectif the followinfg 
artifacts "**/*zip"

When manually launching the job, selecting the (succesful) last build of the 
IFW job, I got the following error:

FATAL:  : only whitespace content allowed before start tag and not h (position: 
START_DOCUMENT seen h... @1:1)
com.thoughtworks.xstream.io.StreamException:  : only whitespace content allowed 
before start tag and not h (position: START_DOCUMENT seen h... @1:1)
at 
com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:78)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:154)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:147)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:126)
at 
com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:111)
at com.thoughtworks.xstream.io.xml.XppReader.(XppReader.java:48)
at 
com.thoughtworks.xstream.io.xml.XppDriver.createReader(XppDriver.java:44)
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:856)
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:848)
at 
hudson.plugins.copyartifact.BuildSelectorParameter.getSelectorFromXml(BuildSelectorParameter.java:81)
at 
hudson.plugins.copyartifact.ParameterizedBuildSelector.getBuild(ParameterizedBuildSelector.java:52)
at 
hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:164)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at 
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:700)
at hudson.model.Build$RunnerImpl.build(Build.java:178)
at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1409)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Caused by: org.xmlpull.v1.XmlPullParserException: only whitespace content 
allowed before start tag and not h (position: START_DOCUMENT seen h... @1:1) 
at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1519)
at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
at 
com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:63)
... 20 more


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira