[JIRA] (JENKINS-40891) Jenkins triggers rebuild prod branch without any code changes
Title: Message Title Marwa Ahmad created an issue Jenkins / JENKINS-40891 Jenkins triggers rebuild prod branch without any code changes Issue Type: Bug Assignee: Unassigned Components: jenkins-tag-cloud Created: 2017/Jan/09 8:51 AM Environment: - TortoiseHg version 3.7.3 with Mercurial-3.7.3, Python-2.7.9, PyQt-4.11.3, Qt-4.8.6 - jenkins -Windows 7 -3 users with the same account but different names are using the source control - I have 3 main branches, if a certain branch tagged then a rebuild will be triggered for the tagged branch Priority: Major Reporter: Marwa Ahmad I want to share with you issue with the source control-build server. I found that the build server; Jenkins, triggered rebuilding the production branch without any changes in the production code/branch with an old commit and the change was triggered by SCM!. Do you know why? Add Comment
[JIRA] (JENKINS-40892) jenkins was sending port and UseSSL to wrong settings fileds
Title: Message Title xiwen zhao created an issue Jenkins / JENKINS-40892 jenkins was sending port and UseSSL to wrong settings fileds Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2017/Jan/09 9:03 AM Priority: Minor Reporter: xiwen zhao ALM UFT MC and Jenkins settings fields should be the same, ALM UFT and MC had made the change in previous release, Jenkins should align the name fields name. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-35524) new ec2 slave is terminated or terminating during launch
Title: Message Title Mika Karjalainen commented on JENKINS-35524 Re: new ec2 slave is terminated or terminating during launch On a seconod look I agree with Neil. This happens for us due to reaching EBS volumes limit in the AWS region. Still, the plugin should understand the situation and avoid flooding aws with instances. 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-40712) Exception when using mavenSettingsConfig
Title: Message Title Alvaro Lobato closed an issue as Fixed Jenkins / JENKINS-40712 Exception when using mavenSettingsConfig Change By: Alvaro Lobato Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40893) UFT ALM MC Jenkins should use same fields names
Title: Message Title xiwen zhao created an issue Jenkins / JENKINS-40893 UFT ALM MC Jenkins should use same fields names Issue Type: Bug Assignee: xiwen zhao Components: hp-application-automation-tools-plugin Created: 2017/Jan/09 9:10 AM Priority: Minor Reporter: xiwen zhao UFT ALM MC Jenkins should use same fields names, UFT ALM MC had made their changes, Jenkins should align same fields names. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40788) Config File Provider v 2.15.1 is not working
Title: Message Title Marc Ruesch commented on JENKINS-40788 Re: Config File Provider v 2.15.1 is not working 2.15.3 is visible in the history but not available for download yet. 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-40788) Config File Provider v 2.15.1 is not working
Title: Message Title Dominik Bartholdi commented on JENKINS-40788 Re: Config File Provider v 2.15.1 is not working yep, I don't know yet what the issue is: here is the file for direct download: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/config-file-provider/2.15.3/config-file-provider-2.15.3.hpi 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-40894) setting not persistent for "ERRORLEVEL to set build unstable"
Title: Message Title Jan Pluntke created an issue Jenkins / JENKINS-40894 setting not persistent for "ERRORLEVEL to set build unstable" Issue Type: Bug Assignee: Unassigned Attachments: config.xml Components: core Created: 2017/Jan/09 9:16 AM Environment: Jenkins 2.32.1 on Windows 8.1 64bit Labels: configuration Priority: Minor Reporter: Jan Pluntke I am trying to use the new feature from https://issues.jenkins-ci.org/browse/JENKINS-23786 together with the "Execute Windows batch command" build step type to have a certain error level/return code of the batch command lead to result "Unstable" instead of "Failed". This works flawlessly when it is configured initially (steps below), but if the Jenkins service is restarted (or if you do "Manage Jenkins" -> "Reload Configuration from Disk" ), the setting is lost. To reproduce: create a new "Freestyle project item" (e.g. "myUnstableTest") "Add build step" -> "Execute Windows batch command" "Command": exit 1 "Advanced" -> "ERRORLEVEL to set
[JIRA] (JENKINS-40792) Pipeline Maven fails when configured to use settings.xml from config file provider
Title: Message Title Alvaro Lobato commented on JENKINS-40792 Re: Pipeline Maven fails when configured to use settings.xml from config file provider What version of config-file-provider do you have installed? 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-40788) Config File Provider v 2.15.1 is not working
Title: Message Title Marc Ruesch commented on JENKINS-40788 Re: Config File Provider v 2.15.1 is not working thank you! 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-39798) System env not available for polled or triggered jobs
Title: Message Title
sudharsan chandrababu commented on JENKINS-39798
Re: System env not available for polled or triggered jobs
AFAI understand this scenario, I think the user has created a label called COMPUTERNAME. If his intention is to run the build having job name < {NODE_NAME} - {JOB_NAME} - {COMPUTERNAME} > on a remotely configured server then he has to create the node with this label. Else jenkins will not be able to point the value of COMPUTERNAME. This feature is available in jenkins.
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-40803) Endless Loop when "provisoning config files..." when run from a build promotion
Title: Message Title Michael Wiles commented on JENKINS-40803 Re: Endless Loop when "provisoning config files..." when run from a build promotion How do you suggest we get the owner? as JobProperty does not expose it (no getOwner method). There is a setOwner method but no getOwner. 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-39616) Discard old items strategy - not working
Title: Message Title Test User commented on JENKINS-39616 Re: Discard old items strategy - not working You need to use properties in jenkinsfile pipeline: properties([buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '', numToKeepStr: ''))]) 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-40402) Define Build triggers
Title: Message Title aurelien leboulanger commented on JENKINS-40402 Re: Define Build triggers Andrew Bayer If i want to add the @Symbol annotation in the code of the plugin, what is the maven dependency to declare to import this java annotation please ? 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-27872) Only first QTP test is executed, others are skipped with "QTP is not launched." error
Title: Message Title Igor Tereshchuk commented on JENKINS-27872 Re: Only first QTP test is executed, others are skipped with "QTP is not launched." error doesn't reproduce anymore. Can be closed 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-40402) Define Build triggers
Title: Message Title aurelien leboulanger commented on JENKINS-40402 Re: Define Build triggers Finally found in: org.jenkins-ci symbol-annotation 1.5 Maybe add this kind of information in the wiki ? 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-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud Hi Michael, the workaround you provided didn't worked for me. I changed the Launch Method the SSH and select the credentials which i already select for the Vsphere host, instead the one i have to use really for SSH connection. But i get the same error before. 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-40895) How to get consolidated email for Jenkins build-pipeline projects
Title: Message Title rajasekaran radhakrishnan created an issue Jenkins / JENKINS-40895 How to get consolidated email for Jenkins build-pipeline projects Issue Type: New Feature Assignee: David van Laatum Components: build-pipeline-plugin, email-ext-plugin, emailext-template-plugin Created: 2017/Jan/09 10:19 AM Environment: jenkins version 2.32.1 Labels: plugin Priority: Major Reporter: rajasekaran radhakrishnan I am running 4 jobs in my Build-Pipeline project and I am trying to send consolidated email for all job information like console output, build version, git changes, etc... In my current configuration I have configured email-ext template for all 4 jobs So, I am getting 4 emails each and every build. I dont want to spam my mailbox. Is there any way to consolidate all 4 jobs information and send a single email even if jobs fail or success. Regards, Raja
[JIRA] (JENKINS-40336) invalid login for second template in one vsphere cloud
Title: Message Title Michel Lawaty commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud Hi Jan, did you press apply after changing to the vsphere user? Maybe the change was not persisted. After checking the template connection successfully you can change back to JNLP or whatever you had as a setting, and go on. 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-40893) UFT ALM MC Jenkins should use same fields names
Title: Message Title xiwen zhao resolved as Fixed Jenkins / JENKINS-40893 UFT ALM MC Jenkins should use same fields names Change By: xiwen zhao Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40387) Tag build from multibranch pipeline throws E200015
Title: Message Title Marc Jegliewski updated an issue Jenkins / JENKINS-40387 Tag build from multibranch pipeline throws E200015 Change By: Marc Jegliewski Priority: Minor Major 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-40896) Μaven build aborts intermittently with message Accept timed out
Title: Message Title Stelios Pap created an issue Jenkins / JENKINS-40896 Μaven build aborts intermittently with message Accept timed out Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2017/Jan/09 10:36 AM Environment: jenkins 2.36 (deb), maven-plugin 2.14, java 1.7.0_65 Labels: maven-plugin Priority: Critical Reporter: Stelios Pap Ι use Jenkins to run my tests, using nodes in amazon that are connected to master via swarm plugin. After upgrading Jenkins, from 1.6.xx to 2.36, I am getting a lot, the following error ERROR: Aborted Maven execution for InterruptedIOException java.net.SocketTimeoutException: Accept timed out at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source) at java.net.AbstractPlainSocketImpl.accept(Unknown Source) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at java.net.ServerSocket.accept(Unknown Source) at hudson.maven.AbstractMavenProcessFactory$SocketHandler$AcceptorImpl.accept(AbstractMavenProcessFactory.java:213) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source)
[JIRA] (JENKINS-40895) How to get consolidated email for Jenkins build-pipeline projects
Title: Message Title David van Laatum closed an issue as Won't Fix If they are separate jobs then no other than switch to the new pipeline stuff that uses a groovy script Jenkins / JENKINS-40895 How to get consolidated email for Jenkins build-pipeline projects Change By: David van Laatum Status: Open Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-34592) unclassified method java.lang.String[] getAt java.lang.Integer
Title: Message Title J Knurek commented on JENKINS-34592 Re: unclassified method java.lang.String[] getAt java.lang.Integer I also experienced this bug, and the work-around suggested by Thomas fixed it: Replacing a.getAt(index) by a[index] 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-40895) How to get consolidated email for Jenkins build-pipeline projects
Title: Message Title rajasekaran radhakrishnan commented on JENKINS-40895 Re: How to get consolidated email for Jenkins build-pipeline projects @david, If I understood correctly, you are asking me to create new pipeline project instead of build-pipeline and add groovy script for all stages.? Can you share some reference to get collective stage information.. --Raja 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-40879) Locked areas are executed multiple times in parallel
Title: Message Title Antonio Muñiz commented on JENKINS-40879 Re: Locked areas are executed multiple times in parallel Is this always happening, or is it only under certain conditions? if so, can you describe such conditions? 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-40895) How to get consolidated email for Jenkins build-pipeline projects
Title: Message Title rajasekaran radhakrishnan commented on JENKINS-40895 Re: How to get consolidated email for Jenkins build-pipeline projects Is there any option to create consolidated email for Build-Pipeline projects?? --Regards, Raja 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-40895) How to get consolidated email for Jenkins build-pipeline projects
Title: Message Title rajasekaran radhakrishnan reopened an issue Is there any option to create consolidated email for Build-Pipeline projects?? Or Jenkins pipeline is the only option to get consolidated email. --Raja Jenkins / JENKINS-40895 How to get consolidated email for Jenkins build-pipeline projects Change By: rajasekaran radhakrishnan Resolution: Won't Fix Status: Closed Reopened 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
[JIRA] (JENKINS-40897) WARNINGs are filling the log
Title: Message Title Ivan Ivanou created an issue Jenkins / JENKINS-40897 WARNINGs are filling the log Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin, token-macro-plugin Created: 2017/Jan/09 11:00 AM Environment: Jenkins version: 2.32.1 Java version: 1.7.0_91 Delivery pipeline plugin version: 0.10.1 Token Macro plugin version: 2.0 OS: CentOS 6.7 Priority: Minor Reporter: Ivan Ivanou Upgrading the Token Macro plugin to version 2.0 leads to filling Jenkins logs with the following messages: Dec 27, 2016 2:59:30 PM WARNING se.diabol.jenkins.pipeline.token.TokenUtils decodedTemplate Workspace is not accessible Most of jobs are configured to run on slaves which comes up only by necessity. Add Comment
[JIRA] (JENKINS-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud Hi, yes saved the settings, but same results. Currently i worked around this bug with a second Cloud Instance. 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-40290) unit tests failures in core on windows
Title: Message Title James Nord commented on JENKINS-40290 Re: unit tests failures in core on windows @batmat not when I ran it (but make sure you use -Dconcurrency=1 otherwise you have a whole slew of random garbage JENKINS-37177) I will run again. 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-40596) 400 upon opening direct link of project in a GitHub organization project
Title: Message Title Daniel Beck commented on JENKINS-40596 Re: 400 upon opening direct link of project in a GitHub organization project You can change this behaviour through the following flag Since https://github.com/jenkinsci/jenkins/commit/cffe9df0176b0ff895554ce7f2ea4d2f20062351#diff-8e93a62dbd0a8a2c62604d3cdd0b9526L59 the reverse proxy monitor I mentioned no longer detects this. Jesse Glick any particular reason why? 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-40803) Endless Loop when "provisoning config files..." when run from a build promotion
Title: Message Title Daniel Beck commented on JENKINS-40803 Re: Endless Loop when "provisoning config files..." when run from a build promotion Good point. I missed that. 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-40746) Tests failures on the test module of the core on Windows
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-40746
Tests failures on the test module of the core on Windows
Change By:
James Nord
This is somehow a followup on JENKINS-40290. I created a separated issue to segregate and clarify work, and the issue reported there by James [~teilo] was only originally on the {{core}} module.{noformat}Test Result (66 failures )hudson.PluginManagerTest.uploadDependencyResolutionhudson.PluginManagerTest.prevalidateConfighudson.model.RunTest.getLogReturnsAnRightOrderorg.jvnet.hudson.test.BuildTriggerTest.testSomethinghudson.ProcStarterTest.testNonInitializedEnvsNPEhudson.ProcTest.remoteProcOutputSynchudson.ProcTest.ioPumpingWithRemoteLaunchhudson.ProcTest.ioPumpingWithLocalLaunchhudson.cli.AbstractBuildRangeCommand2Test.dummyRangeShouldSuccessEvenTheBuildIsStuckInTheQueuehudson.cli.AbstractBuildRangeCommand2Test.dummyRangeShouldSuccessEvenTheBuildIsRunninghudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberMultiShouldSuccesshudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberMultiShouldSuccessIfSomeBuildDoesNotExisthudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberSingleShouldSuccessIfBuildNumberIsZerohudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberSingleShouldSuccesshudson.cli.AbstractBuildRangeCommandTest.dummyRangeRangeMultiShouldSuccesshudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberSingleShouldSuccessIfBuildNumberIsCommahudson.cli.AbstractBuildRangeCommandTest.dummyRangeNumberSingleShouldSuccessIfBuildNumberIsEmptyhudson.cli.AbstractBuildRangeCommandTest.dummyRangeRangeSingleShouldSuccesshudson.cli.AbstractBuildRangeCommandTest.dummyRangeRangeSingleShouldSuccessIfSomeBuildDoesNotExisthudson.cli.AbstractBuildRangeCommandTest.dummyRangeShouldSuccessIfBuildDoesNotExisthudson.cli.ConsoleCommandTest.consoleShouldSuccessWithFollowhudson.cli.ConsoleCommandTest.consoleShouldSuccessWithLastNLinesAndFollowhudson.cli.ConsoleCommandTest.consoleShouldSuccessWithLastNLineshudson.cli.ConsoleCommandTest.consoleShouldSuccessWithLastBuildhudson.cli.ConsoleCommandTest.consoleShouldSuccessWithSpecifiedBuildNumberhudson.cli.DeleteBuildsCommandTest.deleteBuildsShouldSuccessEvenTheBuildIsRunninghudson.cli.ReloadJobCommandTest.reloadJobManyShouldSucceedEvenAJobIsSpecifiedTwicehudson.cli.ReloadJobCommandTest.reloadJobManyShouldSucceedhudson.cli.ReloadJobCommandTest.reloadJobManyShouldFailIfFirstJobDoesNotExisthudson.cli.ReloadJobCommandTest.reloadJobManyShouldFailIfMoreJobsDoNotExisthudson.cli.ReloadJobCommandTest.reloadJobShouldFailWithoutJobReadPermissionhudson.cli.ReloadJobCommandTest.reloadJobShouldSucceedhudson.cli.ReloadJobCommandTest.reloadJobShouldFailWithoutJobConfigurePermissionhudson.cli.ReloadJobCommandTest.reloadJobManyShouldFailIfLastJobDoesNotExisthudson.cli.ReloadJobCommandTest.reloadJobManyShouldFailIfMiddleJobDoesNotExisthudson.cli.SetBuildDescriptionCommandTest.setBuildDescriptionShouldFailWithoutJobReadPermissionhudson.cli.SetBuildDescriptionCommandTest.setBuildDescriptionShouldFailWithoutRunUpdatePermissi
[JIRA] (JENKINS-40894) setting not persistent for "ERRORLEVEL to set build unstable"
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-40894 setting not persistent for "ERRORLEVEL to set build unstable" Change By: Daniel Beck Assignee: Daniel Beck 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-39684) Use docker images from private registry
Title: Message Title Peter Leibiger commented on JENKINS-39684 Re: Use docker images from private registry I can probably test this sometime this week. 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-40722) Poll SCM results in a Pipeline run every interval (unnecessarily)
Title: Message Title Daniel Beck commented on JENKINS-40722 Re: Poll SCM results in a Pipeline run every interval (unnecessarily) Polling intervals shorter than the build duration could the the problem here. 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-40817) Clicking on (?) help icons after session has expired should provided a useful error message
Title: Message Title Daniel Beck commented on JENKINS-40817 Re: Clicking on (?) help icons after session has expired should provided a useful error message Oleg Nenashev That's JENKINS-40344. 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-40687) "Automatic Cleanup and Sync" does not delete non-versioned folders, only files
Title: Message Title Paul Allen commented on JENKINS-40687 Re: "Automatic Cleanup and Sync" does not delete non-versioned folders, only files Sorry you are correct; AutoClean will remove non versioned files within the scope of the Workspace View (p4 clean). However, files outside of the Workspace view will not get removed. RMDIR is a unset as Perforce default; I could override this option in Jenkins, but some better documentation would help. Do let me know if the option works for you. 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-40898) Declarative should provide an easy to disable/enable some steps in an PR context or not
Title: Message Title
Baptiste Mathus created an issue
Jenkins / JENKINS-40898
Declarative should provide an easy to disable/enable some steps in an PR context or not
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Jan/09 11:31 AM
Priority:
Minor
Reporter:
Baptiste Mathus
When writing a Jenkinsfile, if you have email notifications, or notifications in general, this probably does not make sense to send those when building a PR. PR are reviewed through GitHub, have a build status there, and so on. So by default, sending emails to maintainers creates unnecessary noise. Maybe this be globally enabled/disabled by default though the new options block. Like:
options {
notifyOnPullRequest = true // I would argue that we should be opinionated and put it with a default of false
}
And possibly be overridable per step, like:
notOnPR {
mail to: NOTIFICATION_TARGET, subject:"FAILURE: ${currentBuild.fullDisplayName}", body: "Boo, we failed"
}
WDYT? Thanks!
[JIRA] (JENKINS-40470) Jobs didn't finish on Solaris 11 Intel node
Title: Message Title Marcin Gozdalik commented on JENKINS-40470 Re: Jobs didn't finish on Solaris 11 Intel node Oleg Nenashev do you think it's worthwhile to release 2.32.2 with this fix? If not it'd be good to add a warning to release notes that 2.20 (and 2.32.1) break Intel Solaris 11 workers. 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-31003) Exclude plugin from pre-build steps.
Title: Message Title Tobias Kilian commented on JENKINS-31003 Re: Exclude plugin from pre-build steps. Could you please allow Build Step and Post-Build Step? I dont like being forced to have seperate Job definitions for patchset-created and change-merged events. But afaik, i have to do different runs of sonar analysis (preview vs. full) depending on the gerrit event. What i did before was using the conditional build steps plugin to run sonar one way or the other. As posting events to gerrit only makes sense for patchset-crreated i would like to add the plugin to that conditional build step and was very sad to see that config vanished after upgrading to 1.0.5 ( pretty late, I know As that plugin is very nice and the only real option to force developers to investigate their sonar issues I would really like to keep using it.. 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-40484) Unable to use withMaven step inside docker container
Title: Message Title
Alvaro Lobato commented on JENKINS-40484
Re: Unable to use withMaven step inside docker container
Does this work for you?
node('master') {
docker.image('maven').inside {
sh 'mvn -version'
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36817) False warnings: Failed to copy 2016-07-20 02 to .../builds/.../workspace-files/4581fd88.tmp
Title: Message Title Alexander Vorobiev commented on JENKINS-36817 Re: False warnings: Failed to copy 2016-07-20 02 to .../builds/.../workspace-files/4581fd88.tmp The problem is that parsed log file contains no records related to these warnings. No related lines can be found in the jenkins system log either. These are some internal jenkins logs and internal jenkins tmp file that name might be constructed here: https://github.com/jenkinsci/analysis-core-plugin/blob/master/src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java#L366 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-40746) Tests failures on the test module of the core on Windows
Title: Message Title James Nord commented on JENKINS-40746 Re: Tests failures on the test module of the core on Windows Expected: a string containing "Builds: \n" but: was "Builds: " Yet more people think Linux/Mac is the only OS out there in the world. 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-40797) Job DSL Custom config file with name not found
Title: Message Title Subhas Dandapani reopened an issue Hi, apologies for re-opening this, but the new version is not in Jenkins although its released in GitHub and next development has started Maybe it was overlooked, hence reopening this issue Jenkins / JENKINS-40797 Job DSL Custom config file with name not found Change By: Subhas Dandapani Resolution: Fixed Status: Closed Reopened 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 re
[JIRA] (JENKINS-40899) Transitive plugin dependencies not correctly checked when using snapshots
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-40899 Transitive plugin dependencies not correctly checked when using snapshots Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/09 11:47 AM Priority: Minor Reporter: Alvaro Lobato When you use SNAPSHOTs the transitive dependency versions of the plugins are not being checked correctly, indicating the the -SNAPSHOT version is older than the actual version, which in this case is the same resolved to timestamped snapshot version Dec 13, 2016 5:22:09 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin Operations Center Client Plugin v2.19.2.1-SNAPSHOT (private-e20a1be3-alobato) (operations-center-client) java.io.IOException: Operations Center Client Plugin v2.19.2.1-SNAPSHOT (private-e20a1be3-alobato) failed to load. - Operations Center Context v2.19.2.4-SNAPSHOT (private-6f16fea4-alobato) is older than required. To fix, install v2.19.2.4-20161201.084526-6 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621) at hudson.PluginManager$2$1$1.run(PluginManager.java:516) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1038) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
[JIRA] (JENKINS-40900) ci build fails on windows due to username
Title: Message Title James Nord created an issue Jenkins / JENKINS-40900 ci build fails on windows due to username Issue Type: Task Assignee: Unassigned Components: core Created: 2017/Jan/09 11:57 AM Labels: build Priority: Blocker Reporter: James Nord The ci build of Jenkins is failing due to an invalid regexp. I can reproduce the exact issue if the username contains $1 locally mvn install -Duser.name=user$1bob 00:09:33.768 [Windows] [INFO] — build-helper-maven-plugin:1.7:regex-property (version-property) @ pom — 00:09:33.769 [Windows] [INFO] 00:09:33.769 [Windows] [INFO] Reactor Summary: 00:09:33.769 [Windows] [INFO] 00:09:33.769 [Windows] [INFO] Jenkins main module FAILURE [ 17.211 s] 00:09:33.769 [Windows] [INFO] Jenkins cli SKIPPED 00:09:33.769 [Windows] [INFO] Jenkins core ... SKIPPED 00:09:33.769 [Windows] [INFO] Jenkins war SKIPPED 00:09:33.769 [Windows] [INFO] Tests for Jenkins core . SKIPPED 00:09:33.769 [Windows] [INFO] 00:09:33.769 [Windows] [INFO] BUILD FAILURE 00:09:33.769 [Windows] [INFO] --
[JIRA] (JENKINS-29944) Existing project-level report shouldn't disappear when report is not generated
Title: Message Title Javier Naval commented on JENKINS-29944 Re: Existing project-level report shouldn't disappear when report is not generated We face the same problem. We generate reports (Maven Site, Javadoc,etc) in nightly builds. But daily build remove the links of the main project page because the reports doesn't exists. The plugin should be able to link to the last generated report even when is not from the last build. 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-40470) Jobs didn't finish on Solaris 11 Intel node
Title: Message Title Oleg Nenashev commented on JENKINS-40470 Re: Jobs didn't finish on Solaris 11 Intel node Likely it's about 2.32.3 (need to check with Oliver Gondža). But yes, it makes sense to add the reference to this issue to the Jenkins documentarion 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-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title Evaristo Gutierrez created an issue Jenkins / JENKINS-40901 config-file-provider plugin PCT issues against 2.32.1 Issue Type: Task Assignee: Evaristo Gutierrez Components: config-file-provider-plugin Created: 2017/Jan/09 12:15 PM Priority: Minor Reporter: Evaristo Gutierrez Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title
Evaristo Gutierrez updated an issue
Jenkins / JENKINS-40901
config-file-provider plugin PCT issues against 2.32.1
Change By:
Evaristo Gutierrez
{noformat}Caused by: java.io.IOException: Pipeline: SCM Step v1.15 failed to load. - Jenkins Subversion Plug-in v1.54 is older than required. To fix, install v2.5 or later. - Jenkins GIT plugin v2.3.5 is older than required. To fix, install v2.4.1 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621) at hudson.PluginManager$2$1$1.run(PluginManager.java:516)Caused by: java.io.IOException: Jenkins Git plugin v2.4.1 failed to load. - Jenkins Mailer Plugin v1.13 is older than required. To fix, install v1.16 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621) at hudson.PluginManager$2$1$1.run(PluginManager.java:516){noformat}
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 Issue
[JIRA] (JENKINS-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title Evaristo Gutierrez started work on JENKINS-40901 Change By: Evaristo Gutierrez Status: Open In 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-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title Evaristo Gutierrez updated JENKINS-40901 Jenkins / JENKINS-40901 config-file-provider plugin PCT issues against 2.32.1 Change By: Evaristo Gutierrez Status: In Progress 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-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title Dominik Bartholdi commented on JENKINS-40901 Re: config-file-provider plugin PCT issues against 2.32.1 what is PCT? 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-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title Evaristo Gutierrez commented on JENKINS-40901 Re: config-file-provider plugin PCT issues against 2.32.1 Plugin Compatibility Testing, i.e: executing the plugin tests setting a newer Jenkins versions than the baseline one. mvn clean verify -Djenkins.version=2.32.1 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title Harry Mallon commented on JENKINS-38005 Re: Using archiveArtifacts with a non-matching pattern silently fails the build Jesse Glick: Would this patch mean that the archive stage in pipeline steps view would show as failed? 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-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40901 Re: config-file-provider plugin PCT issues against 2.32.1 Code changed in jenkins User: Dominik Bartholdi Path: pom.xml http://jenkins-ci.org/commit/config-file-provider-plugin/0d7b72d8dd3c5613f712f60bc1f89207d1deca4d Log: Merge pull request #27 from varyvol/JENKINS-40901 JENKINS-40901 Update plugin versions to avoid PCT issues. Compare: https://github.com/jenkinsci/config-file-provider-plugin/compare/376d47bead99...0d7b72d8dd3c 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-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title Dominik Bartholdi updated JENKINS-40901 Jenkins / JENKINS-40901 config-file-provider plugin PCT issues against 2.32.1 Change By: Dominik Bartholdi Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40901) config-file-provider plugin PCT issues against 2.32.1
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40901 Re: config-file-provider plugin PCT issues against 2.32.1 Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml http://jenkins-ci.org/commit/config-file-provider-plugin/868f9901bb0ee9916d2bace8818c278607217ccc Log: JENKINS-40901 Update plugin versions to avoid PCT issues. 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-40080) All pages make multiple /classes requests
Title: Message Title Tom FENNELLY updated JENKINS-40080 Jenkins / JENKINS-40080 All pages make multiple /classes requests Change By: Tom FENNELLY Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40902) Unable to use Build parameters or environment varilables like BUILD_NUMBER
Title: Message Title Sille Kyatha created an issue Jenkins / JENKINS-40902 Unable to use Build parameters or environment varilables like BUILD_NUMBER Issue Type: Improvement Assignee: sogabe Components: doclinks-plugin Created: 2017/Jan/09 1:00 PM Environment: Jenkins 2.7 Priority: Major Reporter: Sille Kyatha Unable to use Environment variables or BUILD parameters within the path or name field. Add Comment
[JIRA] (JENKINS-40797) Job DSL Custom config file with name not found
Title: Message Title Daniel Spilker closed an issue as Fixed That's an infrastructure problem, others are also affected. See https://groups.google.com/d/topic/jenkinsci-dev/2HH37mWysRo/discussion. Jenkins / JENKINS-40797 Job DSL Custom config file with name not found Change By: Daniel Spilker Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-i
[JIRA] (JENKINS-12268) Merge downstream job resuls in a single email
Title: Message Title rajasekaran radhakrishnan commented on JENKINS-12268 Re: Merge downstream job resuls in a single email I got the below error while running the above script. [EnvInject] - Loading node environment variables. Building in workspace /var/lib/jenkins/workspace/groovy-template [groovy-template] $ /usr/share/groovy/bin/groovy /var/lib/jenkins/workspace/groovy-template/hudson5159202024351678849.groovy org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: /var/lib/jenkins/workspace/groovy-template/hudson5159202024351678849.groovy: 1: unexpected token: < @ line 1, column 1. <% ^ 1 error 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-40903) SNI is not supported
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-40903 SNI is not supported Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2017/Jan/09 1:31 PM Priority: Major Reporter: Jakub Bochenski When I try to build config-file-provider-plugin-maven with a Nexus server set as proxy it fails with: 12:37:13 Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] 12:37:13 Deleting 1 temporary files 12:37:13 ERROR: Failed to parse POMs 12:37:13 java.io.IOException: remote file operation failed: /home/acme/workspace/config-file-provider-plugin-maven at hudson.remoting.Channel@74a1dda5:IQ-61a8ac47b316: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: 12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 13 12:37:13 12:37:13 at hudson.FilePath.act(FilePath.java:992) 12:37:13 at hudson.FilePath.act(FilePath.java:974) 12:37:13 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:980) 12:37:13 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:692) 12:37:13
[JIRA] (JENKINS-40903) Server Name Indication is not supported
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-40903 Server Name Indication is not supported Change By: Jakub Bochenski Summary: SNI Server Name Indication is not supported 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-40904) Expose Maven "--debug" config parameter at the folder/global config level
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-40904 Expose Maven "--debug" config parameter at the folder/global config level Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2017/Jan/09 1:32 PM Priority: Minor Reporter: Cyrille Le Clerc pipeline-maven-plugin should expose a Maven "--debug" config parameter at the folder/global config level so that a pipeline author who want to debug his pipeline does NOT have to modify / commit his Jenkinsfile to troubleshoot. Note: we don't have to prevent the doubling of the "--debug" param in an "mvn" call as Maven don't cause exception with such duplication: "mvn --debug --debug package" works well. Add Comment
[JIRA] (JENKINS-40904) [pipeline-maven-plugin] Expose Maven "--debug" config parameter at the folder/global config level
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-40904 [pipeline-maven-plugin] Expose Maven "--debug" config parameter at the folder/global config level Change By: Cyrille Le Clerc Summary: [pipeline-maven-plugin] Expose Maven "--debug" config parameter at the folder/global config level 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-15969) Build Stats Plugin Returns so much data it hangs
Title: Message Title saraswathi sankar commented on JENKINS-15969 Re: Build Stats Plugin Returns so much data it hangs Jenkins Version: 1.509.2 Global Build Stats Plugin Version: 1.3 I hit this issue and followed the steps to delete the charts, but in vain. Any session that i open in Chrome in any machine simply hangs and does not load the charts. Any help would be much appreciated. 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-40903) Server Name Indication is not supported
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-40903
Server Name Indication is not supported
Change By:
Jakub Bochenski
When I try to build {{config-file-provider-plugin-maven}} with a Nexus server set as proxy it fails with:{code}12:37:13 Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com]12:37:13 Deleting 1 temporary files12:37:13 ERROR: Failed to parse POMs12:37:13 java.io.IOException: remote file operation failed: /home/acme/workspace/config-file-provider-plugin-maven at hudson.remoting.Channel@74a1dda5:IQ-61a8ac47b316: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 1312:37:13 12:37:13 at hudson.FilePath.act(FilePath.java:992)12:37:13 at hudson.FilePath.act(FilePath.java:974)12:37:13 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:980)12:37:13 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:692)12:37:13 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)12:37:13 at hudson.model.Run.execute(Run.java:1728)12:37:13 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544)12:37:13 at hudson.model.ResourceController.execute(ResourceController.java:98)12:37:13 at hudson.model.Executor.run(Executor.java:404)12:37:13 Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 1312:37:13 12:37:13 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1384)12:37:13 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1118)12:37:13 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731)12:37:13 at hudson.remoting.UserRequest.perform(UserRequest.java:153)12:37:13 at huds
[JIRA] (JENKINS-40903) Server Name Indication is not supported
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-40903
Server Name Indication is not supported
Change By:
Jakub Bochenski
When I try to build {{config-file-provider-plugin-maven}} with a Nexus server set as proxy it fails with:{code}12:37:13 Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com]12:37:13 Deleting 1 temporary files12:37:13 ERROR: Failed to parse POMs12:37:13 java.io.IOException: remote file operation failed: /home/acme/workspace/config-file-provider-plugin-maven at hudson.remoting.Channel@74a1dda5:IQ-61a8ac47b316: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 1312:37:13 12:37:13 at hudson.FilePath.act(FilePath.java:992)12:37:13 at hudson.FilePath.act(FilePath.java:974)12:37:13 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:980)12:37:13 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:692)12:37:13 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)12:37:13 at hudson.model.Run.execute(Run.java:1728)12:37:13 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544)12:37:13 at hudson.model.ResourceController.execute(ResourceController.java:98)12:37:13 at hudson.model.Executor.run(Executor.java:404)12:37:13 Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 1312:37:13 12:37:13 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1384)12:37:13 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1118)12:37:13 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731)12:37:13 at hudson.remoting.UserRequest.perform(UserRequest.java:153)12:37:13 at huds
[JIRA] (JENKINS-12268) Merge downstream job resuls in a single email
Title: Message Title Alex Earl commented on JENKINS-12268 Re: Merge downstream job resuls in a single email Sounds like you are using script= instead of template= 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-28185) Parameterized Remote Trigger fails when calling a job with Matrix Combination parameter
Title: Message Title Tom Ghyselinck commented on JENKINS-28185 Re: Parameterized Remote Trigger fails when calling a job with Matrix Combination parameter We have version 2.2.2 on Jenkins 1.609.3 LTS It triggers a Job on a Jenkins instance 1.651.1 (not LTS) We sill see this issue. 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-36817) False warnings: Failed to copy 2016-07-20 02 to .../builds/.../workspace-files/4581fd88.tmp
Title: Message Title Ulli Hafner commented on JENKINS-36817 Re: False warnings: Failed to copy 2016-07-20 02 to .../builds/.../workspace-files/4581fd88.tmp Sorry, I do not follow. Just to clarify: The content of the file above is an exception trace from my plugin, it helps to identify the problem. What I would like to know: why is there a warning with a broken file-name, so I need to find the cause of this. You wrote above: Warning example. The warning itself is shown at line 15 with text '11 database corruption at line 51393 of': Can you show the full properties of the warning with this text? How does the log file look that contains this message (just that line is interesting). 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-16475) Build stats graph configuration lost after Jenkins Restart
Title: Message Title
Piotr Ossowski commented on JENKINS-16475
Re: Build stats graph configuration lost after Jenkins Restart
I've encountered similar issue. I'm gathering data from 9 Jenkins instances (will be more soon). Charts are dissapearing on one of them after safeRestart. Please see some details below. root@***:/home/jenkins/jenkins# ls -al global-build-stats.xml rw-rr- 1 jenkins bm 22064 Jan 7 19:20 global-build-stats.xml root@***:/home/jenkins/jenkins# ls al global-build-stats.xml #<-- after ( {jenkins_url} /safeRestart) rw-rr- 1 jenkins bm 220 Jan 7 19:27 global-build-stats.xml I've found temporary workaround by restarting jenkins server (and tomcat): service jenkins stop/start Right now global-build-stats.xml file is not cleared but I'm wondering what was the root cause. I've also noted that file is frequently accessed (each few minutes): rw-rr- 1 jenkins bm 22064 Jan 9 14:06 global-build-stats.xml (...) rw-rr- 1 jenkins bm 22064 Jan 9 14:24 global-build-stats.xml Would it be possible (at least) to add button to upload/reload global-build-stats.xml file to easy restore charts (I keep xml files in a separate repository) when such an issue come back again? Jenkins ver: 2.7.4 Global build stats plugin: 1.4
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-40903) Server Name Indication is not supported
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-40903
Re: Server Name Indication is not supported
Workaround: change {{external: \ *}} to {{external:*,!central}} in Maven settings
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-40903) Server Name Indication is not supported
Title: Message Title Jakub Bochenski commented on JENKINS-40903 Re: Server Name Indication is not supported Workaround: change external: to external:,!central in Maven settings 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-40822) After unintentional double-click on Shelve button SCM sync fails and shows log info about project delete in page footer
Title: Message Title Wojciech Błaszczuk updated an issue Jenkins / JENKINS-40822 After unintentional double-click on Shelve button SCM sync fails and shows log info about project delete in page footer Change By: Wojciech Błaszczuk Attachment: Zaznaczenie_006.png 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-39193) Unable to use rbenv plugin together with ruby environment plugin
Title: Message Title Daniel Spilker commented on JENKINS-39193 Re: Unable to use rbenv plugin together with ruby environment plugin Yes, this is a total mess. I linked all related issues. This does not seem to be a Job DSL issue because even reloading config from disc does not seem to work reliable from what I saw in the related tickets. I assume that other XML based API for creating and updating jobs are affected as well, e.g. CLI and REST. I tried to fix this a few days ago but I found no reliable solution. There is a PR (https://github.com/jenkinsci/job-dsl-plugin/pull/965) but that did not work for me either. If we can't find a reliably working configure block, there will not be a reliable built-in version. If no one finds a working solution, I will deprecate support for all Ruby based plugins with the next release for the time being. 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-40903) Server Name Indication is not supported
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-40903
Re: Server Name Indication is not supported
Workaround: change {{external:\*}} to {{external:*,! central repo.jenkins-ci.org }} in Maven settings
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-15969) Build Stats Plugin Returns so much data it hangs
Title: Message Title saraswathi sankar edited a comment on JENKINS-15969 Re: Build Stats Plugin Returns so much data it hangs Jenkins Version: 1.509.2Global Build Stats Plugin Version: 1.3I hit this issue and followed the steps to delete the charts, but in vain. Any session that i open in Chrome / IE in any machine simply hangs and does not load the charts.Any help would be much appreciated. 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-40822) After unintentional double-click on Shelve button SCM sync fails and shows log info about project delete in page footer
Title: Message Title Wojciech Błaszczuk commented on JENKINS-40822 Re: After unintentional double-click on Shelve button SCM sync fails and shows log info about project delete in page footer I will look forward for the crash-course tutorial in develop starting based on VM's and try to fix it on my own by contribute. If you could shortcut me somewhere (with experience on your own tries to test Jenkins locally 'good way') - please write me asap. 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-40903) Server Name Indication is not supported
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-40903
Re: Server Name Indication is not supported
Workaround: change {{external:\*}} to {{external:*,!repo.jenkins-ci.org}} in Maven settings Result is {code}15:02:55 Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com]15:02:55 Downloaded artifact https://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/plugin/2.17/plugin-2.17.pom{code}
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-32018) Multibranch workflow project tracking multiple repositories
Title: Message Title Jesse Glick commented on JENKINS-32018 Re: Multibranch workflow project tracking multiple repositories One possibility is another mode for workflow-multibranch, where the script comes not from a coversioned Jenkinsfile in the same repo but from some independent source. Note that this is already implemented in CloudBees Jenkins Platform: documentation. 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-40905) install-plugins.sh uses always latest instead of plugin version for transitive dependencies
Title: Message Title Esko Suomi created an issue Jenkins / JENKINS-40905 install-plugins.sh uses always latest instead of plugin version for transitive dependencies Issue Type: Bug Assignee: Nicolas De Loof Components: docker Created: 2017/Jan/09 2:07 PM Priority: Major Reporter: Esko Suomi install-plugins.sh, the utility for automatic downloading of plugins bundled with the official Docker image support fails to use correct version for all transitive dependencies. This is caused by resolveDependencies() function at https://github.com/jenkinsci/docker/blob/master/install-plugins.sh#L112-L117 not taking dependency version into account at all. More specifically, I noticed this because I was developing a new feature to our internal Jenkins utilising the GitHub Organization Folder Plugin. My development was finished and today was the rollout but it turned out that it quite didn't work. After some log reading I realized that the plugin dependency hierarchy goes from GOFP 1.5 to Git Plugin 3.0.1 which requires Git Client 2.1.0 which at the time I was developing the feature was 2.1.0 but a newer version, 2.2.0 was released about a week ago which does not seem to be compatible as it fails to resolve the actual GitHub (Enterprise) URL entirely.
[JIRA] (JENKINS-40906) Resolve an SCM from an SCMSource and a list of candidate target branch names
Title: Message Title
Stephen Connolly created an issue
Jenkins / JENKINS-40906
Resolve an SCM from an SCMSource and a list of candidate target branch names
Issue Type:
New Feature
Assignee:
Stephen Connolly
Components:
workflow-multibranch-plugin
Created:
2017/Jan/09 2:13 PM
Priority:
Minor
Reporter:
Stephen Connolly
Use-case: The Apache Maven Jenkinsfile wants to run integration tests when testing a build of Maven core. As new features are added, there is often a need to add associated integration tests. It would be great if the Jenkinsfile could easily determine if there is a matching branch in the maven-integration-testing repository and check that out... but if there is no matching branch then the master branch should be used instead. Something like
def tests=resolveSCM(source:git(url:'https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git'), targets:[env.BRANCH_NAME,'master']))
node('ubuntu') {
stage 'Checkout'{
...
checkout scm
}
...
}
stage 'Integration Test'
parallel linuxJava7:{
node('ubuntu') {
checkout tests
...
}
},linuxJava8: {
node('ubuntu') {
checkout tests
...
}
},winJava7: {
node('windows-2012') {
checkout tests
...
}
},winJava8: {
node('windows-2012') {
checkout tests
...
}
}
...
There are a couple of important features:
We want to use the SCMSource to create the SCM so that it has a pinned revision and the same version o
[JIRA] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs
Title: Message Title saraswathi sankar edited a comment on JENKINS-15969 Re: Build Stats Plugin Returns so much data it hangs Jenkins Version: 1.509.2Global Build Stats Plugin Version: 1.3I hit this issue and followed the steps to delete the charts, but in vain. Any session that i open in Chrome / Firefox / IE in any machine simply hangs and does not load the charts. Any help would be much appreciated. 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-40906) Resolve an SCM from an SCMSource and a list of candidate target branch names
Title: Message Title
Stephen Connolly updated an issue
Jenkins / JENKINS-40906
Resolve an SCM from an SCMSource and a list of candidate target branch names
Change By:
Stephen Connolly
Use-case:The [Apache Maven Jenkinsfile|https://github.com/apache/maven/blob/e51fc87277bb988aed7641d02fd888c77d0a1206/Jenkinsfile] wants to run integration tests when testing a build of Maven core.As new features are added, there is often a need to add associated integration tests. It would be great if the Jenkinsfile could easily determine if there is a matching branch in the maven-integration-testing repository and check that out... but if there is no matching branch then the master branch should be used instead.Something like{code}def tests= resolveSCM resolveScm (source:git(url:'https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git'), targets:[env.BRANCH_NAME,'master']))node('ubuntu') {stage 'Checkout'{...checkout scm} ...}stage 'Integration Test'parallel linuxJava7:{node('ubuntu') {checkout tests...}},linuxJava8: {node('ubuntu') {checkout tests...}},winJava7: {node('windows-2012') {checkout tests...}},winJava8: {node('windows-2012') {checkout tests...}}...{code}There are a couple of important features:# We want to use the {{SCMSource}} to create the {{SCM}} so that it has a pinned revision and the same version of the tests are used on each of the parallel integration test runs# We want to allow a list of branches to be tried in preference order# We want to avoid requiring conditional behaviour to use this feature in the pipeline so that it can also be used from pipeline-model-definition based pipelines
Add Comment
[JIRA] (JENKINS-40906) Resolve an SCM from an SCMSource and a list of candidate target branch names
Title: Message Title Stephen Connolly commented on JENKINS-40906 Re: Resolve an SCM from an SCMSource and a list of candidate target branch names Some similarities and partial overlap in use-cases 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-40907) Can't save jenkins ystem config
Title: Message Title aflat created an issue Jenkins / JENKINS-40907 Can't save jenkins ystem config Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2017/Jan/09 2:17 PM Environment: centos 7 jenkins 2.38 artifactory plugin: 2.8.2 Priority: Blocker Reporter: aflat Whenever I try to save my config I get the stack trace. I only have credentials saved. No docker proxy set up, since I'm not using docker. Docker is not installed on the jenkins server. I can't save my jenkins config anymore. java.io.InvalidClassException: org.jfrog.hudson.pipeline.docker.proxy.BuildInfoProxyManager$1; local class incompatible: stream classdesc serialVersionUID = 3391376971919256168, local class serialVersionUID = 1809589100624711481 java.io.InvalidClassException: org.jfrog.hudson.pipeline.docker.proxy.BuildInfoProxyManager$1; local class incompatible: stream classdesc serialVersionUID = 3391376971919256168, local class serialVersionUID = 1809589100624711481 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:702) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1705) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1600) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1875) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1432) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:428) at hudson.remoting.UserRequest.deserialize(UserRequest.java:217) at hudson.remoting.UserRequest.perform(UserRequest.java:131) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java
[JIRA] (JENKINS-30962) Builds with password parameters cause remote trigger to show failure
Title: Message Title Tom Ghyselinck commented on JENKINS-30962 Re: Builds with password parameters cause remote trigger to show failure Hi, When will this pull request be integrated? We are still bothered by this issue. 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-40908) GitSCMSource: support custom remote and refspec
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-40908 GitSCMSource: support custom remote and refspec Change By: Mark Waite Assignee: Mark Waite 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-40908) GitSCMSource: support custom remote and refspec
Title: Message Title Mark Waite commented on JENKINS-40908 Re: GitSCMSource: support custom remote and refspec Could you provide more details of the use case(s) where you think this would be useful? 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-40908) GitSCMSource: support custom remote and refspec
Title: Message Title jbq commented on JENKINS-40908 Re: GitSCMSource: support custom remote and refspec Added in the description: can be useful for example in the Pipeline: multibranch plugin to fetch merge/pull requests usually available under a different namespace (eg on Github/Gitlab). 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-40907) Can't save jenkins system config
Title: Message Title Andrew Martin updated an issue Jenkins / JENKINS-40907 Can't save jenkins system config Change By: Andrew Martin Summary: Can't save jenkins ystem system config 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-40908) GitSCMSource: support custom remote and refspec
Title: Message Title jbq updated an issue Jenkins / JENKINS-40908 GitSCMSource: support custom remote and refspec Change By: jbq Allow to set custom remote name and refspec in the advanced options of agit source . Can be useful for example in the Pipeline: multibranch plugin to fetch merge/pull requests usually available under a different namespace (eg on Github/Gitlab). 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-40908) GitSCMSource: support custom remote and refspec
Title: Message Title jbq created an issue Jenkins / JENKINS-40908 GitSCMSource: support custom remote and refspec Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2017/Jan/09 2:22 PM Priority: Minor Reporter: jbq Allow to set custom remote name and refspec in the advanced options of a git source Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40336) invalid login for second template in one vsphere cloud
Title: Message Title Jan Bottek commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud I now deleted also my second Cloud Instance and configured a second template to my first Cloud instance, but same result, i cannot get the workaround working. Any idea what is different between our two setups? 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-40905) install-plugins.sh uses always latest plugin version for transitive dependencies
Title: Message Title Esko Suomi updated an issue Jenkins / JENKINS-40905 install-plugins.sh uses always latest plugin version for transitive dependencies Change By: Esko Suomi Summary: install-plugins.sh uses always latest instead of plugin version for transitive dependencies 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-36089) Pipeline support for Promoted Builds Plugin
Title: Message Title Greg Smith commented on JENKINS-36089 Re: Pipeline support for Promoted Builds Plugin Today, I am using "Keep this build forever" as a "poor man's" promotion button. I have a pipeline script that runs every 15 minutes, and searches for builds that have been marked "Keep Forever" and then passes their information / build number to the next build in the promotion. Its not as flexible as the Promoted Builds plugin was originally, but its working well. My only wish is that I could trigger that build off new builds being marked "Keep Forever" instead of requiring that it run polling every 15 minutes. This is just FYI – as I thought it might be interesting to someone else who finds this jira issue. 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.
