[JIRA] [maven-plugin] (JENKINS-15198) Support toolchains configuration file like other Maven configuration files (settings, global settings)
Title: Message Title Robert Kleinschmager commented on JENKINS-15198 Re: Support toolchains configuration file like other Maven configuration files (settings, global settings) although maven 3.3.1 improved usage of the toolchains concept see Release Notes and MNG-5754 one think is missing: configuring toolchains file via command line option. Can imagine, that this is also the cause, why jenkins / config-file-provider cannot set this 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] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Title: Message Title Robert Kleinschmager commented on JENKINS-20263 Re: Artifact Resolver does not retrieve the latest version from central Maven Repository pull request submitted https://github.com/jenkinsci/repository-connector-plugin/pull/11 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] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Title: Message Title Robert Kleinschmager assigned an issue to Robert Kleinschmager Jenkins / JENKINS-20263 Artifact Resolver does not retrieve the latest version from central Maven Repository Change By: Robert Kleinschmager Assignee: RobertKleinschmager 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] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Title: Message Title Robert Kleinschmager commented on JENKINS-20263 Re: Artifact Resolver does not retrieve the latest version from central Maven Repository the problem only occured, if you repository is marked as 'Managed repository'. (cause lies within the usage of mirror-repository of the aether api) 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] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Robert Kleinschmager edited a comment on JENKINS-20263 Artifact Resolver does not retrieve the latest version from central Maven Repository still there in version 1.1.1 maybe it's also related to the own local repo (store at /tmp/repositoryconnector-repo/ by default) 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] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Robert Kleinschmager commented on JENKINS-20263 Artifact Resolver does not retrieve the latest version from central Maven Repository still there in version 1.11 maybe it's also related to the own local repo (store at /tmp/repositoryconnector-repo/ by default) 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] [weblogic-deployer-plugin] (JENKINS-26901) Not possible to run freestyle job with non-set baseDirectory
Robert Kleinschmager created JENKINS-26901 Not possible to run freestyle job with non-set baseDirectory Issue Type: Bug Assignee: Robert Kleinschmager Components: weblogic-deployer-plugin Created: 11/Feb/15 3:24 PM Description: instead of using the workspace by default, the non-null (and not existing) directory will be mourned I will provide a patch via github Environment: release 2.12, freestyle project Project: Jenkins Priority: Minor Reporter: Robert Kleinschmager 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] [repository-connector] (JENKINS-24243) Add ability to disable using the global configured proxy
Robert Kleinschmager commented on JENKINS-24243 Add ability to disable using the global configured proxy ++ important issue also 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 -- 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] [maven-metadata-plugin] (JENKINS-18063) Authentication support for repository
Robert Kleinschmager commented on JENKINS-18063 Authentication support for repository you can use the credential store (https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin) 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] [m2release] (JENKINS-10914) do not run incremental build in release build
Robert Kleinschmager assigned JENKINS-10914 to Robert Kleinschmager do not run incremental build in release build Change By: Robert Kleinschmager (16/Jul/13 6:57 AM) Assignee: teilo RobertKleinschmager 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] [m2release] (JENKINS-10914) do not run incremental build in release build
Robert Kleinschmager commented on JENKINS-10914 do not run incremental build in release build submitted pull request https://github.com/jenkinsci/m2release-plugin/pull/12 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] [m2release] (JENKINS-10914) do not run incremental build in release build
Robert Kleinschmager started work on JENKINS-10914 do not run incremental build in release build Change By: Robert Kleinschmager (16/Jul/13 9:01 AM) Status: Open InProgress 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] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Robert Kleinschmager commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers I also have this problem: all maven2/maven3 jobhave disappeared, when I try to create a new job of type Build a maven2/3 project the same exceptions occurs 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] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Robert Kleinschmager updated JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers Change By: Robert Kleinschmager (11/Jul/13 7:27 AM) Priority: Major Critical 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] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Robert Kleinschmager commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers solved it, you also need to update the Maven Integration plugin/Maven Project plugin to version 1.522 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] [weblogic-deployer] (JENKINS-18685) Support customization of deployment target/environment
Robert Kleinschmager updated JENKINS-18685 Support customization of deployment target/environment Change By: Robert Kleinschmager (10/Jul/13 6:49 AM) Affects Version/s: current 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] [weblogic-deployer] (JENKINS-18685) Support customization of deployment target/environment
Robert Kleinschmager created JENKINS-18685 Support customization of deployment target/environment Issue Type: New Feature Assignee: Raphael CHAUMIER Components: weblogic-deployer Created: 10/Jul/13 6:48 AM Description: I use jenkins to deploy to several different environments. For this I 've setup a build pipeline, where the deployment environment can be chosen by the user (as parameter). It would be very handy, to pass this parameters to the jenkins job, which deploys to weblogic. Project: Jenkins Labels: plugin Priority: Major Reporter: Robert Kleinschmager 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-9249) Svn information is not cloned
Robert Kleinschmager edited a comment on JENKINS-9249 Svn information is not cloned as JENKINS-13888 is resolved, this issue seems also resolved and released with version 0.5 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-9249) Svn information is not cloned
[ https://issues.jenkins-ci.org/browse/JENKINS-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163012#comment-163012 ] Robert Kleinschmager commented on JENKINS-9249: --- as JENKINS-9778 is resolved now, this issue must be fixed too. Any idea, when this will be ready? Svn information is not cloned - Key: JENKINS-9249 URL: https://issues.jenkins-ci.org/browse/JENKINS-9249 Project: Jenkins Issue Type: Improvement Components: clone-workspace Reporter: Michael Pisula Assignee: abayer When cloning a workspace the .svn directories are not cloned. This is a problem for jobs that need this information e.g. Sonar. I guess there is a set of default excludes that prevents those directories from being copied, in this case it would be great to be able to have the option to turn off the default excludes. -- 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
