[JIRA] (JENKINS-41856) Cannot initialize beans with named parameters and the default constructor
Title: Message Title Laurent TOURREAU closed an issue as Cannot Reproduce Jenkins / JENKINS-41856 Cannot initialize beans with named parameters and the default constructor Change By: Laurent TOURREAU Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43129) When integrated with octane and jenkins pipeline build number increased incorrectly
Title: Message Title Laurent TOURREAU commented on JENKINS-43129 Re: When integrated with octane and jenkins pipeline build number increased incorrectly This issue is duplicated Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43129) When integrated with octane and jenkins pipeline build number increased incorrectly
Title: Message Title Laurent TOURREAU closed an issue as Duplicate Jenkins / JENKINS-43129 When integrated with octane and jenkins pipeline build number increased incorrectly Change By: Laurent TOURREAU Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-42675 Override default NodeJS registry when installing in global mode on Global Tools Configuration page Change By: Laurent TOURREAU Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Laurent TOURREAU commented on JENKINS-42675 Re: Override default NodeJS registry when installing in global mode on Global Tools Configuration page I agree with you regarding the global installation mainly concern 3rd party tools like bower, gulp, etc. It's our case. But in our company we use a corporate registry to achieve better network performance and avoid external traffic. The problem now if I set Jenkins proxy settings, the "No proxy" setting is ignored by "Global Tools Configuration" and I get HTTP 403. I tried to set --no-proxy "mycorporaterepo.mycompany.com" without any success. I also try --noproxy or --no_proxy option without any positive result. As workaround I set no_proxy environment variable beside JENKINS_HOME in my tomcat.conf script -> I can access to the internal repo now when Jenkins settings are enabled. The NodeJS plugin should be able to set no_proxy variable to deal with such requested feature. I change the priority to Major because to sum up, it involves two workarounds now: set --registry parameter in "Global npm packages to install" set no_proxy environment variable at Jenkins startup -> it could have other side effect on other Jenkins features. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-42675 Override default NodeJS registry when installing in global mode Change By: Laurent TOURREAU Summary: Override default NodeJS registry when installing with in global mode Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-42675 Override default NodeJS registry when installing in global mode on Global Tools Configuration page Change By: Laurent TOURREAU Summary: Override default NodeJS registry when installing in global mode on Global Tools Configuration page Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42675) Override default NodeJS registry when installing in global mode
Title: Message Title Laurent TOURREAU reopened an issue I reopen the ticket because it doesn't work when specifying "Global npm packages to install" option with "Install from node.js" on NodeJS installations section of Global Tools Configuration page. As workaround I have to add --registry argument in "Global npm packages to install" option. Jenkins / JENKINS-42675 Override default NodeJS registry when installing in global mode Change By: Laurent TOURREAU Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing with global mode
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-42675 Override default NodeJS registry when installing with global mode Change By: Laurent TOURREAU Summary: Override default NodeJS registry when installing in with global mode Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42675) Override default NodeJS registry when installing in global mode
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-42675 Override default NodeJS registry when installing in global mode Issue Type: Improvement Assignee: Unassigned Components: nodejs-plugin Created: 2017/Mar/10 5:53 PM Environment: Jenkins 2.32.3 LTS / NodeJS plugin 1.1.2 Priority: Critical Reporter: Laurent TOURREAU Currently the default registry is set to http://registry.nodejs.org for global mode module installation. Can you implement a way to override this registry? (We use our corporate NPM registry) Regards Add Comment
[JIRA] (JENKINS-41856) Cannot initialize beans with named parameters and the default constructor
Title: Message Title Laurent TOURREAU edited a comment on JENKINS-41856 Re: Cannot initialize beans with named parameters and the default constructor [~craftendo64] @Jess Glick What it the alternative for JsonOutput? 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-41856) Cannot initialize beans with named parameters and the default constructor
Title: Message Title Laurent TOURREAU edited a comment on JENKINS-41856 Re: Cannot initialize beans with named parameters and the default constructor @ Jess Jesse GlickWhat it the alternative for JsonOutput? 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-41856) Cannot initialize beans with named parameters and the default constructor
Title: Message Title Laurent TOURREAU commented on JENKINS-41856 Re: Cannot initialize beans with named parameters and the default constructor Jessee Simpson What it the alternative for JsonOutput? 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-41904) NPE when selectin a scan credential for GitHub SCM on Pipeline Libraries
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-41904 NPE when selectin a scan credential for GitHub SCM on Pipeline Libraries Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Feb/09 7:02 PM Environment: Jenkins 2.32.2 / GitHub Branch Source plugin 2.0.1 Labels: pipeline library github Priority: Major Reporter: Laurent TOURREAU Use case: I want to add a Global Pipeline Library. 1/ Go to Manage Jenkins -> Configuration 2/ On Global Pipeline Libraries section I click on Add button. 3/ I fill Name field 4/ I select Modern SCM ratio button on Retrieval method section 5/ I select GitHub button on Source Code Management section 6/ I fill Owner field 7/ I select a Scan credentials Just after selecting a credential i get this following stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
[JIRA] (JENKINS-41856) Cannot initialize beans with named parameters and the default constructor
Title: Message Title
Laurent TOURREAU created an issue
Jenkins / JENKINS-41856
Cannot initialize beans with named parameters and the default constructor
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Feb/08 6:39 PM
Environment:
Jenkins 2.32.2 / Pipeline 2.5
Priority:
Major
Reporter:
Laurent TOURREAU
On my Jenkins i define a bean :
class Property {
String name
}
Then i instanciate the bean:
def json = JsonOutput.toJson(new Property(name : "a"))
I get an error : unclassified new Property java.util.LinkedHashMap.
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified new Property java.util.LinkedHashMap
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onNewInstance(SandboxInterceptor.java:126)
at org.kohsuke.groovy.sandbox.impl.Checker$3.call(Checker.java:191)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedConstructor(Checker.java:188)
at
[JIRA] (JENKINS-41535) NodeJS installation configuration is not persisted to file
Title: Message Title Laurent TOURREAU commented on JENKINS-41535 Re: NodeJS installation configuration is not persisted to file Same issue with Jenkins 2.32.2 LTS. The config is lost after Jenkins is restarted. 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-37845) GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
Title: Message Title Laurent TOURREAU commented on JENKINS-37845 Re: GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with I confirm this strange behavior. I used a fresh Jenkins 2.32.1 installed today with all Git/Plugins updated to their latest version before writing a new pipeline. To make the hook registering to work, I must run the pipeline first time ensuring a first checkout is performed. Once it is done, i disable GitHub hook trigger for GITScm polling option, save the job , re-enable the option and save again the job. Registration is done (i can see the webhook on githib project settings) and now the pipeline can be triggered. If is the expected process to register the hook, it should be documented clearly 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-26886) Variables not being substituted in github URLs for $JOB_NAME
Title: Message Title Laurent TOURREAU commented on JENKINS-26886 Re: Variables not being substituted in github URLs for $JOB_NAME Kanstantsin Shautsou : You said "env vars exists only in build context" -> I now understand that. What i would like is to avoid configuration duplication between jobs. All the jobs have the same base GitHub URL -> Having the GitHub base URL in a variable can help to reduce the maintenance effort if i have to change the GitHub host URL on hundred jobs. Moreover it avoid to duplicate the base URL in the same job because the URL is the same on SCM configuration section. According to you the best solution is to generate the jobs using dsl plugin to avoid such overhead? 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-28157) Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org
Title: Message Title Laurent TOURREAU closed an issue as Won't Do I don't follow this ticket anymore. Jenkins / JENKINS-28157 Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org Change By: Laurent TOURREAU Status: Reopened Closed Resolution: Won't Do 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
[JIRA] (JENKINS-28070) Maven 3.3.1 build fails on Unix if this Maven version doesn't match with the one in $PATH
Title: Message Title Laurent TOURREAU closed an issue as Won't Do I don't follow this ticket anymore. Jenkins / JENKINS-28070 Maven 3.3.1 build fails on Unix if this Maven version doesn't match with the one in $PATH Change By: Laurent TOURREAU Status: Open Closed Resolution: Won't Do 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
[JIRA] (JENKINS-23186) "Got conflicting probe from ourselves" warning message on Jenkins startup
Title: Message Title Laurent TOURREAU closed an issue as Won't Do I don't follow this issue anymore. Jenkins / JENKINS-23186 "Got conflicting probe from ourselves" warning message on Jenkins startup Change By: Laurent TOURREAU Status: Reopened Closed Resolution: Won't Do 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
[JIRA] (JENKINS-34012) Fail to automatically install JDK 1.8.0_77
Title: Message Title Laurent TOURREAU closed an issue as Won't Do Hi close this issue because I haven't followed it anymore. Jenkins / JENKINS-34012 Fail to automatically install JDK 1.8.0_77 Change By: Laurent TOURREAU Status: Reopened Closed Resolution: Won't Do 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
[JIRA] (JENKINS-41465) Github : Retrieve Project URL in a variable
Title: Message Title
Laurent TOURREAU created an issue
Jenkins / JENKINS-41465
Github : Retrieve Project URL in a variable
Issue Type:
Improvement
Assignee:
Kirill Merkushev
Components:
github-plugin
Created:
2017/Jan/26 7:38 AM
Priority:
Major
Reporter:
Laurent TOURREAU
It should be possible to get the filled Project URL in a build variable. So we will able to retrieve it to avoid configuration duplication when specifying Git scm repository Url which is the same like Github project URL. I suggest : ${GITHUB_PROJECT_URL}
Add Comment
[JIRA] (JENKINS-26886) Variables not being substituted in github URLs for $JOB_NAME
Title: Message Title
Laurent TOURREAU commented on JENKINS-26886
Re: Variables not being substituted in github URLs for $JOB_NAME
The problem persists with $JOB_NAME. I also tried $ {JOB_NAME} , substitution is not done. It is difficult to define a job template without using variables.
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-26886) Variables not being substituted in github URLs for $JOB_NAME
Title: Message Title
Laurent TOURREAU edited a comment on JENKINS-26886
Re: Variables not being substituted in github URLs for $JOB_NAME
I reopen this issue because i have a similar problem with GitHub plugin *1.25.1* / Jenkins *2.32.1* I create a Jenkins variable environment on System configuration screen:GITHUB_BASE_URL = https://mygihubentrepriseurl.comOn Project Url field in my job i enter this value :$\{GITHUB_BASE_URL}/MyOrg/MyProjectResult : On the left pane of job page the GitHub button points to the job page URL instead of pointing to GitHub URL i mentionned on the Project URL field.What's wrong?
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-26886) Variables not being substituted in github URLs for $JOB_NAME
Title: Message Title
Laurent TOURREAU edited a comment on JENKINS-26886
Re: Variables not being substituted in github URLs for $JOB_NAME
I reopen this issue because i have a similar problem with GitHub plugin *1 . 25.1* I create a Jenkins variable environment on System configuration screen:GITHUB_BASE_URL = https://mygihubentrepriseurl.comOn Project Url field in my job i enter this value :$\{GITHUB_BASE_URL}/MyOrg/MyProjectResult : On the left pane of job page the GitHub button points to the job page URL instead of pointing to GitHub URL i mentionned on the Project URL field.What's wrong?
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-26886) Variables not being substituted in github URLs for $JOB_NAME
Title: Message Title
Laurent TOURREAU edited a comment on JENKINS-26886
Re: Variables not being substituted in github URLs for $JOB_NAME
I reopen this issue because i have a similar problem.I create a Jenkins variable environment on System configuration screen:GITHUB_BASE_URL = https://mygihubentrepriseurl.comOn Project Url field in my job i enter this value :$ \ {GITHUB_BASE_URL}/MyOrg/MyProjectResult : On the left pane of job page the GitHub button points to the job page URL instead of pointing to GitHub URL i mentionned on the Project URL field.What's wrong?
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-26886) Variables not being substituted in github URLs for $JOB_NAME
Title: Message Title
Laurent TOURREAU reopened an issue
I reopen this issue because i have similar problem. I create a Jenkins variable environment on System configuration screen: GITHUB_BASE_URL = https://mygihubentrepriseurl.com On Project Url field in my job i enter this value : $ {GITHUB_BASE_URL} /MyOrg/MyProject Result : On the left pane of job page the GitHub button points to the job page URL instead of pointing to GitHub URL i mentionned on the Project URL field. What's wrong?
Jenkins / JENKINS-26886
Variables not being substituted in github URLs for $JOB_NAME
Change By:
Laurent TOURREAU
Resolution:
Incomplete
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26886) Variables not being substituted in github URLs for $JOB_NAME
Title: Message Title
Laurent TOURREAU edited a comment on JENKINS-26886
Re: Variables not being substituted in github URLs for $JOB_NAME
I reopen this issue because i have a similar problem.I create a Jenkins variable environment on System configuration screen:GITHUB_BASE_URL = https://mygihubentrepriseurl.comOn Project Url field in my job i enter this value :${GITHUB_BASE_URL}/MyOrg/MyProjectResult : On the left pane of job page the GitHub button points to the job page URL instead of pointing to GitHub URL i mentionned on the Project URL field.What's wrong?
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-21323) Global default maven settings providers not working
Title: Message Title Laurent TOURREAU reopened an issue I reopen this issue because for me it is very bad documented. At least, an update should be made to [Build Maven2 project] page to describe the behaviour Daniel is talking about. Another ticket should be opened, to improve online help on Maven Configuration section on Tools Global Configuration page. Jenkins / JENKINS-21323 Global default maven settings providers not working Change By: Laurent TOURREAU Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received
[JIRA] (JENKINS-21323) Global default maven settings providers not working
Title: Message Title Laurent TOURREAU resolved as Not A Defect Jenkins / JENKINS-21323 Global default maven settings providers not working Change By: Laurent TOURREAU Status: In Progress Resolved 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-21323) Global default maven settings providers not working
Title: Message Title Laurent TOURREAU updated JENKINS-21323 Jenkins / JENKINS-21323 Global default maven settings providers not working Change By: Laurent TOURREAU Status: Resolved In Review 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-21323) Global default maven settings providers not working
Title: Message Title Laurent TOURREAU updated JENKINS-21323 Jenkins / JENKINS-21323 Global default maven settings providers not working Change By: Laurent TOURREAU Status: In Review Progress 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-41265) Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID
Title: Message Title Laurent TOURREAU commented on JENKINS-41265 Re: Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID @Cyrille. Since you have updated the docs, it is enough for me. Thanks for your clarification. Small typo on your answer: globalMavenSettingsConfig and mavenSettingsConfig use the ID, not the name of the Maven settings file (resp Maven Global Settings file). 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-41265) Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID
Title: Message Title Laurent TOURREAU commented on JENKINS-41265 Re: Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID It should be more consistent to rename the argument globalMavenSettingsConfigId instead of globalMavenSettingsConfig. Or the doc should be clearer for this point: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Maven+Plugin "Maven Global Settings Config (globalMavenSettingsConfig): Select a global Maven settings file *ID *from Config File Provider 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.
[JIRA] (JENKINS-41265) Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID
Title: Message Title
Laurent TOURREAU updated an issue
Jenkins / JENKINS-41265
Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID
Change By:
Laurent TOURREAU
I added a Global Maven setttings.xml in configuration file provider and named it : my-maven-global-settings.When using Maven Pipeline withMaven clause, it ignores the name provided as globalMavenSettingsConfig argument:{code:java}withMaven( maven: "maven-3.3.9", globalMavenSettingsConfig: "my-maven-global-settings") {...}{code}The build because it cannot find settings.xmlAs workaround I have to specify config file ID instead: {code:java} withMaven( maven: "maven-3.3.9", globalMavenSettingsConfig: "2bde3e90-eada-4573-9a33-bfeb95135d97") {...} {code} It works
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
[JIRA] (JENKINS-41265) Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID
Title: Message Title
Laurent TOURREAU created an issue
Jenkins / JENKINS-41265
Pipeline Maven Plugin : globalMavenSettingsConfig argument doesn't get configuration file name but ID
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
config-file-provider-plugin, pipeline-maven-plugin
Created:
2017/Jan/20 4:22 PM
Environment:
Jenkins 2.32.1 / Config File Provider 2.15.5 / Pipeline Maven Integration Plugin 0.5
Labels:
2.0. pipeline pipeline-maven config-file-provider
Priority:
Major
Reporter:
Laurent TOURREAU
I added a Global Maven setttings.xml in configuration file provider and named it : my-maven-global-settings. When using Maven Pipeline withMaven clause, it ignores the name provided as globalMavenSettingsConfig argument:
withMaven(
maven: "maven-3.3.9",
globalMavenSettingsConfig: "my-maven-global-settings"
) {
...
}
The build because it cannot find settings.xml As workaround I have to specify config file ID instead: withMaven( maven: "maven-3.3.9", globalMavenSettingsConfig: "2bde3e90-eada-4573-9a33-bfeb95135d97" ) { ... } It works
[JIRA] (JENKINS-36266) Amazon EC2 : HTTP 500 when try to generate a Public Key
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-36266 Amazon EC2 : HTTP 500 when try to generate a Public Key Change By: Laurent TOURREAU Summary: Amazon EC2 : HTTP 500 when try to generate a Public Key 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-36266) 500 when try to generate a Public Key
Title: Message Title
Laurent TOURREAU edited a comment on JENKINS-36266
Re: 500 when try to generate a Public Key
Same error on Jenkins 2.32.1 / Ubuntu 16.04.1 LTS / Amazon EC2 plugin 1.36 :{code} Jenkins [Jenkins]var isRunAsTest=false; var rootURL="/jenkins"; var resURL="/jenkins/static/b0807472";crumb.init("Jenkins-Crumb", "6d763508ba1f644abd56cec1453ed216");Skip to content S'identifier createSearchBox("/jenkins/search/");Jenkins Jenkins project Bug tracker Mailing Lists Twitter: @jenkinsci Oops!A problem occurred while processing the request.Please check our bug tracker to see if a similar problem has already been reported.If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.If you think this is a new issue, please file a new issue.When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.The users list might be also useful in understanding what has happened.Stack tracejava.lang.IllegalArgumentException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:80) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-36266) 500 when try to generate a Public Key
Title: Message Title Laurent TOURREAU commented on JENKINS-36266 Re: 500 when try to generate a Public Key Same error on Jenkins 2.32.1 / Ubuntu 16.04.1 LTS: "/jenkins/static/b0807472" data-rooturl="/jenkins" data-resurl="/jenkins/static/b0807472"> Jenkins [Jenkins]"stylesheet" href="" class="code-quote" style="color: #009100">"/jenkins/static/b0807472/css/layout-common.css" type="text/css" />"stylesheet" href="" class="code-quote" style="color: #009100">"/jenkins/static/b0807472/css/style.css" type="text/css" />"stylesheet" href="" class="code-quote" style="color: #009100">"/jenkins/static/b0807472/css/color.css" type="text/css" />"stylesheet" href="" class="code-quote" style="color: #009100">"/jenkins/static/b0807472/css/responsive-grid.css" type="text/css" />"shortcut icon" href="" class="code-quote" style="color: #009100">"/jenkins/static/b0807472/favicon.ico" type="image/vnd.microsoft.icon" />"black" rel="mask-icon" href="" class="code-quote" style="color: #009100">"/jenkins/images/mask-icon.svg" />var isRunAsTest=false; var rootURL="/jenkins"; var resURL="/jenkins/static/b0807472";"/jenkins/static/b0807472/scripts/prototype.js"type="text/_javascript_">"/jenkins/static/b0807472/scripts/behavior.js" type="text/_javascript_">"/jenkins/static/b0807472/scripts/yui/yahoo/yahoo-min.js">"/jenkins/static/b0807472/scripts/yui/dom/dom-min.js">"/jenkins/static/b0807472/scripts/yui/event/event-min.js">"/jenkins/static/b0807472/scripts/yui/animation/animation-min.js">"/jenkins/static/b0807472/scripts/yui/dragdrop/dragdrop-min.js">"/jenkins/static/b0807472/scripts/yui/container/container-min.js">"/jenkins/static/b0807472/scripts/yui/connection/connection-min.js">"/jenkins/static/b0807472/scripts/yui/datasource/datasource-min.js">"/jenkins/static/b0807472/scripts/yui/autocomplete/autocomplete-min.js">"/jenkins/static/b0807472/scripts/yui/menu/menu-min.js">"/jenkins/[JIRA] [workflow-plugin] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installedTitle: Message Title Laurent TOURREAU commented on JENKINS-33966 Re: JAVA_HOME is not set when Maven is automatically installed To be clearer in this ticket, I quote your comment in JENKINS-34012: "The tool step merely ensures that the tool is present. Its return value is the path. If you want to set environment variables, that is up to you. JENKINS-28718 would help automate it." 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] [core] (JENKINS-34012) Fail to automatically install JDK 1.8.0_77
Title: Message Title Laurent TOURREAU commented on JENKINS-34012 Re: Fail to automatically install JDK 1.8.0_77 Indeed, I removed the links to JENKINS-28718 and JENKINS-33966 because them don't have any relationship with this issue. 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] [core] (JENKINS-34012) Fail to automatically install JDK 1.8.0_77
Title: Message Title Laurent TOURREAU commented on JENKINS-34012 Re: Fail to automatically install JDK 1.8.0_77 Not sure : exit code is not the same (Exit code=-80) and i don't have any slave node configured. I only use the master here. 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] [core] (JENKINS-34012) Fail to automatically install JDK 1.8.0_77
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-34012 Fail to automatically install JDK 1.8.0_77 Change By: Laurent TOURREAU On Windows 10, after configuring under Global Tool Configuration a new JDK installation called "JDK-1.8" and selecting _Install automatically_ (I selected _Java SE Development Kit 8u77_ in the combo box) and running the following pipeline code{code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' tool 'JDK-1.8' bat "\"${mvnHome}\"\\bin\\mvn -B verify"}{code} I get this error: {code}[Pipeline] Allocate node : StartRunning on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline[Pipeline] node {[Pipeline] gitFetching changes from the remote Git repositoryChecking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master)[Pipeline] tool[Pipeline] toolInstalling JDK jdk-8u77-oth-JPRDownloading JDK from http://download.oracle.com/otn-pub/java/jdk/8u77-b03/jdk-8u77-windows-i586.exeDownloading 190848568 bytesInstalling C:\Program Files (x86)\Jenkins\tools\hudson.model.JDK\JDK-1.8\jdk.exe[JDK-1.8] $ "C:\Program Files (x86)\Jenkins\tools\hudson.model.JDK\JDK-1.8\jdk.exe" /s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress "INSTALLDIR=C:\Program Files (x86)\Jenkins\tools\hudson.model.JDK\JDK-1.8" /L "C:\Program Files (x86)\Jenkins\tools\hudson.model.JDK\install6891913520880051828log"Failed to install JDK. Exit code=1 619[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineERROR: nullFinished: FAILURE{code} Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34012) Fail to automatically install JDK 1.8.0_77
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-34012 Fail to automatically install JDK 1.8.0_77 Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/04 10:01 PM Environment: Windows 10. Jenkins 2.0-beta-1 Labels: 2.0 2.0-beta jdk installation java8 Priority: Critical Reporter: Laurent TOURREAU On Windows 10, after configuring under Global Tool Configuration a new JDK installation called "JDK-1.8" and selecting Install automatically (I selected Java SE Development Kit 8u77 in the combo box) and running the following pipeline code node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' tool 'JDK-1.8' bat "\"${mvnHome}\"\\bin\\mvn -B verify" }
[JIRA] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed
Title: Message Title Laurent TOURREAU commented on JENKINS-33966 Re: JAVA_HOME is not set when Maven is automatically installed I did this as it : node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' def javaHome = tool 'JDK-1.8' bat "\"${mvnHome}\"\\bin\\mvn -B verify" } I still get the error: [Pipeline] Allocate node : Start Running on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline [Pipeline] node { [Pipeline] git Fetching changes from the remote Git repository Checking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master) [Pipeline] tool [Pipeline] tool [Pipeline] bat [myPipeline] Running batch script C:\Program Files (x86)\Jenkins\workspace\myPipeline>"C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3"\bin\mvn -B verify Error: JAVA_HOME not found in your environment. Please set the JAVA_HOME variable in your environment to match the location of your Java installation. [Pipeline] } //node [Pipeline] Allocate node : End [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE If i explicitely set JAVA_HOME, it works node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' env.JAVA_HOME = tool 'JDK-1.8' bat "\"${mvnHome}\"\\bin\\mvn -B verify" } Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed
Title: Message Title Laurent TOURREAU edited a comment on JENKINS-33966 Re: JAVA_HOME is not set when Maven is automatically installed I did this as it :{code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' def javaHome = tool 'JDK-1.8' bat "\"${mvnHome}\"\\bin\\mvn -B verify"}{code}I still get the error:{code}[Pipeline] Allocate node : StartRunning on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline[Pipeline] node {[Pipeline] gitFetching changes from the remote Git repositoryChecking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master)[Pipeline] tool[Pipeline] tool[Pipeline] bat[myPipeline] Running batch scriptC:\Program Files (x86)\Jenkins\workspace\myPipeline>"C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3"\bin\mvn -B verify Error: JAVA_HOME not found in your environment. Please set the JAVA_HOME variable in your environment to match the location of your Java installation. [Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code}If i explicitely set JAVA_HOME, it works{code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' env.JAVA_HOME = tool 'JDK-1.8' bat "\"${mvnHome}\"\\bin\\mvn -B verify"}{code} 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] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed
Title: Message Title Laurent TOURREAU edited a comment on JENKINS-33966 Re: JAVA_HOME is not set when Maven is automatically installed On Global Tool Configuration, I add a new JDK installation called "JDK-1.8".I set the JAVA_HOME field under installation name to C:\Program Files\Java\jdk1.8.0_77 and run the job again -> same result JAVA_HOME is not found. 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] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed
Title: Message Title Laurent TOURREAU commented on JENKINS-33966 Re: JAVA_HOME is not set when Maven is automatically installed On Global Tool Configuration, I add a new JDK installation called "JDK-1.8". I set the JAVA_HOME to C:\Program Files\Java\jdk1.8.0_77 and run the job again -> same result JAVA_HOME is not found. 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] [core] (JENKINS-33966) JAVA_HOME is not set when Maven is automatically installed
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-33966 JAVA_HOME is not set when Maven is automatically installed Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/31 9:25 PM Environment: Windows 10, Jenkins 2.0-beta-1, JDK 1.8.0_77 Labels: 2.0 2.0-beta Priority: Minor Reporter: Laurent TOURREAU I run Jenkins 2.0 beta binary under Windows 10. I declared a Maven installation "M3" under Global Tool Configuration. I created the pipeline job with the following script: node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "${mvnHome}\\bin\\mvn -B verify" } I get the following error when installing Maven:
[JIRA] [core] (JENKINS-33884) java.io.IOException: Failed to rename Maven installation directory
Title: Message Title Laurent TOURREAU commented on JENKINS-33884 Re: java.io.IOException: Failed to rename Maven installation directory Daniel, one interesting thing : I have got rid of MacAfee LiveSafe and installed Avast Free Antivirus instead. I performed a clean install of Jenkins and relaunched the job -> Maven installation works without any problem. We can conclude this issue could depend of the antivirus installed. 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] [workflow-plugin] (JENKINS-33913) Unable to run a bat step if the double-quoted path argument contains whitespace
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-33913 Unable to run a bat step if the double-quoted path argument contains whitespace Change By: Laurent TOURREAU I run Jenkins 2.0 beta binary under Windows 10.Following tutorial in https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md,I created a pipeline job with the following script:{code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "${mvnHome}\\bin\\mvn -B verify"}{code}I get the following error when running the job:{code}Started by user Administrateur[Pipeline] Allocate node : StartRunning on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline[Pipeline] node {[Pipeline] gitCloning the remote Git repositoryremote: Counting objectsReceiving objectsResolving deltasUpdating referencesChecking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master)First time build. Skipping changelog.[Pipeline] toolUnpacking http://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-bin.zip to C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3 on Jenkins[Pipeline] bat[myPipeline] Running batch scriptC:\Program Files (x86)\Jenkins\workspace\myPipeline>C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3\bin\mvn -B verify 'C:\Program' is not recognized as internal or external command, an executable program or a commands file.[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code}Workaround: I have to surround $\{mvnHome\} reference between escaped double quote:{code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "\"${mvnHome}\"\\bin\\mvn -B verify" }{code} Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-33913) Unable to run a bat step if the double-quoted path argument contains whitespace
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-33913 Unable to run a bat step if the double-quoted path argument contains whitespace Change By: Laurent TOURREAU I run Jenkins 2.0 beta binary under Windows 10.Following tutorial in https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md,I created a pipeline job with the following script:{code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "${mvnHome}\\bin\\mvn -B verify"}{code}I get the following error when running the job:{code}Started by user Administrateur[Pipeline] Allocate node : StartRunning on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline[Pipeline] node {[Pipeline] gitCloning the remote Git repositoryremote: Counting objectsReceiving objectsResolving deltasUpdating referencesChecking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master)First time build. Skipping changelog.[Pipeline] toolUnpacking http://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-bin.zip to C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3 on Jenkins[Pipeline] bat[myPipeline] Running batch scriptC:\Program Files (x86)\Jenkins\workspace\myPipeline>C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3\bin\mvn -B verify 'C:\Program' is not recognized as internal or external command, an executable program or a commands file.[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code}Workaround: I have to surround $ \ {mvnHome \ } reference between escaped double quote:{code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "\"${mvnHome}\"\\bin\\mvn -B verify" }{code} Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-33913) Unable to run a bat step if the double-quoted path argument contains whitespace
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-33913 Unable to run a bat step if the double-quoted path argument contains whitespace Change By: Laurent TOURREAU I run Jenkins 2.0 beta binary under Windows 10.Following tutorial in https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md,I created a pipeline job with the following script:{code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "${mvnHome}\\bin\\mvn -B verify"}{code}I get the following error when running the job:{code}Started by user Administrateur[Pipeline] Allocate node : StartRunning on master in C:\Program Files (x86)\Jenkins\workspace\myPipeline[Pipeline] node {[Pipeline] gitCloning the remote Git repositoryremote: Counting objectsReceiving objectsResolving deltasUpdating referencesChecking out Revision 7dac409d4bd2fec35a4ccde0cb424042cba671df (refs/remotes/origin/master)First time build. Skipping changelog.[Pipeline] toolUnpacking http://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.3.9/apache-maven-3.3.9-bin.zip to C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3 on Jenkins[Pipeline] bat[myPipeline] Running batch scriptC:\Program Files (x86)\Jenkins\workspace\myPipeline>C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3\bin\mvn -B verify 'C:\Program' is not recognized as internal or external command, an executable program or a commands file.[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code}Workaround: I have to surround ${mvnHome} reference between escaped double quote: {code}node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "\"${mvnHome}\"\\bin\\mvn -B verify"}{code} Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-33913) Unable to run a bat step if the double-quoted path argument contains whitespace
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-33913 Unable to run a bat step if the double-quoted path argument contains whitespace Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Mar/30 8:59 PM Environment: Windows 10. Jenkins 2.0-beta Labels: 2.0 2.0-beta pipeline workflow Priority: Major Reporter: Laurent TOURREAU I run Jenkins 2.0 beta binary under Windows 10. Following tutorial in https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md, I created a pipeline job with the following script: node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "${mvnHome}\\bin\\mvn -B verify" } I get the following error when running the job:
[JIRA] [core] (JENKINS-33884) java.io.IOException: Failed to rename Maven installation directory
Title: Message Title Laurent TOURREAU commented on JENKINS-33884 Re: java.io.IOException: Failed to rename Maven installation directory Could what you said about antivirus be documented in the wiki? I think it should be mentionned in Windows installation section. 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] [core] (JENKINS-33884) java.io.IOException: Failed to rename Maven installation directory
Title: Message Title Laurent TOURREAU commented on JENKINS-33884 Re: java.io.IOException: Failed to rename Maven installation directory Today. I relaunched the job -> Same result. So it is reproductible. I disabled McAfee LiveSafe - Internet Security real time analysis and rerun the job. Now it run correctly: [Pipeline] bat [myPipeline] Running batch script C:\Program Files (x86)\Jenkins\workspace\myPipeline>C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\M3\bin\mvn -B verify 'C:\Program' is not recognized as internal or external command... [Pipeline] } //node Obviously it is another error now (I will dig this topic in another JIRA) but Maven has been installed. If I re-enable McAfee and i run the job again, of course the Maven installation issue won't occur since it is already installed. The main question is : How can it be fixed to avoid antivirus issue when dynamically install Maven or any other tool? We can't ask to disable antivirus because the installation event could not be defined beforehand. 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] [core] (JENKINS-33884) java.io.IOException: Failed to rename Maven installation directory
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-33884 java.io.IOException: Failed to rename Maven installation directory Change By: Laurent TOURREAU Labels: 2.0 2.0-beta installation 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] [core] (JENKINS-33884) java.io.IOException: Failed to rename Maven installation directory
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-33884 java.io.IOException: Failed to rename Maven installation directory Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/29 8:13 PM Environment: Windows 10. Labels: 2.0-beta 2.0 Priority: Critical Reporter: Laurent TOURREAU I run Jenkins 2.0 beta binary under Windows 10. I declared a Maven installtion "M3" under Global Tool Configuration. I created the pipeline job with the following script: node { git url: 'https://github.com/jglick/simple-maven-project-with-tests.git' def mvnHome = tool 'M3' bat "${mvnHome}\\bin\\mvn -B verify" } I get the following error when installing Maven:
[JIRA] [core] (JENKINS-33800) java.io.FileNotFoundException: /var/jenkins_home/secrets/initialAdminPassword when upgrading from 1.642.2 LTS to 2.0-beta-1
Title: Message Title Laurent TOURREAU commented on JENKINS-33800 Re: java.io.FileNotFoundException: /var/jenkins_home/secrets/initialAdminPassword when upgrading from 1.642.2 LTS to 2.0-beta-1 It was empty (no jobs defined). I viewed and save the global configuration form (updating security settings : I enabled LDAP authentication and "Enable Slave → Master Access Control"). 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] [core] (JENKINS-33800) java.io.FileNotFoundException: /var/jenkins_home/secrets/initialAdminPassword when upgrading from 1.642.2 LTS to 2.0-beta-1
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-33800 java.io.FileNotFoundException: /var/jenkins_home/secrets/initialAdminPassword when upgrading from 1.642.2 LTS to 2.0-beta-1 Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Mar/24 11:10 PM Environment: Docker image: jenkinsci/jenkins:2.0-beta-1 Labels: 2.0 2.0-beta Priority: Critical Reporter: Laurent TOURREAU When upgrading from 1.662.2 LTS i got this issue when connecting to main page: INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@8ba8667: display name [Root WebApplicationContext]; startup date [Thu Mar 24 22:45:02 UTC 2016]; root of context hierarchy Mar 24, 2016 10:45:02 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory INFO: Bean factory for application context
[JIRA] [subversion-plugin] (JENKINS-32169) NPE in Subversion Plug-in 2.5.5
Title: Message Title Laurent TOURREAU commented on JENKINS-32169 Re: NPE in Subversion Plug-in 2.5.5 Hi I've tried with 2.5.6 version The issue is still present too. 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] [job-dsl-plugin] (JENKINS-31653) readFileFromWorkspace doesn't not update the shell step if the referenced file content has changed
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-31653 readFileFromWorkspace doesn't not update the shell step if the referenced file content has changed Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 19/Nov/15 1:38 PM Environment: Jenkins 1.637 Job DSL plugin 1.40 Labels: job-dsl shell workspace Priority: Major Reporter: Laurent TOURREAU readFileFromWorkspace doesn't not update the shell step if the referenced file content has changed. I have checked that Action for existing jobs and views -> Ignore changes box is NOT ticked. Exemple: step { shell(readFileFromWorkspace("/apps/tools/scripts/myscript.sh")) } myscript.sh content:
[JIRA] [job-dsl-plugin] (JENKINS-31542) Add Extension-Name field in MANIFEST.MF
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-31542 Add Extension-Name field in MANIFEST.MF Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 13/Nov/15 1:48 PM Environment: Jenkins 1.637 Job DSL 1.40 Priority: Major Reporter: Laurent TOURREAU Please add Extension-Name field in MANIFEST.MF : Extension-Name: job-dsl Add Comment
[JIRA] [svnmerge-plugin] (JENKINS-31502) SVN Merge plugin : Automatically update the pom.xml on Maven project when branching
Title: Message Title Laurent TOURREAU created an issue Jenkins / JENKINS-31502 SVN Merge plugin : Automatically update the pom.xml on Maven project when branching Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 11/Nov/15 10:31 AM Environment: Jenkins 1.637 Priority: Major Reporter: Laurent TOURREAU This plugin should be able to update the pom.xml of the project. It should use release:branch maven plugin goal which perform that perfectly : http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html http://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html Add Comment
[JIRA] [svnmerge-plugin] (JENKINS-31502) SVN Merge plugin : Automatically update the pom.xml on Maven project when branching
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-31502 SVN Merge plugin : Automatically update the pom.xml on Maven project when branching Change By: Laurent TOURREAU This plugin should be able to update the pom.xml of the project.It should use release:branch maven plugin goal which perform performs that perfectly :http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.htmlhttp://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html 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] [svnmerge-plugin] (JENKINS-31502) SVN Merge plugin : Automatically update the pom.xml on Maven project when branching
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-31502 SVN Merge plugin : Automatically update the pom.xml on Maven project when branching Change By: Laurent TOURREAU This plugin should be able to update the pom.xml of the project when branching .It should use release:branch maven plugin goal which performs that perfectly :http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.htmlhttp://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html 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] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Title: Message Title Laurent TOURREAU commented on JENKINS-6817 Re: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel Sometimes I have this problem when running Jenkins 1.637 (Tomcat 8.0.28 / Windows 10) [WARNING] Couldn't clean up oid=9 from null hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:575) at hudson.remoting.RemoteInvocationHandler$PhantomReferenceImpl.cleanup(RemoteInvocationHandler.java:360) at hudson.remoting.RemoteInvocationHandler$PhantomReferenceImpl.access$700(RemoteInvocationHandler.java:319) at hudson.remoting.RemoteInvocationHandler$Unexporter.run(RemoteInvocationHandler.java:420) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1077) at hudson.remoting.Channel$1.handle(Channel.java:498) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command close created at at hudson.remoting.Command.(Command.java:56) at hudson.remoting.Channel$CloseCommand.(Channel.java:1071) at hudson.remoting.Channel$CloseCommand.(Channel.java:1069) at hudson.remoting.Channel.close(Channel.java:1153) at hudson.remoting.Channel.close(Channel.java:1135) at hudson.maven.ProcessCache$MavenProcess.discard(ProcessCache.java:150) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:861) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Finished: SUCCESS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-2111) removing a job does not remove the workspace
Title: Message Title Laurent TOURREAU commented on JENKINS-2111 Re: removing a job does not remove the workspace Hi this issue is very annoying when dealing with hundred jobs you manage dynamically. In long term, this causes a lot of space disk issues. I agree this not desirable when having a workspace shared with others jobs. In this case it should be the responsibility of the job author to know if the job deletion (along with its workspace) should impact others jobs. To avoid such case I suggest to add a check box "Don't delete the workspace if this job is deleted" in job configuration and find a way to mark a directory not eraseable. Concerning the slaves I suggest to check once a the node is reconnected, the list of orphan job workspaces and remove them automaticaly. Is it conceivable? 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] [envinject-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Title: Message Title Laurent TOURREAU edited a comment on JENKINS-13348 Re: EnvInject overriding WORKSPACE variable I have installed 1.92.1 the problem is present.I have downgraded until {color:red}1.38{color} which is the latest version that doesn't have this defect.Here a log extract:{code}Building remotely on quality in workspace /apps/homes/jenkins/node_quality/workspace/sonar_build[sonar_build] $ /bin/sh -xe /tmp/hudson4867033689412661438.sh+ echo now Launching the build workspace...now Launching the build workspace...+ /apps/tools/misc-tools/build_test.shWORKSPACE=/apps/tools/homes/jenkins -calypso /node_quality{code}As you can see WORKSPACE variable is not set correctly 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] [envinject-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Title: Message Title Laurent TOURREAU commented on JENKINS-13348 Re: EnvInject overriding WORKSPACE variable I have installed 1.92.1 the problem is present. I have downgraded until 1.38 which is the latest version that doesn't have this defect. Here a log extract: Building remotely on quality in workspace /apps/homes/jenkins/node_quality/workspace/sonar_build [sonar_build] $ /bin/sh -xe /tmp/hudson4867033689412661438.sh + echo now Launching the build workspace... now Launching the build workspace... + /apps/tools/misc-tools/build_test.sh WORKSPACE=/apps/tools/homes/jenkins-calypso/node_quality As you can see WORKSPACE variable is not set correctly 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] [maven-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if this Maven version doesn't match with the one in $PATH
Laurent TOURREAU updated JENKINS-28070 Maven 3.3.1 build fail on Unix if this Maven version doesnt match with the one in $PATH I added more precision of the configuration. Change By: Laurent TOURREAU (29/Apr/15 8:31 AM) Summary: Maven3.3.1buildfailonUnixif this Maven is versiondoesntmatchwith the defaultinstallation onein$PATH Description: WefacethefollowingbuilderrorwhenusingMaven3.3.1 ( inJenkinswith the unique followingsetup:* Maven installation) 3.3.1isinstalledon/apps/tools/distrib/apache-maven-3.3.1*Maven3.1.1isinstalledon/apps/tools/distrib/apache-maven-3.1.1*Wehaveasymboliclink/apps/tools/distrib/maven-/apps/tools/distrib/apache-maven-3.1.1*Wehaveadded/apps/tools/distrib/maven/bin in $PATHOSenvironmentvariable*On Jenkins wehaveconfiguredaMaveninstallation(name:MAVEN,path:/apps/tools/distrib/apache-maven-3 . 3.1) {code}Buildingonmasterinworkspace/myapp/mymoduleUpdatingsvn://svn.mycompany.com/mymoduleatrevision2015-04-23T16:00:24.616+0100Atrevision37434nochangeforsvn://svn.mycompany.com/mymodulesincethepreviousbuild[build_mymodule]$mvn-DparentVersion=[31.0.26]versions:update-parentversions:use-releases-XBuildstepInvoketop-levelMaventargetsmarkedbuildasfailure{code} 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-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if this Maven version doesn't match with the one in $PATH
Laurent TOURREAU updated JENKINS-28070 Maven 3.3.1 build fail on Unix if this Maven version doesnt match with the one in $PATH Change By: Laurent TOURREAU (29/Apr/15 8:51 AM) Description: WefacethefollowingbuilderrorwhenusingMaven3.3.1inJenkinswiththefollowingsetup:*Maven3.3.1isinstalledon/apps/tools/distrib/apache-maven-3.3.1*Maven3.1.1isinstalledon/apps/tools/distrib/apache-maven-3.1.1*Wehaveasymboliclink/apps/tools/distrib/maven-/apps/tools/distrib/apache-maven-3.1.1*Wehaveadded/apps/tools/distrib/maven/binin$PATHOSenvironmentvariable*OnJenkinswehaveconfiguredaMaveninstallation(name:MAVEN,path:/apps/tools/distrib/apache-maven-3.3.1) *ThejobwewanttorunisaMavenprojectwhichhaveapre-stepInvoketop-levelMaventargetshaving(Default)asMavenversionselected. {code}Buildingonmasterinworkspace/myapp/mymoduleUpdatingsvn://svn.mycompany.com/mymoduleatrevision2015-04-23T16:00:24.616+0100Atrevision37434nochangeforsvn://svn.mycompany.com/mymodulesincethepreviousbuild[build_mymodule]$mvn-DparentVersion=[31.0.26]versions:update-parentversions:use-releases-XBuildstepInvoketop-levelMaventargetsmarkedbuildasfailure{code} 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-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if this Maven version doesn't match with the one in $PATH
Laurent TOURREAU commented on JENKINS-28070 Maven 3.3.1 build fail on Unix if this Maven version doesnt match with the one in $PATH The issue disappears if a set the symbolic link /apps/tools/distrib/maven to /apps/tools/distrib/apache-maven-3.3.1. The build is run. Conclusion : We can't mix Maven version used by "Invoke top-level Maven targets" in Pre-Step section and the Maven used in Build section of 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-28070) Maven 3.3.1 build fails on Unix if this Maven version doesn't match with the one in $PATH
Laurent TOURREAU updated JENKINS-28070 Maven 3.3.1 build fails on Unix if this Maven version doesnt match with the one in $PATH Change By: Laurent TOURREAU (29/Apr/15 2:12 PM) Summary: Maven3.3.1build fail fails onUnixifthisMavenversiondoesntmatchwiththeonein$PATH 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] [core] (JENKINS-28157) Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org
Laurent TOURREAU created JENKINS-28157 Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org Issue Type: Bug Assignee: Unassigned Components: core Created: 29/Apr/15 2:27 PM Description: We have changed the update site in Plugin Manager: http://ourmachine.intra:8080/docs/update-center.json When we click on check now, we have the following screen Oops stack trace: java.net.UnknownHostException: updates.jenkins-ci.org at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) at java.net.Socket.connect(Socket.java:579) at java.net.Socket.connect(Socket.java:528) at sun.net.NetworkClient.doConnect(NetworkClient.java:180) at sun.net.www.http.HttpClient.openServer(HttpClient.java:378) at sun.net.www.http.HttpClient.openServer(HttpClient.java:473) at sun.net.www.http.HttpClient.init(HttpClient.java:203) at sun.net.www.http.HttpClient.New(HttpClient.java:290) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:995) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:931) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:849) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1299) at hudson.model.DownloadService.loadJSONHTML(DownloadService.java:181) at hudson.model.DownloadService$Downloadable.updateNow(DownloadService.java:342) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:897) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:183) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at
[JIRA] [core] (JENKINS-28157) Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org
Laurent TOURREAU updated JENKINS-28157 Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org Change By: Laurent TOURREAU (29/Apr/15 2:33 PM) Description: WehavechangedtheupdatesiteinPluginManager:http://ourmachine.intra:8080/docs/update-center.json AllHTTPproxyconfigurationfieldsareleftblanked. Whenweclickonchecknow,wehavethefollowingscreenOopsstacktrace:{code}java.net.UnknownHostException:updates.jenkins-ci.org atjava.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) atjava.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) atjava.net.Socket.connect(Socket.java:579) atjava.net.Socket.connect(Socket.java:528) atsun.net.NetworkClient.doConnect(NetworkClient.java:180) atsun.net.www.http.HttpClient.openServer(HttpClient.java:378) atsun.net.www.http.HttpClient.openServer(HttpClient.java:473) atsun.net.www.http.HttpClient.init(HttpClient.java:203) atsun.net.www.http.HttpClient.New(HttpClient.java:290) atsun.net.www.http.HttpClient.New(HttpClient.java:306) atsun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:995) atsun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:931) atsun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:849) atsun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1299) athudson.model.DownloadService.loadJSONHTML(DownloadService.java:181) athudson.model.DownloadService$Downloadable.updateNow(DownloadService.java:342) athudson.PluginManager.doCheckUpdatesServer(PluginManager.java:897) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:601) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) atorg.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) atorg.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:183) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:876) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:649) atorg.kohsuke.stapler.Stapler.service(Stapler.java:238) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:717) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
[JIRA] [core] (JENKINS-28157) Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org
Laurent TOURREAU commented on JENKINS-28157 Changed update site is not taken into account : java.net.UnknownHostException: updates.jenkins-ci.org Does it mean we can't change the update site URL if we want to use another corporate update site? 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-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if Maven is the default installation
Laurent TOURREAU commented on JENKINS-28070 Maven 3.3.1 build fail on Unix if Maven is the default installation The linked issue concerns Windows not Unix. 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-plugin] (JENKINS-28070) Maven 3.3.1 build fail on Unix if Maven is the default installation
Laurent TOURREAU created JENKINS-28070 Maven 3.3.1 build fail on Unix if Maven is the default installation Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 23/Apr/15 3:26 PM Description: We face the following build error when using Maven 3.3.1 (the unique Maven installation) in Jenkins. Building on master in workspace /myapp/mymodule Updating svn://svn.mycompany.com/mymodule at revision '2015-04-23T16:00:24.616 +0100' At revision 37434 no change for svn://svn.mycompany.com/mymodule since the previous build [build_mymodule] $ mvn -DparentVersion=[31.0.26] versions:update-parent versions:use-releases -X Build step 'Invoke top-level Maven targets' marked build as failure Environment: Red Hat Linux 6.6, Jenkins 1.609 Project: Jenkins Priority: Blocker Reporter: Laurent TOURREAU 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] [subversion-plugin] (JENKINS-26440) svn: E200015: authentication cancelled (subversion plugin 2.5)
Laurent TOURREAU commented on JENKINS-26440 svn: E200015: authentication cancelled (subversion plugin 2.5) I confirm the issues with 1.609 subversion 2.5 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] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Laurent TOURREAU commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Hi I have upgraded from 1.607 to 1.610. I face the same issue. Regards 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] [ldap] (JENKINS-24894) LDAP : Cannot change displayname once user account is created
Laurent TOURREAU commented on JENKINS-24894 LDAP : Cannot change displayname once user account is created Here is the use case: 1/ Enable security in "Configure Global Security" 2/ Select LDAP as Security Realm 3/ Enter LDAP settings. Enter"CN" as displayname. 4/ Save the config. 5/ Log as a new LDAP registered user. On the top right you see your First Name + Full Name (depending the CN field content on LDAP user record). -- Until that it's ok. 6/ Unlog from Jenkins. 7/ Go back in "Configure Global Security" 8/ In LDAP settings, change displayname by "mail" 9/ Save the config 10 / Log as previous LDAP registered user. On the top right you should see user's mail, but it's not the case, instead you get First Name + Full Name as "CN" was again the displayname. 11/ The workaround : Delete the user from Jenkins and relog as it again, this will recreate it and this time you will get user's mail displayed as expected on the top right. Regards 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] [ldap] (JENKINS-24894) LDAP : Cannot change displayname once user account is created
Laurent TOURREAU edited a comment on JENKINS-24894 LDAP : Cannot change displayname once user account is created Here is the use case: 1/ Enable security in "Configure Global Security" 2/ Select LDAP as Security Realm 3/ Enter LDAP settings. Enter"CN" as displayname. 4/ Save the config. 5/ Log as a new LDAP registered user. On the top right you see your First Name + Full Name (depending the CN field content on LDAP user record). -- Until that it's ok. 6/ Unlog from Jenkins. 7/ Go back in "Configure Global Security" 8/ In LDAP settings, change displayname by "mail" 9/ Save the config 10 / Log as previous LDAP registered user. On the top right you should see user's mail, but it's not the case, instead you get First Name + Full Name as "CN" was again the displayname. The workaround : Delete the user from Jenkins and relog as it again, this will recreate it and this time you will get user's mail displayed as expected on the top right. N.B. I tried to stop and restart Jenkins server after changing displayname at step 8, it doesn't solve the problem Regards 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] [ldap] (JENKINS-24894) Users' display names should be synchronized with LDAP
Laurent TOURREAU commented on JENKINS-24894 Users display names should be synchronized with LDAP Thanks for the reply. Concerning the distinction between out of date display name and custom name, we should deal that as it: On user configuration screen we have a ratio button choice -Allow display name synchronization with LDAP - This will make the custom name text box read only, leaving it in grey background color. -Custom display name - This will enable the custom name text box for edition. So we take account that custom display name instead of this from realm. What's your opinion? 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] [ldap] (JENKINS-24894) LDAP : Cannot change displayname once user account is created
Laurent TOURREAU created JENKINS-24894 LDAP : Cannot change displayname once user account is created Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap Created: 27/Sep/14 9:42 PM Description: When changing display name on LDAP settings, if a user account is already created, the change won't be reflected. Project: Jenkins Priority: Major Reporter: Laurent TOURREAU 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] [ldap] (JENKINS-24894) LDAP : Cannot change displayname once user account is created
Laurent TOURREAU updated JENKINS-24894 LDAP : Cannot change displayname once user account is created Change By: Laurent TOURREAU (27/Sep/14 9:44 PM) Environment: Jenkins1.581,LDAPplugin1.10.2 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] [core] (JENKINS-23186) Got conflicting probe from ourselves warning message on Jenkins startup
Laurent TOURREAU commented on JENKINS-23186 Got conflicting probe from ourselves warning message on Jenkins startup What is the appropriate setup according to you? Is it mandatory to have 1 instance by VM max? We have constraint about our architecture. For me, we should not get such reported message if everything is ok. 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.
