[JIRA] (JENKINS-37046) Wrong Ivy XML file is being looked for

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37046  
 
 
  Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Released As: 
 1.27  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-37046) Wrong Ivy XML file is being looked for

2017-01-12 Thread kevin.form...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Formsma resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Should be fixed in ivy-plugin 1.27.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37046  
 
 
  Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
Change By: 
 Kevin Formsma  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-37046) Wrong Ivy XML file is being looked for

2017-01-11 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
 Code changed in jenkins User: imod Path: build.gradle http://jenkins-ci.org/commit/ivy-plugin/f5edb34584fe04e760975f3962d6efcabfb4fc50 Log: [FIXED JENKINS-37046] [FIXED JENKINS-35139] [FIXED JENKINS-34192] update to released config-file-provider  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-37046) Wrong Ivy XML file is being looked for

2016-12-27 Thread d...@fortysix.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Bartholdi commented on  JENKINS-37046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
 Kevin Formsma version 2.15 of config-file-provider is now released, feel free to do a release of your plugin to keep compatibility. The PR is uptodate: https://github.com/jenkinsci/ivy-plugin/pull/23  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-37046) Wrong Ivy XML file is being looked for

2016-11-14 Thread d...@fortysix.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Bartholdi edited a comment on  JENKINS-37046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
 [~arothian] many thanks for your help!!! I just released a first beta version of the config-file-provider-plugin and created a PR for the ivy-plugin: https://github.com/jenkinsci/ivy-plugin/pull/23This PR depends on the 2.14-beta version of the config-file-provider-plugin. Please test it with this one and hold the proper release until I released the config-file-provider-plugin with a stable version. If you like, you could do a beta release of the ivy-plugin too: https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-37046) Wrong Ivy XML file is being looked for

2016-11-14 Thread d...@fortysix.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Bartholdi commented on  JENKINS-37046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
 Kevin Formsma many thanks for your help!!! I just released a first beta version of the config-file-provider-plugin and created a PR for the ivy-plugin: https://github.com/jenkinsci/ivy-plugin/pull/23 This PR depends on the 2.14-beta version of the config-file-provider-plugin. Please test it with this one and hold the proper release until I released the config-file-provider-plugin with a stable version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-37046) Wrong Ivy XML file is being looked for

2016-10-16 Thread kevin.form...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Formsma commented on  JENKINS-37046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
 Dominik Bartholdi Thanks for the message. I'm not actively using the Ivy plugin myself anymore; that said, I'm happy to help merge in any PRs on the repo and push out new versions. If you have the fixes, I don't have any qualms about updating the plugin to require a newer jenkins core.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-37046) Wrong Ivy XML file is being looked for

2016-10-12 Thread d...@fortysix.ch (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Bartholdi commented on  JENKINS-37046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
 Kevin Formsma I'm the maintainer of the config-file-provider plugin and I just did a major update of the same plugin. It will now support folders and configuration files on folder scope. While working on it I came across the integration of the config-file-provider into the ivy plugin. For what I can see, the implementation is very faulty and not compatible with the other xml configuration files provided by it. (also see JENKINS-35139, JENKINS-37046).  Because of the current implementation I'm not able to properly migrate the existing configurations to the new format.  I did all required changes on the ivy plugin to fix the above issues, but this will require the ivy plugin to upgrade to a more resent jenkins core (1.642.3) - WDYT?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-37046) Wrong Ivy XML file is being looked for

2016-07-28 Thread phillip.l.vi...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Phillip Viana created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37046  
 
 
  Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Timothy Bingaman  
 
 
Components: 
 ivy-plugin  
 
 
Created: 
 2016/Jul/28 9:17 PM  
 
 
Labels: 
 ivy  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Phillip Viana  
 

  
 
 
 
 

 
 I have the latest Ivy plug-ins installed in a Jenkins 2 instance. The structure of my project is: build/ com.mycompany.myproj.bootstrap.central/ com.mycompany.myproj.bootstrap.site/ com.mycompany.myproj.central.app/ com.mycompany.myproj.cinstall.central/ com.mycompany.myproj.cinstall.site/ com.mycompany.myproj.site.app/ README.md All these projects (beginning with com.mycompany) have an ivy.xml file in them, whilst the build/ directory has ivysettings.xml. My job is configured with build/ivysettings.xml as the "Ivy settings" config and **/ivy.xml as the "Ivy xml files" config, I am facing the error below when I run an Ivy build: Error while reading the default Ivy 2.1 settings: failed to load settings from file:/var/lib/jenkins/jobs/Build/jobs/IvyTest/workspace/ivy382275822984563930xml: either url or file should be given for classpath element