[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-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-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-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-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-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-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-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-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
[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-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-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-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-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-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
[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-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-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
[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
[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-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-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-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-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-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-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-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-43194) Optimize Jenkinsfile loading (github multibranch source)
Title: Message Title Max Gurela updated an issue Jenkins / JENKINS-43194 Optimize Jenkinsfile loading (github multibranch source) Change By: Max Gurela Summary: Optimize Jenkinsfile loading (github multibranch source) 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-43196) Trac links missing on individual Build and Job Changes page for Pipeline builds
Title: Message Title Shannon Kerr created an issue Jenkins / JENKINS-43196 Trac links missing on individual Build and Job Changes page for Pipeline builds Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2017-03-29 at 1.18.39 PM.png Components: pipeline, trac-plugin Created: 2017/Mar/29 5:20 PM Environment: Jenkins 2.32.3, Trac Plugin 1.13, Subversion Plugin 2.7.2 Priority: Minor Reporter: Shannon Kerr For non-pipeline builds, we get Trac links in the changes list on the individual build pages and on the Job's Changes page. Links work great. For pipeline builds using either Auto or explicit Trac browser, no links, just the svn details (so we get a svn revision and the list of changed files). I attached an image showing the missing links. Add Comment
[JIRA] (JENKINS-43195) non-relocated "com.github.fge.jsonschema" classes can cause issues elsewhere
Title: Message Title Andrew Bayer updated JENKINS-43195 Jenkins / JENKINS-43195 non-relocated "com.github.fge.jsonschema" classes can cause issues elsewhere Change By: Andrew Bayer Status: In Progress Review 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-43195) non-relocated "com.github.fge.jsonschema" classes can cause issues elsewhere
Title: Message Title Andrew Bayer commented on JENKINS-43195 Re: non-relocated "com.github.fge.jsonschema" classes can cause issues elsewhere Easy PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/148 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-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-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-25048) Git plugin ignores included/excluded paths when triggering build on commit nitification
Title: Message Title Mark Waite commented on JENKINS-25048 Re: Git plugin ignores included/excluded paths when triggering build on commit nitification No, the proposed pull request is still open. I'd love to have assistance evaluating pull requests. You could take the tip of the current plugin master branch, apply that proposed change to it, and then report your results to the pull request. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Jon Whitcraft edited a comment on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException For now as a workaround, i've recompiled workflow-durable-task-plugin with [this line|https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L327] commented out. IMO the logger a few lines up should produce an error instead of fine, and no not taint the job console like it is.I'd be willing to issue a PR to make this change, if [~jglick] 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-43194) Optimize Jenkinsfile loading
Title: Message Title Max Gurela created an issue Jenkins / JENKINS-43194 Optimize Jenkinsfile loading Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Mar/29 5:04 PM Labels: multibranch pipeline Priority: Minor Reporter: Max Gurela Please pull in the changes made to the SCM API to reduce the number of checkouts required for pipelines. Related to JENKINS-33273 There was a mention in the referenced issue about PRs needing special treatment: "there is no implementation currently for github-branch-source-plugin in the case of a PR job configured to merge with the base branch, as GitHub does not offer an API dedicated to this purpose. In the case that the merge can be assumed to be a fast-forward (there is no base branch change subsequent to the common ancestor), this plugin could in principle load content via API from the PR branch; it would still need to fall back to full checkout and Git merge otherwise." - https://issues.jenkins-ci.org/browse/JENKINS-33273?focusedCommentId=292273#comment-292273
[JIRA] (JENKINS-43195) non-relocated "com.github.fge.jsonschema" classes can cause issues elsewhere
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-43195 non-relocated "com.github.fge.jsonschema" classes can cause issues elsewhere Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Mar/29 5:10 PM Priority: Minor Reporter: Andrew Bayer We don't relocate "com.github.fge.jsonschema.*" but probably should - not relocating them means anyone else trying to depend on a different version of the library gets hosed, and anyone trying to depend on that version ends up with weird relocated Jackson APIs. So...we should relocate this too. Add Comment
[JIRA] (JENKINS-25048) Git plugin ignores included/excluded paths when triggering build on commit nitification
Title: Message Title Danrisha Young commented on JENKINS-25048 Re: Git plugin ignores included/excluded paths when triggering build on commit nitification Has there been any resolution for this? 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-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-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-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-35475) Multibranch pipeline displays SCM views multiple times
Title: Message Title Mark Waite commented on JENKINS-35475 Re: Multibranch pipeline displays SCM views multiple times Included in git plugin 3.2.0 released 28 mar 2017 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-43195) non-relocated "com.github.fge.jsonschema" classes can cause issues elsewhere
Title: Message Title Andrew Bayer started work on JENKINS-43195 Change By: Andrew Bayer 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-42959) Failed known_hosts verification for SSH agent
Title: Message Title Steven Loomis commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I needed this workaround from the mailing list: > ssh -o HostKeyAlgorithms=ssh-rsa slave2.example.com The implication below is that Jenkins is using weaker encryption. https://groups.google.com/d/msgid/jenkinsci-users/7006ab93-7ca4-4063-baf6-7c844be60165%40googlegroups.com 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-43198) Clean before checkout fails (jgit and gitignore with dir/subdir pattern
Title: Message Title Alexandre Feblot created an issue Jenkins / JENKINS-43198 Clean before checkout fails (jgit and gitignore with dir/subdir pattern Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2017/Mar/29 6:00 PM Priority: Critical Reporter: Alexandre Feblot The root cause of the issue is the following jgit bug, reproduced up to the lastest (4.6.1) version: https://bugs.eclipse.org/bugs/show_bug.cgi?id=514434 Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-43199) Credentials Binding plugin causes File Descriptor leak
Title: Message Title Elliott Butler commented on JENKINS-43199 Re: Credentials Binding plugin causes File Descriptor leak This may potentially cause the same issue for the pipeline variant, but is not used by us at this 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-43045) support for writing awscli profiles
Title: Message Title Thorsten Hoeger commented on JENKINS-43045 Re: support for writing awscli profiles Can you elaborate on the use case? Did you have a look at the withAWS step? 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-43198) Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-43198 Clean before checkout fails (jgit and gitignore with dir/subdir pattern) Change By: Mark Waite Assignee: Mark Waite 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-43176) MercurialChangeLogParser fails in parallel checkouts
Title: Message Title Victor Yap updated an issue Jenkins / JENKINS-43176 MercurialChangeLogParser fails in parallel checkouts Change By: Victor Yap Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43197) Deadlock when many jobs running
Title: Message Title
Hans-Juergen Hafner updated an issue
Jenkins / JENKINS-43197
Deadlock when many jobs running
Change By:
Hans-Juergen Hafner
After update of Jenkins from 2.8 to 2.48 nodes get stuck from time to time.Thread dump shows:{code:java}"Executor #0 for my_node : executing my_job #510" #266539 daemon prio=5 os_prio=0 tid=0x7f5fc1268800 nid=0x4885 waiting for monitor entry [0x7f5f471f3000] java.lang.Thread.State: BLOCKED (on object monitor) at org.codehaus.groovy.reflection.ClassInfo$GlobalClassSet.add(ClassInfo.java:477) - waiting to lock <0x7f621754d9c0> (a org.codehaus.groovy.util.ManagedLinkedList) at org.codehaus.groovy.reflection.ClassInfo$1.computeValue(ClassInfo.java:83) at org.codehaus.groovy.reflection.ClassInfo$1.computeValue(ClassInfo.java:79) at org.codehaus.groovy.reflection.GroovyClassValuePreJava7$EntryWithValue.(GroovyClassValuePreJava7.java:37) at org.codehaus.groovy.reflection.GroovyClassValuePreJava7$GroovyClassValuePreJava7Segment.createEntry(GroovyClassValuePreJava7.java:64) at org.codehaus.groovy.reflection.GroovyClassValuePreJava7$GroovyClassValuePreJava7Segment.createEntry(GroovyClassValuePreJava7.java:55) at org.codehaus.groovy.util.AbstractConcurrentMap$Segment.put(AbstractConcurrentMap.java:157) at org.codehaus.groovy.util.AbstractConcurrentMap$Segment.getOrPut(AbstractConcurrentMap.java:100) at org.codehaus.groovy.util.AbstractConcurrentMap.getOrPut(AbstractConcurrentMap.java:38) at org.codehaus.groovy.reflection.GroovyClassValuePreJava7.get(GroovyClassValuePreJava7.java:94) at org.codehaus.groovy.reflection.ClassInfo.getClassInfo(ClassInfo.java:144) at org.codehaus.groovy.runtime.metaclass.MetaClassRegistryImpl.getMetaClass(MetaClassRegistryImpl.java:258) at org.codehaus.groovy.runtime.InvokerHelper.getMetaClass(InvokerHelper.java:883) at groovy.lang.GroovyObjectSupport.(GroovyObjectSupport.java:34) at groovy.lang.Script.(Script.java:42):{code}In changelog we found that with Jenkins version 2.47 Groovy was updated to 2.4.8 "_to address memory leak issue_".Possibly this issue is related to[https://issues.apache.org/jira/browse/GROOVY-8067: |https://issues.apache.org/jira/browse/GROOVY-8067]*Possible deadlock when creating new ClassInfo entries in the cache*which is in Groovy 2.4.8 and solved in 2.4.9
[JIRA] (JENKINS-43199) Credentials Binding plugin causes File Descriptor leak
Title: Message Title
Elliott Butler created an issue
Jenkins / JENKINS-43199
Credentials Binding plugin causes File Descriptor leak
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2017/Mar/29 6:14 PM
Priority:
Minor
Reporter:
Elliott Butler
Our deployment of Jenkins with this plugin is currently on an NFS share. In testing a job with this plugin, a file descriptor was apparently left open. We found this out when attempting to delete the test job after it ran. (It was a simple echo job to make sure masking worked as expected, nothing else) The issue appears to be related to the anonymous sub-class of the LineTransformationOutputStream class returned by the Wrapper class and similar to the bug resolved in JENKINS-28409 for EnvInject. The sub-class needs to clean up it's parent outputstream and the super class on close.
@Override
public void close() throws IOException {
super.close();
out.close();
}
[JIRA] (JENKINS-41745) Remoting-free CLI
Title: Message Title Jesse Glick commented on JENKINS-41745 Re: Remoting-free CLI Tasks not tracked in core PR: offer a support-core-plugin patch check acceptance-test-harness 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-26481) Mishandling of binary methods accepting Closure
Title: Message Title Marat S commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Is there any workaround for this issue? What is the deadline for solving 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-26481) Mishandling of binary methods accepting Closure
Title: Message Title Marat S updated an issue Jenkins / JENKINS-26481 Mishandling of binary methods accepting Closure Change By: Marat S Priority: Major 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-36451) Repository Browser URL not saved in Project Pipeline Configuration
Title: Message Title Chris Russell updated an issue Jenkins / JENKINS-36451 Repository Browser URL not saved in Project Pipeline Configuration Change By: Chris Russell 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-43198) Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title Alexandre Feblot updated an issue Jenkins / JENKINS-43198 Clean before checkout fails (jgit and gitignore with dir/subdir pattern) Change By: Alexandre Feblot Summary: Clean before checkout fails (jgit and gitignore with dir/subdir pattern ) 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-42394) Error loading shared library (404 on BitBucket) during a replay of a previous build
Title: Message Title Coltrey Mather updated an issue Jenkins / JENKINS-42394 Error loading shared library (404 on BitBucket) during a replay of a previous build Change By: Coltrey Mather Component/s: bitbucket-branch-source-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-42895) Pipeline stage view is not showing the stages visually
Title: Message Title Jenny Huang commented on JENKINS-42895 Re: Pipeline stage view is not showing the stages visually Sam Van Oort Do you have trouble reproduce it? The stage view is gone completely on the server that I have. It shows up occasionally(rarely though), but most of time, it is invisible. I have more than one build items setup and I cannot see the stage view visually in any of them. But I am pretty sure it was working fine when I set it up initially. 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-42833) Cosmetic: mavenmoduleset.png not available on http site
Title: Message Title Arnaud Héritier commented on JENKINS-42833 Re: Cosmetic: mavenmoduleset.png not available on http site Effectively I need to verify. It was changed by Stephen Connolly It is broken in 2.15+ 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-43199) Credentials Binding plugin causes File Descriptor leak
Title: Message Title RAVIKUMAR t started work on JENKINS-43199 Change By: RAVIKUMAR t 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-43199) Credentials Binding plugin causes File Descriptor leak
Title: Message Title RAVIKUMAR t updated JENKINS-43199 Jenkins / JENKINS-43199 Credentials Binding plugin causes File Descriptor leak Change By: RAVIKUMAR t Status: In Progress Review 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-43197) Deadlock when many jobs running
Title: Message Title Hans-Juergen Hafner created an issue Jenkins / JENKINS-43197 Deadlock when many jobs running Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/29 5:27 PM Environment: Jenkins 2.48 xUnit plugin 1.102 JUnit Plugin 1.20 Plot Plugin 1.9 RHEL6.3, Java 1.8.0_92 Priority: Critical Reporter: Hans-Juergen Hafner Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-36451) Repository Browser URL not saved in Project Pipeline Configuration
Title: Message Title Chris Russell commented on JENKINS-36451 Re: Repository Browser URL not saved in Project Pipeline Configuration Jenkins 2.52, All plugins up to date Seeing this behavior on pipeline-from-scm jobs, but standard maven jobs save fine. In my case, GitLab is my repo browser. The config files does get updated on disk, but the configuration UI always shows "Auto" and the changelog does not link to GitLab as would be expected. 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-43198) Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title Alexandre Feblot updated an issue Jenkins / JENKINS-43198 Clean before checkout fails (jgit and gitignore with dir/subdir pattern) Change By: Alexandre Feblot The root cause of the issue is the following jgit bug, reproduced up to the lastest (4.6.1) version: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=514434] Proposed fix: https://github.com/jenkinsci/git-client-plugin/pull/238 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-43103) ClassNotFoundException org.joda.time.ReadablePartial: Jacoco plugin does not work after update from 2.1.0 to 2.2.0
Title: Message Title
miguel deanda commented on JENKINS-43103
Re: ClassNotFoundException org.joda.time.ReadablePartial: Jacoco plugin does not work after update from 2.1.0 to 2.2.0
i've confirmed that disabling these 2 options lets it work:
Change build status according the thresholds
Fail the build if coverage degrades more than the delta thresholds
i had a small project with only the following configured in the pom:
junit
junit
4.10
test
org.apache.commons
commons-lang3
3.5
log4j
log4j
1.2.17
package
org.apache.maven.plugins
maven-compiler-plugin
2.0.2
1.8
1.8
UTF-8
true
org.apache.maven.plugins
maven-surefire-plugin
2.18.1
${argLine}
${skipTests}
methods
2
${run.test.local}
test
org.jacoco
jacoco-maven-plugin
0.7.9
prepare-agent
report
prepare-package
report
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-37527) IllegalArgumentException: array element type mismatch from GroovyCallSiteSelector.parametersForVarargs calling String.join with a List
Title: Message Title Alex Varju commented on JENKINS-37527 Re: IllegalArgumentException: array element type mismatch from GroovyCallSiteSelector.parametersForVarargs calling String.join with a List Seeing the same thing here when calling a constructor that has overloads where one variant uses varargs: String paramName = "whatever" List parameters = [ new BooleanParameterValue( paramName, true ) ] CollectionadditionalSafeParameters = [ paramName ] new ParametersAction( parameters, additionalSafeParameters ) 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-43098) Bug 102421 - The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43098 Re: Bug 102421 - The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups Code changed in jenkins User: Andrew Cho Path: pom.xml src/main/java/jenkins/plugins/coverity/CIMInstance.java src/main/java/jenkins/plugins/coverity/CheckConfig.java http://jenkins-ci.org/commit/coverity-plugin/5489ec7191da66bdbdab927b021780df729f1c14 Log: Changes for 1.9.1 release [maven-release-plugin] prepare for next development iteration [FIX JENKINS-43098] If the needed permissions are not found in the directly user assigned roles, iterate through the group roles. (see e1474c4f302921a7b9837b7e9a7700e8beb0acb9) Fix trivial typos (see 360b2f9f2fa6cdecf769c3ed14599770729b2097) 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-43098) Bug 102421 - The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-43098 Bug 102421 - The check for "commitToStream" and "viewDefects" permissions fails if they are inherited from groups Change By: SCM/JIRA link daemon 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...@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 updated JENKINS-27624 Jenkins / JENKINS-27624 Upgrade minimum require Java version from 7 to 8 Change By: Baptiste Mathus Status: In Progress Review 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-43148) Developer can load and save pipelines from the editor using native git
Title: Message Title Michael Neale commented on JENKINS-43148 Re: Developer can load and save pipelines from the editor using native git Ben has been busy cooking up dank memes for the @loveskuchen twitter account, give him some slack. 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' >
[JIRA] (JENKINS-38971) Add support SAML ForceAuthn, AuthnContextClassRef, custom EntityId, and session timeout
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-38971 Change By: Ivan Fernandez Calvo 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-42405) “Could not initialize class ProcessLiveness$LibC” running sh on Windows
Title: Message Title Thorsten Meinl commented on JENKINS-42405 Re: “Could not initialize class ProcessLiveness$LibC” running sh on Windows Well, everything works perfectly with Freestyle jobs under Windows. This essentially means, executing shell (bash) scripts under Windows isn't supported with pipelines? And I guess I cannot execute shell scripts with the bat command? Using batch files isn't an option. 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-43178) Can't send email to unknown email address
Title: Message Title kendall trego stopped work on JENKINS-43178 Change By: kendall trego 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-43178) Can't send email to unknown email address
Title: Message Title kendall trego started work on JENKINS-43178 Change By: kendall trego 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-43201) BlueOcean: when browser size is smaller than pipeline, we're unable to scroll to the beginning of the pipeline
Title: Message Title Nguyen Nguyen created an issue Jenkins / JENKINS-43201 BlueOcean: when browser size is smaller than pipeline, we're unable to scroll to the beginning of the pipeline Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2017-03-29 at 1.23.10 PM.png Components: blueocean-plugin Created: 2017/Mar/29 8:23 PM Priority: Minor Reporter: Nguyen Nguyen BlueOcean: when browser size is smaller than pipeline, we're unable to scroll to the beginning of the pipeline. Chrome Steps: create a very long pipeline open Chrome, and go to the BlueOcean UI for the pipeline resize the browser to be shorter than the length of the pipeline try to scroll to the beginning of the pipeline Result: Notice we're unable to scroll to the start of the pipeline. Now we're unable to select a step and view it's results. See attached. Scroll bar is not available to scroll to the left of the page.
[JIRA] (JENKINS-42515) User education empty state updates
Title: Message Title Cliff Meyers commented on JENKINS-42515 Re: User education empty state updates Brody Maclean a few assets / design requests related to this ticket: Could you make the "double checkmark" and "failed X" assets from the top of the test results screen exportable in Zeplin? We need an updated design for the Artifacts tab. Right now if there are over 100 artifacts it displays a simple "only showing first 100 artifacts" message using the old "empty state" blue gradient. Perhaps it could look like the widget at the top of "test results" except with a different icon and a grey stripe? 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-43198) Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title
Mark Waite edited a comment on JENKINS-43198
Re: Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
I'm not able to duplicate the bug from my Jenkins interactive tests. I've created a branch in my jenkins-bugs repo to duplicate the problem and have constructed both a pipeline freestyle job and , a freestyle multi-configuration job to see if I can duplicate (Windows and Linux), and a pipeline job. None of them show the bug problem .The steps I took to try to duplicate the problem:# Clone, build, and run the docker instance{code} $ git lfs clone https://github.com/MarkEWaite/docker-lfs JENKINS-43198 $ cd JENKINS-43198 $ git lfs fetch origin origin/lts-with-plugins $ git checkout -b lts-with-plugins origin/lts-with-plugins $ docker build -t jenkins:JENKINS-43198 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-43198{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Bugs - Individual Checks" / JENKINS-43198-freestyle-jgit-clean-fails job and build itThere is also a Jenkinsfile based pipeline job trying to duplicate the same problem in the "Bugs - Pipeline Checks" folder, the jenkins-bugs directory. Unfortunately, neither of those cases show a problem cleaning files from JGit.
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
[JIRA] (JENKINS-43118) User can access the Pipeline editor without a repository
Title: Message Title James Dumay commented on JENKINS-43118 Re: User can access the Pipeline editor without a repository Brent Laster you can find a description of it on JENKINS-43116. 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-42709) Unable to build Jenkins with Java 8 set as target version
Title: Message Title Baptiste Mathus started work on JENKINS-42709 Change By: Baptiste Mathus 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-42709) Unable to build Jenkins with Java 8 set as target version
Title: Message Title Baptiste Mathus updated JENKINS-42709 Jenkins / JENKINS-42709 Unable to build Jenkins with Java 8 set as target version Change By: Baptiste Mathus Status: In Progress Review 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-42709) Unable to build Jenkins with Java 8 set as target version
Title: Message Title Baptiste Mathus stopped work on JENKINS-42709 Change By: Baptiste Mathus 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-42709) Unable to build Jenkins with Java 8 set as target version
Title: Message Title Baptiste Mathus started work on JENKINS-42709 Change By: Baptiste Mathus 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-42905) Git tag action in build results sidebar ("No tags") sliently rejects tags with spaces
Title: Message Title
Mark Waite closed an issue as Won't Fix
Git doesn't support tags with spaces, so the plugin is correct to reject them as well.
Jenkins / JENKINS-42905
Git tag action in build results sidebar ("No tags") sliently rejects tags with spaces
Change By:
Mark Waite
Status:
Open Closed
Resolution:
Won't Fix
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
[JIRA] (JENKINS-43200) withEnv does not work with kubernetes-plugin
Title: Message Title
Jon Whitcraft created an issue
Jenkins / JENKINS-43200
withEnv does not work with kubernetes-plugin
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2017/Mar/29 8:08 PM
Environment:
Jenkins 2.32.x
Priority:
Major
Reporter:
Jon Whitcraft
Inside of a container i want to define withEnv before running a shell script or something else, the environment variables are not passed in. This what i have inside of my container step
container('java') {
withEnv(['test=test']) {
sh """
export
"""
}
}
I would expect to see test=test. but it is not output.
Add Comment
[JIRA] (JENKINS-43198) Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title Mark Waite commented on JENKINS-43198 Re: Clean before checkout fails (jgit and gitignore with dir/subdir pattern) I'm not able to duplicate the bug from my Jenkins interactive tests. I've created a branch in my jenkins-bugs repo to duplicate the problem and have constructed both a pipeline job and a freestyle multi-configuration job to see if I can duplicate the bug. The steps I took to try to duplicate the problem: Clone, build, and run the docker instance $ git lfs clone https://github.com/MarkEWaite/docker-lfs JENKINS-43198 $ cd JENKINS-43198 $ git lfs fetch origin origin/lts-with-plugins $ git checkout -b lts-with-plugins origin/lts-with-plugins $ docker build -t jenkins:JENKINS-43198 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-43198 Connect a web browser to that docker instance (http://localhost:8080) Open the "Bugs - Individual Checks" / JENKINS-43198-freestyle-jgit-clean-fails job and build it There is also a Jenkinsfile based pipeline job trying to duplicate the same problem in the "Bugs - Pipeline Checks" folder, the jenkins-bugs directory. Unfortunately, neither of those cases show a problem cleaning files from JGit. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-33610) IOException with Clover 4.6 plugin
Title: Message Title Nancy Chopra commented on JENKINS-33610 Re: IOException with Clover 4.6 plugin I am facing the same issue. Could this be causing the clover xml to not be parsed? The build status is marked as green no matter what the thresh hold is. 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-43167) Erro ao usar Trigger a remote parameterized job
Title: Message Title Ricardo Gomes commented on JENKINS-43167 Re: Erro ao usar Trigger a remote parameterized job Problema resolvido. O erro ocorria porque o usuário do job chamador não tinha acesso de deploy, read e cancel no job remoto. Após os acessos serem concedidos, o erro parou de ocorrer. 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
Krzysztof Wolny edited a comment on JENKINS-36195
Re: Pipeline polling ignores special polling rules
[~jglick] I know that , and I think it should be easy to pass properties to "parent" . But that's the point of using {{git}} - simplicity. If you go this way you proposed further, we can remove {{git}} - and use {{checkout}}, right?
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 Krzysztof Wolny commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules Jesse Glick I know that. But that's the point of using git - simplicity. If you go this way you proposed further, we can remove git - and use checkout, right? 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-35453) Allow disabling the default commit status notifier
Title: Message Title Sparkle Pony commented on JENKINS-35453 Re: Allow disabling the default commit status notifier I'd also like to give a +1 that it's a bummer I can't turn these off. I'm using my own custom notification, so having these in there as well creates confusing clutter that I have to explain to my coworkers. 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-43201) BlueOcean: when browser size is smaller than pipeline, we're unable to scroll to the beginning of the pipeline
Title: Message Title Nguyen Nguyen updated an issue Jenkins / JENKINS-43201 BlueOcean: when browser size is smaller than pipeline, we're unable to scroll to the beginning of the pipeline Change By: Nguyen Nguyen Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42405) “Could not initialize class ProcessLiveness$LibC” running sh on Windows
Title: Message Title Wynand van Wyk commented on JENKINS-42405 Re: “Could not initialize class ProcessLiveness$LibC” running sh on Windows This error is present on linux nodes as well... 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-43198) Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title Alexandre Feblot commented on JENKINS-43198 Re: Clean before checkout fails (jgit and gitignore with dir/subdir pattern) Mark, I'm not sure to understand your comment. I understand your instructions 1 and 2 here lead to a getting a local jenkins running. What is doing 3 ? To reproduce this issue in jenkins, you need at least a job cloning a git repo having this line in its .gitignore /this_is/not_ok * with clean before checkout behavior and the following shell build step mkdir -p this_is/not_ok/dir1/dir2 echo hi > this_is/not_ok/dir1/dir2/hi.txt Then, run the job multiple times: run1 will succeed and generate hi.txt run2 will clean it and fail before executing the build step run3 will succeed and generate hi.txt run4 will clean it and fail before executing the build step etc... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) --
[JIRA] (JENKINS-43198) Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title
Alexandre Feblot edited a comment on JENKINS-43198
Re: Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Mark, I'm not sure to understand your comment. I understand your instructions 1 and 2 here lead to a getting a local jenkins running. What is doing 3 ?To reproduce this issue in jenkins, you need at least a job * cloning a git repo having this line in its .gitignore{ { code:java} /this_is/not_ok {code } } * with clean before checkout behavior * and the following shell build step{ { code:java} mkdir -p this_is/not_ok/dir1/dir2 }} {{ echo hi > this_is/not_ok/dir1/dir2/hi.txt {code } } Then, run the job multiple times: * run1 will succeed and generate hi.txt * run2 will clean it and fail before executing the build step * run3 will succeed and generate hi.txt * run4 will clean it and fail before executing the build step * etc...
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-43202) sendToIndividuals fails to mail culprits in declarative pipeline
Title: Message Title
Jon Dufresne created an issue
Jenkins / JENKINS-43202
sendToIndividuals fails to mail culprits in declarative pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
mailer-plugin
Created:
2017/Mar/30 12:30 AM
Environment:
Jenkins: 2.52 Mailer plugin: 1.20 Git plugin: 3.1.0
Priority:
Minor
Reporter:
Jon Dufresne
I have a declarative pipeline job. The Jenkinsfile has the following snippet: post { failure { step([$class: 'Mailer', recipients: 'c...@example.com', sendToIndividuals: true]) } } When the build fails, the addresses in the recipients string successfully receive mail. However the culprits responsible for the broken commit do not receive an individual email. As I have set the sendToIndividuals, I expect that they would. I've been unable to find any logs that might suggest a misconfiguration. I have been able to workaround this issue with the mail-ext plugin by changing the above snippet to: post { failure { step([ $class: 'Mailer', recipients: ['c...@example.com', emailextrecipients([[$class: 'CulpritsRecipientProvider'], [$class: 'RequesterRecipientProvider']])].join(' ') ]) {{ }}} } But I had hoped that this would work without introducing another plugin.
