[JIRA] [core] (JENKINS-34748) PluginManager::addDependencies() improperly handles plugin trees
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-34748 PluginManager::addDependencies() improperly handles plugin trees Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/12 5:48 AM Environment: jenkins-2.2 Labels: regression installation Priority: Critical Reporter: Oleg Nenashev The issue has been introduced in https://github.com/jenkinsci/jenkins/commit/036a8e94ed37cf851f0cafb9cb12c21e3496ed7c PluginManager::addDependencies() is supposed to recursively check the plugin dependency tree and to construct a list. But calls in if (dependencyURL != null) are misordered If pluginA depends on pluginB, which depends on pluginC... 1) We invoke addDependencies() for pluginB if pluginA is being loaded 2) We pass through the first iteration of the method and get into if (dependencyURL != null) 3) We add pluginB to the list and invoke addDependencies
[JIRA] [core] (JENKINS-34730) DNSIncoming dumps in to the Log
Title: Message Title Morten Rick commented on JENKINS-34730 Re: DNSIncoming dumps in to the Log It dit not help May 12, 2016 7:31:45 AM WARNING javax.jmdns.impl.DNSIncoming DNSIncoming() dump dns[response,192.168.56.74:5353, length=885, id=0x0, flags=0x8400:r:aa, answers=5 answers: [Text@705867 type: TYPE_TXT index 16, class: CLASS_IN index 1-unique, name: EPSONBE528D (XP-312 313 315 Series)._ipp._tcp.local. ttl: '4499/4500' text: ' txtvers=1 qtotal...'] [Pointer@24838765 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: _services._dns-sd._udp.local. ttl: '4499/4500' alias: '_ipp._tcp.local.'] [Pointer@1602742 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: _universal._sub._ipp._tcp.local. ttl: '4499/4500' alias: 'EPSONBE528D (XP-312 313 315 Series)._ipp._tcp.local.'] [Pointer@2305990 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: _sub._sub._ipp._tcp.local. ttl: '4499/4500' alias: 'EPSONBE528D (XP-312 313 315 Series)._ipp._tcp.local.'] [Pointer@16620180 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: _ipp._sub._ipp._tcp.local. ttl: '4499/4500' alias: 'EPSONBE528D (XP-312 313 315 Series)._ipp._tcp.local.']] answer: [Text@705867 type: TYPE_TXT index 16, class: CLASS_IN index 1-unique, name: EPSONBE528D (XP-312 313 315 Series)._ipp._tcp.local. ttl: '4499/4500' text: ' txtvers=1 qtotal...'] answer: [Pointer@24838765 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: _services._dns-sd._udp.local. ttl: '4499/4500' alias: '_ipp._tcp.local.'] answer: [Pointer@1602742 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: _universal._sub._ipp._tcp.local. ttl: '4499/4500' alias: 'EPSONBE528D (XP-312 313 315 Series)._ipp._tcp.local.'] answer: [Pointer@2305990 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: _sub._sub._ipp._tcp.local. ttl: '4499/4500' alias: 'EPSONBE528D (XP-312 313 315 Series)._ipp._tcp.local.'] answer: [Pointer@16620180 type: TYPE_PTR index 12, class: CLASS_IN index 1, name: _ipp._sub._ipp._tcp.local. ttl: '4499/4500' alias: 'EPSONBE528D (XP-312 313 315 Series)._ipp._tcp.local.'] 0: 840c 000523455053 4f4e424535323844 202858502d333132 #EPS ONBE528D .(XP-312 20: 2033313320333135 2053657269657329 045f697070045f74 6370056c6f63616c .313.315 .Series) ._ipp._t cp.local 40: 10800111 9401760974787476 6572733d31087174 6f74616c3d312672 ..v.txtv ers=1.qt otal=1 60: 703d4550534f4e42 45353238445f2858 502d3331325f3331 335f3331355f5365 p=EPSONB E528D_(X P-312_31 3_315_Se 80: 7269657329267479 3d4550534f4e4245 3532384420285850 2d33313220333133 ries) =EPSONBE 528D.(XP -312.313 a0: 2033313520536572 696573291c6e6f74 653d4c6f64616d2d 56434c58312e6c6f .315.Ser ies).not e=Lodam- VCLX1.lo c0: 64616d2e6c6f6361 6c0a7072696f7269 74793d302d70726f 647563743d284550 dam.loca l.priori ty=0-pro duct=(EP e0: 534f4e4245353238 44202858502d3331 3220333133203331 3520536572696573 SONBE528 D.(XP-31 2.313.31 5.Series 100: 29290d5472616e73 706172656e743d54 0842696e6172793d 5407436f6c6f723d )).Trans parent=T .Binary= T.Color= 120: 46084475706c6578 3d4608537461706c 653d4608436f7069 65733d5409436f6c F.Duplex =F.Stapl e=F.Copi es=T.Col 140: 6c6174653d460750 756e63683d460642 696e643d4606536f 72743d4606536361 late=F.P unch=F.B ind=F.So rt=F.Sca 160: 6e3d463270646c3d 6170706c69636174 696f6e2f7064662c 696d6167652f7572 n=F2pdl= applicat ion/pdf, image/ur 180: 662c696d6167652f 6a7065672c696d61 67652f706e670855 52463d6e6f6e650f f,image/ jpeg,ima ge/png.U RF=none. 1a0: 7072696e7465722d 73746174653d3311 7072696e7465722d 747970653d307834 printer- state=3. printer- type=0x4 1c0: 41095f7365727669 636573075f646e73 2d7364045f756470 c03a000c0001 A._servi ces._dns -sd._udp .:.. 1e0: 11940002c0300a5f 756e697665727361 6c045f737562c030 000c00011194 .0._ universa l._sub.0
[JIRA] [publish-over-ssh-plugin] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Ashudeep Budhiraja commented on JENKINS-27963 Re: Please add support for jenkins pipeline plugin to publish-over-ssh Hi Jesse, Peter, Getting - java.lang.NoSuchMethodError: No such DSL method 'sshagent' found among Thanks 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-34747) Jenkins failed to check out xcode project from GIT repo via GIT plugin
Title: Message Title Hamo Chai updated an issue Jenkins / JENKINS-34747 Jenkins failed to check out xcode project from GIT repo via GIT plugin Change By: Hamo Chai Summary: Jenkins failed to check out xcode project from GIT repo via GIT 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] [git-plugin] (JENKINS-34747) Jenkins failed to check out xcode project from GIT via GIT plugin
Title: Message Title Hamo Chai edited a comment on JENKINS-34747 Re: Jenkins failed to check out xcode project from GIT via GIT plugin Just got timeout error after 10mins from the build start , but still dont know why it cannot check out the project. 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-34747) Jenkins failed to check out xcode project from GIT via GIT plugin
Title: Message Title Hamo Chai updated an issue Jenkins / JENKINS-34747 Jenkins failed to check out xcode project from GIT via GIT plugin Just got timeout error after 10mins from the build start Change By: Hamo Chai Attachment: jen3.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] [git-plugin] (JENKINS-34747) Jenkins failed to check out xcode project from GIT via GIT plugin
Title: Message Title Hamo Chai updated an issue Jenkins / JENKINS-34747 Jenkins failed to check out xcode project from GIT via GIT plugin Change By: Hamo Chai No error and no timeout but just hanged http://scm.hactl.com is our internal web site 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-34747) Jenkins failed to check out xcode project from GIT via GIT plugin
Title: Message Title Hamo Chai updated an issue Jenkins / JENKINS-34747 Jenkins failed to check out xcode project from GIT via GIT plugin Change By: Hamo Chai Git failed to check out xcode project from GIT, no No error and no timeout but just hanged 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-34747) Jenkins failed to check out xcode project from GIT via GIT plugin
Title: Message Title Hamo Chai updated an issue Jenkins / JENKINS-34747 Jenkins failed to check out xcode project from GIT via GIT plugin Change By: Hamo Chai Summary: Git Jenkins failed to check out xcode project from GIT via GIT 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] [git-plugin] (JENKINS-34747) Git failed to check out xcode project from GIT
Title: Message Title Hamo Chai commented on JENKINS-34747 Re: Git failed to check out xcode project from GIT The project can be checked out by xcode or TortoiseGit. Just failed to check out by Jenkins Git plugin only. Any one can help? Thanks 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-26137) Mysterious serialization errors
Title: Message Title
Thomas Goeppel updated an issue
Jenkins / JENKINS-26137
Mysterious serialization errors
Change By:
Thomas Goeppel
A flow which just had{code}node('...') {sh 'echo hi'}{code}waited for a node matching the label. I restarted Jenkins after changing something so that the label would be available. The shell step ran, but then the flow failed with{code:none}...Running: Allocate node : EndRunning: End of Workflowjava.io.NotSerializableException: org.jenkinsci.plugins.workflow.job.WorkflowJob at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:890) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1062) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java: 1018 10S18 ) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:884) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:584) at org.jboss.marshalling.AbstractObjectOutput.writeObject(AbstractObjectOutput.java:58) at org.jboss.marshalling.AbstractMarshaller.writeObject(AbstractMarshaller.java:111) at org.jenkinsci.plugins.workflow.support.pickles.serialization.RiverWriter.close(RiverWriter.java:145) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:341) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:323) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:297) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:71) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:183) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.call(CpsThreadGroup.java:181) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at org.jenkinsci.plugins.workflow.cps.CpsVmThread.run(CpsVmThread.java:21)Caused by: an exception which occurred: in field task in object java.util.ArrayList@401ac88Finished: FAILURE{code}{{CpsStepContext.getThread}} then began complaining that{code:none}no thread 2 among []{code}as the {{DurableTaskStep$Execution.run}} kept on running.It is not apparent from this stack trace why something is trying to serialize the job.Observed also in PR 21; https://github.com/jenkinsci/workflow-plugin/commit/a594618516a22e9e8bcd016808ca487efee80fff fixed it. Turned out in that case that the culprit was {{ExecutorPickle}}. But why could the error message not say that? It only said {{field task}}, which was not enough information.
[JIRA] [git-plugin] (JENKINS-34747) Git failed to check out xcode project from GIT
Title: Message Title Hamo Chai created an issue Jenkins / JENKINS-34747 Git failed to check out xcode project from GIT Issue Type: Bug Assignee: Mark Waite Attachments: 螢幕快照 2016-05-12 下午12.43.52.png Components: git-plugin Created: 2016/May/12 4:48 AM Environment: xcode, jenkins v2.3 Priority: Blocker Reporter: Hamo Chai Git failed to check out xcode project from GIT, no error no timeout but just hanged Add Comment
[JIRA] [workflow-plugin] (JENKINS-25925) More polite reporting of NotSerializableException
Title: Message Title
Thomas Goeppel commented on JENKINS-25925
Re: More polite reporting of NotSerializableException
The real problem is that CPS isn't quite Groovy, and what may be perfectly valid CPS code in one scope (e.g. on the top level, or in node('master') {}) is invalid in other places (e.g. when used in a closure in a map for parallel execution).
Sometimes being polite is the wrong approach. Avoiding surprises is better.
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-34638) org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.Random
Title: Message Title Ashudeep Budhiraja commented on JENKINS-34638 Re: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.Random Hi Kieran, Can you kindly explain further on how to achieve it? Thanks. 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] [publish-over-ssh-plugin] (JENKINS-27963) Please add support for jenkins pipeline plugin to publish-over-ssh
Title: Message Title Ashudeep Budhiraja updated an issue Jenkins / JENKINS-27963 Please add support for jenkins pipeline plugin to publish-over-ssh Change By: Ashudeep Budhiraja Priority: Major Critical 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] [bitbucket-pullrequest-builder-plugin] (JENKINS-34746) Href for pull request link
Title: Message Title Daniel Gomez created an issue Jenkins / JENKINS-34746 Href for pull request link Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-05-11 at 10.52.26 PM.png Components: bitbucket-pullrequest-builder-plugin Created: 2016/May/12 4:01 AM Environment: Jenkins 2.0-rc1 Pull Request plugin 1.4.16 Labels: plugins Priority: Major Reporter: Daniel Gomez Pull requests url are bad formatted and jenkins dont show it as links in the builds history.
[JIRA] [delivery-pipeline-plugin] (JENKINS-34041) Improve Delivery Pipeline plugin stylesheets
Title: Message Title Suresh Kumar commented on JENKINS-34041 Re: Improve Delivery Pipeline plugin stylesheets Tommy Tynjä Yes, Still I kept Blue as the progress bar color. Build job showing Success color. Deploy job showing Unstable color. Test job showing Fail color. PerfTest job showing Abort color. I am working on the gradients and box-shadows of the Stage and Task panels. Info panels trying to keep as simple as possible for best readability. 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-34721) error when going to configure any project
Title: Message Title Lluis Santos commented on JENKINS-34721 Re: error when going to configure any project I resolved the error by downgrading from 2.2 to 2.1. because I had work to do, but If I can help in any thing to try to find the problem tell me, so I respond your questions: > Are you managing your plugins manually, e.g. by placing the hpi/jpi files in the plugins/ directory? I manage my plugins manually. > If Lluis Santos also has Artifactory Plugin installed, but not Ant Plugin, a similar bug could be the reason for this issue. I have the Artifactory Plugin and Ant Plugin also installed (and it cannot be uninstalled because dependencies). 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-34721) error when going to configure any project
Title: Message Title Lluis Santos updated an issue Jenkins / JENKINS-34721 error when going to configure any project Change By: Lluis Santos Attachment: Screenshot from 2016-05-12 02-12-12.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] [core] (JENKINS-34745) Check Updates PeriodicWork dies horribly in the case of invalid signature
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-34745 Check Updates PeriodicWork dies horribly in the case of invalid signature Issue Type: Bug Assignee: Oleg Nenashev Components: core Created: 2016/May/11 10:28 PM Environment: jenkins-2.2 Priority: Major Reporter: Oleg Nenashev Runtime exceptions should be handled at least Stacktrace: May 12, 2016 12:24:18 AM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException SEVERE: A thread (Download metadata thread/57) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:653) at java.util.ArrayList.get(ArrayList.java:429) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:85) at hudson.model.UpdateSite.verifySignature(UpdateSite.java:224) at hudson.model.UpdateSite.updateData(UpdateSite.java:203) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:175) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1408) at
[JIRA] [simple-parameterized-builds-report-plugin] (JENKINS-34525) StackOverflowError in Jenkins 2.0 with Simple Parameterized Builds Report
Title: Message Title
Daniel Spilker commented on JENKINS-34525
Re: StackOverflowError in Jenkins 2.0 with Simple Parameterized Builds Report
This has been reported as GROOVY-7826 and also affects Script Console, a simple script like def foo(Run r) {} will not run.
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-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title Phil Johnson edited a comment on JENKINS-28492 Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection. Hello. I'm getting a similar issue.*Server Log:*May 11, 2016 2:39:30 PM hudson.slaves.ChannelPinger$1 onDeadINFO: Ping failed. Terminating the channel build7.java.util.concurrent.TimeoutException: Ping started at 1462995330113 hasn't completed by 1462995570113Seems (although certainly not absolute) network-ish ??*Client Log:* 2016-05-11 14:39:45 - Stopping jenkinsslave-D__Jenkins2016-05-11 14:39:45 - ProcessKill 36082016-05-11 14:39:45 - Found child process: 4432 Name: conhost.exe2016-05-11 14:39:45 - Stopping process 44322016-05-11 14:39:45 - Send SIGINT 44322016-05-11 14:39:45 - SIGINT to 4432 failed - Killing as fallback2016-05-11 14:39:45 - Stopping process 36082016-05-11 14:39:45 - Send SIGINT 36082016-05-11 14:39:45 - SIGINT to 3608 failed - Killing as fallback2016-05-11 14:39:45 - Finished jenkinsslave-D__Jenkins2016-05-11 14:39:46 - Starting C:\Program Files\Java\jre7\bin\java.exe -Xrs -jar "D:\Jenkins\slave.jar" -jnlpUrl http://ci.infinitecampus.com/computer/build7/slave-agent.jnlp -secret f3e11d126c1c85e9065c7b1d1e8f60b07cac090b63828cb64532bb49da4e0d18 2016-05-11 14:39:46 - Started 2348 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-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title Jesse Glick started work on JENKINS-27421 Change By: Jesse Glick 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] [workflow-plugin] (JENKINS-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title Jesse Glick updated JENKINS-27421 Jenkins / JENKINS-27421 Unserializable iterator & entry classes from Java Collections Change By: Jesse Glick Status: Reopened Open 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-27421) Unserializable iterator & entry classes from Java Collections
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27421 Unserializable iterator & entry classes from Java Collections Change By: Jesse Glick Summary: java.util.ArrayList$Itr is not Serializable Unserializable iterator & entry classes from Java Collections 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-34744) Node environment variables case insensitive
Title: Message Title Alexander Kanevskiy created an issue Jenkins / JENKINS-34744 Node environment variables case insensitive Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/11 8:51 PM Environment: Jenkins on Linux, slave Linux hosts Priority: Major Reporter: Alexander Kanevskiy In node properties (master or slave), it's possible to define environment variables specific to that host. If for some reason user needs to define variable "A=1" and "a=2", after saving those settings, jenkins would show next time "A=2". That's not expected behaviour as environment variables should be case sensitive. Add Comment
[JIRA] [workflow-plugin] (JENKINS-27421) java.util.ArrayList$Itr is not Serializable
Title: Message Title Jesse Glick reopened an issue Best to reopen since the original fix covered only ArrayList, not other collections. Jenkins / JENKINS-27421 java.util.ArrayList$Itr is not Serializable Change By: Jesse Glick Resolution: Fixed Status: Resolved Reopened 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-34681) Allow customization of default PluginManager
Title: Message Title Andres Rodriguez updated an issue Jenkins / JENKINS-34681 Allow customization of default PluginManager Change By: Andres Rodriguez Provide a mechanism to incorporate a custom PluginManager when launching Jenkins as a webapp. The motivating use case for this change is custom wars that want to implement some kind of custom "bundling-like" functionality, in the sense of modifying the available plugins before they are loaded.Because of the point in the initialization sequence the hook must be introduced, an extension point to be implemented by a plugin is not a feasible solution. 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-34681) Allow customization of default PluginManager
Title: Message Title Andres Rodriguez updated an issue Jenkins / JENKINS-34681 Allow customization of default PluginManager Change By: Andres Rodriguez Summary: Allow customization of default PluginManager 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] [ant-plugin] (JENKINS-26056) Workflow build step for Ant
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-26056 Workflow build step for Ant Change By: Jesse Glick Assignee: Jesse Glick 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] [ant-plugin] (JENKINS-26056) Workflow build step for Ant
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-26056 Workflow build step for Ant Change By: Jesse Glick Assignee: Jesse Glick 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-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title Phil Johnson commented on JENKINS-28492 Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection. Hello. I'm getting a similar issue. Server Log: May 11, 2016 2:39:30 PM hudson.slaves.ChannelPinger$1 onDead INFO: Ping failed. Terminating the channel build7. java.util.concurrent.TimeoutException: Ping started at 1462995330113 hasn't completed by 1462995570113 Seems (although certainly not absolute) network-ish ?? Client Log: 2016-05-11 14:39:45 - Stopping jenkinsslave-D__Jenkins 2016-05-11 14:39:45 - ProcessKill 3608 2016-05-11 14:39:45 - Found child process: 4432 Name: conhost.exe 2016-05-11 14:39:45 - Stopping process 4432 2016-05-11 14:39:45 - Send SIGINT 4432 2016-05-11 14:39:45 - SIGINT to 4432 failed - Killing as fallback 2016-05-11 14:39:45 - Stopping process 3608 2016-05-11 14:39:45 - Send SIGINT 3608 2016-05-11 14:39:45 - SIGINT to 3608 failed - Killing as fallback 2016-05-11 14:39:45 - Finished jenkinsslave-D__Jenkins 2016-05-11 14:39:46 - Starting C:\Program Files\Java\jre7\bin\java.exe -Xrs -jar "D:\Jenkins\slave.jar" -jnlpUrl http://ci.infinitecampus.com/computer/build7/slave-agent.jnlp -secret f3e11d126c1c85e9065c7b1d1e8f60b07cac090b63828cb64532bb49da4e0d18 2016-05-11 14:39:46 - Started 2348 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-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title Phil Johnson edited a comment on JENKINS-28492 Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection. Hello. I'm getting a similar issue.*Server Log:*May 11, 2016 2:39:30 PM hudson.slaves.ChannelPinger$1 onDeadINFO: Ping failed. Terminating the channel build7.java.util.concurrent.TimeoutException: Ping started at 1462995330113 hasn't completed by 1462995570113Seems (although certainly not absolute) network-ish ?? * Client Log: * 2016-05-11 14:39:45 - Stopping jenkinsslave-D__Jenkins2016-05-11 14:39:45 - ProcessKill 36082016-05-11 14:39:45 - Found child process: 4432 Name: conhost.exe2016-05-11 14:39:45 - Stopping process 44322016-05-11 14:39:45 - Send SIGINT 44322016-05-11 14:39:45 - SIGINT to 4432 failed - Killing as fallback2016-05-11 14:39:45 - Stopping process 36082016-05-11 14:39:45 - Send SIGINT 36082016-05-11 14:39:45 - SIGINT to 3608 failed - Killing as fallback2016-05-11 14:39:45 - Finished jenkinsslave-D__Jenkins2016-05-11 14:39:46 - Starting C:\Program Files\Java\jre7\bin\java.exe -Xrs -jar "D:\Jenkins\slave.jar" -jnlpUrl http://ci.infinitecampus.com/computer/build7/slave-agent.jnlp -secret f3e11d126c1c85e9065c7b1d1e8f60b07cac090b63828cb64532bb49da4e0d182016-05-11 14:39:46 - Started 2348 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-34738) Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Jesse Glick resolved as Not A Defect example Jenkins / JENKINS-34738 Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM Change By: Jesse Glick Status: Open Resolved 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] [workflow-plugin] (JENKINS-34737) SCM polling is not being performed in multibranch pipeline with Mercurial SCM
Title: Message Title Jesse Glick commented on JENKINS-34737 Re: SCM polling is not being performed in multibranch pipeline with Mercurial SCM This test verifies basic changelog/polling behavior for Mercurial in Pipeline generally, but it does not look like there is such a test currently for multibranch usage. 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-34735) Problem to create multibranch pipeline with Mercurial SCM
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-34735 Problem to create multibranch pipeline with Mercurial SCM Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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] [mercurial-plugin] (JENKINS-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title Jesse Glick commented on JENKINS-28121 Re: Mercurial GeneralSCM step does not create intermediary directories. Probably suffices to have the script do something to create the directory before checkout. The existing test does not reproduce such a 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] [mercurial-plugin] (JENKINS-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-28121
Mercurial GeneralSCM step does not create intermediary directories.
Change By:
Jesse Glick
Base slave install with nothing in the home directory.Standard Freestyle project creates the full path {{$JENKINS_HOME\ \ workspace\ \ \ \ }}.Workflow project fails the scm step with {{abort: The system cannot find the path specified: $JENKINS_HOME\workspace\\}}Manually creating the {{$JENKINS_HOME\workspace}} directory fixes the issue unless the scm step specifies a sub-directory, in which case the parent of the sub-directory also has to be manually created.Workflow script was a simple:{code}node('slave-name') { checkout([$class: 'MercurialSCM', ...])}{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-28121
Mercurial GeneralSCM step does not create intermediary directories.
Change By:
Jesse Glick
Base slave install with nothing in the home directory.Standard Freestyle project creates the full path ( {{ $JENKINS_HOME\\workspace\\\\ ) }} .Workflow project fails the scm step with ' {{ abort: The system cannot find the path specified: $JENKINS_HOME\workspace\\ ' }} Manually creating the {{ $JENKINS_HOME\workspace }} directory fixes the issue unless the scm step specifies a sub-directory, in which case the parent of the sub-directory also has to be manually created.Workflow script was a simple: {code} node('slave-name') { checkout([$class: 'MercurialSCM', ...])} {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-28121) Mercurial GeneralSCM step does not create intermediary directories.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28121 Mercurial GeneralSCM step does not create intermediary directories. Change By: Jesse Glick Component/s: workflow-plugin Labels: scm workflow 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-34738) Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky updated an issue Jenkins / JENKINS-34738 Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Environment: CentOS 7 ServerJenkins 2.2 from standard Docker imagelatest versions of plugins:- pipeline and relevant plugins plugin 2.1 - pipeline multibranch plugin 2.3- Mercurial plugin 1.54 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] [delivery-pipeline-plugin] (JENKINS-34041) Improve Delivery Pipeline plugin stylesheets
Title: Message Title Tommy Tynjä commented on JENKINS-34041 Re: Improve Delivery Pipeline plugin stylesheets PR 178 merged to master. Also added another theme named contrast in PR 180 (also merged). The contrast theme is more suitable for fullscreen mode on information radiators. 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-34735) Problem to create multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky updated an issue Jenkins / JENKINS-34735 Problem to create multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Environment: CentOS 7 ServerJenkins 2.2 from standard Docker imagelatest versions of plugins:- pipeline and relevant plugins plugin 2.1 - pipeline multibranch plugin 2.3- Mercurial plugin 1.54 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-34737) SCM polling is not being performed in multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky commented on JENKINS-34737 Re: SCM polling is not being performed in multibranch pipeline with Mercurial SCM Are there any related logs? Sorry, but Jenkins just do nothing until start jobs manually. 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-34737) SCM polling is not being performed in multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky updated an issue Jenkins / JENKINS-34737 SCM polling is not being performed in multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Environment: CentOS 7 ServerJenkins 2.2 from standard Docker imagelatest versions of plugins:- pipeline and relevant plugins plugin 2.1 - pipeline multibranch plugin 2.3- Mercurial plugin 1.54 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Cannot create new items after upgrade to 2.2 when underscore is present in the hostname Change By: Roy Tinker Summary: Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin 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-34738) Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34738 Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM Change By: Oleg Nenashev Priority: Minor Major 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-34738) Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev commented on JENKINS-34738 Re: Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM Seems to be a duplicate 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-34737) SCM polling is not being performed in multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34737 SCM polling is not being performed in multibranch pipeline with Mercurial SCM Change By: Oleg Nenashev Priority: Minor Critical 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-34737) SCM polling is not being performed in multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev commented on JENKINS-34737 Re: SCM polling is not being performed in multibranch pipeline with Mercurial SCM Critical as well. Are there any related logs? Would be also great to explicitly mention versions since "latest" may change 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-34737) SCM polling don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34737 SCM polling don't performed in multibranch pipeline with Mercurial SCM Change By: Oleg Nenashev Summary: SCM pooling polling don't performed in multibranch pipeline with Mercurial SCM 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-34737) SCM polling is not being performed in multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34737 SCM polling is not being performed in multibranch pipeline with Mercurial SCM Change By: Oleg Nenashev Summary: SCM polling don't is not being performed in multibranch pipeline with Mercurial SCM 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-34735) Problem to create multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34735 Problem to create multibranch pipeline with Mercurial SCM Change By: Oleg Nenashev Priority: Minor Critical 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-34735) Problem to create multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev commented on JENKINS-34735 Re: Problem to create multibranch pipeline with Mercurial SCM Seems to be critical 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-34735) Problem to create multibranch pipeline with Mercurial SCM
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34735 Problem to create multibranch pipeline with Mercurial SCM Change By: Oleg Nenashev Summary: Broblem Problem to create multibranch pipeline with Mercurial SCM 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTP (i.e. using httpPort=80 and eliminating httpsPort=443)JENKINS-34648 doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.Note: RFC 952 restricts hostnames to letters, hyphens, and numerals. However, later I18n-oriented standards allow encoding other characters in hostnames. In practice, there are a lot of hostnames in the wild with underscores, especially in internal Windows domains (NetBIOS names are allowed to have underscores , thus modern Windows domain controllers continue to allow them and serve them via DNS without complaint ). Further reading: http://stackoverflow.com/questions/2180465/can-domain-name-subdomains-have-an-underscore-in-it
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-34738) Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky assigned an issue to Jesse Glick Jenkins / JENKINS-34738 Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Assignee: Matthew DeTullio Jesse Glick 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-34737) SCM pooling don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky assigned an issue to Jesse Glick Jenkins / JENKINS-34737 SCM pooling don't performed in multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Assignee: Matthew DeTullio Jesse Glick 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-34735) Broblem to create multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky assigned an issue to Jesse Glick Jenkins / JENKINS-34735 Broblem to create multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Assignee: Matthew DeTullio Jesse Glick 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-34737) SCM pooling don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky updated an issue Jenkins / JENKINS-34737 SCM pooling don't performed in multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Component/s: workflow-plugin Component/s: multi-branch-project-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] [workflow-plugin] (JENKINS-34735) Broblem to create multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky updated an issue Jenkins / JENKINS-34735 Broblem to create multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Component/s: workflow-plugin Component/s: multi-branch-project-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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTP (i.e. using httpPort=80 and eliminating httpsPort=443)JENKINS-34648 doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.Note: RFC 952 restricts hostnames to letters, hyphens, and numerals. However, later I18n-oriented standards allow encoding other characters in hostnames. In practice, there are a lot of hostnames in the wild with underscores, especially in internal Windows domains (NetBIOS names are allowed to have underscores, thus modern Windows domain servers controllers continue to allow them and serve them via DNS without complaint). Further reading: http://stackoverflow.com/questions/2180465/can-domain-name-subdomains-have-an-underscore-in-it
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-34738) Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM
Title: Message Title Victor Verbitsky updated an issue Jenkins / JENKINS-34738 Discarding of the old builds don't performed in multibranch pipeline with Mercurial SCM Change By: Victor Verbitsky Component/s: workflow-plugin Component/s: multi-branch-project-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] [checkmarx-plugin] (JENKINS-33607) getServerLicenseData: no corresponding wsdl operation
Title: Message Title Igor Matlin commented on JENKINS-33607 Re: getServerLicenseData: no corresponding wsdl operation Downgrade to Checkmarx plugin v8.0.1 (previous version). It is available from Checkmarx download site: https://www.checkmarx.com/plugins/. 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTP (i.e. using httpPort=80 and eliminating httpsPort=443)JENKINS-34648 doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.Note: RFC 952 restricts hostnames to letters, hyphens, and numerals. However, later I18n-oriented standards allow encoding other characters in hostnames. In practice, there are a lot of hostnames in the wild with underscores , especially Windows servers in Windows domains (NetBIOS names are allowed to have underscores, thus modern Windows domain servers continue to allow them and serve them via DNS without complaint) . Further reading: http://stackoverflow.com/questions/2180465/can-domain-name-subdomains-have-an-underscore-in-it
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTP (i.e. using httpPort=80 and eliminating httpsPort=443)JENKINS-34648 doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.Note: RFC 952 restricts hostnames to letters, hyphens, and numerals. However, later I18n-oriented standards allow encoding other characters in hostnames. In practice, there are a lot of hostnames in the wild with underscores, especially Windows servers in internal Windows domains (NetBIOS names are allowed to have underscores, thus modern Windows domain servers continue to allow them and serve them via DNS without complaint). Further reading: http://stackoverflow.com/questions/2180465/can-domain-name-subdomains-have-an-underscore-in-it
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [github-branch-source-plugin] (JENKINS-34727) WebHook events are not always successfully triggering Jenkins pipeline
Title: Message Title Antonio Muñiz commented on JENKINS-34727 Re: WebHook events are not always successfully triggering Jenkins pipeline Root cause found. GitHub is not reliably returning the right commit SHA through the API if you request that information just after the push is done. It seems to be some kind of cache at Github side delaying the information to be available in the API. As github-branch-source is using the API to retrieve the last commit in a branch just after the webhook is received, that commit is not visible (sometimes, depending on timing) thus not built. Worth to note that this behavior is only reproducible when pushing commits by HTTPS to Github. It seems that pushing by SSH is triggering the webhooks after the commit is available in the API (which seems the right behavior). 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTP (i.e. using httpPort=80 and eliminating httpsPort=443)JENKINS-34648 doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.Note: RFC 952 restricts hostnames to letters, hyphens, and numerals. However, later I18n-oriented standards allow encoding other characters in hostnames. In practice, there are a lot of hostnames in the wild with underscores. Further reading: http://stackoverflow.com/questions/2180465/can-domain-name-subdomains-have-an-underscore-in-it
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTP (i.e. using httpPort=80 and eliminating httpsPort=443)JENKINS-34648 doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list. Note: RFC 952 restricts hostnames to letters, hyphens, and numerals. However, later standards allow encoding other characters in hostnames. In practice, there are a lot of hostnames in the wild with underscores. Further reading: http://stackoverflow.com/questions/2180465/can-domain-name-subdomains-have-an-underscore-in-it
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTP (i.e. using httpPort=80 and eliminating httpsPort=443) I'm aware of https://issues.jenkins-ci.org/browse/ JENKINS-34648 , and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list. RFC 952 restricts hostnames to letters, hyphens, and numerals. However, later standards allow encoding other characters in hostnames. In practice, there are a lot of hostnames in the wild with underscores. Further reading: http://stackoverflow.com/questions/2180465/can-domain-name-subdomains-have-an-underscore-in-it
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [maven-plugin] (JENKINS-34743) 2.2 Maven Installations - System Configuration Missing
Title: Message Title Sylvester Jakubowski commented on JENKINS-34743 Re: 2.2 Maven Installations - System Configuration Missing I was able to workaround this issue by copying hudson.tasks.Maven.xml From my old jenkins, But it still doesn't show up in the Manage Jenkins ui. It DOES show those options in the job now. 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin Change By: Roy Tinker Labels: 2.0 https security url 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared.Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTP (i.e. using httpPort=80 and eliminating httpsPort=443) I'm aware of https://issues.jenkins-ci.org/browse/JENKINS-34648, and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.
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
[JIRA] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title Harry Soehalim commented on JENKINS-29652 Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin I'm running ver 1.19 and still seeing this issue - fyi. 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] [join-plugin] (JENKINS-28979) Trigger if a failed dependency is retried and succeeds
Title: Message Title Harry Soehalim commented on JENKINS-28979 Re: Trigger if a failed dependency is retried and succeeds I'm running ver 1.19 and still seeing this issue. Could we prioritize the fix for this problem, plz? 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-34743) 2.2 Maven Installations - System Configuration Missing
Title: Message Title Sylvester Jakubowski created an issue Jenkins / JENKINS-34743 2.2 Maven Installations - System Configuration Missing Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/May/11 6:51 PM Priority: Minor Reporter: Sylvester Jakubowski Create a new Jenkins 2.2 install. Add a Maven project. Jenkins job prompts: " Maven Version Jenkins needs to know where your Maven is installed. Please do so from the system configuration." Which is expected. Navigate to Manage Jenkins. No "Maven" section present to add installation. Section is present in Jenkins 1.6 "Maven Project Configuration" is present but that is not the "Maven" section that allows installers. Add Comment
[JIRA] [delivery-pipeline-plugin] (JENKINS-34041) Improve Delivery Pipeline plugin stylesheets
Title: Message Title Tommy Tynjä commented on JENKINS-34041 Re: Improve Delivery Pipeline plugin stylesheets I'm looking in to the PR now. Will add any feedback directly in GitHub. Regarding the bootstrap theme; what's dictating the colors in deploy and perftest? I assume Build (green) means success and Test (red) means fail. Is build in progress still blinking blue? 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-33689) com.google.api.client.googleapis.json.GoogleJsonResponseException: 500 Internal Server Error
Title: Message Title Christopher Orr commented on JENKINS-33689 Re: com.google.api.client.googleapis.json.GoogleJsonResponseException: 500 Internal Server Error Skjalg Mæhre: Thanks for the update! That sucks that it's consistently broken for you, but in that case I would definitely encourage you to get in touch with Google Play Developer Support — if it's always broken for certain APKs, then they should really fix their API… https://support.google.com/googleplay/android-developer/contact/publishing?extra.IssueType=submitting=en=publish=publish_cf=escalationflow.email=3=1 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] [delivery-pipeline-plugin] (JENKINS-34041) Improve Delivery Pipeline plugin stylesheets
Title: Message Title Tommy Tynjä assigned an issue to Suresh Kumar Jenkins / JENKINS-34041 Improve Delivery Pipeline plugin stylesheets Change By: Tommy Tynjä Assignee: Patrik Boström Suresh Kumar 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared. The Jenkins URL is set correctly (scheme is https, hostname is the server's FQDN). Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Using a hostname without an underscore, Changes that do not fix the problem:- Switching to HTTPI'm aware of https://issues.jenkins-ci.org/browse/JENKINS-34648, and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.
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"
[JIRA] [script-security-plugin] (JENKINS-34741) Unclassified error when using Groovy struct constructors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34741 Re: Unclassified error when using Groovy struct constructors Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/fc8324a204edf7c2484118100ae43a65eb7a5306 Log: JENKINS-34741 Noting issue number. 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Cannot create new items after upgrade to 2.2 when underscore is present in the hostname suborigin Change By: Roy Tinker Summary: Cannot create new items after upgrade to 2.2 when underscore is present in the server's FQDN hostname suborigin 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the server's FQDN
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when underscore is present in the server's FQDN
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared. I'm running Jenkins using HTTPS (directly, not through a reverse proxy). The Jenkins URL is set correctly (scheme is https, hostname is the server's FQDN).Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Accessing Jenkins via Using a hostname without an underscore, Changes that do not fix the server's IP address (i.e. `https problem : //1.2.3.4/view/All/newJob`) - Switching to HTTP I'm aware of https://issues.jenkins-ci.org/browse/JENKINS-34648, and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [script-security-plugin] (JENKINS-34741) Unclassified error when using Groovy struct constructors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34741 Re: Unclassified error when using Groovy struct constructors Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/ac5d5bf06fb15122437d43d69f5199266897ab64 Log: Merge pull request #67 from jglick/structConstructor JENKINS-34741 Reproduced problem in test Compare: https://github.com/jenkinsci/script-security-plugin/compare/32d766ac9dcb...ac5d5bf06fb1 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-34740) Cannot create new items after upgrade to 2.2 when underscore is present in the server's FQDN
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Cannot create new items after upgrade to 2.2 when underscore is present in the server's FQDN Change By: Roy Tinker Summary: Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN 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-34742) FilePath#installIfNecessaryFrom consistently fails to download certain files
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-34742 FilePath#installIfNecessaryFrom consistently fails to download certain files Issue Type: Bug Assignee: Oleg Nenashev Components: core Created: 2016/May/11 6:13 PM Environment: Jenkins 1.532 and 2.0; running on OS X 10.11.4 and Ubuntu 14.04.3 Priority: Major Reporter: Christopher Orr When testing the Go Plugin, which is a ToolInstaller and so makes use of this FilePath API, I've seen that it consistently fails to download certain files — regardless of which OS Jenkins is running on, and from which web server the files are being downloaded from (and whether HTTP or HTTPS). An typical stacktrace: java.io.IOException: Failed to install https://storage.googleapis.com/golang/go1.6.2.darwin-amd64.tar.gz to /tmp/jenkins/tools/Go_1.6.2 at hudson.FilePath.installIfNecessaryFrom(FilePath.java:832) at Repro.main(Repro.java:31) Caused by: java.io.IOException: Failed to unpack https://storage.googleapis.com/golang/go1.6.2.darwin-amd64.tar.gz (158817 bytes read of total 84750242) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:826) ... 1 more Caused by: java.io.IOException: Failed to extract
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared. I'm running Jenkins using HTTPS (directly, not through a reverse proxy). The Jenkins URL is set correctly (scheme is https, hostname is the server's FQDN).Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} (so it's not equal to the true suborigin) -- which may be the trigger that is causing the problem.Changes that fix the problem:- Reverting to Jenkins 1.6- Accessing Jenkins via the server's IP address (i.e. `https://1.2.3.4/view/All/newJob`)I'm aware of https://issues.jenkins-ci.org/browse/JENKINS-34648, and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared. I'm running Jenkins using HTTPS (directly, not through a reverse proxy). The Jenkins URL is set correctly (scheme is https, hostname is the server's FQDN).Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} -- which may be the trigger that is causing the problem. Changes that fix the problem:- Reverting to Jenkins 1.6 fixes - Accessing Jenkins via the problem server's IP address (i . e. `https://1.2.3.4/view/All/newJob`) I'm aware of https://issues.jenkins-ci.org/browse/JENKINS-34648, and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN Change By: Roy Tinker Attachment: screenshot275126.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] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Title: Message Title Roy Tinker updated an issue Jenkins / JENKINS-34740 Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN Change By: Roy Tinker Attachment: screenshot275126.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] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared. I'm running Jenkins using HTTPS (directly, not through a reverse proxy). The Jenkins URL is set correctly (scheme is https, hostname is the server's FQDN).Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows: !screenshot275126.png|thumbnail! Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} -- which may be the trigger that is causing the problem.Reverting to Jenkins 1.6 fixes the problem.I'm aware of https://issues.jenkins-ci.org/browse/JENKINS-34648, and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.
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
[JIRA] [script-security-plugin] (JENKINS-34741) Unclassified error when using Groovy struct constructors
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-34741 Unclassified error when using Groovy struct constructors Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin Created: 2016/May/11 6:02 PM Priority: Major Reporter: Jesse Glick new Class(field: value) syntax does not work from the sandbox. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeared. I'm running Jenkins using HTTPS (directly, not through a reverse proxy). The Jenkins URL is set correctly (scheme is https, hostname is the server's FQDN).Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows: !screenshot275126.png|thumbnail! Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} -- which may be the trigger that is causing the problem.Reverting to Jenkins 1.6 fixes the problem.I'm aware of https://issues.jenkins-ci.org/browse/JENKINS-34648, and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.
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
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Title: Message Title
Roy Tinker updated an issue
Jenkins / JENKINS-34740
Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Change By:
Roy Tinker
I just upgraded to 2.2 from 1.6, and this issue appeard appeared . I'm running Jenkins using HTTPS (directly, not through a reverse proxy). The Jenkins URL is set correctly (scheme is https, hostname is the server's FQDN).Navigating to {{https://servername_vm.example.com/view/All/newJob}} results in a blank page. No items show up.!screenshot275124.png|thumbnail!In the console, I see:!screenshot275125.png|thumbnail!Navigating to the Network tab of the devtools, the headers associated with the failed XHR are as follows:!screenshot275126.png|thumbnail!Note that I'm _not_ authenticated as anonymous (even though the X-You-Are-Authenticated-As header says so) -- see the first screenshot. Also of interest is the "Suborigin" request header. It's equal to the part of the server's name _before_ {{_vm}} -- which may be the trigger that is causing the problem.Reverting to Jenkins 1.6 fixes the problem.I'm aware of https://issues.jenkins-ci.org/browse/JENKINS-34648, and that doesn't describe the issue I'm having. I suspect my issue may be another problem caused by the same commit - that's why I named the external-monitor-job-plugin in the components list.
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
[JIRA] [core] (JENKINS-34740) Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN
Title: Message Title Roy Tinker created an issue Jenkins / JENKINS-34740 Cannot create new items after upgrade to 2.2 when hosted via HTTPS and an underscore is present in the server's FQDN Issue Type: Bug Assignee: Unassigned Attachments: screenshot275124.png, screenshot275125.png, screenshot275126.png Components: core, external-monitor-job-plugin Created: 2016/May/11 6:01 PM Environment: - Jenkins 2.2 - Server OS: Windows 7 Enterprise (64-bit) - Plugins: ace-editor 1.1, active-directory 1.45, ant 1.2, antisamy-markup-formatter 1.3, any-buildstep 0.1, branch-api 1.7, build-pipeline-plugin 1.5.2, buildresult-trigger 0.17, cloudbees-folder 5.9, conditional-buildstep 1.3.3, credentials 1.28, credentials-binding 1.7, cvs 2.12, dashboard-view 2.9.7, durable-task 1.9, extended-choice-parameter 0.72, external-monitor-job 1.4, fstrigger 0.39, flexible-publish 0.15.2, handlebars 1.1.1, git 2.4.4, git-client 1.19.6, git-server 1.6, github 1.19.0, github-api 1.75, github-branch-source 1.6, github-organization-folder 1.3, icon-shim 2.0.3, javadoc 1.3, job-restrictions 0.4, jquery 1.11.2-0, jquery-detached 1.2.1, junit 1.13, ldap 1.12, mailer 1.17, mapdb-api 1.0.6.0, matrix-auth 1.3.2, matrix-project 1.6, maven-plugin 1.12.1, multi-slave-config-plugin 1.2.0, nodelabelparameter 1.7.2, momentjs 1.1.1, pam-auth 1.2, parameterized-trigger 2.30, pipeline-build-step 2.0, pipeline-input-step 2.0, pipeline-stage-view 1.3, pipeline-stage-step 2.1, plain-credentials 1.1, powershell 1.3, run-condition 1.0, scm-api 1.2, scm-sync-configuration 0.0.9, script-security 1.19, ssh-credentials 1.11, ssh 2.4, ssh-slaves 1.11, structs 1.1, subversion 2.5.7, token-macro 1.12.1, translation 1.14, windows-exe-runner 1.2, windows-slaves 1.1, workflow-aggregator 2.1, workflow-api 2.0, workflow-basic-steps 2.0, workflow-cps 2.2, workflow-job 2.1, workflow-multibranch 2.3, workflow-durable-task-step 2.0, workflow-scm-step 2.0, workflow-cps-global-lib 2.0, workflow-step-api 2.0,
[JIRA] [github-organization-folder-plugin] (JENKINS-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine
Title: Message Title Alex Hunt updated an issue Jenkins / JENKINS-34563 Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine Change By: Alex Hunt Comment: This seems to also be the case for Jenkins 2.2 with GitHub Organization Folder Plugin 1.3, and Pipeline 2.1The webhooks fire and are received by Jenkins, but do not create new jobs for new branches or repositories, nor does it create jobs for branches that existed previously without a Jenkinsfile but now have a Jenkinsfile. 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-organization-folder-plugin] (JENKINS-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine
Title: Message Title Alex Hunt commented on JENKINS-34563 Re: Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine This seems to also be the case for Jenkins 2.2 with GitHub Organization Folder Plugin 1.3, and Pipeline 2.1 The webhooks fire and are received by Jenkins, but do not create new jobs for new branches or repositories, nor does it create jobs for branches that existed previously without a Jenkinsfile but now have a Jenkinsfile. 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-32273) Refactor and unify issue handling in CLI commands
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32273 Re: Refactor and unify issue handling in CLI commands Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/cli/GetNodeCommandTest.java test/src/test/java/hudson/cli/UpdateNodeCommandTest.java http://jenkins-ci.org/commit/jenkins/9f3f352ee989c861e5304dc0ac4e7b06f7fd1403 Log: JENKINS-32273 CLI exit codes changed as of #1997 in 1.649. 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-26775) Items reported twice via ItemGroup /api on JDK 8 (and JDK 7u80+)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26775 Re: Items reported twice via ItemGroup /api on JDK 8 (and JDK 7u80+) Code changed in jenkins User: Jesse Glick Path: test/src/test/java/hudson/model/ApiTest.java http://jenkins-ci.org/commit/jenkins/e4b97c5918c06e0a40bbdbc13b1a86fa3f69ada9 Log: JENKINS-26775 Suppress ApiTest.wrappedMultipleItems prior to 1.651 where it is fixed for JDK 8. 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] [script-security-plugin] (JENKINS-34739) Varargs not supported
Title: Message Title Jesse Glick started work on JENKINS-34739 Change By: Jesse Glick 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.
