[JIRA] (JENKINS-43177) env.WHATEVER not considered for environment variable cross reference resolution in Declarative
Title: Message Title Andrew Bayer commented on JENKINS-43177 Re: env.WHATEVER not considered for environment variable cross reference resolution in Declarative Got an approach that avoids that. woot. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43193) VM is not started if it is specified in the Cloud with ID
Title: Message Title Roman Kulikov created an issue Jenkins / JENKINS-43193 VM is not started if it is specified in the Cloud with ID Issue Type: Bug Assignee: Roman Kulikov Components: parallels-desktop-plugin Created: 2017/Mar/29 4:25 PM Priority: Minor Reporter: Roman Kulikov If one adds VM to Parallels Desktop Cloud via "name" everything flies ok. But if VM is specified with "id" (UUID enclosed in curly braces) – this VM cannot be started by the plugin. Add Comment This message was sent by
[JIRA] (JENKINS-43192) Bitbucket merge don't trigger the target branch
Title: Message Title Albert V created an issue Jenkins / JENKINS-43192 Bitbucket merge don't trigger the target branch Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2017/Mar/29 4:08 PM Environment: Jenkins 2.43 Bitbucket-branch-source-plugin 2.1.2 Labels: hook bitbucket Priority: Minor Reporter: Albert V When I merged a pull request, Bitbucket is sending a signal to Jenkins but the target branch don't launch a new build. I don't know if this plugin implementing this behavior or if something isn't working well. I want to build the target branch because it may have a different environment that is required for my workflow. Add Comment
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jon Whitcraft commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException For now as a workaround, i've recompiled workflow-durable-task-plugin with this line commented out. IMO the logger a few lines up should produce an error instead of fine, and no taint the job console like it is. I'd be willing to issue a PR to make this change, if Jesse Glick agrees. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Brent Laster commented on JENKINS-42428 Re: Jenkins master throwing java.io.IOException when running pipeline in swarm client Jesse Glick So I am getting the same error message repeatedly in the same circumstances of activity on an agent (activity to every agent actually). And this same error message is fixed by doing the same revert of the same plugin. That certainly doesn't seem like an unrelated issue. How do I use the logger to diagnose more precisely? Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Cannot contact worker_node1: java.io.IOException: Remote call on worker_node1 failed Running shell script [worker2] + /usr/share/gradle/bin/gradle -D test.single=TestExample3 test [worker2] Cannot contact worker_node2: java.io.IOException: Remote call on worker_node2 failed [worker2] Cannot contact worker_node2: java.io.IOException: Remote call on worker_node2 failed [worker2] Cannot contact worker_node2: java.io.IOException: Remote call on worker_node2 failed [worker2] Cannot contact worker_node2: java.io.IOException: Remote call on worker_node2 failed [worker2] Cannot contact worker_node2: java.io.IOException: Remote call on worker_node2 failed [worker2] Cannot contact worker_node2: java.io.IOException: Remote call on worker_node2 failed [worker2] Cannot contact worker_node2: java.io.IOException: Remote call on worker_node2 failed [worker2] Cannot contact worker_node2: java.io.IOException: Remote call on worker_node2 failed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43191) Unable to exclude "tags" directories in a nested subversion tree
Title: Message Title R. Tyler Croy assigned an issue to Unassigned This is not an issue with the Jenkins project infrastructure and therefore not an INFRA related ticket. Please file future tickets in the appropriate project, which will likely be JENKINS. Jenkins / JENKINS-43191 Unable to exclude "tags" directories in a nested subversion tree Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43191) Unable to exclude "tags" directories in a nested subversion tree
Title: Message Title R. Tyler Croy moved an issue Jenkins / JENKINS-43191 Unable to exclude "tags" directories in a nested subversion tree Change By: R. Tyler Croy Project: Infrastructure Jenkins Key: INFRA JENKINS - 1119 43191 Workflow: classic default workflow JNJira + In-Review Component/s: subversion-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You recei
[JIRA] (JENKINS-43190) Cannot access to docker step in second level closure
Title: Message Title
ludovic SMADJA created an issue
Jenkins / JENKINS-43190
Cannot access to docker step in second level closure
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2017/Mar/29 3:15 PM
Environment:
Jenkins 2.51 Docker plugin 0.16.2 Docker pipeline 1.10 Docker Commons plugin 1.6
Labels:
pipeline docker
Priority:
Minor
Reporter:
ludovic SMADJA
I'm using jenkins pipeline with global variables. The definition of my job is :
DBTest{
prepareDB = {
dbImgName="ibmcom/db2express-c:latest"
this.docker.image(dbImgName).pull()
dbContainerId = sh returnStdout:true, script:"docker run -d ${dbImgName} /init_db.sh"
return dbContainerId
}
}
and DBtest.groovy is like :
def call(body) {
// evaluate the body block, and collect configuration into the object
def config = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = config
body()
properties([buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '14', numToKeepStr: '14')), pipelineTriggers([cron('H H
[JIRA] (JENKINS-43189) [docker-fixtures] Add git executable to the JavaContainer
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-43189 [docker-fixtures] Add git executable to the JavaContainer Issue Type: New Feature Assignee: Cyrille Le Clerc Components: core Created: 2017/Mar/29 3:11 PM Priority: Minor Reporter: Cyrille Le Clerc As discussed on the mailing list Jenkins Developers › [Test Harness - Docker Fixtures] Java Git Docker Image?, the Pipeline Maven Plugin wants to write ATH tests with a Remote Agent with a JDK and the git executable. The Git Plugin and @markewaite are also interested in having git-lfs on a remote agent. Add Comment
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Jesse Glick assigned an issue to Unassigned To be clear, from the description I am assuming this is a bug not a feature. Would require someone to take time to do the analysis. Offhand I have no idea where the problem lies. Jenkins / JENKINS-36195 Pipeline polling ignores special polling rules Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Jesse Glick commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules Krzysztof Wolny the git step is only for the most simplistic use cases. Use checkout. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Change By: Jesse Glick Component/s: workflow-scm-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Jesse Glick resolved as Not A Defect As designed. Polling behavior is done in accordance with the SCMs used in the last successful build. Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Jesse Glick commented on JENKINS-42428 Re: Jenkins master throwing java.io.IOException when running pipeline in swarm client Brent Laster Even seems to happen in the very simplest test case where you have a Linux slave on the same system as a master (no swarm involved). Then you are probably seeing some unrelated issue. Use the logger to diagnose more precisely. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Jesse Glick assigned an issue to Kohsuke Kawaguchi A recent version of workflow-durable-task-step began reporting connectivity errors that had previously been suppressed unless you happened to have a FINE logger on DurableTaskStep. The error is somewhere in the Remoting layer, generally specific to the agent connection method. Jenkins / JENKINS-42428 Jenkins master throwing java.io.IOException when running pipeline in swarm client Change By: Jesse Glick Component/s: workflow-durable-task-step-plugin Labels: jenkins pipeline regression swarm Assignee: CloudBees Inc. Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-42428 Jenkins master throwing java.io.IOException when running pipeline in swarm client Change By: Jesse Glick Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42405) “Could not initialize class ProcessLiveness$LibC” running sh on Windows
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42405 “Could not initialize class ProcessLiveness$LibC” running sh on Windows Not really a regression; the problem was always there, but until recently not reported unless you happened to have enabled a FINE logger in DurableTaskStep. The problem here is that you trying to run the sh step on Windows. It is only tested on Linux. Use bat. Probably sh could be supported under some configurations, but this would require some further development to disable features which will not run in a non-POSIX system, including the process liveness check, as well as an automated test environment capable of running basic scenarios and detecting regressions. Change By: Jesse Glick Summary: Lots of remote channel errors with pipelines and “Could not initialize class ProcessLiveness$LibC” running sh on Windows slaves Component/s: durable-task-plugin Component/s: pipeline Labels: regression windows Add Comment
[JIRA] (JENKINS-39867) Message: Unauthorized from OpenShift API after some time
Title: Message Title Albert V commented on JENKINS-39867 Re: Message: Unauthorized from OpenShift API after some time Is there any update of this? It is still happening even in the latest (0.11) version. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title Julian F. assigned an issue to Julian F. Jenkins / JENKINS-40997 Add way to get locked resource name in pipeline Change By: Julian F. Assignee: Julian F. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title Julian F. started work on JENKINS-40997 Change By: Julian F. Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title Julian F. commented on JENKINS-40997 Re: Add way to get locked resource name in pipeline Hi i tried to implement this with https://github.com/jenkinsci/lockable-resources-plugin/pull/50 Maybe someone can take a look? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title Julian F. edited a comment on JENKINS-40997 Re: Add way to get locked resource name in pipeline Hi i tried to implement this with [https://github.com/jenkinsci/lockable-resources-plugin/pull/50]Maybe someone can take have a look? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43181) Unable to use the same buildWithParameter variable webhook across different repositories
Title: Message Title Kirill Merkushev updated an issue Jenkins / JENKINS-43181 Unable to use the same buildWithParameter variable webhook across different repositories Change By: Kirill Merkushev Component/s: github-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43181) Unable to use the same buildWithParameter variable webhook across different repositories
Title: Message Title Kirill Merkushev assigned an issue to huybrechts Jenkins / JENKINS-43181 Unable to use the same buildWithParameter variable webhook across different repositories Change By: Kirill Merkushev Assignee: Kirill Merkushev huybrechts Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40127) GDSL for Declarative
Title: Message Title Gijs L updated an issue Jenkins / JENKINS-40127 GDSL for Declarative Change By: Gijs L Comment: In which repo is the code for the (Intellij IDEA) GDSL? I'd want to have a look Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36570) Implement pipeline compatibility
Title: Message Title Dominic Hargreaves commented on JENKINS-36570 Re: Implement pipeline compatibility I was probably coming at this from the wrong direction. I can confirm that job groups/priority sorting works on a pipeline job as a whole and that is good enough for us at the moment. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Sukhman Sandhu commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted I get this even after upgrading to version 2.52. Restarting the master connects to windows jnlp agents for few hours and then see this error on slave home page: Restarting the windows service doesn't connect and throws "None of the protocols were accepted" error in .err file. java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:714) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1368) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at com.google.common.util.concurrent.ForwardingExecutorService.submit(ForwardingExecutorService.java:110) at jenkins.util.InterceptingExecutorService.submit(InterceptingExecutorService.java:49) at hudson.remoting.SingleLaneExecutorService.execute(SingleLaneExecutorService.java:105) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:595) Caused: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@65e5440d[name=Channel to /XX.XXX.XXX.XXX] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210) at org.jenkinsci.remoting.nio.NioChannelHub.abortAll(NioChannelHub.java:686) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:663) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-41778) Investigate effect of failures when running setup wizard
Title: Message Title Keith Zantow started work on JENKINS-41778 Change By: Keith Zantow Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43188) kubernetes-plugin: cd command in shell-skript
Title: Message Title
Sascha Vujevic created an issue
Jenkins / JENKINS-43188
kubernetes-plugin: cd command in shell-skript
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2017/Mar/29 1:44 PM
Environment:
Jenkins 2.51, Linux, kubernetes-plugin 0.11
Labels:
kubernetes-plugin
Priority:
Minor
Reporter:
Sascha Vujevic
Hello developers, we use the slave-concept with the kubernetes-plugin and have the problem, that if we have a shell-execution in our jenkinsfile
stage("Build package") {
sh "mvn -B -e -DskipTests=true package"
}
following output will be generated:
14:28:09 [slave-test-maven] Running shell script
14:28:10 Executing shell script inside container [maven] of pod [kubernetes-0dc050be67154d298f102ee26ddd426a-98614902c33e1]
14:28:10 Executing command: sh -c echo $$ > '/home/jenkins/workspace/slave-test-maven@tmp/durable-0c724a72/pid'; jsc=durable-8ba4134c5915e9a1902ba50cb9868750; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/slave-test-maven@tmp/durable-0c724a72/script.sh' > '/home/jenkins/workspace/slave-test-maven@tmp/durable-0c724a72/jenk
[JIRA] (JENKINS-35350) New 2.7 install ignores the plugins I deselect and installs everything anyway.
Title: Message Title Keith Zantow commented on JENKINS-35350 Re: New 2.7 install ignores the plugins I deselect and installs everything anyway. Oleg Nenashev Matthew Adams automatically checking + disabling dependencies is a doable thing, it already lists the dependencies for each of the plugins, though, so not really sure it's necessary. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31141) In Ukrainian locale, some text in update center is displayed in Korean
Title: Message Title Daniel Beck commented on JENKINS-31141 Re: In Ukrainian locale, some text in update center is displayed in Korean Forgot about this. WRT changelog, seemed too minor to note. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31141) In Ukrainian locale, some text in update center is displayed in Korean
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-31141 In Ukrainian locale, some text in update center is displayed in Korean Change By: Daniel Beck Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32289) RFE - Access to Plugins Manager in without Administer permission
Title: Message Title Daniel Beck resolved as Won't Do This makes absolutely no sense. If someone can upload plugins, they can give themselves Administer permission by writing and uploading give-me-admin-permission plugin. Jenkins / JENKINS-32289 RFE - Access to Plugins Manager in without Administer permission Change By: Daniel Beck Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving ema
[JIRA] (JENKINS-42131) JDL Dropdowns in wrong place on Firefox
Title: Message Title Cliff Meyers commented on JENKINS-42131 Re: JDL Dropdowns in wrong place on Firefox We had used the approach of appending to body in past apps, and it worked well, although it's certainly more DOM gymnastics than just using the position: fixed approach (which I thought was effective). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title
Elmar Weber edited a comment on JENKINS-35246
Re: Kubernetes nodes not getting deleted when a pipeline job fails
We build a simple scriptlet that we scheduled to take care of this, nothing fancy, in case anyone looks for something similar:{{for (aSlave in hudson.model.Hudson.instance.slaves) \{}}{{ if (aSlave.getComputer().isOffline()) \{}} } {{ println(aSlave.name + ' Deleted');}} } {{ aSlave.getComputer().doDoDelete();}} } {{ }}}{{ }}}From [ http://stackoverflow.com/questions/24072354/jenkins-is-there-a-way-to-remove-all-offline-nodes-slaves-batch-remove-nod ]
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title
Elmar Weber edited a comment on JENKINS-35246
Re: Kubernetes nodes not getting deleted when a pipeline job fails
We build a simple scriptlet that we scheduled to take care of this, nothing fancy, in case anyone looks for something similar: \{code} {{ for (aSlave in hudson.model.Hudson.instance.slaves) \{ }} {{ if (aSlave.getComputer().isOffline()) \{ }} {{ println(aSlave.name + ' Deleted'); }} {{ aSlave.getComputer().doDoDelete(); }} {{ } } } \ { code { } }}From http://stackoverflow.com/questions/24072354/jenkins-is-there-a-way-to-remove-all-offline-nodes-slaves-batch-remove-nod
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title
Elmar Weber commented on JENKINS-35246
Re: Kubernetes nodes not getting deleted when a pipeline job fails
We build a simple scriptlet that we scheduled to take care of this, nothing fancy, in case anyone looks for something similar: {code} for (aSlave in hudson.model.Hudson.instance.slaves) { if (aSlave.getComputer().isOffline()) { println(aSlave.name + ' Deleted'); aSlave.getComputer().doDoDelete(); } } {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41736 Re: Better descriptions for jenkins.branch.BranchEventCause Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/jenkins/branch/BranchEventCause.java src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/OrganizationFolder.java src/main/resources/jenkins/branch/BranchEventCause/description.jelly src/main/resources/jenkins/branch/BranchEventCause/description.properties http://jenkins-ci.org/commit/branch-api-plugin/a5e6362d03fdf31f6d7d7905885b38b67464a532 Log: Merge pull request #96 from stephenc/jenkins-41736 JENKINS-41736 Leverage the new event description API to expose event descriptions Compare: https://github.com/jenkinsci/branch-api-plugin/compare/e6975cda8daf...a5e6362d03fd Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41736 Re: Better descriptions for jenkins.branch.BranchEventCause Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/jenkins/branch/BranchEventCause.java src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/OrganizationFolder.java http://jenkins-ci.org/commit/branch-api-plugin/4a79b68138ee98f0f66d75fa5d80ab3948850aeb Log: JENKINS-41736 Leverage the new event description API to expose event descriptions Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41736 Re: Better descriptions for jenkins.branch.BranchEventCause Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/PullRequestGHEventSubscriber.java src/main/java/org/jenkinsci/plugins/github_branch_source/PushGHEventSubscriber.java http://jenkins-ci.org/commit/github-branch-source-plugin/fcae3b5cd07e87083c3ca3afaf0c92f564f880f5 Log: JENKINS-41736 Leverage the new event description API to expose event descriptions Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41736 Re: Better descriptions for jenkins.branch.BranchEventCause Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/MultiBranchProject.java src/main/java/jenkins/branch/OrganizationFolder.java src/main/resources/jenkins/branch/BranchEventCause/description.jelly src/main/resources/jenkins/branch/BranchEventCause/description.properties http://jenkins-ci.org/commit/branch-api-plugin/84b6a6d419b2599f553b6fa2a5a4aa7f1b034756 Log: JENKINS-41736 More places the description can be used Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41736 Re: Better descriptions for jenkins.branch.BranchEventCause Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/PullRequestGHEventSubscriber.java src/main/java/org/jenkinsci/plugins/github_branch_source/PushGHEventSubscriber.java http://jenkins-ci.org/commit/github-branch-source-plugin/7baeac0f9159c35d69391cb44d9e322680bcbdce Log: Merge pull request #129 from stephenc/jenkins-41736 JENKINS-41736 Leverage the new event description API to expose event descriptions Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/f4403aecf858...7baeac0f9159 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40834) Report primary branch
Title: Message Title Stephen Connolly resolved as Fixed git-plugin 3.2.0 Jenkins / JENKINS-40834 Report primary branch Change By: Stephen Connolly Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43187) Add a column in blue ocean dashboard view using extensions
Title: Message Title deenbandhu agrawal updated an issue Jenkins / JENKINS-43187 Add a column in blue ocean dashboard view using extensions Change By: deenbandhu agrawal Issue Type: Task New Feature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29638) Build promotion will allow running of a job a user doesn't have permission to start
Title: Message Title
olivier olivier commented on JENKINS-29638
Re: Build promotion will allow running of a job a user doesn't have permission to start
I'v got the same behaviour, permission are by-pass when using biuld("job2" ) in pipeline ( without using promotion builb) an issue is open for my case, it's very annoying because we need a strong isolation between jobs. https://issues.jenkins-ci.org/browse/JENKINS-43026
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Stephen Connolly commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Sheamus Roche this all depends on your definition of fix. In Jenkins, job names cannot contain a / ever. In 2.0.8 (and some earlier versions), we ensure that the job names never contain a / by encoding the / as %2F which fixes the job name. There are also fixed any places where we found links to jobs that were not correctly encoding links to the job (as to work correctly the URL needs to be double encoded so you get %2F -> %252F (which the browsers "helpfully" display as %2F so you might not realise that the URL has been double-encoded) Now on-disk, there are different rules that govern the on-disk filename, so we instead apply an encoding to map job names into 32-char max names with only a safe character set used and when necessary a hash of the full name is used to abbreviate the job name to ensure it fits into 32-char max. Next there are issues with workspace paths for jobs, so there is another encoding of the job workspace (I'd like to switch that to use the same mapping as for the job name, but that is a different feature) this means that the job workspace on agents will be another name that is controlled by -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=... Finally the env.BRANCH_NAME should be the unescaped un-modified name of the branch. All the above is basically functioning as intended... so the question is "what was your 'issue' and - assuming it is the workspace path length one - did you change the system property and find your issue fixed?" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43187) Add a column in blue ocean dashboard view using extensions
Title: Message Title deenbandhu agrawal created an issue Jenkins / JENKINS-43187 Add a column in blue ocean dashboard view using extensions Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/29 1:00 PM Priority: Minor Reporter: deenbandhu agrawal I want to add a new column i.e. commit_author along with commit_message and branchname in blueocean ui Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Todd Morrison commented on JENKINS-36776 Re: Support Windows Server Containers Has anyone tried installing cygwin (via chocolatey) in the Dockerfile and attempting to set the default shell as the *nix sh? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39353) Include filtering by class name when splitting tests
Title: Message Title Daniel Beland commented on JENKINS-39353 Re: Include filtering by class name when splitting tests I'd like to have the same functionality but for a different reason. I have a maven project with multiple fast unit tests run by the surefire plugin and a few longer integration tests run by the failsafe plugin. When I split my test I always en up with one split that contains only unit tests or only integration tests so effectively neither the execution of surefire or failsafe is optimal. It would be nice if I could specify test includes/excludes patterns and split the tests twice for my 2 test execution context. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Ethan Thornburg edited a comment on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Is there any other resolutions for this?-Xmx1025m in jenkins.xml didn't resolve the issue for me. Using force clean does, but my builds all take a very long time now. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Ethan Thornburg commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Is there any other resolutions for this? -Xmx1025m in jenkins.xml didn't resolve the issue for me. Using force clean does, but my builds all take a very long time now. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility
Title: Message Title Omer van Kloeten commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility Was really surprised disabling pipeline builds was not supported. +1 for resolving this issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27413) Handle file parameters
Title: Message Title Yuriy Burtsev commented on JENKINS-27413 Re: Handle file parameters "file parameter" and "stash" enough for load file to job running on different nodes. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43185) Not able to split Jenkinsfile into "sub scripts"
Title: Message Title benjamin le botland updated an issue Jenkins / JENKINS-43185 Not able to split Jenkinsfile into "sub scripts" Change By: benjamin le botland Summary: Not able to split Jenkins file Jenkinsfile into "sub scripts" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Sheamus Roche commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hi Stephen Connolly, does 2.0.8 fix handling "/" in jenkins job name or not? I've just created my first multi-branch pipeline and coming across this issue in job generated from feature/development branch for the first time... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Roch Devost commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Since I am using pipeline multi-branch jobs with GitHub, I will add a helper to our shared libraries as you suggested. Thank you very much for your help! (I still think however that there should be a way to globally override the default checkout behaviour since it is incompatible with the largest Git provider on the planet) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title
Lev Tartakovsky edited a comment on JENKINS-43038
Re: Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
I've managed to catch the exception which may shed some light at on the problem.Please review the attached pipeline_log.txt At the same time build log printed:[Pipeline] stage[Pipeline] \{ (Create GIT TAG)[Pipeline] sh10:45:26 [CISystem_generic@2] Running shell script10:45:37 Cannot contact ##: java.lang.InterruptedException10:45:47 Cannot contact ##: java.lang.InterruptedException10:45:57 Cannot contact ##: java.lang.InterruptedException10:46:07 Cannot contact ##: java.lang.InterruptedException10:46:18 Cannot contact ##: java.lang.InterruptedException10:46:28 Cannot contact ##: java.lang.InterruptedException10:46:38 Cannot contact ##: java.lang.InterruptedException10:46:48 Cannot contact ##: java.lang.InterruptedException10:46:59 Cannot contact ##: java.lang.InterruptedException10:47:09 Cannot contact ##: java.lang.InterruptedException10:47:19 Cannot contact ##: java.lang.InterruptedException10:47:29 Cannot contact ##: java.lang.InterruptedException10:47:40 Cannot contact ##: java.lang.InterruptedException10:47:50 Cannot contact ##: java.lang.InterruptedException10:48:00 Cannot contact ##: java.lang.InterruptedException10:48:10 Cannot contact ##: java.lang.InterruptedException10:48:21 Cannot contact ##: java.lang.InterruptedException10:48:31 Cannot contact ##: java.lang.InterruptedException10:48:41 Cannot contact ##: java.lang.InterruptedException10:48:51 Cannot contact ##: java.lang.InterruptedException10:49:02 Cannot contact ##: java.lang.InterruptedException10:49:12 Cannot contact ##: java.lang.InterruptedException10:49:22 Cannot contact ##: java.lang.InterruptedException10:49:32 Cannot contact ##: java.lang.InterruptedException10:49:43 Cannot contact ##: java.lang.InterruptedException10:49:53 Cannot contact ##: java.lang.InterruptedException10:50:03 Cannot contact ##: java.lang.InterruptedException10:50:13 Cannot contact ##: java.lang.InterruptedException10:50:24 Cannot contact ##: java.lang.InterruptedException10:50:34 Cannot contact ##: java.lang.InterruptedException10:50:44 Cannot contact ##: java.lang.InterruptedException10:50:54 Cannot contact ##: java.lang.InterruptedException10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a ## -m Created by Jenkins10:51:00 + git tag -a #
[JIRA] (JENKINS-39922) Upgrade Jenkins Docker Agent images to Remoting 3
Title: Message Title Oleg Nenashev updated JENKINS-39922 https://github.com/jenkinsci/docker-jnlp-slave and https://github.com/jenkinsci/docker-slave have been significantly updated. Both master and alpine branches are on Remoting 3.7 now Jenkins / JENKINS-39922 Upgrade Jenkins Docker Agent images to Remoting 3 Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop recei
[JIRA] (JENKINS-43166) Java File Class in Pipeline Script on Linux Server and Windwos Agent
Title: Message Title Marc Vollmer updated an issue Jenkins / JENKINS-43166 Java File Class in Pipeline Script on Linux Server and Windwos Agent Change By: Marc Vollmer Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Mihai Stoichitescu commented on JENKINS-42860 Re: RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Albert V This does not appear on `In-process Script Approval` unfortunately. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Mihai Stoichitescu assigned an issue to Mihai Stoichitescu Jenkins / JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Change By: Mihai Stoichitescu Assignee: Kohsuke Kawaguchi Mihai Stoichitescu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Mihai Stoichitescu assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-42860 RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Change By: Mihai Stoichitescu Assignee: Mihai Stoichitescu Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42590) code or javadoc is wrong to hide a descriptor.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42590 Re: code or javadoc is wrong to hide a descriptor. Code changed in jenkins User: ADSL Path: core/src/main/java/hudson/model/ReconfigurableDescribable.java http://jenkins-ci.org/commit/jenkins/a3ef5b6048d66e59e48455b48623e30c14be8df4 Log: JENKINS-42590 : remove text mentioning getDisplayName==null Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42590) code or javadoc is wrong to hide a descriptor.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42590 Re: code or javadoc is wrong to hide a descriptor. Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/ReconfigurableDescribable.java http://jenkins-ci.org/commit/jenkins/0ae38f553a3f04d581ff83352e65ff3432cd3da2 Log: Merge pull request #2785 from TristanFAURE/JENKINS-42590 JENKINS-42590 : remove text mentioning getDisplayName==null Compare: https://github.com/jenkinsci/jenkins/compare/a3b939849c4b...0ae38f553a3f Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Arno Moonen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 Thanks, that does work. I'll update my templates. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43186) should not use `docker inspect `
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-43186 should not use `docker inspect ` Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2017/Mar/29 9:42 AM Environment: docker pipeline relies on `docker inspect` to check for image to exist, but this can result in false positive as this command to look for containers, networks, volumes, plugins and images. Should use `docker images -q` and check for result count, or on 1.13 and later `docker image inspect `. Priority: Minor Reporter: Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43186) should not use `docker inspect `
Title: Message Title Nicolas De Loof updated an issue Jenkins / JENKINS-43186 should not use `docker inspect ` Change By: Nicolas De Loof docker pipeline relies on `docker inspect` to check for image to exist, but this can result in false positive as this command to look for containers, networks, volumes, plugins and images.Should use `docker images -q` and check for result count, or on 1.13 and later `docker image inspect `. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27624) Upgrade minimum require Java version from 7 to 8
Title: Message Title Baptiste Mathus commented on JENKINS-27624 Re: Upgrade minimum require Java version from 7 to 8 I have this PR in flight. I hope to be able to get back to it at the end of this week. But any feedback/hint there about how to solve the issue with infradna/bridge-method-injector to work with JDK8 is welcome in the meantime before I dig into it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38260) Kubernetes plugin does not respect Container Cap
Title: Message Title Tomasz Bienkowski commented on JENKINS-38260 Re: Kubernetes plugin does not respect Container Cap I don't know how the fabricat8's Kubernetes client works, but looking at the source code of "addProvisionedSlave" method here: https://github.com/jenkinsci/kubernetes-plugin/blob/kubernetes-0.10/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java I was wandering if this could be a racing condition. Perhaps fabricat8's client does not return any pod until it is actually ready (started). If so, this might explain why the Container Capacity is not respected. The sequence of events could be like this: Jenkins wants to create a slave pod. Container capacity is not exceeded. The pod is being deployed to Kubernetes (it is starting). Jenkins wants to create another pod, it asks the fabricat8's client if there are any slave pods running. fabricat8's client responds that there are no pods (because the pod from step (2) is still being deployed (it is not running yet)). Jenkins creates another pod, effectively exceeding Container Capacity setting. Is this reasonable? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed t
[JIRA] (JENKINS-43185) Not able to split Jenkins file into "sub scripts"
Title: Message Title benjamin le botland created an issue Jenkins / JENKINS-43185 Not able to split Jenkins file into "sub scripts" Issue Type: Bug Assignee: James Dumay Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2017/Mar/29 9:34 AM Priority: Critical Reporter: benjamin le botland Hi, I want to split each step from the pipeline into his own file. The Jenkinsfile will only work as a master script calling every step as a sub script (kind of an include in php). I already tried a static method in a static class but the compiler is returning me this error : "org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.io.File java.lang.String" Maybe there is another/better way to do it. Can you support me on this topic? Thanks, Benjamin. Add Comment
[JIRA] (JENKINS-43072) jenkinsci/jnlp not connecting to master
Title: Message Title Zalan Meggyesi commented on JENKINS-43072 Re: jenkinsci/jnlp not connecting to master Okay, I did the legwork on this issue. It turns out, the Kubernetes plugin is working as designed, which is good. One half of the problem lies in commit 1e9541ce, which implements passing the MAC and agent name as env vars to the container. At this point, the Jenkins agent image does not take advantage of this, so it's all good, but this will come back to haunt. The other half comes from the Jenkins agent image itself. 2017-03-16: env vars are used in the Jenkins agent image, while still passing "$@" to the jar as the last argument, but at this point, the agent name var doesn't match the one being sent by the Kubernetes plugin. The MAC does, however, so KENNETH RITHVIK's setup breaks. 2017-03-27: additional logic is implemented in the slave startup script, which correlates the var set by the Kubernetes plugin to the one used by the script. Now, the agent name is doubled up as well, leading to the behavior I saw. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Joseph Petersen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 Arno Moonen sadly who ever though it was a good idea to make sub-path as part of the filter when filter wasn't specified made it harder for themself Your Filter for Poll should be using simple wildcards. example sub-path: uncle/bob, Jenkinsfile Filter: unclue/bob/*, Jenkinsfile Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Albert V commented on JENKINS-42860 Re: RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Did you tried to go to $JENKINS_URL/scriptApproval/ and look if you have some signatures pending to approve? I had this problem and I had to update this page to add 4 different signatures. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41165) Ignore parent changes not working since v0.7.7
Title: Message Title Arno Moonen commented on JENKINS-41165 Re: Ignore parent changes not working since v0.7.7 @Joseph Petersen: I'm running 0.7.11 now and it seems that the filter is broken again. I've promoted changes to files that are within the Sub-path defined in the AccuRev SCM configuration, however, a poll does not trigger the build. I've also tried with the Filter for Poll SCM option set to the same path, but with the same result. This is my last week at the client that uses AccuRev. Hopefully I will be able to find some time and get you some additional info. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Title: Message Title Oleg Nenashev commented on JENKINS-26545 Re: Persist build(s) log(s) in MySQL (or similar) FTR there was some design work and prototyping in JENKINS-38313 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38313) External Build Log storage for Jenkins
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-38313 External Build Log storage for Jenkins Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38313) External Build Log storage for Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-38313 Re: External Build Log storage for Jenkins I am not working on these stories anymore. I have been assigned to another project in October by my company Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38313) External Build Log storage for Jenkins
Title: Message Title Oleg Nenashev stopped work on JENKINS-38313 Change By: Oleg Nenashev Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38314) External Build Log storage for Jenkins. Prototype #1
Title: Message Title Oleg Nenashev resolved as Fixed I think the first prototyping phase is done. If somebody have time and interest to proceed, see the linked issues Jenkins / JENKINS-38314 External Build Log storage for Jenkins. Prototype #1 Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegro
[JIRA] (JENKINS-38314) External Build Log storage for Jenkins. Prototype #1
Title: Message Title Oleg Nenashev stopped work on JENKINS-38314 Change By: Oleg Nenashev Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility
Title: Message Title Anna Tikhonova commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility Having Disable Build/Project feature for pipelines would be somewhat a workaround for Safe Restart, since Safe Restart is broken for many pipeline steps. It's a pain to maintain Jenkins having many lng pipelines. Keeps us away from droping Build Flow plugin completely in favour of pipeline. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26398) Fix createSlave for RestartableJenkinsRule
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-26398 Fix createSlave for RestartableJenkinsRule Change By: Oleg Nenashev Component/s: jenkins-test-harness Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Change By: Oleg Nenashev Labels: build database format jenkins logs persistence pluggable-s Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Lev Tartakovsky commented on JENKINS-43038 Re: Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins I've managed to catch the exception which may shed some light at the problem. Please review the attached pipeline_log.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-26545 Persist build(s) log(s) in MySQL (or similar) Change By: Oleg Nenashev Component/s: logging-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26883) SEVERE: Restarting VM as requested by username
Title: Message Title Oleg Nenashev commented on JENKINS-26883 Re: SEVERE: Restarting VM as requested by username No strong opinion. SEVERE is intentional to make it visible in system logs, but I admit it may confuse external monitoring systems Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Lev Tartakovsky updated an issue Jenkins / JENKINS-43038 Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins Change By: Lev Tartakovsky Attachment: pipeline_log.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27074) Build parameters and build steps lost when upgrade from Hudson 2.2.1 to Jenkins 1.599
Title: Message Title Oleg Nenashev resolved as Incomplete There is not enough details to analyze the issue. It's 2 years old w/o any response, so I suppose it is not actual anyway Jenkins / JENKINS-27074 Build parameters and build steps lost when upgrade from Hudson 2.2.1 to Jenkins 1.599 Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-43184) JSONObject["useSecurity"] is not a JSONObject
Title: Message Title Sambhaji Biradar created an issue Jenkins / JENKINS-43184 JSONObject["useSecurity"] is not a JSONObject Issue Type: Bug Assignee: Unassigned Components: security Created: 2017/Mar/29 8:52 AM Priority: Major Reporter: Sambhaji Biradar Adding an user through Global security for matrix type on Jenkins 2.32.2, gave the following error: javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["useSecurity"] is not a JSONObject. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:219) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:196) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:110) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44) at hudson.plu
[JIRA] (JENKINS-27186) Dashboard throws illegal argument Exception
Title: Message Title Oleg Nenashev assigned an issue to Evan Van Dyke Jenkins / JENKINS-27186 Dashboard throws illegal argument Exception Change By: Oleg Nenashev Assignee: Evan Van Dyke Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27186) Dashboard throws illegal argument Exception
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-27186 Dashboard throws illegal argument Exception Change By: Oleg Nenashev Component/s: dashboard-view-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27624) Upgrade minimum require Java version from 7 to 8
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-27624 Upgrade minimum require Java version from 7 to 8 Change By: Oleg Nenashev Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27624) Upgrade minimum require Java version from 7 to 8
Title: Message Title Oleg Nenashev started work on JENKINS-27624 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27624) Upgrade minimum require Java version from 7 to 8
Title: Message Title Oleg Nenashev commented on JENKINS-27624 Re: Upgrade minimum require Java version from 7 to 8 Assigned to Baptiste Mathus, who is de-facto driving this activity now Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27624) Upgrade minimum require Java version from 7 to 8
Title: Message Title Oleg Nenashev assigned an issue to Baptiste Mathus Jenkins / JENKINS-27624 Upgrade minimum require Java version from 7 to 8 Change By: Oleg Nenashev Assignee: Nicolas De Loof Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29470) NPE in AbstractProject.checkout
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-29470 NPE in AbstractProject.checkout Change By: Oleg Nenashev Labels: newbie-friendly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29869) Build Executors doesn't detect Windows 10
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-29869 Build Executors doesn't detect Windows 10 Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30617) In Jenkins 1.609.3 - after Plugins upgrading plugins got exception error
Title: Message Title Oleg Nenashev resolved as Not A Defect Closing as "Not a defect". There is no clue the issue is related to Jenkins somehow Jenkins / JENKINS-30617 In Jenkins 1.609.3 - after Plugins upgrading plugins got exception error Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googl
[JIRA] (JENKINS-30909) queue.xml only gets persisted on successful shutdown
Title: Message Title Oleg Nenashev commented on JENKINS-30909 Re: queue.xml only gets persisted on successful shutdown Queue persistence on Windows has been fixed in JENKINS-32820 (2.47, backported to 2.46.1). Not sure what else we can do in this ticket Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30923) Auto Upgrade from 1.632 to 1.633 broken
Title: Message Title Oleg Nenashev resolved as Incomplete Closing as Incomplete. Andrew didn't provide the system logs according to the request, and the version is too old to diagnose anyway. Jenkins / JENKINS-30923 Auto Upgrade from 1.632 to 1.633 broken Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsu
