[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title GMC Software Development B Corporate commented on JENKINS-60153 Re: NullPointerException in Build failure analyzer Same failure with build-failure-analyzer 1.24.1 and Jenkins LTS version 2.190.3 on Windows Server 2019. org.apache.commons.jelly.JellyTagException: jar:file:/C:/webserver/Jenkins/war/WEB-INF/lib/jenkins-core-2.190.3.jar!/hudson/model/AbstractBuild/index.jelly:110:84: java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) ... and much more (see comment above). IMHO, I've raised the severity from minor to major. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203018.1573630888000.9230.1575010620237%40Atlassian.JIRA.
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title GMC Software Development B Corporate updated an issue Jenkins / JENKINS-60153 NullPointerException in Build failure analyzer Change By: GMC Software Development B Corporate Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203018.1573630888000.9227.1575010560272%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Bruno P. Kinoshita commented on JENKINS-60319 Re: Reactive Parameter ignores toString Oh, interesting problem. Thanks for reporting. I'll need to debug to understand what's going on. Might have time this coming Sunday (NZ time). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203316.1574954163000.9205.1574989500397%40Atlassian.JIRA.
[JIRA] (JENKINS-60326) Remove unused dependencies
Title: Message Title César Soto Valero created an issue Jenkins / JENKINS-60326 Remove unused dependencies Issue Type: Improvement Assignee: Unassigned Components: cli, core Created: 2019-11-28 23:57 Priority: Minor Reporter: César Soto Valero Hello, I noticed that the dependency org.jvnet.hudson:jtidy is declared in module core. However, this direct dependency is not used and, therefore, it can be removed safely from this module. I'm intriguing with the exclusion of jdom from org.jvnet.hudson:jtidy in commit https://github.com/jenkinsci/jenkins/commit/fe8df9651a276720f6d9a93ea4fb7d9e3e5a45dc , if we look at the dependency tree, we can notice that jdom is not a dependency of org.jvnet.hudson:jtidy. On the other hand, the transitive dependencies org.jenkins-ci:constant-pool-scanner and net.i2p.crypto:eddsa are not used in core and therefore they can be excluded from org.jenkins-ci.main:remoting and org.jenkins-ci.main:cli, respectively. This makes the core library slimmer, the dependency tree smaller, and the pom clearer. In addition, the dependency commons-codec is declared in module cli and it is also unused. Add Comment
[JIRA] (JENKINS-60325) Remove unused dependencies
Title: Message Title César Soto Valero created an issue Jenkins / JENKINS-60325 Remove unused dependencies Issue Type: Improvement Assignee: Unassigned Components: cli, core Created: 2019-11-28 23:56 Priority: Minor Reporter: César Soto Valero Hello, I noticed that the dependency org.jvnet.hudson:jtidy is declared in module core. However, this direct dependency is not used and, therefore, it can be removed safely from this module. I'm intriguing with the exclusion of jdom from org.jvnet.hudson:jtidy in commit https://github.com/jenkinsci/jenkins/commit/fe8df9651a276720f6d9a93ea4fb7d9e3e5a45dc , if we look at the dependency tree, we can notice that jdom is not a dependency of org.jvnet.hudson:jtidy. On the other hand, the transitive dependencies org.jenkins-ci:constant-pool-scanner and net.i2p.crypto:eddsa are not used in core and therefore they can be excluded from org.jenkins-ci.main:remoting and org.jenkins-ci.main:cli, respectively. This makes the core library slimmer, the dependency tree smaller, and the pom clearer. In addition, the dependency commons-codec is declared in module cli and it is also unused. Add Comment
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Ken Rachynski commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing Oh good catch. I have jglick as one of my users and I recall that's because I built his sample pipeline job from github directly. The unknown user in my case is one of our current staff members, but it's likely that record was added before I switched to Active Directory as my source. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.9188.1574981520482%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Peter Lieverdink commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing Ken Rachynski Yep, confirmed. I checked the users.xml file and also found an "unknown" entry in there pointing at an old format token in users/foo/config.xml. I've deleted said user, in theory that'll mean the warning doesn't come back after a restart. I am pretty sure that entry in list of users is courtesy of GitHub integration; Jenkins tries to enumerate people its finds in git commits, whether they have actual Jenkins logins or not. The "unknown" user in question has an email address that does match a former staff member, but it's not one that we ever used in LDAP. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.9172.1574981220631%40Atlassian.JIRA.
[JIRA] (JENKINS-60313) Confusing error message when MySQL API plugin isn't installed
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-60313 Confusing error message when MySQL API plugin isn't installed Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203309.1574933501000.9148.1574976060186%40Atlassian.JIRA.
[JIRA] (JENKINS-60324) nested Parallel in declarative results in temporary misrendering
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-60324
nested Parallel in declarative results in temporary misrendering
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
image-2019-11-28-15-13-12-961.png, image-2019-11-28-15-13-20-794.png, image-2019-11-28-15-13-25-702.png
Components:
blueocean-plugin, pipeline
Created:
2019-11-28 21:10
Priority:
Minor
Reporter:
Josh Soref
We're using a declarative pipeline that happens to use
def {}
// and
script {}
// and
parallel objects
def projectName(projectPrefix, flavor) {
return "${projectPrefix} ${flavor}"
}
def templateProjectNode (project, flavor, publish) {
return {
node {
stage(projectName(project, flavor)) {
try {
sh "hostname"
script {
sh label: "Compile + Test + Publish", script: "hostname"
}
}
finally {
junit "*/target/test-reports/**/*.xml"
archiveArtifacts "*/target/test-reports/**"
archiveArtifacts "*/target/*/*report/**"
}
}
}
}
}
def generateProjects (projectList) {
def projects = projectList.collectEntries {
[(projectName(it[0],
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Ken Rachynski commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing As near as I can tell right now, the Revoke selected token(s) button calls this method: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor.java#L159-L185 But none of the logging present there seems to be hitting my Jenkins logs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.9132.1574969820388%40Atlassian.JIRA.
[JIRA] (JENKINS-60323) Jenkins build never finishes even after console shows BUILD SUCCEEDED
Title: Message Title Julius Wiatowski created an issue Jenkins / JENKINS-60323 Jenkins build never finishes even after console shows BUILD SUCCEEDED Issue Type: Bug Assignee: Unassigned Attachments: Jenkins Dump.txt, Jenkins screenshot.bmp Components: core Created: 2019-11-28 19:04 Environment: Windows Server 2016 Priority: Major Reporter: Julius Wiatowski In the console the build shows as completed successfully however the build never stops unless I cancel it by clicking the 'x' on the project page. I have left the build running overnight to see if it would finish by the next day but it is still stuck the next day. I am using the most recent version of jenkins and installed it on Windows 2016 server using the the Jenkins windows installer. Add Comment
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title
Ken Rachynski edited a comment on JENKINS-53266
Re: Legacy token for user "unknown" keeps reappearing
Since I suspect this is due to a plugin upgrade at some point, I decided to do some digging. It looks like revoking legacy tokens for some users isn't actually revoking them. I have one unknown user on my system that shows up every time I restart Jenkins. I've been revoking the token each time it comes up without luck.Logging into my Jenkins host computer, I looked in the users folder for my unknown user. users.xml told me what directory it was in and the config.xml confirmed the legacy token.{{ }} {{ tokenhash }} {{ }}The new format looks more like{{ }} {{ }} {{ }} {{ }} {{ uuid }} {{ mytoken }} {{ 2019-11-28 18:37:11.655 UTC }} {{ }} {{ 11 }} {{ tokenhash }} {{ }} {{ }} {{ }} {{ }} {{ }}Since I was looking to revoke the token outright, I just deleted the {{}} line in config.xml and restarted Jenkins.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.9111.1574967120583%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title
Ken Rachynski commented on JENKINS-53266
Re: Legacy token for user "unknown" keeps reappearing
Since I suspect this is due to a plugin upgrade at some point, I decided to do some digging. It looks like revoking legacy tokens for some users isn't actually revoking them. I have one unknown user on my system that shows up every time I restart Jenkins. I've been revoking the token each time it comes up without luck. Logging into my Jenkins host computer, I looked in the users folder for my unknown user. users.xml told me what directory it was in and the config.xml confirmed the legacy token. {{ tokenhash }} The new format looks more like {{ uuid mytoken 2019-11-28 18:37:11.655 UTC 11 tokenhash }} Since I was looking to revoke the token outright, I just deleted the line in config.xml and restarted Jenkins.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.9096.1574966940448%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Ken Rachynski commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing I can suggest three more removals from Filipe Roque's list. I do not have Build Pipeline Plugin, Dashboard View, or Pipeline Graph Analysis Plugin on the server where I'm seeing this behaviour. I set up a Docker instance and added most of my production plugins in by hand and have not been able to reproduce this behaviour yet. I say most because I have a NCover plugin in production that doesn't seem to exist any more. As I haven't been able to reproduce this empty token issue, I'm beginning to suspect that this is due to an upgrade somewhere along the lines. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.9081.1574964540516%40Atlassian.JIRA.
[JIRA] (JENKINS-60322) updateGitlabCommitStatus doesn't work after cloning the second GitLab project
Title: Message Title Gennady Krasnikov created an issue Jenkins / JENKINS-60322 updateGitlabCommitStatus doesn't work after cloning the second GitLab project Issue Type: Bug Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-11-28 18:06 Environment: Jenkins ver. 2.190.2 1.5.12 GitLab Plugin GitLab Community Edition 11.6.5 Pipeline from SCM, groovy file Priority: Critical Reporter: Gennady Krasnikov If there is only one GitLab project which is cloned in the pipeline, updateGitlabCommitStatus works fine. If two different projects were cloned before updateGitlabCommitStatus, it stops to work. That is if you clone two projects at the very top of the pipeline, no one updateGitlabCommitStatus will work. If you clone the second project on some stage at the end of the pipeline, all updateGitlabCommitStatus above this will work fine, but all updateGitlabCommitStatus after cloning of the second project will fail. There is issue https://github.com/jenkinsci/gitlab-plugin/issues/522 for the plugin about gitlabCommitStatus and it was resolved with documentation changing that it should be close to the corresponding SCM definition: NOTE: If you use Pipeline global libraries, or if you clone your project's Jenkinsfile from a repo different from the one that contains the relevant source code, you need to be careful about when you send project status. In short, make sure you put your gitlabCommitStatus or other similar steps after the SCM step that clones your project's source. Otherwise, you may get HTTP 400 errors, or you may find build status being sent to the wrong repo https://github.com/jenkinsci/gitlab-plugin This doesn't work for updateGitlabCommitStatus. You can try to clone the first project just before updateGitlabCommitStatus, but this will not help.
[JIRA] (JENKINS-60227) Users other than admin but with job configure privileges are unable to configure jobs
Title: Message Title Bruno Meneguello commented on JENKINS-60227 Re: Users other than admin but with job configure privileges are unable to configure jobs I'm having the same issue. How was this fixed? Something will be updated? There is a workaround? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203202.1574249655000.9076.1574963040165%40Atlassian.JIRA.
[JIRA] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service Change By: Mark Waite Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151876.1383181122000.9074.1574960463696%40Atlassian.JIRA.
[JIRA] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Title: Message Title Mark Waite commented on JENKINS-20356 Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service Assumed resolved after two years with no further comments. The ssh-slaves plugin now includes instructions to allow recent Windows versions to use the Windows OpenSSH service to run agents. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151876.1383181122000.9057.1574960400760%40Atlassian.JIRA.
[JIRA] (JENKINS-58299) Pencil icon removed from Blue Ocean top bar
Title: Message Title Mark Waite closed an issue as Fixed Confirmed it is working as expected in the Declarative Pipeline with Jenkins webinar Jenkins / JENKINS-58299 Pencil icon removed from Blue Ocean top bar Change By: Mark Waite Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title
Matthew Brunton updated an issue
Jenkins / JENKINS-60321
Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Change By:
Matthew Brunton
When using the *p4* plugin and the *Pipeline:* *Multibranch with defaults* plugin, scanning a multibranch pipeline with a default Jenkinsfile results in a _java.lang.ClassCastException._To reproduce, I used the jenkins/jenkins:2.190.3 docker image of Jenkins with p4-plugin (1.10. 3 7 ) and the Pipeline: Multibranch with defaults plugin (2.1), as well as a clean docker instance of Perforce ([https://github.com/p4paul/helix-docker]). I created a stream depot with a couple of dummy streams to use for tests.I created a new multibranch pipeline, set up the Branch source to be the p4 depot with the dummy streams, and set the Build configuration to use _by default Jenkinsfile._It results in the following output:{code:java}Started by user admin[Thu Nov 28 16:40:12 UTC 2019] Starting branch indexing.. p4 streams //testDepot/... +ERROR: [Thu Nov 28 16:40:12 UTC 2019] Could not fetch branches from source f9f7c9b6-5fe3-4b7b-bec1-b56ed976ef85java.lang.ClassCastException: org.jenkinsci.plugins.pipeline.multibranch.defaults.PipelineBranchDefaultsProjectFactory cannot be cast to org.jenkinsci.plugins.workflow.multibranch.WorkflowBranchProjectFactory at org.jenkinsci.plugins.p4.scm.AbstractP4ScmSource.getLastScan(AbstractP4ScmSource.java:383) at org.jenkinsci.plugins.p4.scm.AbstractP4ScmSource.getRevision(AbstractP4ScmSource.java:310) at org.jenkinsci.plugins.p4.scm.AbstractP4ScmSource.retrieve(AbstractP4ScmSource.java:158)Caused: java.io.IOException at org.jenkinsci.plugins.p4.scm.AbstractP4ScmSource.retrieve(AbstractP4ScmSource.java:194) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:635) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1026) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)[Thu Nov 28 16:40:12 UTC 2019] Finished branch indexing. Indexing took 92 msFATAL: Failed to recompute children of testMultibranchDefaults2java.io.IOException: java.lang.ClassCastException: org.jenkinsci.plugins.pipeline.multibranch.defaults.PipelineBranchDefaultsProjectFactory cannot be cast to org.jenkinsci.plugins.workflow.multibranch.WorkflowBranchProjectFactory at org.jenkinsci.plugins.p4.scm.AbstractP4ScmSource.retrieve(AbstractP4ScmSource.java:194) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:635) at
[JIRA] (JENKINS-59527) Trim white space from pipeline library name and version field
Title: Message Title Mark Waite updated JENKINS-59527 Jenkins / JENKINS-59527 Trim white space from pipeline library name and version field Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202156.1569432268000.9038.1574960100337%40Atlassian.JIRA.
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title Mark Waite commented on JENKINS-60316 Re: Git client plugin doesn't quote file locations in askpass wrappers Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.9034.1574959800194%40Atlassian.JIRA.
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title Mark Waite edited a comment on JENKINS-60316 Re: Git client plugin doesn't quote file locations in askpass wrappers Which version of git client plugin are you using? The git client plugni 4 plugin 3 .0.0 release includes an attempt to handle this case and other cases related to atypical project and temporary directory names. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.9032.1574959800140%40Atlassian.JIRA.
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title Matthew Brunton created an issue Jenkins / JENKINS-60321 Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-11-28 16:48 Environment: Docker image jenkins/jenkins:2.190.3 in a docker network with a Perforce instance (https://github.com/p4paul/helix-docker) using p4-plugin 1.10.7 and Pipeline: Multibranch with defaults 2.1 Priority: Blocker Reporter: Matthew Brunton When using the p4 plugin and the Pipeline: Multibranch with defaults plugin, scanning a multibranch pipeline with a default Jenkinsfile results in a java.lang.ClassCastException. To reproduce, I used the jenkins/jenkins:2.190.3 docker image of Jenkins with p4-plugin (1.10.3) and the Pipeline: Multibranch with defaults plugin (2.1), as well as a clean docker instance of Perforce (https://github.com/p4paul/helix-docker). I created a stream depot with a couple of dummy streams to use for tests. I created a new multibranch pipeline, set up the Branch source to be the p4 depot with the dummy streams, and set the Build configuration to use by default Jenkinsfile. It results in the following output: Started by user admin [Thu Nov 28 16:40:12 UTC 2019] Starting branch indexing... ... p4 streams //testDepot/... +ERROR: [Thu Nov 28 16:40:12 UTC 2019] Could not fetch branches from source f9f7c9b6-5fe3-4b7b-bec1-b56ed976ef85 java.lang.ClassCastException: org.jenkinsci.plugins.pipeline.multibranch.defaults.PipelineBranchDefaultsProjectFactory cannot be cast to
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title Waldemar Zurowski commented on JENKINS-60316 Re: Git client plugin doesn't quote file locations in askpass wrappers I checked the master branch in Github and the problem was still there. Anyhow - the version we use is 3.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.9029.1574959380117%40Atlassian.JIRA.
[JIRA] (JENKINS-56125) Add Job DSL support
Title: Message Title
aspel aspel commented on JENKINS-56125
Re: Add Job DSL support
configure {
it / 'properties' / 'hudson.model.ParametersDefinitionProperty' / 'parameterDefinitions' / 'alex.jenkins.plugins.FileSystemListParameterDefinition' {
'name'('IMAGES')
'description'('for')
'path'('/releases')
'selectedType'('DIRECTORY')
'sortByLastModified'('true')
'sortReverseOrder'('true')
'selectedEnumType'('DIRECTORY')
'regexIncludePattern'('.*PNG$')
'regexExcludePattern'('')
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197561.1550066903000.9021.1574958000142%40Atlassian.JIRA.
[JIRA] (JENKINS-58741) Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin
Title: Message Title Jim Spriggs commented on JENKINS-58741 Re: Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Vote++ This would be a big help for me when deploying to multiple embedded systems (I'm testing with hardware in the loop). Currently I'm using (and maintaining) one traditional freestyle job for each system . Parameterized Publishing as it stands is of no real benefit since I would still have to add a complete server-block for each system. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201043.1564584295000.9019.1574957700188%40Atlassian.JIRA.
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title Jorge Cordoba updated JENKINS-60307 Jenkins / JENKINS-60307 CreateItem with rest api impossible with some character Change By: Jorge Cordoba Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.9015.1574956380146%40Atlassian.JIRA.
[JIRA] (JENKINS-60320) Jenkins server error
Title: Message Title pradeep boorla updated an issue Jenkins / JENKINS-60320 Jenkins server error Change By: pradeep boorla Component/s: matrix-auth-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203317.1574955776000.9013.1574956020075%40Atlassian.JIRA.
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title Mark Waite commented on JENKINS-60316 Re: Git client plugin doesn't quote file locations in askpass wrappers Which version of git client plugin are you using? The git client plugni 4.0.0 release includes an attempt to handle this case and other cases related to atypical project and temporary directory names. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.9007.1574955780311%40Atlassian.JIRA.
[JIRA] (JENKINS-60320) Jenkins server error
Title: Message Title pradeep boorla created an issue Jenkins / JENKINS-60320 Jenkins server error Issue Type: Bug Assignee: Unassigned Attachments: Picture1.png Components: _unsorted Created: 2019-11-28 15:42 Environment: QAT Labels: jenkins server mapper security GlobalMatrixAuthorizationStrategy matrix global Priority: Blocker Reporter: pradeep boorla Below is the error when we tried to access the jenkins server on 8080 port VERSION : Jenkins ver. 2.205 com.thoughtworks.xstream.mapper.CannotResolveClassException: hudson.security.GlobalMatrixAuthorizationStrategy at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60316 Git client plugin doesn't quote file locations in askpass wrappers Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.9009.1574955780337%40Atlassian.JIRA.
[JIRA] (JENKINS-59640) Migrate versioncolumn plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated JENKINS-59640 Jenkins / JENKINS-59640 Migrate versioncolumn plugin documentation from Wiki to GitHub Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202322.1570091047000.9003.1574955480086%40Atlassian.JIRA.
[JIRA] (JENKINS-59565) Automatically label Linux Mint agents
Title: Message Title Mark Waite updated JENKINS-59565 Jenkins / JENKINS-59565 Automatically label Linux Mint agents Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202200.1569604425000.8998.1574955360086%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Mark Waite edited a comment on JENKINS-60297 Re: Jenkins could not read from remote repository As far as I can tell, the issue is reported by command line git and can only be handled by command line git. The git plugin might be extended to retry on command line git errors, but retry on error is a complication that has not been added to the Jenkins git plugin yet.I assume that / / SERVERNAME/path/to/repository is accessing the git repository through a Windows network file system protocol (likely CIFS). If so, then you'll need to request assistance from the git for Windows development team or the git development team. I have a personal suspicion that the git team does not spend significant effort assuring that the various implementations of CIFS (Windows 7, Windows 10, Windows Server 2008, Windows Server 2012, Windows Server 2016, Windows Server 2019, Samba in various versions on FreeNAS, FreeBSD, Linux, and macOS) provide the necessary file locking and data transfer semantics that command line git assumes.Refer to this [stackoverflow article|https://stackoverflow.com/questions/37051071/git-wont-reset-file-permissions-over-cifs-mount] for information from one user that struggled with a git repository over CIFS.If you must use CIFS, then you may consider enabling [core.ignoreStat|https://git-scm.com/docs/git-config/2.16.0#git-config-coreignoreStat] in hopes of reducing issues.I don't plan to spend any further effort on this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60297 Jenkins could not read from remote repository Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203291.1574843814000.8995.1574955240288%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Mark Waite commented on JENKINS-60297 Re: Jenkins could not read from remote repository As far as I can tell, the issue is reported by command line git and can only be handled by command line git. The git plugin might be extended to retry on command line git errors, but retry on error is a complication that has not been added to the Jenkins git plugin yet. I assume that /SERVERNAME/path/to/repository is accessing the git repository through a Windows network file system protocol (likely CIFS). If so, then you'll need to request assistance from the git for Windows development team or the git development team. I have a personal suspicion that the git team does not spend significant effort assuring that the various implementations of CIFS (Windows 7, Windows 10, Windows Server 2008, Windows Server 2012, Windows Server 2016, Windows Server 2019, Samba in various versions on FreeNAS, FreeBSD, Linux, and macOS) provide the necessary file locking and data transfer semantics that command line git assumes. Refer to this stackoverflow article for information from one user that struggled with a git repository over CIFS. If you must use CIFS, then you may consider enabling core.ignoreStat in hopes of reducing issues. I don't plan to spend any further effort on this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title
Stefan Cordes commented on JENKINS-38447
Re: Bitbucket hooks don't work for Pipeline jobs
Cesar Tron-Lozai : With
pipelineTriggers([
// build at least build onetime a month
// MINUTE HOUR DOM MONTH DOW
// see https://jenkins.io/doc/book/pipeline/syntax/#triggers
// # Build at least once a month
cron('H H(10-17) H * 1-5')
// for test every 5 minutes
//cron('*/5 * * * *')
,
// poll scm nightly to ensure no push events were lost.
pollSCM('H H(3-7) * * *')
,
// https://issues.jenkins-ci.org/browse/JENKINS-38447?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=true
[$class: 'com.cloudbees.jenkins.plugins.BitBucketTrigger']
,
snapshotDependencies()
])
it worked for me when using $JENKINS_HOME/bitbucket-hook/ when
https bitbucket URL and not ssh
git and not bitbucket-source in "Project Repository"
(reason: see com.cloudbees.jenkins.plugins.BitbucketJobProbe.match(..))
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are
[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title Stefan Cordes updated an issue Jenkins / JENKINS-38447 Bitbucket hooks don't work for Pipeline jobs Change By: Stefan Cordes Attachment: branch-sources-https-and-pure-git.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174627.1474550199000.8894.1574954583189%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Mark Waite updated JENKINS-60297 Jenkins / JENKINS-60297 Jenkins could not read from remote repository Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203291.1574843814000.8892.1574954400202%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title
Alexander Biryukov created an issue
Jenkins / JENKINS-60319
Reactive Parameter ignores toString
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Attachments:
image-2019-11-28-18-15-26-268.png
Components:
active-choices-plugin
Created:
2019-11-28 15:16
Priority:
Minor
Reporter:
Alexander Biryukov
class Choice {
String tag
String branch
@Override
String toString() {
return tag + ' / ' + branch
}
}
def obj1 = new Choice(branch: '1', tag:"3")
def obj2 = new Choice(branch: '2', tag:"4")
return [obj1, obj2]
The following groovy script works fine for Active Choice parameter, but broken for Reactive one. For some reason, Reactive version ignores toString (yet it shows correct string for a second), showing "Object" string instead: First paramater is reactive, the second is non-reactive
[JIRA] (JENKINS-20073) Add an action to allow moving credentials between credential domains
Title: Message Title Kalle Niemitalo commented on JENKINS-20073 Re: Add an action to allow moving credentials between credential domains Is there any reason why this issue should not be closed? src/test/java/com/cloudbees/plugins/credentials/CredentialsStoreActionTest.java does not yet contain a test for moving a credential. I guess that is why this issue is still open. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151593.1381922552000.8884.1574954100297%40Atlassian.JIRA.
[JIRA] (JENKINS-49325) @script folder contains full git checkout and is not deleted on cleanup
Title: Message Title Petr H commented on JENKINS-49325 Re: @script folder contains full git checkout and is not deleted on cleanup Having the same issue. It's really annoying and can consume a lot of disk space if you've got a multitude of multibranch jobs. Note that the @script directory isn't the only one, There's also @libs: workspace@script, workspace@libs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188188.1517523474000.8880.1574950741346%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Peter Willekens commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file OK, thx for the confirmation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.8852.1574948820652%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Radi Berkovich commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file included, I also will change status of issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.8822.1574947802415%40Atlassian.JIRA.
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title Max Kaskevich commented on JENKINS-60305 Re: Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required Have the same issue with "The 'permissions' query parameter is required." jenkins 2.190.3(docker image) Jira plugin 3.0.11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203300.1574868719000.8849.1574947803580%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Radi Berkovich updated JENKINS-55836 Jenkins / JENKINS-55836 Unable to delete workspace due to locked git .pack file Change By: Radi Berkovich Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.8847.1574947803525%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Peter Willekens commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Can you confirm this beta fix was included in version 5.9 ? Status of this issue suggests otherwise ... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.8775.1574947560692%40Atlassian.JIRA.
[JIRA] (JENKINS-12003) GIT_BRANCH not set on initial checkout
Title: Message Title ovi craciun commented on JENKINS-12003 Re: GIT_BRANCH not set on initial checkout Gyula Juhasz, so if it is the workspace that is the culprit, where the fix should go? How can one fix this situation in which $GIT_BRANCH is ending up incorrect? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142275.1323177235000.8772.1574947260368%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Radi Berkovich commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file In versions 5.9 we did several related fixes in the area. Version 5.9 was released in september. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.8743.1574946960768%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Peter Willekens commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file When will this fix actually be Released ? As far as I can see it was not in 5.9. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.8719.1574946540595%40Atlassian.JIRA.
[JIRA] (JENKINS-58967) Credentials not available after upgrade to LTS 2.176.2
Title: Message Title Kalle Niemitalo commented on JENKINS-58967 Re: Credentials not available after upgrade to LTS 2.176.2 This seems to be working: Add a "jenkins-build" user to the security realm. Configure Authorize Project to run all builds as the "jenkins-build" user, without allowing per-job configuration. Add -Dcom.cloudbees.plugins.credentials.UseItemPermission=true to the Java options of the Jenkins master. Configure Role-based Authorization Strategy like this: Define the global role "build" with only these global permissions: Overall/Read (might not be necessary) Credentials/UseItem (this requires the option that was set above) Agent/Build Job/Read Assign the global role "build" to the user "jenkins-build". Add a certificate credential to the global credential domain of a multibranch pipeline job. Reference the credential using withCredentials in the Jenkinsfiles of branches of that job. If I then log in as the "jenkins-build" user, I do not see the credentials, because of the missing Credentials/View permission. However, the builds can use the credentials just fine. Add Comment
[JIRA] (JENKINS-60318) NULL Pointer Exception - Pipeline view is not rendered
Title: Message Title Kabilan Selvakumar created an issue Jenkins / JENKINS-60318 NULL Pointer Exception - Pipeline view is not rendered Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-11-28 12:37 Priority: Blocker Reporter: Kabilan Selvakumar Reproduce steps: Create a pipeline view using a DSL script. Delete pipeline view in browser window page. Create a pipeline view again using a DSL script. Open a pipeline view in browser window and the below exception will be reported in browser window itself. Exception stack trace org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.199.jar!/hudson/model/View/sidepanel.jelly:75:50: java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at
[JIRA] (JENKINS-20073) Add an action to allow moving credentials between credential domains
Title: Message Title Kalle Niemitalo edited a comment on JENKINS-20073 Re: Add an action to allow moving credentials between credential domains AFAICT, this is already works in Credentials Plugin 2.3.0 (and presumably has worked since version 1.16) ; if you have multiple credential domains in the same credential store, then the UI lets you move a credential from one domain to another. Is there any reason why this issue should not be closed?However, it is not yet possible to move credentials from one project or folder to another. That feature request been filed separately as JENKINS-20075. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151593.1381922552000.8707.1574943840330%40Atlassian.JIRA.
[JIRA] (JENKINS-59331) withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-59331
Re: withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Credentials Binding Plugin has done this ever since the certificate binding feature was added in [commit 7d789a8c590fd87cb9dd61c89c894a5df26a0605|https://github.com/jenkinsci/credentials-binding-plugin/commit/7d789a8c590fd87cb9dd61c89c894a5df26a0605] and merged in [PR#39|https://github.com/jenkinsci/credentials-binding-plugin/pull/39]. The commit message even mentions the assumption that the credential description matches the keystore alias name, but I don't think I have seen it documented anywhere else. When I edit the description of a certificate credential, the help text "An optional description to help tell similar credentials apart" certainly gives no hint of any such requirement.CertificateMultiBinding already calls {{credentials.getKeyStore()}}, so perhaps it could just enumerate the returned KeyStore and get the alias name from there, without needing changes in the Credentials Plugin. If the {{aliasVariable}} parameter is specified but the KeyStore actually contains more than one key, then CertificateMultiBinding could log a warning about that , perhaps unless the description of the credential matches one of these aliases .If each certificate credential normally contains only one certificate and private key, then the keystore alias name is not really needed for selecting the correct certificate, and I think users are likely to choose short words like "cert" as keystore alias names. If the {{withCredentials}} step is then changed to store these to the {{aliasVariable}}, there may be a risk that Jenkins starts unnecessarily masking this word in unrelated output. Perhaps the keystore alias name should be exempt from this masking, like JENKINS-44860 requests for usernames.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60317) Encrypt the temporary keystore and keys with a random password in certificate binding
Title: Message Title Kalle Niemitalo created an issue Jenkins / JENKINS-60317 Encrypt the temporary keystore and keys with a random password in certificate binding Issue Type: New Feature Assignee: Unassigned Components: credentials-binding-plugin Created: 2019-11-28 11:59 Environment: Jenkins 2.190.3 Credentials Binding Plugin 1.20 Credentials Plugin 2.3.0 Priority: Minor Reporter: Kalle Niemitalo Current behaviour Nowadays, when the Credentials Binding Plugin is used on a certificate credential, CertificateMultiBinding calls credentials.getPassword() and credentials.getKeyStore() and saves the KeyStore to a temporary file encrypted with this password. Typically, any private keys within the KeyStore have already been encrypted with the same password; otherwise, the Credentials Plugin would have warned about the unaccessible key when the PKCS#12 file was uploaded to Jenkins. Desired change CertificateMultiBinding could be changed to generate a random password and use that when it passes the credential to the job. This would mean: Generate a cryptographically random temporary password. Create a temporary KeyStore. Enumerate the KeyStore of the credential. Decrypt each key with the password of the credential, encrypt with the temporary password, and add to the temporary KeyStore. Save the temporary KeyStore to the temporary file, encrypting it with the temporary password. Pass the temporary password to the
[JIRA] (JENKINS-59331) withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-59331
Re: withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Credentials Binding Plugin has done this ever since the certificate binding feature was added in [commit 7d789a8c590fd87cb9dd61c89c894a5df26a0605|https://github.com/jenkinsci/credentials-binding-plugin/commit/7d789a8c590fd87cb9dd61c89c894a5df26a0605] and merged in [PR#39|https://github.com/jenkinsci/credentials-binding-plugin/pull/39]. The commit message even mentions the assumption that the credential description matches the keystore alias name, but I don't think I have seen it documented anywhere else. When I edit the description of a certificate credential, the help text "An optional description to help tell similar credentials apart" certainly gives no hint of any such requirement.CertificateMultiBinding already calls {{credentials.getKeyStore()}}, so perhaps it could just enumerate the returned KeyStore and get the alias name from there, without needing changes in the Credentials Plugin. If the {{aliasVariable}} parameter is specified but the KeyStore actually contains more than one key, then CertificateMultiBinding could log a warning about that.If each certificate credential normally contains only one certificate and private key, then the keystore alias name is not really needed for selecting the correct certificate, and I think users are likely to choose short words like "cert" as keystore alias names. If the {{withCredentials}} step is then changed to store these to the {{aliasVariable}}, there may be a risk that Jenkins starts unnecessarily masking this word in unrelated output. Perhaps the keystore alias name should be exempt from this masking , like JENKINS-44860 requests for usernames .
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59331) withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name
Title: Message Title Kalle Niemitalo commented on JENKINS-59331 Re: withCredentials certificate(aliasVariable: ) stores description of credential, not keystore alias name In the Certificate Plugin, CertificateCredentialsImpl.KeyStoreSourceDescriptor#validateCertificateKeystore apparently supports multiple certificate entries and multiple key entries in the same KeyStore. StandardCertificateCredentials.NameProvider#getSubjectDN only uses one key entry, though. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201882.1568291887000.8674.1574940061181%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Filipe Roque commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing I also have this problem. Two users that after revoking legacy tokens, keep coming back. I have attached plugins-merged.lieverdink.kolinek.froque.txt with common plugins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.8660.1574939460416%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Filipe Roque updated an issue Jenkins / JENKINS-53266 Legacy token for user "unknown" keeps reappearing Change By: Filipe Roque Attachment: plugins-merged.lieverdink.kolinek.froque.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.8645.1574939340597%40Atlassian.JIRA.
[JIRA] (JENKINS-60316) Git client plugin doesn't quote file locations in askpass wrappers
Title: Message Title Waldemar Zurowski updated an issue Jenkins / JENKINS-60316 Git client plugin doesn't quote file locations in askpass wrappers Change By: Waldemar Zurowski Summary: Git client plugin doesn't quote file locations in askpass wrappers Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203313.1574939216000.8642.1574939280631%40Atlassian.JIRA.
[JIRA] (JENKINS-60316) Git client doesn't quote file locations in askpass wrappers
Title: Message Title Waldemar Zurowski created an issue Jenkins / JENKINS-60316 Git client doesn't quote file locations in askpass wrappers Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2019-11-28 11:06 Priority: Minor Reporter: Waldemar Zurowski We have a project which uses blank spaces and other characters for its name. This name is used to create a temporary folder for files containing username and password consumed by a script generated by CliGitAPIImpl class. Because these names of these files are not quoted in the generated shell script, a script has a syntax errors and we run into following problem: using GIT_ASKPASS to set credentials token to authenticate with github for XXX > git fetch --no-tags --force --progress -- https://github.com/corda/XXX.git +refs/heads/master:refs/remotes/origin/master # timeout=10 ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from https://github.com/corda/XXX.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:899) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1114) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1145) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.lambda$doRetrieve$1(SCMSourceRetriever.java:154) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrySCMOperation(SCMSourceRetriever.java:104) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:153) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:93) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at
[JIRA] (JENKINS-59669) Support retrieval of secrets from a different AWS account
Title: Message Title Chris Kilding resolved as Fixed Notes on how to set up cross-account secret retrieval through IAM roles were added to the README. Jenkins / JENKINS-59669 Support retrieval of secrets from a different AWS account Change By: Chris Kilding Status: In Progress Resolved Resolution: Fixed Released As: 0.1.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59669) Support retrieval of secrets from a different AWS account
Title: Message Title Chris Kilding closed an issue as Fixed Jenkins / JENKINS-59669 Support retrieval of secrets from a different AWS account Change By: Chris Kilding Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202361.1570220679000.8638.1574938500377%40Atlassian.JIRA.
[JIRA] (JENKINS-59669) Support retrieval of secrets from a different AWS account
Title: Message Title Chris Kilding started work on JENKINS-59669 Change By: Chris Kilding Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202361.1570220679000.8636.1574938441077%40Atlassian.JIRA.
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Chris Kilding closed an issue as Fixed Jenkins / JENKINS-58339 Support new types of credentials Change By: Chris Kilding Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.8635.1574938441034%40Atlassian.JIRA.
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Chris Kilding resolved as Fixed Jenkins / JENKINS-58339 Support new types of credentials Change By: Chris Kilding Status: In Progress Resolved Resolution: Fixed Released As: 0.1.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.8630.1574938440830%40Atlassian.JIRA.
[JIRA] (JENKINS-60315) "Indication" drop-down raises exception in Javascript console
Title: Message Title Allan Lewis created an issue Jenkins / JENKINS-60315 "Indication" drop-down raises exception in _javascript_ console Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-11-28 10:46 Environment: Jenkins v2.176.2 Build Failure Analyzer Plugin 1.24.1 Fedora 30 Firefox 70.0.1 / Google Chrome 78.0.3904.108 Priority: Minor Reporter: Allan Lewis On a build status page where a failure has been identified, each "indication" has a drop-down arrow next to it; this appears when hovering over the text. Clicking this should presumably present some options, but instead it throws a _javascript_ exception that can be seen in the console: Firefox 70 SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data prototype.js:747:17 Chrome 78 hudson-behavior.js:2995 Uncaught SyntaxError: Unexpected token < in JSON at position 0 at JSON.parse () at
[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Thomas BASILIEN commented on JENKINS-60314 Re: Git knowledge base Thanks for your input, I will dig in the code to see what I can do ! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203311.1574934344000.8585.1574936940382%40Atlassian.JIRA.
[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Tomas Westling commented on JENKINS-60314 Re: Git knowledge base Hi Thomas, I think it sounds like a good idea. The information that is to be stored is suited well for git, since it is human-readable text. The biggest pro for it would be the history, which sounds like a good reason to do it, in both of the current solutions, we only have a latest version of a failure cause. And implementation-wise I guess it wouldn't be that hard to integrate with the existing git plugins. It isn't something I have the time to look at, but feel free to hack away and create a pull request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203311.1574934344000.8583.1574936460160%40Atlassian.JIRA.
[JIRA] (JENKINS-29198) Console logs get truncated without reason
Title: Message Title ASHOK MOHANTY commented on JENKINS-29198 Re: Console logs get truncated without reason In our case - "Console logs get truncated when job runs for a long time". Are there any log size limit !? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163659.1435857275000.8541.1574934905801%40Atlassian.JIRA.
[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Thomas BASILIEN updated an issue Jenkins / JENKINS-60314 Git knowledge base Change By: Thomas BASILIEN I saw that currently, we can save the elements on : - Jenkins : filesystem - Mongodb.I would like to know your output about using git as the database ? My pros for this are : * We can add the git workflow to add / change / delete rules (with MR) * We have the history of rules. * The database can be readonly, if necessary (it my case, we have a lot constrain about service user with write rights) * we have our Jenkins conf centralized on the same place (pipeline can get their conf from git) * git manage files, the so it should work out of the box with the current jenkins database implementation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you 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-60314) Git knowledge base
Title: Message Title Thomas BASILIEN updated an issue Jenkins / JENKINS-60314 Git knowledge base Change By: Thomas BASILIEN I saw that currently, we can save the elements on : - Jenkins : filesystem - Mongodb. I would like to know your output about using git as the database ? My pros for this are : * We can add the git workflow to add / change / delete rules (with MR) * We have the history of rules. * The database can be readonly, if necessary (it my case, we have a lot constrain about service user with write rights) * we have our Jenkins conf centralized on the same place (pipeline can get their conf from git) * git manage files, the it should work out of the box with the current jenkins database implementation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you 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-60314) Git knowledge base
Title: Message Title Thomas BASILIEN updated an issue Jenkins / JENKINS-60314 Git knowledge base Change By: Thomas BASILIEN I saw that currently, we can save the elements on : - Jenkins : filesystem- Mongodb. I would like to know your output about using git as the database ?My pros for this are : * We can add the git workflow to add / change / delete rules (with MR) * We have the history of rules. * The database can be readonly, if necessary (it my case, we have a lot constrain about service user with write rights) * we have our Jenkins conf centralized on the same place (pipeline can get their conf from git) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Thomas BASILIEN created an issue Jenkins / JENKINS-60314 Git knowledge base Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-11-28 09:45 Priority: Minor Reporter: Thomas BASILIEN I saw that currently, we can save the elements on : Jenkins : filesystem Mongodb. I would like to know your output about using git as the database ? My pros for this are : We can add the git workflow to add / change / delete rules (with MR) We have the history of rules. The database can be readonly, if necessary (it my case, we have a lot constrain about service user with write rights) we have our Jenkins conf centralized on the same place (pipeline can get their conf from git)
[JIRA] (JENKINS-60313) Confusing error message when MySQL API plugin isn't installed
Title: Message Title
Josh Watson updated an issue
Jenkins / JENKINS-60313
Confusing error message when MySQL API plugin isn't installed
Change By:
Josh Watson
I just encountered issue JENKINS-54587, but had to search online to resolve it as the error message in the log from the plug-in is incorrect. The log message states:{code:java}2019-11-28 08:43:45.873+ [id=206] INFOhudson.model.AsyncPeriodicWork$1#run: Finished DockerContainerWatchdog Asynchronous Periodic Work. 7 ms2019-11-28 08:43:50.207+ [id=14]WARNING o.j.p.p.m.GlobalPipelineMavenConfig#getDao: Exception creating database dao, skipjava.lang.RuntimeException: MySql driver 'com.mysql.cj.jdbc.Driver' not found. Please install the 'MySQL Database Plugin' to install the MySql driverat org.jenkinsci.plugins.pipeline.maven.GlobalPipelineMavenConfig.getDao(GlobalPipelineMavenConfig.java:322)at org.jenkinsci.plugins.pipeline.maven.NonProductionGradeDatabaseWarningAdministrativeMonitor.isActivated(NonProductionGradeDatabaseWarningAdministrativeMonitor.java:19) {code}So I went to check my plug-ins and found confirmed I have the MySQL Database Plugin installed. After a bit of googling, I fcouldn couldn 't find a solution, so looked at the plugin plug-in configuration. When testing the plugin plug-in configuration it states that I should install the 'MySQL API Plugin' - I didn't have this installed and this resolved the issue.The issue is just a misleading error message. Thanks for all the hard work on Jenkins and the plugins!
Add Comment
[JIRA] (JENKINS-60313) Confusing error message when MySQL API plugin isn't installed
Title: Message Title
Josh Watson updated an issue
Jenkins / JENKINS-60313
Confusing error message when MySQL API plugin isn't installed
Change By:
Josh Watson
I just encountered the issue JENKINS-54587, but had to search online to resolve it as the error message in the log from the plug-in is incorrect. The log message states:{code:java}2019-11-28 08:43:45.873+ [id=206] INFOhudson.model.AsyncPeriodicWork$1#run: Finished DockerContainerWatchdog Asynchronous Periodic Work. 7 ms2019-11-28 08:43:50.207+ [id=14]WARNING o.j.p.p.m.GlobalPipelineMavenConfig#getDao: Exception creating database dao, skipjava.lang.RuntimeException: MySql driver 'com.mysql.cj.jdbc.Driver' not found. Please install the 'MySQL Database Plugin' to install the MySql driverat org.jenkinsci.plugins.pipeline.maven.GlobalPipelineMavenConfig.getDao(GlobalPipelineMavenConfig.java:322)at org.jenkinsci.plugins.pipeline.maven.NonProductionGradeDatabaseWarningAdministrativeMonitor.isActivated(NonProductionGradeDatabaseWarningAdministrativeMonitor.java:19) {code}So I went to check my plug-ins and found I have the MySQL Database Plugin installed. After a bit of googling, I fcouldn't find a solution, so looked at the plugin configuration. When testing the plugin configuration it states that I should install the 'MySQL API Plugin' - I didn't have this installed and this resolved the issue.The issue is just a misleading error message. Thanks for all the hard work on Jenkins and the plugins!
Add Comment
This message was sent
[JIRA] (JENKINS-60313) Confusing error message when MySQL API plugin isn't installed
Title: Message Title Josh Watson created an issue Jenkins / JENKINS-60313 Confusing error message when MySQL API plugin isn't installed Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2019-11-28 09:31 Environment: Jenkins 2.190.3 LTS, Pipeline Maven Plugin 3.8.2, MySQL Database Plugin 1.3 Priority: Trivial Reporter: Josh Watson I just encountered the JENKINS-54587, but had to search online to resolve it as the error message in the log from the plug-in is incorrect. The log message states: 2019-11-28 08:43:45.873+ [id=206] INFOhudson.model.AsyncPeriodicWork$1#run: Finished DockerContainerWatchdog Asynchronous Periodic Work. 7 ms 2019-11-28 08:43:50.207+ [id=14]WARNING o.j.p.p.m.GlobalPipelineMavenConfig#getDao: Exception creating database dao, skip java.lang.RuntimeException: MySql driver 'com.mysql.cj.jdbc.Driver' not found. Please install the 'MySQL Database Plugin' to install the MySql driver at org.jenkinsci.plugins.pipeline.maven.GlobalPipelineMavenConfig.getDao(GlobalPipelineMavenConfig.java:322) at org.jenkinsci.plugins.pipeline.maven.NonProductionGradeDatabaseWarningAdministrativeMonitor.isActivated(NonProductionGradeDatabaseWarningAdministrativeMonitor.java:19) So I went to check my plug-ins and found I have the MySQL Database Plugin installed. After a bit of googling, I fcouldn't find a solution, so looked at the plugin configuration. When testing the plugin configuration it states that I
[JIRA] (JENKINS-60312) jenkins getting blocked
Title: Message Title hemant vishe assigned an issue to Unassigned Jenkins / JENKINS-60312 jenkins getting blocked Change By: hemant vishe Assignee: hemant vishe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203308.1574932518000.8507.1574932920952%40Atlassian.JIRA.
[JIRA] (JENKINS-60312) jenkins getting blocked
Title: Message Title hemant vishe assigned an issue to hemant vishe Jenkins / JENKINS-60312 jenkins getting blocked Change By: hemant vishe Assignee: hemant vishe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203308.1574932518000.8506.1574932920851%40Atlassian.JIRA.
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title Yann-Thomas Le Moigne commented on JENKINS-60307 Re: CreateItem with rest api impossible with some character I am using CDATA for escape xml value in this case. Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.8500.1574932620592%40Atlassian.JIRA.
[JIRA] (JENKINS-60307) CreateItem with rest api impossible with some character
Title: Message Title Yann-Thomas Le Moigne edited a comment on JENKINS-60307 Re: CreateItem with rest api impossible with some character I am using CDATA for escape xml value in this case. Thank you. I think this ticket could be closed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203302.157487527.8502.1574932621002%40Atlassian.JIRA.
[JIRA] (JENKINS-60312) jenkins getting blocked
Title: Message Title hemant vishe commented on JENKINS-60312 Re: jenkins getting blocked what is issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203308.1574932518000.8498.1574932620266%40Atlassian.JIRA.
[JIRA] (JENKINS-60312) jenkins getting blocked
Title: Message Title hemant vishe created an issue Jenkins / JENKINS-60312 jenkins getting blocked Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-11-28 09:15 Environment: ubuntu Priority: Critical Reporter: hemant vishe Stack trace java.lang.NullPointerException at hudson.security.TokenBasedRememberMeServices2.autoLogin(TokenBasedRememberMeServices2.java:164) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at
[JIRA] (JENKINS-56654) raw HTML text being displayed by Rich Text Publisher plugin in Dashboard view
Title: Message Title Valentin Baranov commented on JENKINS-56654 Re: raw HTML text being displayed by Rich Text Publisher plugin in Dashboard view Bindu Latha I'm also facing the same problem. Instead of table, raw html is displayed on my build page. Can you please fix it as soon as possible? I tried to downgrade the plugin to 1.3 but it didn't help. Jenkins version is 2.190.1 For now, because of this bug, we lost on-page quick summaries about the build results and it makes us to do additional checks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198286.1553152716000.8486.1574928300276%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Benjamin Loeffler assigned an issue to Mark Waite Jenkins / JENKINS-60297 Jenkins could not read from remote repository Change By: Benjamin Loeffler Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203291.1574843814000.8483.1574928120222%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Benjamin Loeffler commented on JENKINS-60297 Re: Jenkins could not read from remote repository Thanks Mark Waite for this very fast response! But I cant resolve the issue. Yes, I clone a repository from a server we host. The error occures, when just a single clone is done and when nothing happens on the server (tried at night and on the early morning when noone is at work). I clone the GIT repo in the jenkins-job "Source-Code-Management" in "Repository URL" via //SERVERNAME/x/x/x/x/.git No credentials are used. (The error occures too if credentials are used: username and password of the user jenkins is running and which has access rights to the server) This should work without ssh or https right? Use of ssh or https is not needed, its a internal server and access is only via the LAN. So whats the poblem that it works sometimes and sometimes not? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203291.1574843814000.8479.1574928061122%40Atlassian.JIRA.
[JIRA] (JENKINS-60297) Jenkins could not read from remote repository
Title: Message Title Benjamin Loeffler updated JENKINS-60297 Jenkins / JENKINS-60297 Jenkins could not read from remote repository Change By: Benjamin Loeffler Resolution: Not A Defect Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203291.1574843814000.8480.1574928061274%40Atlassian.JIRA.
