[JIRA] (JENKINS-61417) maven plugin does not load .mvn config (jvm.config,maven.config)
Title: Message Title Adam Gent created an issue Jenkins / JENKINS-61417 maven plugin does not load .mvn config (jvm.config,maven.config) Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2020-03-10 16:17 Environment: Jenkins version 2.164.2 maven integration plugin 3.4 Priority: Major Reporter: Adam Gent Maven style builds (which use the maven integration plugin) do not load or respect .mvn/*.config. This is not to be confused with a previous issue with Maven itself where -f could not find .mvn. That is freestyle builds work fine and even executing maven pre or post steps work fine. An easy way to test this is to create a project with .mvn/jvm.config or .mvn/maven.config with some property defined like -DsomeProperty=true Then set the goal to: org.apache.maven.plugins:maven-help-plugin:3.2.0:evaluate -Dexpression='someProperty' Add Comment
[JIRA] (JENKINS-26618) "Use private Maven repository" within "Invoke top-level Maven targets" issues.
Title: Message Title Adam Gent commented on JENKINS-26618 Re: "Use private Maven repository" within "Invoke top-level Maven targets" issues. I'm seeing this issue as well. The check private repository settings save correctly but when reloaded it always checks it to true. However I have a rather upgraded jenkins so perhaps its some old data somewhere. 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-19887) Allow time zone to be set on a per user basis
Title: Message Title Adam Gent commented on JENKINS-19887 Re: Allow time zone to be set on a per user basis I briefly looked around and this would not be that hard to implement if only you could get the root JellyContext. Once you have the JellyContext then just you just intercept the calls: JellyContext.getVariable(Config.FMT_TIME_ZONE); Or set the variable since the context is mutable. The JellyContext is already bound to a request via a ThreadLocal in ExpressionFactory2 so you just need to setup the parent JellyContext to look at user config. The problem is that Stapler makes its own JellyContext called CustomJellyContext in DefaultScriptInvoker per request (which is good)! So in theory a custom DefaultScriptInvoker that pulls user configuration logic and sets the context with that user logic should be able to set the correct time zone variable. 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-36614) Ignoring specific files or commit strings for change detection required
Title: Message Title Adam Gent commented on JENKINS-36614 Re: Ignoring specific files or commit strings for change detection required He is talking about JENKINS-30189 . It is a desirable feature and I'm shocked it isn't in yet particularly since the Git Jenkins plugin supports this behavior (since 2014 version 2.2.9). It is fairly trivial feature to add. I'll see if I can put a pull request. 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-30189) Add option to ignore certain commits, e.g. by user
Title: Message Title Adam Gent commented on JENKINS-30189 Re: Add option to ignore certain commits, e.g. by user @Jesse Glick JENKINS-7239 is actually far less useful. Especially in the case if you are using Maven and the pom.xml file is altered all the time by both the build system and users (maven release plugin, and maven versions plugin). The Git plugin already does what this issue is requesting so people familiar with the Git plugin should be able to easily use this plugin. 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.
