[JIRA] [lockable-resources-plugin] (JENKINS-34273) Extend quantity configuration to Pipeline lock step
Title: Message Title
Florian Hug commented on JENKINS-34273
Re: Extend quantity configuration to Pipeline lock step
This functionality has been implemented (together with the label functionality of JENKINS-34268) in PR26. Since this is my first Jenkins plugin contribution (and my first actual Java implementation) I'm open for any kind of feedback.
lock(label: "MyLabelName", quantity: 3) {
// body
}
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] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Florian Hug commented on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
Antonio Muñiz, maybe you could have a look at PR26 where I tried to implement the functionality for label and quantity. Since this is my first Jenkins plugin contribution (and my first actual Java implementation) I'm open for any kind of feedback. Would be great if we get this merged in.
lock(label: "MyLabelName", quantity: 3) {
// body
}
Note however, that for closing this Issue the functionality to specify a list of resources is still missing. JENKINS-34273 however could be closed completely. I couldn't figure out how the DataBoundSetter for this would need to be modified within the actual LockStep. The actual implementation for dealing with several required resources is already available.
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] [junit-plugin] (JENKINS-34407) junit-plugin parse error
Title: Message Title André Fügenschuh created an issue Jenkins / JENKINS-34407 junit-plugin parse error Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2016/Apr/23 2:12 AM Priority: Major Reporter: André Fügenschuh Upgrading the junit-plugin from 1.11 to 1.12 fails with a parse error. I guess this relates to "PR #35" because the skipped (Ignore attr.) test result file's "time" attr. is empty. While the originator of the file (NUnit) should store a meaningful default (like "00:00:00"), its up to the consumer to provide robust parsing, either by ignoring the "skipped" tests at all or by ignoring the empty string. // Jenkins log stacktrace [16:48:06.879] ERROR: Step ‘Publish NUnit test result report’ aborted due to exception: [16:48:06.879] java.io.IOException: Failed to read C:\Jenkins\workspace\Foo\temporary-junit-reports\TEST-Bar.Common.Test.Utils.AccessorTest_13_2.xml [16:48:06.879] at hudson.tasks.junit.TestResult.parse(TestResult.java:306) [16:48:06.879] at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:244) [16:48:06.879] at hudson.tasks.junit.TestResult.parse(TestResult.java:175) [16:48:06.879] at hudson.tasks.junit.TestResult.parse(TestResult.java:154) [16:48:06.879] at hudson.tasks.junit.TestResult.(TestResult.java:126) [16:48:06.879] at hudson.plugins.nunit.NUnitPublisher$1.invoke(NUnitPublisher.java:243) [16:48:06.879] at hudson.plugins.nunit.NUnitPublisher$1.invoke(NUnitPublisher.java:226) [16:48:06.879] at hudson.FilePath.act(FilePath.java:990) [16:48:06.879] at hudson.FilePath.act(FilePath.java:968) [16:48:06.879] at hudson.plugins.nunit.NUnitPublisher.getTestResult(N
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33109) Log window appear at top of the page
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-33109 Log window appear at top of the page Change By: Sam Van Oort Assignee: Sam Van Oort 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-34406) Failed to Initialize Jenkins Incompatible Ant
Title: Message Title Bruce Coveny created an issue Jenkins / JENKINS-34406 Failed to Initialize Jenkins Incompatible Ant Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/23 12:30 AM Environment: JENKINS WAR VERSION 2.0 WINDOWS SERVER 2008 R2 ENTERPRISE AMD OPTERON(TM) PROCESSOR 6136 2.4 GHZ (4 PROCESSORS) 6.0 GB RAM 64-BIT OPERATION SYSTEM WEBSPHERE APPLICATION SERVER 8.5.5.8 JAVA 1.7.1 Labels: jenkins2.0 ant Priority: Blocker Reporter: Bruce Coveny Upgraded to version 2.0 of Jenkins. Upon restarting server Jenkins fails to initialize saying an incompatible Ant version loaded. [4/22/16 20:20:51:658 EDT] 008f BootFailure E Failed to initialize Jenkins hudson.util.IncompatibleAntVersionDetected: Incompatible Ant loaded from bundleresource://130.fwk2046797665:4/org/apache/tools/ant/types/FileSet.class at hudson.WebAppMain.contextInitialized(WebAppMain.java:180) at com.ibm.ws.webcontainer.webapp.WebApp.notifyServletContextCreated(WebA
[JIRA] [cloudbees-folder-plugin] (JENKINS-33329) Robot-plugin incorrectly recognized CloudBees Folder project to display Robot results column
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-33329 Robot-plugin incorrectly recognized CloudBees Folder project to display Robot results column Change By: Rick Liu Component/s: cloudbees-folder-plugin 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-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34146 Re: Disabled parametrized jobs could be build from build URL Code changed in jenkins User: Ivan Fernandez Calvo Path: core/src/main/java/jenkins/model/ParameterizedJobMixIn.java http://jenkins-ci.org/commit/jenkins/37e7856b017fcf700d314086a709f00601edef00 Log: JENKINS-34146 check if build is build able before to ask for parameters 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-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34146 Disabled parametrized jobs could be build from build URL Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed 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-34146) Disabled parametrized jobs could be build from build URL
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34146 Re: Disabled parametrized jobs could be build from build URL Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/model/ParameterizedJobMixIn.java http://jenkins-ci.org/commit/jenkins/f6e431b80c4d162560419fa51633224a9724bb0d Log: Merge pull request #2262 from kuisathaverat/ JENKINS-34146 [FIX JENKINS-34146] check if build is build able before to ask for parameters Compare: https://github.com/jenkinsci/jenkins/compare/ce9de5a19dce...f6e431b80c4d 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] [cli] (JENKINS-34228) IOException produced in CLI 'delete-builds'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34228 Re: IOException produced in CLI 'delete-builds' Code changed in jenkins User: Ing. Pavel Janousek Path: core/src/main/java/hudson/cli/DeleteBuildsCommand.java http://jenkins-ci.org/commit/jenkins/efc1285d67fb7a8e3df2cd1d499a15edc6641d02 Log: JENKINS-34228 Fixed IOException in DeleteBuildsCommand class 'delete-builds' CLi can be invoked with more occurence of the same build number. Handle such a situation is responsibility of the command impl. itself. 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] [cli] (JENKINS-34228) IOException produced in CLI 'delete-builds'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34228 Re: IOException produced in CLI 'delete-builds' Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/cli/DeleteBuildsCommand.java http://jenkins-ci.org/commit/jenkins/ce9de5a19dceb82aea49787c4401e9886c21e09a Log: Merge pull request #2263 from pjanouse/JENKINS-34228 JENKINS-34228 Fixed IOException in DeleteBuildsCommand class Compare: https://github.com/jenkinsci/jenkins/compare/e1dc525fda14...ce9de5a19dce 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] [s3-plugin] (JENKINS-34316) NullPointerException in S3BucketPublisher.perform()
Title: Message Title Jos Backus commented on JENKINS-34316 Re: NullPointerException in S3BucketPublisher.perform() Hi Alexander, Thanks for the quick fix! However, when I use 0.9.3 in a pipeline I now see: Publish artifacts to S3 Bucket Build was not finished correctly. Is not compeleted yet: true and the artifacts are not published. This is likely because it is part of the current build which is obviously still running. 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-34090) "@since TODO" javadoc comments need updating for the master merge.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34090 Re: "@since TODO" javadoc comments need updating for the master merge. Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/util/HttpResponses.java core/src/main/java/jenkins/I18n.java core/src/main/java/jenkins/model/AssetManager.java core/src/main/java/jenkins/model/item_category/Categories.java core/src/main/java/jenkins/util/ResourceBundleUtil.java core/src/main/java/jenkins/util/xml/XMLUtils.java http://jenkins-ci.org/commit/jenkins/658a854491d51aa34cf818a9767c632f18336141 Log: Merge pull request #2270 from daniel-beck/JENKINS-34090 JENKINS-34090 Add 'since 2.0' annotations Compare: https://github.com/jenkinsci/jenkins/compare/84698df80b05...658a854491d5 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-34090) "@since TODO" javadoc comments need updating for the master merge.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34090 Re: "@since TODO" javadoc comments need updating for the master merge. Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/util/HttpResponses.java core/src/main/java/jenkins/I18n.java core/src/main/java/jenkins/model/AssetManager.java core/src/main/java/jenkins/model/item_category/Categories.java core/src/main/java/jenkins/util/ResourceBundleUtil.java core/src/main/java/jenkins/util/xml/XMLUtils.java http://jenkins-ci.org/commit/jenkins/9e9cd2ef78f3b7820dc95ecda1f1e40fb6c3110c Log: JENKINS-34090 Add 'since 2.0' annotations 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-34281) Queue isn't saved on any shutdown
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34281 Re: Queue isn't saved on any shutdown Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/WebAppMain.java http://jenkins-ci.org/commit/jenkins/84698df80b055e15bdc8c1176167d858b10c513e Log: Merge pull request #2280 from svanoort/fix-shutdown-permissions-issue-JENKINS-34281-mk3 [FIX JENKINS-34281] Run shutdown as system user Compare: https://github.com/jenkinsci/jenkins/compare/5d90f816566a...84698df80b05 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-34281) Queue isn't saved on any shutdown
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34281 Re: Queue isn't saved on any shutdown Code changed in jenkins User: Sam Van Oort Path: core/src/main/java/hudson/WebAppMain.java http://jenkins-ci.org/commit/jenkins/543b947e79d862149a1e52a529c1944e53943b25 Log: Fix JENKINS-34281 by running shutdown as system user Replicates the key bit of dad9b04422d572003c83f0fc4543060a70971cc0 But does not include the likely-unneeded ACL.SYSTEM change before System.exit(0) 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title
H F edited a comment on JENKINS-33908
Re: github plugin generates lots of undesired threaddumps on recreate webhooks
We also see this some times: (maybe it is related) {code}WARNING: Failed to remove hook from GitHubRepositoryName[host=github.com,username= wkda bea ,repository= classifieds zim -service]java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username= wkda bea ,repository= classifieds zim -service]at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231)at org.jenkinsci.plugins.github.webhook.WebhookManager.unregisterFor(WebhookManager.java:118)at com.cloudbees.jenkins.Cleaner.doRun(Cleaner.java:72)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)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)## A fatal error has been detected by the Java Runtime Environment:## SIGSEGV (0xb) at pc=0x7ff91bd52e01, pid=14452, tid=140707534501632## JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27)# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops)# Problematic frame:# J 5534 C2 com.trilead.ssh2.crypto.cipher.AES.encryptBlock([[I)V (1195 bytes) @ 0x7ff91bd52e01 [0x7ff91bd52a00+0x401]## Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again## An error report file with more information is saved as:# /tmp/hs_err_pid14452.log## If you would like to submit a bug report, please visit:# http://bugreport.java.com/bugreport/crash.jsp#{code}And yes.. Jenkins goes to the Pub
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33714) Stage view displays large artifact sizes incorrectly
Title: Message Title Sam Van Oort started work on JENKINS-33714 Change By: Sam Van Oort Status: Open In Progress 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] [pipeline-stage-view-plugin] (JENKINS-33714) Stage view displays large artifact sizes incorrectly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33714 Re: Stage view displays large artifact sizes incorrectly Code changed in jenkins User: Sam Van Oort Path: ui/src/main/js/util/formatters.js http://jenkins-ci.org/commit/pipeline-stage-view-plugin/2eb2a5c3f91d2b78c20462b40483f92da36332e8 Log: Fix calculation of data sizes (1024 kB per MB, etc) - JENKINS-33714 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] [pipeline-stage-view-plugin] (JENKINS-33714) Stage view displays large artifact sizes incorrectly
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-33714 Stage view displays large artifact sizes incorrectly Change By: Sam Van Oort Assignee: Antonio Muñiz Sam Van Oort 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] [pipeline-stage-view-plugin] (JENKINS-33351) Missing artifact names in popover
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-33351 Missing artifact names in popover Change By: Sam Van Oort URL: https://github.com/jenkinsci/pipeline-stage-view-plugin/pull/10 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] [pipeline-stage-view-plugin] (JENKINS-33351) Missing artifact names in popover
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33351 Re: Missing artifact names in popover Code changed in jenkins User: Sam Van Oort Path: rest-api/src/main/java/com/cloudbees/workflow/rest/external/BuildArtifactExt.java http://jenkins-ci.org/commit/pipeline-stage-view-plugin/abf6e1da4ed02446bddf0a3c79157e9f07b72880 Log: Use relativePath for artifact names if they're not set due to exceeding LIST_CUTOFF JENKINS-33351 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] [_unsorted] (JENKINS-34405) java.io.ioexception: unable to establish loopback connection
Title: Message Title Rahul jadhav updated an issue Jenkins / JENKINS-34405 java.io.ioexception: unable to establish loopback connection Change By: Rahul jadhav 1. i download the War jenkins.war file.2. paste it into C:\jenkins\jenkins.war3. opening Command prompt and executing command "java -jar jenkins.war"after loading file i am , getting error like "java.io.ioexception: unable to establish loopback connection"for more information kindly check Logs.txt and Screenshots. 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] [_unsorted] (JENKINS-34405) java.io.ioexception: unable to establish loopback connection
Title: Message Title Rahul jadhav started work on JENKINS-34405 Change By: Rahul jadhav Status: Open In Progress 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] [_unsorted] (JENKINS-34405) java.io.ioexception: unable to establish loopback connection
Title: Message Title Rahul jadhav created an issue Jenkins / JENKINS-34405 java.io.ioexception: unable to establish loopback connection Issue Type: Bug Assignee: Oleg Nenashev Attachments: Logs.txt, scrrenshots.jpg, scrrenshots_2.jpg, scrrenshots_3.jpg, scrrenshots_4.jpg, scrrenshots_5.jpg, scrrenshots_6.jpg Components: _unsorted Created: 2016/Apr/22 8:59 PM Environment: Jenkins version_1.642.2 windows 7_X64 Java 1.8.45 Priority: Major Reporter: Rahul jadhav 1. i download the War file. 2. paste it into C:\jenkins\jenkins.war 3. opening Command prompt and executing command "java -jar jenkins.war" after loading file i am getting error like "java.io.ioexception: unable to establish loopback connection" for more information kindly check Logs.txt and Screenshots.
[JIRA] [durable-task-plugin] (JENKINS-32701) Slashes in branch names cause 'bat' workflow task to hang
Title: Message Title Jesse Glick resolved as Fixed Not clear why this was reopened. Newly mentioned problem seems unrelated. Jenkins / JENKINS-32701 Slashes in branch names cause 'bat' workflow task to hang Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title Kirill Merkushev commented on JENKINS-33908 Re: github plugin generates lots of undesired threaddumps on recreate webhooks Please make sure that user which owns token also have admin rights on this repo. About jobs i mean which type - pipeline|freestyle|maven? 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] [testng-plugin] (JENKINS-34404) testng-plugin: 502 Bad Gateway when using custom Home directory
Title: Message Title Mike Jones created an issue Jenkins / JENKINS-34404 testng-plugin: 502 Bad Gateway when using custom Home directory Issue Type: Bug Assignee: Nalin Makar Attachments: 502 Bad Gateway.png Components: testng-plugin Created: 2016/Apr/22 8:01 PM Environment: Jenkins ver. 1.574 Testng-Plugin version: 1.10 Priority: Minor Reporter: Mike Jones When using Jenkins with a custom Home directory (ex: /home/jenkins/jenkins-prometheus), it appears that a 502 Bad Gateway error occurs when clicking on the Class Name on a testng test result. Here is an example of the URL that the plugin is trying to navigate to: [domain]/jenkins/job/OAM%20-%20Positive%20Testing/8/testngreports/automationFramework/Example_NewUserRegistration Changing the URL to the following successfully loads the page for the Class Name: [domain]/jenkins-prometheus/job/OAM%20-%20Positive%20Testing/8/testngreports/automationFramework/Example_NewUserRegistration
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-34403) docker build fails if Dockerfile pip-installs simplejson
Title: Message Title Ilya Margolin commented on JENKINS-34403 Re: docker build fails if Dockerfile pip-installs simplejson Pull request: https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/55 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] [docker-custom-build-environment-plugin] (JENKINS-34403) docker build fails if Dockerfile pip-installs simplejson
Title: Message Title
Ilya Margolin created an issue
Jenkins / JENKINS-34403
docker build fails if Dockerfile pip-installs simplejson
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
docker-custom-build-environment-plugin
Created:
2016/Apr/22 7:44 PM
Environment:
jenkins 1.625.2, docker-custom-build-environment-plugin 1.6.5
Labels:
plugin
Priority:
Minor
Reporter:
Ilya Margolin
When using a Dockerfile, if docker build output contains "Successfully built" in stdout of some layer, that unrelated output will be taken as image id.
Happens with a Dockerfile containing `RUN pip install simplejson`, for example.
pip install outputs {{Successfully built simplejson }}
And docker outputs
{{Successfully built cb74fa59e071 }}
[JIRA] [core] (JENKINS-33937) setup wizard plugin selection - no links to wiki...
Title: Message Title Keith Zantow resolved as Fixed Jenkins / JENKINS-33937 setup wizard plugin selection - no links to wiki... Change By: Keith Zantow Status: In Progress Resolved Resolution: Fixed 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-33936) setup wizard plugin selection - "WTF is plugin X"?
Title: Message Title Keith Zantow resolved as Fixed Jenkins / JENKINS-33936 setup wizard plugin selection - "WTF is plugin X"? Change By: Keith Zantow Status: In Progress Resolved Resolution: Fixed 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-34137) Possible to close install wizard during plugin install.
Title: Message Title Keith Zantow resolved as Fixed Jenkins / JENKINS-34137 Possible to close install wizard during plugin install. Change By: Keith Zantow Status: In Progress Resolved Resolution: Fixed 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] [sauce-ondemand-plugin] (JENKINS-34011) Sauce On Demand plugin 1.150 Fails to Install. Version 1.149 is OK
Title: Message Title Satyajit Malugu commented on JENKINS-34011 Re: Sauce On Demand plugin 1.150 Fails to Install. Version 1.149 is OK I am seeing the exact same issue on 1.151 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] [logstash-plugin] (JENKINS-29762) Make inclusion of build and environment variables configurable
Title: Message Title Rusty Gerard closed an issue as Fixed Jenkins / JENKINS-29762 Make inclusion of build and environment variables configurable Change By: Rusty Gerard Status: Resolved Closed 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] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Lakshmi Narasimhan Vaikuntam resolved as Fixed Fixed in 1.2.0.0 Jenkins / JENKINS-34117 java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Change By: Lakshmi Narasimhan Vaikuntam Status: In Progress Resolved Resolution: Fixed 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated I didn't get from your response that you had actually checked that the same protocol is used in the submodules as is used in the parent. Can you check that? 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Anthony Ferrari commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Thank you for the quick response! Yes, we are using SSH in the git plugin settings referencing a global credentials store in Jenkins/Manage/Credentials (username/key). SSH works fine with the git plugin except when we attempt to retrieve submodules. We have the "Recursively update submodules" checkbox checked. I can do this no problem using command line gitthe submodules are resolved ok. Any ideas? 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-34402) Windows Server 2008 R2 Crashes on systems running Jenkins and EMC Avamar 7.0
Title: Message Title Matthew Preall created an issue Jenkins / JENKINS-34402 Windows Server 2008 R2 Crashes on systems running Jenkins and EMC Avamar 7.0 Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Apr/22 5:45 PM Environment: Windows Server 2008 R2 Jenkins 1.625.1 and 1.625.3 (and previous versions) Priority: Major Reporter: Matthew Preall In our corporate environment, all of our servers run the EMC Avamar backup client. Last year they upgraded to v7.0 of the client across the corporation, and the only systems with problems are my 2 Jenkins servers. Both of these servers are running on nearly identical Win Server 2008 R2 VM's and are currently running 1.625.1 and 1.625.3 respectively. When Avamar backup utility runs while Jenkins is active, the VM has a failure and reboots. There are no recorded error messages in Jenkins or in the System log other than a recovery event. The crash happens 100% of the time on both machines when the backup runs, and has never happened on any of the hundreds/thousands of other servers on the corporate network.
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Anthony Ferrari, the same credentials are used for the parent repository and the submodule repositories. That generally means you need to use the same protocol for the parent repository and the submodules. For example, if the parent is g...@github.com:MarkEWaite/git-plugin.git (ssh protocol), then the submodules cannot be https://github.com/MarkEWaite/git-client-plugin.git, they must also be ssh protocol. Are you using the same protocol for parent repository and submodule repositories? Do the the parent repository credentials work for the submodule repositories outside the Jenkins job? 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] [image-gallery-plugin] (JENKINS-34401) Comparative gallery base root, image urls, and image links
Title: Message Title Tom PIetrosanti created an issue Jenkins / JENKINS-34401 Comparative gallery base root, image urls, and image links Issue Type: Improvement Assignee: Bruno P. Kinoshita Attachments: 2016-04-22 13_33_31-Integration_Testing_Dev2 #14 [Jenkins].png, 2016-04-22 13_34_27-Integration_Testing_Dev2 #16 [Jenkins].png Components: image-gallery-plugin Created: 2016/Apr/22 5:35 PM Priority: Minor Reporter: Tom PIetrosanti I may be misunderstanding the functionality here, so I'll describe my goal and expectation, along with the resulting issues. I have a regression test that compares screenshots to a baseline. I would love to show those side-by-side. They are currently stored in separate root directories with the same subdirectory structure. Something like: path/to/screenshots/base/testcase/browser/resolution/a.png path/to/screenshots/fail/testcase/browser/resolution/a.png path/to/screenshots/new/testcase/browser/resolution/a.png I configured the common base dir to be path/to/screenshots/ The resulting structure looked good, but the images were broken. I had a nice tree like this: -test A --browser 1 — Resolution a root: base (img) root: fail (img) root: new (img) Turns out the resulti
[JIRA] [p4-plugin] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM
Title: Message Title Paul Allen commented on JENKINS-24070 Re: Error: Wipe Out Workspace blocked by SCM Can you let me know if the owner of the workspace differs from the user in the Jenkins 'Perforce Credential' as it could be a permission issue. Perhaps the client workspace has been set to locked? 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Anthony Ferrari commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated We have Jenkins ver. 1.596.2 with plugins: git 2.5.0-beta5 git-client 1.20.0-beta3 Unfortunately, we still see the error when retrieving submodules.: C:\git\bin\git.exe config --get remote.origin.url # timeout=10 > C:\git\bin\git.exe config --get-regexp ^submodule # timeout=10 > C:\git\bin\git.exe config --get submodule.helloivy.url # timeout=10 > C:\git\bin\git.exe submodule update --init --recursive helloivy FATAL: Command "C:\git\bin\git.exe submodule update --init --recursive helloivy" returned status code 1: stdout: stderr: Cloning into 'helloivy'... Permission denied (publickey). fatal: Could not read from remote repository. 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] [ec2-plugin] (JENKINS-25832) Launch multiple slaves in parallel for jobs with same node label
Title: Message Title Vikas Thakur commented on JENKINS-25832 Re: Launch multiple slaves in parallel for jobs with same node label We were facing the same issue earlier and then we tuned our jam with these 2 settings -Dhudson.model.LoadStatistics.decay=0.1 -Dhudson.model.LoadStatistics.clock=1000 and then this issue was gone 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] [swarm-plugin] (JENKINS-28518) Slaves not discovering when Maven is not enabled on the master
Title: Message Title Joshua Knarr commented on JENKINS-28518 Re: Slaves not discovering when Maven is not enabled on the master Bumping for me. I am using puppet to install jenkins and was pulling my hair out. Loading the configuration and clicking "save" once fixes this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33719) PipelineScript from SCM does not support job parameters
Title: Message Title Mathias Schreck commented on JENKINS-33719 Re: PipelineScript from SCM does not support job parameters I’ve exactly the same problem. This bug is blocking me from using pipeline jobs. 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] [mission-control-view-plugin] (JENKINS-34373) Ability to filter jobs in mission control
Title: Message Title Andrey Shevtsov commented on JENKINS-34373 Re: Ability to filter jobs in mission control There is a couple of ways this can be implemented. 1) Add a new filter field where one can specify a regular _expression_ to filter jobs by name. This can be combined with a check box "Display disabled". 2) Reuse other "basic" view, so all jobs of that view will be displayed in the dashboard. Second is very easy to implement but regex option will require less tabs/views and Jenkins will be less cluttered. Let me know what you think. 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] [jira-ext-plugin] (JENKINS-34335) JIRA-EXT not available as promotion build step
Title: Message Title Dan Alvizu started work on JENKINS-34335 Change By: Dan Alvizu Status: Open In Progress 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] [jira-ext-plugin] (JENKINS-34335) JIRA-EXT not available as promotion build step
Title: Message Title Dan Alvizu commented on JENKINS-34335 Re: JIRA-EXT not available as promotion build step Okay, thanks Oleg. I'm able to reproduce the issue - my builder is indeed not showing up. I'll have to look into 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] [cli] (JENKINS-34287) [2.0] CLI over HTTP doesn't work
Title: Message Title Keith Zantow commented on JENKINS-34287 Re: [2.0] CLI over HTTP doesn't work Dieter Blomme there are a few issues at play, here. What you posted is the same error reported here: JENKINS-23232 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-34394) Maven build fails with stack overflow
Title: Message Title Xenofon Papadopoulos commented on JENKINS-34394 Re: Maven build fails with stack overflow We figured out that if we take -U out of mvn arguments it works fine. Still, we'd like to use 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-34400) APT repository doesn't have version 1.652 anymore
Title: Message Title Marek Obuchowicz created an issue Jenkins / JENKINS-34400 APT repository doesn't have version 1.652 anymore Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, packaging Created: 2016/Apr/22 3:06 PM Priority: Major Reporter: Marek Obuchowicz Version 2.0 is now the "lowest" version that can be downloaded from APT repository at the moment. Even though the "full backward compatibility" of Jenkins 2.0 is advertised - we have found the case when it's not. The software vendor I work with uses jenkins internally from cronjob management (only on local network). Version 2.0 by default requires authentication setup, which breaks the application. As the lifecycle of their releases is pretty long, I would be very happy to be able to stick to "older" version, but sadly - it's not available in repository anymore. It is generally a very good practice to allow people to download all older versions and not force them to use the latest one. Would that be considered at Jenkins, or do we have to fall back to non-elegant methods like repository mirror with v.1.652 ? Add Comment
[JIRA] [robot-plugin] (JENKINS-32118) Opening Robot Framework log failed
Title: Message Title Yang Li edited a comment on JENKINS-32118 Re: Opening Robot Framework log failed same issue, any updates on this? I am using Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/LinuxJenkins 2.0 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] [cli] (JENKINS-34287) [2.0] CLI over HTTP doesn't work
Title: Message Title Dieter Blomme commented on JENKINS-34287 Re: [2.0] CLI over HTTP doesn't work I get the same error server side, but client-side a different error: Apr 22, 2016 2:55:03 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://localhost:8080/cli java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.Request.abort(Request.java:303) at hudson.remoting.Channel.terminate(Channel.java:847) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) at ..remote call to Chunked connection to http://localhost:8080/cli(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250) at hudson.remoting.$Proxy1.waitForProperty(Unknown Source) at hudson.remoting.Channel.waitForRemoteProperty(Channel.java:1258) at hudson.cli.CLI.(CLI.java:147) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:479) at hudson.cli.CLI.main(CLI.java:390) Caused by: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:807) at java.io.ObjectInputStream.(ObjectInputStream.java:302) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Add Comment This message was sent by Atlassian
[JIRA] [git-plugin] (JENKINS-32436) Polling SCM results in infinite builds after pushing changes on GITLab repository
Title: Message Title Iulian Petcu commented on JENKINS-32436 Re: Polling SCM results in infinite builds after pushing changes on GITLab repository This issue occurs randomly and the only fix that I've found was to enable advance clone behaviours - shallow clone with depth 0. 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title H F edited a comment on JENKINS-33908 Re: github plugin generates lots of undesired threaddumps on recreate webhooks Ohh Thanks for your reply.regarding Oauth scope i think they are present? Please see attached screenshot.Regarding the flow .. it is the following:User pushes code to github branch/ creates a PR +> github webhook calls jenkins -> jenkins create comment on PR --> triggers jenkins job build ---> jenkins reports status of build sucess or failure ---> github allow to merge or not (button) based on the "build status" ... if failure button is disabled .. other way merge button shows up green for mergingJobs are just re-saved when there are changes made.. but might be that during troubleshooting / testing they can be saved several time times ... ( dows does it make a difference? Why it would cause troubles ?)Thanks & regards 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title H F commented on JENKINS-33908 Re: github plugin generates lots of undesired threaddumps on recreate webhooks Ohh Thanks for your reply. regarding Oauth scope i think they are present? Please see attached screenshot. Regarding the flow .. it is the following: User pushes code to github branch/ creates a PR +> github webhook calls jenkins -> jenkins create comment on PR --> triggers jenkins job build ---> jenkins reports status of build sucess or failure ---> github allow to merge or not (button) based on the "build status" ... if failure button is disabled .. other way merge button shows up green for merging Jobs are just re-saved when there are changes made.. but might be that during troubleshooting / testing they can be saved several time ... (dows it make a difference? Why it would cause troubles ?) Thanks & regards 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] [cli] (JENKINS-16287) Race condition in 'build' CLI command
Title: Message Title Wolf-Michael Bolle commented on JENKINS-16287 Re: Race condition in 'build' CLI command Yes, this problem is solved by JENKINS-14772 . Your suggestion to use "-r INT" really did it for me. Thank you Anatoliy Guts! Kohsuke Kawaguchi ultimately decided to hide the option in core/src/main/java/hudson/cli/BuildCommand.java: users shouldn't be exposed to a bug in the code The default is a retryCnt of 10. On my system, I had to increase that value. 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] [robot-plugin] (JENKINS-32118) Opening Robot Framework log failed
Title: Message Title Yang Li commented on JENKINS-32118 Re: Opening Robot Framework log failed same issue, any updates on this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title Kirill Merkushev commented on JENKINS-33908 Re: github plugin generates lots of undesired threaddumps on recreate webhooks Jenkins will try to manage hooks in 2 cases: You manually press the btn in global config. You save job configuration (with GH trigger enabled or disabled) So normally it can't produce lot of such logs by itself. What jobs do you use with this trigger? And did you read the message: "There is no credentials with admin access to manage hooks on" ? Please check your scopes twice. It should have admin:hooks scope. 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] [git-plugin] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title
vincent fiset commented on JENKINS-30296
Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build
Mark Waite honestly I don't understand what happened.
one of my 200+ project started to misbehave like in OP description.
I removed the */ in */$branch (which I need for mvn releases) then it stopped. I waited a couple of polling cycle. I putted the */ in $branch and it continued to work properly without continuously rebuilding.
here is my job config
"maven-plugin@2.7.1">
Transactional-api
false
"maven-info@0.2.0">
false
false
"hudson.tasks.LogRotator">
-1
10
-1
-1
"slack@1.8">
ticketmaster
xuTFXjqUjVqmr57Nf68hweIo
#microflex-dev-api-scm
false
false
false
true
false
true
false
true
false
true
false
PUBLISH_TYPE
"java.util.Arrays$ArrayList">
"string-array">
development
maintenance
SKIPIT
Skip integration tests.
false
SKIPUT
Skip unit tests.
false
SKIPTESTS
Skip all tests.
false
BRANCH_NAME
master
"hudson.plugins.git.GitSCM" plugin="git@2.4.4">
2
git@git:xyz.git
62f224b6-a771-4e10-bba2-6ff557e441a0
${BRANCH_NAME}
false
"hudson.plugins.git.browser.GitLab">
https://git/xyz
7.0
"list"/>
*/${BRANCH_NAME}
true
false
false
false
JAVA_1-8
H/5 * * * *
true
false
mfx.services
transactional-api-parent
-Dtm.config.path= ${MAVEN_GIT_ALTCREDENTIALS} ${MAVEN_DEFAULT_PROFILES} ${MAVEN_BUILD_TARGETS} ${MAVEN_TEST_OPTS}
-ea -XX:-UseSplitVerifier -XX:MaxPermSize=300m -Dfile.encoding=UTF-8 -Duser.timezone=GMT
true
false
false
false
false
false
false
false
-1
false
false
true
"jenkins.mvn.DefaultSettingsProvider"/>
"jenkins.mvn.DefaultGlobalSettingsProvider"/>
"warnings@4.35">
low
[WARNINGS]
false
false
false
"analysis-core@1.54">
false
true
true
Java Compiler (javac)
mfx.repo.dist.snapshot
true
true
IS_M2RELEASEBUILD
"postbuild-task@1.8">
tar
ANDoperator>
false
false
/usr/bin/python27 /bld/shared/scm/scripts/package-sha-mapping.py
"mailer@1.16">
microflexapidevelopmentt...@livenation.com
false
true
"slack@1.8">
ticketmaster
NBWPd5TSYGtD0pNOKdDkNToF
/
#mfxe
"ws-cleanup@0.25">
false
"m2release@0.12.0">
IS_M2RELEASEBUILD
-Dtm.config.path= ${MAVEN_GIT_ALTCREDENTIALS} ${MAVEN_DEFAULT_PROFILES} ${MAVEN_RELEASE_TARGETS} ${MAVEN_TEST_OPTS}
${MAVEN_DEFAULT_PROFILES} ${MA
[JIRA] [mstestrunner-plugin] (JENKINS-30457) FATAL: No test files was found since update to v1.2.0
Title: Message Title Armando Fernandez commented on JENKINS-30457 Re: FATAL: No test files was found since update to v1.2.0 A workaround for this would be to remove the ".\" at the beginning of your test file path. It was indeed allowed in previous versions. That's why I have raised this PR to hopefully fix 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] [active-directory-plugin] (JENKINS-3404) mix LDAP and local Hudson users
Title: Message Title Jens Rosenthal commented on JENKINS-3404 Re: mix LDAP and local Hudson users Another important - at least I think so - use case is, that in case there is an LDAP problem, that needs a config update, I cannot login to jenkins to fix the problem. So a "standard" account (the admin or root), that is NOT tied to the configured LDAP is needed. 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title H F updated an issue Jenkins / JENKINS-33908 github plugin generates lots of undesired threaddumps on recreate webhooks Change By: H F Attachment: Screen Shot 2016-04-22 at 16.11.42.png 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title H F updated an issue Jenkins / JENKINS-33908 github plugin generates lots of undesired threaddumps on recreate webhooks Change By: H F Attachment: Screen Shot 2016-01-13 at 11.33.05.png 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title H F updated an issue Jenkins / JENKINS-33908 github plugin generates lots of undesired threaddumps on recreate webhooks Change By: H F Attachment: Screen Shot 2016-01-13 at 11.33.05.png 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title
H F edited a comment on JENKINS-33908
Re: github plugin generates lots of undesired threaddumps on recreate webhooks
We also see this some time times : (maybe it is related) {code}WARNING: Failed to remove hook from GitHubRepositoryName[host=github.com,username=wkda,repository=classifieds-service]java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=wkda,repository=classifieds-service]at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231)at org.jenkinsci.plugins.github.webhook.WebhookManager.unregisterFor(WebhookManager.java:118)at com.cloudbees.jenkins.Cleaner.doRun(Cleaner.java:72)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)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)## A fatal error has been detected by the Java Runtime Environment:## SIGSEGV (0xb) at pc=0x7ff91bd52e01, pid=14452, tid=140707534501632## JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27)# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops)# Problematic frame:# J 5534 C2 com.trilead.ssh2.crypto.cipher.AES.encryptBlock([[I)V (1195 bytes) @ 0x7ff91bd52e01 [0x7ff91bd52a00+0x401]## Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again## An error report file with more information is saved as:# /tmp/hs_err_pid14452.log## If you would like to submit a bug report, please visit:# http://bugreport.java.com/bugreport/crash.jsp#{code}And yes.. Jenkins goes to the Pub
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title H F commented on JENKINS-33908 Re: github plugin generates lots of undesired threaddumps on recreate webhooks We also see some time: WARNING: Failed to remove hook from GitHubRepositoryName[host=github.com,username=wkda,repository=classifieds-service] java.lang.NullPointerException: There is no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=wkda,repository=classifieds-service] at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:231) at org.jenkinsci.plugins.github.webhook.WebhookManager.unregisterFor(WebhookManager.java:118) at com.cloudbees.jenkins.Cleaner.doRun(Cleaner.java:72) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 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) # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7ff91bd52e01, pid=14452, tid=140707534501632 # # JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops) # Problematic frame: # J 5534 C2 com.trilead.ssh2.crypto.cipher.AES.encryptBlock([[I)V (1195 bytes) @ 0x7ff91bd52e01 [0x7ff91bd52a00+0x401] # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/hs_err_pid14452.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # And yes.. Jenkins goes to the Pub Add Comment This message was sent by Atlassian JIRA (v6.4.
[JIRA] [groovy-postbuild-plugin] (JENKINS-34399) Groovy Postbuild documentation states incorrect type for "build" veriable
Title: Message Title Magnus Reftel created an issue Jenkins / JENKINS-34399 Groovy Postbuild documentation states incorrect type for "build" veriable Issue Type: Bug Assignee: wolfs Components: groovy-postbuild-plugin Created: 2016/Apr/22 2:06 PM Labels: documentation Priority: Minor Reporter: Magnus Reftel The documentation in help.jelly links to the Javadoc for hudson.model.AbstractBuild for the build variable, but it is actually a `hudson.model.Run`. Documentation: https://github.com/jenkinsci/groovy-postbuild-plugin/blob/master/src/main/resources/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorder/help.jelly#L8 Declaration: https://github.com/jenkinsci/groovy-postbuild-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildRecorder.java#L110
[JIRA] [groovy-postbuild-plugin] (JENKINS-34399) Groovy Postbuild documentation states incorrect type for "build" variable
Title: Message Title Magnus Reftel updated an issue Jenkins / JENKINS-34399 Groovy Postbuild documentation states incorrect type for "build" variable Change By: Magnus Reftel Summary: Groovy Postbuild documentation states incorrect type for "build" veriable variable 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-33937) setup wizard plugin selection - no links to wiki...
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33937 Re: setup wizard plugin selection - no links to wiki... Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/PluginManager.java core/src/main/resources/jenkins/install/pluginSetupWizard.properties war/src/main/js/templates/pluginSelectionPanel.hbs war/src/main/less/pluginSetupWizard.less http://jenkins-ci.org/commit/jenkins/20d3d8a52920fe035e8eed8fe45e04ca1b74d50c Log: Merge pull request #2260 from kzantow/JENKINS-33936-links-to-wiki JENKINS-33936 JENKINS-33937 add links to wiki for plugins during setup Compare: https://github.com/jenkinsci/jenkins/compare/d1bcd1feba0c...20d3d8a52920 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-33936) setup wizard plugin selection - "WTF is plugin X"?
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33936 Re: setup wizard plugin selection - "WTF is plugin X"? Code changed in jenkins User: kzantow Path: core/src/main/java/hudson/PluginManager.java core/src/main/resources/jenkins/install/pluginSetupWizard.properties war/src/main/js/templates/pluginSelectionPanel.hbs war/src/main/less/pluginSetupWizard.less http://jenkins-ci.org/commit/jenkins/9622bbedbb80e2d710fe6ac6a536eeae871a0f2f Log: JENKINS-33936 JENKINS-33937 - add links to wiki for plugins during setup wizard 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-33936) setup wizard plugin selection - "WTF is plugin X"?
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33936 Re: setup wizard plugin selection - "WTF is plugin X"? Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/PluginManager.java core/src/main/resources/jenkins/install/pluginSetupWizard.properties war/src/main/js/templates/pluginSelectionPanel.hbs war/src/main/less/pluginSetupWizard.less http://jenkins-ci.org/commit/jenkins/20d3d8a52920fe035e8eed8fe45e04ca1b74d50c Log: Merge pull request #2260 from kzantow/JENKINS-33936-links-to-wiki JENKINS-33936 JENKINS-33937 add links to wiki for plugins during setup Compare: https://github.com/jenkinsci/jenkins/compare/d1bcd1feba0c...20d3d8a52920 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-33937) setup wizard plugin selection - no links to wiki...
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33937 Re: setup wizard plugin selection - no links to wiki... Code changed in jenkins User: kzantow Path: core/src/main/java/hudson/PluginManager.java core/src/main/resources/jenkins/install/pluginSetupWizard.properties war/src/main/js/templates/pluginSelectionPanel.hbs war/src/main/less/pluginSetupWizard.less http://jenkins-ci.org/commit/jenkins/9622bbedbb80e2d710fe6ac6a536eeae871a0f2f Log: JENKINS-33936 JENKINS-33937 - add links to wiki for plugins during setup wizard 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] [github-plugin] (JENKINS-33908) github plugin generates lots of undesired threaddumps on recreate webhooks
Title: Message Title H F commented on JENKINS-33908 Re: github plugin generates lots of undesired threaddumps on recreate webhooks Kirill Merkushev Thanks for your reply.. No sure what do you mean with "why it recreates hooks so often?" .. it only comes to my mind that on Manage Jenkins there"s something to create on Gihub side the job webhooks? The scopes (I guess you mean oauth scopes?) and yes.. access token has allowed scopes for manage hooks etc.. 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-26407) Support expandableTextbox form validation
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-26407 Support expandableTextbox form validation Change By: Manuel Jesús Recena Soto Assignee: Oliver Gondža Manuel Jesús Recena Soto 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] [awseb-deployment-plugin] (JENKINS-34398) No configuration options for ElasticBeanstalk build step
Title: Message Title Andrew Eacott created an issue Jenkins / JENKINS-34398 No configuration options for ElasticBeanstalk build step Issue Type: Bug Assignee: Unassigned Attachments: AWSEB build step working.png, AWSEB build step.png Components: awseb-deployment-plugin Created: 2016/Apr/22 1:42 PM Environment: Jenkins 1.656 AWSEB deployment plugin, v0.37 Priority: Critical Reporter: Andrew Eacott After updating to version 0.37 of the plugin, there are no configuration options at all when configuring the AWS ElasticBeanstalk build step. See attached screenshot. v0.37 (broken) v0.35 (working) My jenkins server is 1.656
[JIRA] [git-plugin] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title Kanstantsin Shautsou commented on JENKINS-30296 Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build There are a lot of cases when such problem may appear https://issues.jenkins-ci.org/browse/JENKINS-30345 https://issues.jenkins-ci.org/browse/JENKINS-29714 And PR that solved at least for me in production logic missbehaviour https://github.com/jenkinsci/git-plugin/pull/352 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] [git-plugin] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title Mark Waite edited a comment on JENKINS-30296 Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build [~vincentf] can you describe the steps you take to see this problem? The use case described in the bug report is so common that I would expect hundreds of users to report that problem if it existed in a general configuration. I have many, many jobs which use the "*/master" branch spec, and none of them run continuously or build continuously. 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] [mstestrunner-plugin] (JENKINS-34378) Would be convenient to have validation in the step configuration
Title: Message Title Armando Fernandez assigned an issue to Armando Fernandez Jenkins / JENKINS-34378 Would be convenient to have validation in the step configuration Change By: Armando Fernandez Assignee: Armando Fernandez 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] [mstestrunner-plugin] (JENKINS-30457) FATAL: No test files was found since update to v1.2.0
Title: Message Title Armando Fernandez started work on JENKINS-30457 Change By: Armando Fernandez Status: Open In Progress 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] [mstestrunner-plugin] (JENKINS-34378) Would be convenient to have validation in the step configuration
Title: Message Title Armando Fernandez started work on JENKINS-34378 Change By: Armando Fernandez Status: Open In Progress 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] [mstestrunner-plugin] (JENKINS-30457) FATAL: No test files was found since update to v1.2.0
Title: Message Title Armando Fernandez assigned an issue to Armando Fernandez Jenkins / JENKINS-30457 FATAL: No test files was found since update to v1.2.0 Change By: Armando Fernandez Assignee: Armando Fernandez 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-34397) Support kallithea for pipeline organization
Title: Message Title A. Klitzing created an issue Jenkins / JENKINS-34397 Support kallithea for pipeline organization Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Apr/22 1:32 PM Priority: Minor Reporter: A. Klitzing I like to request a plugin for another pipeline plugin for an organization like "GitHub Organization Folder Plugin". As a lot of companies do not host the source code on github it would be helpful if "self hosted" repositories could be supported with kallithea. Kallithea is open source, provides git and mercurial support and provides a REST-API that could be used. https://kallithea-scm.org/ http://docs.kallithea-scm.org/en/latest/api/api.html Add Comment
[JIRA] [jacoco-plugin] (JENKINS-23066) Allow cleaning up parts of Jacoco report artifcats retained
Title: Message Title
Nikolas Falco commented on JENKINS-23066
Re: Allow cleaning up parts of Jacoco report artifcats retained
Me too. In addition due actually limitation of plugin to describe which source folder should be keept, for a tycho-maven build for example, we specify something like /src//, all files in these folder (source and resources like .xml .pdf .js .html .jps .gif.) are copied to jobs/JOB1/builds/$BUILD_ID/jacoco/sources, gathering about 2.2GB for each build. I think plugins should collect only files that matches entry in .exec file and/or permit a better selector on which resources have to copy.
Actual workaround add a shell script that delete sources folder in jacoco folder for previous build.
export BUILDS_FOLDER=`dirname $WORKSPACE`/builds
for folder in `ls $BUILDS_FOLDER | grep "[0-9]\{1,\}" | grep -v $BUILD_ID`; do
echo Deleting "$BUILDS_FOLDER/$folder/jacoco/sources" ; rm -rf "$BUILDS_FOLDER/$folder/jacoco/sources" ;
done;
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] [git-plugin] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title Mark Waite commented on JENKINS-30296 Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build vincent fiset can you describe the steps you take to see this problem? 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] [git-plugin] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title vincent fiset commented on JENKINS-30296 Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build I am affected by this exact problem with Jenkins ver. 1.651.1 and Git plugin 2.4.2 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] [vmware-vrealize-orchestrator-plugin] (JENKINS-34178) There *may* be a problem with the vm@VC:VirtualMachine parameter name.
Title: Message Title Agila Govindaraju commented on JENKINS-34178 Re: There *may* be a problem with the vm@VC:VirtualMachine parameter name. Thanks for giving me enough details. I see that ORC603 is a display name of the VC:VirtualMachine type. Can you please check the same in the inventory tab of VCO and get me the screen shot of that. I can help help you out to see which Id you can use. 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] [gitlab-plugin] (JENKINS-34396) Gitlab plugin does not work with jenkins pipeline plugin
Title: Message Title Andreas Skoog created an issue Jenkins / JENKINS-34396 Gitlab plugin does not work with jenkins pipeline plugin Issue Type: Bug Assignee: Robin Müller Components: gitlab-plugin Created: 2016/Apr/22 12:34 PM Priority: Minor Reporter: Andreas Skoog It seems that the gitlab plugin does not work very well with the jenkins pipeline plugin in jenkins 2.0. If you create a new pipeline job in jenkins you are not able to trigger it from a gitlab web hook since the project has no SCM connection (the scm connection is defined in the pipeline dsl) WARNING: Error while serving http:///project/ java.lang.reflect.InvocationTargetException 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:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) ... Caused by: java.lang.IllegalArgumentException: This project does not use git: at com.dabsquared.gitlabjenkins.GitLabPushTrigger$DescriptorImpl.getSourceRepoNameDefault(GitLabPushTrigger.java:894) at com.dabsquared.gitlabjenkins.GitLabPushTrigger.createActions(GitLabPushTrigger.java:289) at com.dabsquared.gitlabjenkins.GitLabPushTrigger.onPost(GitLabPushTrigger.java:238) at com.dabsquared.gitlabjenkins.GitLabWebHook.generatePushBuild(GitLabWebHook.java:378) at com.dabsquared.gitlab
[JIRA] [google-play-android-publisher-plugin] (JENKINS-33518) Invalid JWT: Token must be a short-lived token and in a reasonable timeframe
Title: Message Title Christopher Orr commented on JENKINS-33518 Re: Invalid JWT: Token must be a short-lived token and in a reasonable timeframe Thanks for the update! I've added a troubleshooting note for this issue to this plugin's wiki page. 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] [google-play-android-publisher-plugin] (JENKINS-33518) Invalid JWT: Token must be a short-lived token and in a reasonable timeframe
Title: Message Title Dmytro Pohromskyy commented on JENKINS-33518 Re: Invalid JWT: Token must be a short-lived token and in a reasonable timeframe I can confirm that I've resolved the original problem by synchronizing Jenkins' server time. Thank you wataru oguchi for pointing out to the relevant StackOverflow thread. I'm closing the 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] [google-play-android-publisher-plugin] (JENKINS-33518) Invalid JWT: Token must be a short-lived token and in a reasonable timeframe
Title: Message Title Dmytro Pohromskyy closed an issue as Not A Defect Jenkins / JENKINS-33518 Invalid JWT: Token must be a short-lived token and in a reasonable timeframe Change By: Dmytro Pohromskyy Status: Open Closed Resolution: Not A Defect 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] [collapsing-console-sections-plugin] (JENKINS-34387) Jenkins 2.0 breaks collapse console plugin
Title: Message Title Sam Gleske commented on JENKINS-34387 Re: Jenkins 2.0 breaks collapse console plugin Errors on LTS the same way so perhaps not restricted to Jenkins 2.0 since LTS is currently <2.0. 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] [github-branch-source-plugin] (JENKINS-34395) Support for building tags
Title: Message Title George Shammas created an issue Jenkins / JENKINS-34395 Support for building tags Issue Type: Bug Assignee: Jesse Glick Components: github-branch-source-plugin Created: 2016/Apr/22 11:39 AM Priority: Minor Reporter: George Shammas Right now, using Jenkins to build releases is much harder than it should be. For every git repo I need to create two jobs. One to build branches and one to build tags. This is less than ideal, but works around the limitation that Jenkins hates git tags. This works decently on the other git plugin, but completely impossible with this plugin. I think it would be fantastic to have this plugin build tags, and communicate with github about the build data. Add Comment
[JIRA] [dynamic-axis-plugin] (JENKINS-34389) starting parallel matrix jobs with dynamic axes causes in wrong build configuration
Title: Message Title Benjamin Böhmke commented on JENKINS-34389 Re: starting parallel matrix jobs with dynamic axes causes in wrong build configuration I have a similar issue and tried to fix it. Bug origin: I found that the method "MatrixBuild.MatrixBuildExecution.doRun" is called in multiple threads without locks. If there are parallel builds of the same projects they sometimes call the "MatrixProject.rebuildConfigurations" at the same time before they can get the axis -> the build that is a bit slower overwrites the axes of the first one. Fix: I created a mutex for the MatrixProject instance and locked it before the "MatrixProject.rebuildConfigurations" is triggered and unlocked it after the axis is copied. Additional I used the fix from JENKINS-30437 for a deep copy of the axes. The full fix can be found here (based on matrix-project 1.6). 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-34394) Maven build fails with stack overflow
Title: Message Title Xenofon Papadopoulos created an issue Jenkins / JENKINS-34394 Maven build fails with stack overflow Issue Type: Bug Assignee: Unassigned Attachments: pom.xml Components: maven-plugin Created: 2016/Apr/22 11:19 AM Environment: Jenkins 1.625.3, Maven 3.3.3, Maven Integration Plugin 2.12.1, OpenJDK 1.8.0_77 Priority: Blocker Reporter: Xenofon Papadopoulos Just moved Jenkins to a new box, most projects build fine, except one which fails with the following error: 11:50:21 Parsing POMs 11:50:21 FATAL: null 11:50:21 java.lang.StackOverflowError 11:50:21 at java.lang.Exception.(Exception.java:102) 11:50:21 at java.lang.ReflectiveOperationException.(ReflectiveOperationException.java:89) 11:50:21 at java.lang.reflect.InvocationTargetException.(InvocationTargetException.java:72) 11:50:21 at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) 11:50:21 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
[JIRA] [mstestrunner-plugin] (JENKINS-34378) Would be convenient to have validation in the step configuration
Title: Message Title Armando Fernandez commented on JENKINS-34378 Re: Would be convenient to have validation in the step configuration Test Files is an expandabletextbox that does not support form validation at the moment. See JENKINS-26407. So, only validation for result files will be added. 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] [mstestrunner-plugin] (JENKINS-34378) Would be convenient to have validation in the step configuration
Title: Message Title Armando Fernandez edited a comment on JENKINS-34378 Re: Would be convenient to have validation in the step configuration Test Files is an expandabletextbox that does not support form validation at the moment. See [JENKINS-26407|https://issues.jenkins-ci.org/browse/JENKINS-26407]. So, only validation for result files file name will be added. 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] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Alex Earl commented on JENKINS-34267 Re: Email-ext doesn'r replace all tokens any more I'm just glad it is working! 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] [mail-watcher-plugin] (JENKINS-34385) Node online status cannot find node when using Pipeline job
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-34385 Node online status cannot find node when using Pipeline job Change By: Oliver Gondža Component/s: workflow-plugin 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.
