[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Thanks Vincent Massol ! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54640) Workspace folders are not unique
Title: Message Title kpop closed an issue as Fixed Nov 21, 2018 8:23:35 AM FINE allocating $WORKSPACE/Config1_BranchWithRatherLongName for WorkflowJob@11fe5 [Repo/ProjectA/Config1/BranchWithRatherLongName] Nov 21, 2018 8:33:18 AM FINER index collision onConfig1_BranchWithRatherLongName for WorkflowJob@16ea9b8[Repo/ProjectB/Config1/BranchWithRatherLongName] Nov 21, 2018 8:33:18 AM FINE allocating $WORKSPACE/nfig1_BranchWithRatherLongName_2 for WorkflowJob@16ea9b8[Repo/ProjectB/Config1/BranchWithRatherLongName] The above log illustrates that collisions as correctly resolved by appending a something to the folder name to make it unique. That unique name is also correctly stored in workspaces.txt. Jenkins / JENKINS-54640 Workspace folders are not unique Change By: kpop Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-48283) InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy)
Title: Message Title Vincent Massol commented on JENKINS-48283 Re: InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy) Thanks Cyrille Le Clerc. Doing this now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54699) Durable Task Version 1.28 break jenkins pipeline
Title: Message Title laurent gil commented on JENKINS-54699 Re: Durable Task Version 1.28 break jenkins pipeline Devin Nusbaum, yes we rollback Durable Tasks to the version 1.27. Our script security plugin is in version 1.48. Basically we update all the plugins once a week except Durable Tasks and Docker pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54711) jenkins-jobs.mv.db failed
Title: Message Title Cyrille Le Clerc commented on JENKINS-54711 Re: jenkins-jobs.mv.db failed You would have to bump to 3.6.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Vincent Massol commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Cyrille Le Clerc Thanks! I'm upgrading right now and will let you know how it goes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54733) After 10 builds Pipeline Stage View disappears.
Title: Message Title Omar Malik commented on JENKINS-54733 Re: After 10 builds Pipeline Stage View disappears. Looking at the log I also see a warning OwnerPipeline/Pipeline #11 was not in the list to begin with: [] Not sure how to proceed here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25842) User Permissions Wiped After Jenkins Restart
Title: Message Title Ishaan Gupta commented on JENKINS-25842 Re: User Permissions Wiped After Jenkins Restart The same is the issue with the latest version of Jenkins. (1.3.8). Using Jenkins on Docker and on plugin installation and restart, the LDAP properties get reset to own user database. Have to reconfigure the security configurations and also set the file configurations as that also gets reset. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54640) Workspace folders are not unique
Title: Message Title kpop commented on JENKINS-54640 Re: Workspace folders are not unique Many thanks Jesse Glick for this quick fix! Just to be sure, I've also emptied my workspace folder. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54576) hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder'
Title: Message Title Mez Pahlan commented on JENKINS-54576 Re: hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder' Hi Dominik Bartholdi I've made some changes that should render the baseUrlHolder / baseUrl completely optional if not specified. Are you able to test these changes out? You can get an updated plugin from the PR branch artefacts. The PR itself is on Github #58. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54743) Contribute JIRA_URL environment variable
Title: Message Title benoit guerin started work on JENKINS-54743 Change By: benoit guerin Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54743) Contribute JIRA_URL environment variable
Title: Message Title benoit guerin commented on JENKINS-54743 Re: Contribute JIRA_URL environment variable Pull request link attached Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54743) Contribute JIRA_URL environment variable
Title: Message Title benoit guerin updated JENKINS-54743 Jenkins / JENKINS-54743 Contribute JIRA_URL environment variable Change By: benoit guerin Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54744) Publish over ssh is not transferring directories created by file operations plugin
Title: Message Title gowthaman v created an issue Jenkins / JENKINS-54744 Publish over ssh is not transferring directories created by file operations plugin Issue Type: Bug Assignee: Suresh Kumar Attachments: folders.png Components: file-operations-plugin, publish-over-ssh-plugin Created: 2018-11-21 07:08 Environment: operating system : ubuntu 16.04 /debian 8 jenkins version : 2.138.3 [ fresh install via apt-get ] publish over ssh plugin version : 1.20.1 file operations plugin version : 1.7 java version : 1.8 Priority: Blocker Reporter: gowthaman v Installed jenkins via apt-get Added Publish over ssh , file operations plugin Added folder create [3 folders created ] options in build options. configured post-build actions -> send build artifacts overs ssh with source files */ Inside workspace directory, the folders specified by file operation plugin are created when i see the files in the remote directory , folders created via file operation plugin is not transferred . With older version it worked fine .
[JIRA] (JENKINS-54742) Can't load shared library multiple times on parallel stages
Title: Message Title William Laszlo updated an issue Jenkins / JENKINS-54742 Can't load shared library multiple times on parallel stages Change By: William Laszlo Summary: Can't load shared library more than once multiple times on parallel stages Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54743) Contribute JIRA_URL environment variable
Title: Message Title benoit guerin created an issue Jenkins / JENKINS-54743 Contribute JIRA_URL environment variable Issue Type: Improvement Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2018-11-21 07:03 Priority: Minor Reporter: benoit guerin The idea is to use this environment variable to, for example, build links to issues We can get this information by calling getServerInfo() but we have it from configuration, so if a remote call can be avoid ... Add Comment This message
[JIRA] (JENKINS-54742) Can't load shared library more than once on parallel stages
Title: Message Title
William Laszlo updated an issue
Jenkins / JENKINS-54742
Can't load shared library more than once on parallel stages
Change By:
William Laszlo
I have two parallel stages that are using a shared library loaded on fly and I'm using it to upload some artifacts to somewhere else, but i'm getting an error. Simple Jenkinsfile:{code:java}pipeline {agent nonestages {stage ('Build') {failFast trueparallel {stage ('Windows x86') {agent { label 'win_x86'}steps { bat "build_x86.bat" dir ("${PACKAGE_DIR}") { stash name: "win_x86" }}}stage ('Windows x64') {agent { label 'win_x64'}steps { bat "build_x64.bat" dir ("${PACKAGE_DIR}") { stash name: "win_x64" }}}}}stage ('Tests') {failFast trueparallel {stage ('Windows x86') {agent { label 'win_x86'}steps { unstash "win_x86" bat "test_x86.bat"}}stage ('Windows x64') {agent { label 'win_x64'}steps { unstash "win_x64" bat "test_x64.bat"}}}}stage ('Package') {failFast trueparallel {stage ('Windows x86 Pkg ') {agent { label 'win_x86'}steps { unstash "win_x86"}library 'MyLibrary@v1.0.0'myLibraryExec("x86", "foo")}stage ('Windows x64 Pkg ') {agent { label 'win_x64'}steps { unstash "win_x64"}library 'MyLibrary@v1.0.0'myLibraryExec("x64", "bar")}}}}}{code}Error:{code:java}15:43:01 [Windows x64 Pkg] Loading library MyLibrary@v1.0.015:43:01 [Windows x64 Pkg] Attempting to resolve v1.0.0 from remote references...15:43:01 [Windows x64 Pkg] > git --version # timeout=1015:43:01 [Windows x64 Pkg] using GIT_ASKPASS to set credentials Jenkins Faceless Account15:43:01 [Windows x64 Pkg] > git ls-remote -h https://host/repo.git # timeout=1015:43:05 [Windows x86 Pkg] Only using first definition of library ArtifactoryPush15:43:06 [Windows x86 Pkg] Failed in
[JIRA] (JENKINS-54742) Can't load shared library more than once on parallel stages
Title: Message Title
William Laszlo updated an issue
Jenkins / JENKINS-54742
Can't load shared library more than once on parallel stages
Change By:
William Laszlo
I have two parallel stages that are using a shared library loaded on fly and I'm using it to upload some artifacts to somewhere else, but i'm getting an error. Simple Jenkinsfile:{code:java}pipeline {agent nonestages {stage ('Build') {failFast trueparallel {stage ('Windows x86') {agent { label 'win_x86'}steps { bat "build_x86.bat" dir ("${PACKAGE_DIR}") { stash name: "win_x86" }}}stage ('Windows x64') {agent { label 'win_x64'}steps { bat "build_x64.bat" dir ("${PACKAGE_DIR}") { stash name: "win_x64" }}}}}stage ('Tests') {failFast trueparallel {stage ('Windows x86') {agent { label 'win_x86'}steps { unstash "win_x86" bat "test_x86.bat"}}stage ('Windows x64') {agent { label 'win_x64'}steps { unstash "win_x64" bat "test_x64.bat"}}}}stage ('Package') {failFast trueparallel {stage ('Windows x86') {agent { label 'win_x86'}steps { unstash "win_x86"}library 'MyLibrary@v1.0.0'myLibraryExec("x86", "foo")}stage ('Windows x64') {agent { label 'win_x64'}steps { unstash "win_x64"}library 'MyLibrary@v1.0.0'myLibraryExec("x64", "bar")}}}}}{code}Error:{ noformat code:java }15:43:01 [Windows x64 Pkg] Loading library MyLibrary@v1.0. 015:43:01 [Windows x64 Pkg] Loading library MyLibrary@v1. 0 .015 15 :43:01 [Windows x64 Pkg] Attempting to resolve v1.0.0 from remote references... 15:43:01 [Windows x64 Pkg] > git --version # timeout= 1015 1015 :43:01 [Windows x64 Pkg] using GIT_ASKPASS to set credentials Jenkins Faceless Account15 Account15 :43:01 [Windows x64 Pkg] > git ls-remote -h https://host/repo.git # timeout= 1015 1015 :43:05 [Windows x86
[JIRA] (JENKINS-54742) Can't load shared library more than once on parallel stages
Title: Message Title
William Laszlo updated an issue
Jenkins / JENKINS-54742
Can't load shared library more than once on parallel stages
Change By:
William Laszlo
I have two parallel stages that are using a shared library loaded on fly and I'm using it to upload some artifacts to somewhere else, but i'm getting an error. Simple Jenkinsfile:{code:java}pipeline {agent nonestages {stage ('Build') {failFast trueparallel {stage ('Windows x86') {agent { label 'win_x86'}steps { bat "build_x86.bat" dir ("${PACKAGE_DIR}") { stash name: "win_x86" }}}stage ('Windows x64') {agent { label 'win_x64'}steps { bat "build_x64.bat" dir ("${PACKAGE_DIR}") { stash name: "win_x64" }}}}}stage ('Tests') {failFast trueparallel {stage ('Windows x86') {agent { label 'win_x86'}steps { unstash "win_x86" bat "test_x86.bat"}}stage ('Windows x64') {agent { label 'win_x64'}steps { unstash "win_x64" bat "test_x64.bat"}}}}stage ('Package') {failFast trueparallel {stage ('Windows x86') {agent { label 'win_x86'}steps { unstash "win_x86"}library 'MyLibrary@v1.0.0'myLibraryExec("x86", "foo")}stage ('Windows x64') {agent { label 'win_x64'}steps { unstash "win_x64"}library 'MyLibrary@v1.0.0'myLibraryExec("x64", "bar")}}}}}{code}Error:{ code:java noformat }15:43:01 [Windows x64 Pkg] Loading library MyLibrary@v1.0.015:43:01 [Windows x64 Pkg] Loading library MyLibrary@v1.0.015:43:01 [Windows x64 Pkg] Attempting to resolve v1.0.0 from remote references...15:43:01 [Windows x64 Pkg] > git --version # timeout=1015:43:01 [Windows x64 Pkg] using GIT_ASKPASS to set credentials Jenkins Faceless Account15:43:01 [Windows x64 Pkg] > git ls-remote -h https://host/repo.git # timeout=1015:43:05 [Windows x86 Pkg] Only using first definition of
[JIRA] (JENKINS-54742) Can't load shared library more than once on parallel stages
Title: Message Title
William Laszlo created an issue
Jenkins / JENKINS-54742
Can't load shared library more than once on parallel stages
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
shared-objects-plugin
Created:
2018-11-21 07:00
Environment:
Jenkins ver. 2.121.1
Priority:
Minor
Reporter:
William Laszlo
I have two parallel stages that are using a shared library loaded on fly and I'm using it to upload some artifacts to somewhere else, but i'm getting an error. Simple Jenkinsfile:
pipeline {
agent none
stages {
stage ('Build') {
failFast true
parallel {
stage ('Windows x86') {
agent {
label 'win_x86'
}
steps {
bat "build_x86.bat"
dir ("${PACKAGE_DIR}") {
stash name: "win_x86"
}
}
}
stage ('Windows x64') {
agent {
label 'win_x64'
}
steps {
bat "build_x64.bat"
dir ("${PACKAGE_DIR}") {
stash name: "win_x64"
}
}
}
}
}
stage ('Tests') {
failFast true
parallel {
stage ('Windows x86') {
agent {
label 'win_x86'
}
steps {
[JIRA] (JENKINS-9366) Merge the functionality of plugins: Backup, thinBackup, Exclusive Execution - to create a single fully-functional backup plugin.
Title: Message Title Torsten Werner commented on JENKINS-9366 Re: Merge the functionality of plugins: Backup, thinBackup, Exclusive Execution - to create a single fully-functional backup plugin. There is a small problem when I use a dedicated volume for the backup: SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path '/var/backup/jenkins'. java.io.IOException: Failed to list contents of /var/lib/jenkins/lost+found at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1408) at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1426) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1389) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1310) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupAdditionalFiles(HudsonBackup.java:289) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:171) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:89) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.execute(ThinBackupPeriodicWork.java:70) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:53) at java.lang.Thread.run(Thread.java:748) The workaround is quite clear. On the other hand: 'lost+found' is a well known name, thinBackup should ignore it if it is unreadable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48327) Support for GitHub Organization style Project
Title: Message Title Daniel Gront stopped work on JENKINS-48327 Change By: Daniel Gront Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48327) Support for GitHub Organization style Project
Title: Message Title Daniel Gront started work on JENKINS-48327 Change By: Daniel Gront Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53868) Show full date and time when stage triggered
Title: Message Title Tommy Tynjä edited a comment on JENKINS-53868 Re: Show full date and time when stage triggered Proposed solution (with some additional refactorings): [[ https://github.com/Diabol/delivery-pipeline-plugin/pull/295 ||https://github.com/Diabol/delivery-pipeline-plugin/pull/295.] [https://github.com/Diabol/delivery-pipeline-plugin/pull/295|https://github.com/Diabol/delivery-pipeline-plugin/pull/295.] []|https://github.com/Diabol/delivery-pipeline-plugin/pull/295.] Adding absolute dates and times as a configurable option on the pipeline views (preserving the current relative dates and times as the default). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53868) Show full date and time when stage triggered
Title: Message Title Tommy Tynjä edited a comment on JENKINS-53868 Re: Show full date and time when stage triggered Proposed solution (with some additional refactorings): [ [ https://github.com/Diabol/delivery-pipeline-plugin/pull/295| | https://github.com/Diabol/delivery-pipeline-plugin/pull/295.] [https://github.com/Diabol/delivery-pipeline-plugin/pull/295|https://github.com/Diabol/delivery-pipeline-plugin/pull/295.] []|https://github.com/Diabol/delivery-pipeline-plugin/pull/295.] Adding absolute dates and times as a configurable option on the pipeline views (preserving the current relative dates and times as the default). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53868) Show full date and time when stage triggered
Title: Message Title Tommy Tynjä edited a comment on JENKINS-53868 Re: Show full date and time when stage triggered Proposed solution (with some additional refactorings): [https://github.com/Diabol/delivery-pipeline-plugin/pull/295 |https://github . com/Diabol/delivery-pipeline-plugin/pull/295. ]Adding absolute dates and times as a configurable option on the pipeline views (preserving the current relative dates and times as the default). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53868) Show full date and time when stage triggered
Title: Message Title Tommy Tynjä commented on JENKINS-53868 Re: Show full date and time when stage triggered Proposed solution (with some additional refactorings): https://github.com/Diabol/delivery-pipeline-plugin/pull/295. Adding absolute dates and times as a configurable option on the pipeline views (preserving the current relative dates and times as the default). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54701) Support branch indexing and branch event trigger causes
Title: Message Title Tommy Tynjä updated JENKINS-54701 Proposed solution merged to master. Will be part of next release of the delivery pipeline plugin. Jenkins / JENKINS-54701 Support branch indexing and branch event trigger causes Change By: Tommy Tynjä Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54738) Unable to view console because of Jelly error
Title: Message Title jam lee commented on JENKINS-54738 Re: Unable to view console because of Jelly error i got the error too. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54711) jenkins-jobs.mv.db failed
Title: Message Title Владислав Ненашев commented on JENKINS-54711 Re: jenkins-jobs.mv.db failed Pipeline Maven plugin 3.5.12 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-44715) Pipeline plugin won't get updated PR github title
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-44715 Re: Pipeline plugin won't get updated PR github title The "edited" action of PR events does not trigger a refresh of a [PR job metadata](https://github.com/jenkinsci/branch-api-plugin/blob/branch-api-2.1.1/src/main/java/jenkins/branch/BranchNameContributor.java). However, those metadata would be refreshed by Branch Indexing since branch indexing observes PRs and [refreshes metadata](https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.4.1/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L2093-L2098) accordingly (even if a build is not to be triggered because there is no changes). Note: A workaround would be to use the GIT REST API to get information about the PR instead of relying on the `CHANGE_TITLE` variable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54741) JVM version column of agent running Java is blank
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-54741 JVM version column of agent running Java is blank Issue Type: Bug Assignee: Baptiste Mathus Attachments: jvm-11-not-listed.png Components: versioncolumn-plugin Created: 2018-11-21 03:00 Environment: Jenkins 2.152 on Java 11 (from the docker image, for example) See https://github.com/MarkEWaite/docker-lfs/tree/lts-slimjdk11-with-plugins for my precise configuration Labels: java11 Priority: Minor Reporter: Mark Waite The versioncolumn plugin helps me detect outdated agent jar files and outdated java virtual machines running agents. Unfortunately, the JVM version column is empty when running the master on Java 11 with an agent running Java 11. The version column is not empty if the agent is running Java 8 and master Java 11. The version column is not empty if the agent is running Java 8 and the master Java 8. See
[JIRA] (JENKINS-54159) Support configuration as code plugin
Title: Message Title Jie Shen commented on JENKINS-54159 Re: Support configuration as code plugin Tim Jacomb yes, but instead of starting from vm plugin, I will start from some basic plugins because Azure Jenkins plugins have dependencies from each other. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53127) Parallel sequential stages should display stage label
Title: Message Title Hokwang Lee commented on JENKINS-53127 Re: Parallel sequential stages should display stage label Thank you for your dedication. Nicolae Pascu By the way, when will this fix release? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53127) Parallel sequential stages should display stage label
Title: Message Title Nicolae Pascu updated JENKINS-53127 Jenkins / JENKINS-53127 Parallel sequential stages should display stage label Change By: Nicolae Pascu Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54694) PTC integrity plugin throw error for project not registered in the current server
Title: Message Title jian gao updated an issue Jenkins / JENKINS-54694 PTC integrity plugin throw error for project not registered in the current server Change By: jian gao when I create a job for integrity and do build, but the console output display as following:Started by user Administrator Building in workspace C:\Program Files (x86)\Jenkins\workspace\integrityDocs [Local Client] Checkout started using local client for :/Projects Preparing to execute si projectinfo for /Projects [Local Client] An API Exception was caught! The project /Projects could not be located on the server CYSVR037ALM01:7001: MKS125211: The project file /Projects is not registered with the current server. si projectinfo --user=administrator --port=7001 --hostname=CYSVR037ALM01 --project=/Projects – returned exit code 128 ERROR: [Local Client] Caught Integrity APIException! Finished: FAILURE Can anyone Who can help me on this issue? thanks in advance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54740) Jenkins running build for every branch in repository.
Title: Message Title Mark Waite commented on JENKINS-54740 Re: Jenkins running build for every branch in repository. I suspect that the build.xml files from each build in the repository record the SHA1 hash(es) of the build. I haven't investigated deeply to confirm that, but that is my suspicion. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54740) Jenkins running build for every branch in repository.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54740 Jenkins running build for every branch in repository. Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54740) Jenkins running build for every branch in repository.
Title: Message Title
michael giroux created an issue
Jenkins / JENKINS-54740
Jenkins running build for every branch in repository.
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2018-11-21 00:13
Environment:
Jenkins 2.138.3 Git-Plugin 3.9.1 Linux ${HOSTNAME} 3.10.0-862.14.4.el7.x86_64 #1 SMP Fri Sep 21 09:07:21 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Priority:
Minor
Reporter:
michael giroux
User has configured a job with branch specifier "**". When the user ran the build, Jenkins ran a build for every branch in the repository. We've seen this before. The twist here is that we upgraded the Jenkins hardware, and Jenkins version. We did an rsync of the old jenkins data directory to the new server. On the old server, the job only ran when a new commit was pushed to the repository, and only the branch that changed. This ticket is more of a question than a problem since we expect this for a fresh install, but we were surprised that the builds were running for every branch since we copied the original workspace. The question than is how does jenkins keep track of which branches/commits have been built? What additional files, and/or precautions do we need to take to make sure this does not happen again. We are unable to locate any documentation that explains exactly how the git plugin manages to keep track of which commits have been build.
[JIRA] (JENKINS-54739) Accessing tests from BlueOcean UI results in http threads pegging cpu in TreeMap.java (put)
Title: Message Title Harry Weppner created an issue Jenkins / JENKINS-54739 Accessing tests from BlueOcean UI results in http threads pegging cpu in TreeMap.java (put) Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2018-11-20 at 2.32.19 PM.png, Screen Shot 2018-11-20 at 3.42.18 PM.png Components: core Created: 2018-11-20 23:57 Environment: OS: 4.14.47-56.37.amzn1.x86_64 JRE: Java: Java(TM) SE Runtime Environment, 1.8.0_192-b12 Jenkins: 2.147 BlueOcean: 1.9.0 Priority: Critical Reporter: Harry Weppner Accessing tests from the BlueOcean UI results in five http requests to be spinning in TreeMap.java:568. It's not yet clear what environment change caused this but it's a severe issue so I am reporting it here asap. Add Comment
[JIRA] (JENKINS-54711) jenkins-jobs.mv.db failed
Title: Message Title Cyrille Le Clerc started work on JENKINS-54711 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54669) Use sensible defaults settings for the datasource configuration
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-54669 Use sensible defaults settings for the datasource configuration Change By: Cyrille Le Clerc Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54437) Add support for MySql database
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-54437 Add support for MySql database Change By: Cyrille Le Clerc Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs Vincent Massol Can you upgrade to the pipeline maven plugin v3.6.1 and use a MySQL database instead of the embedded H2 database as documented in Pipeline Maven Plugin Setup > Using a MySQL Database (since 3.6.0) ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54437) Add support for MySql database
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-54437 Re: Add support for MySql database Delivered in 3.6.0Setup documented in " [Pipeline Maven Plugin Setup > Using a MySQL Database (since 3.6.0)|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-UsingaMySQLDatabase(since3.6.0)] " ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54026) Database maybe alredy in use "Server is running"(pipeline+maven)
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-54026 Re: Database maybe alredy in use "Server is running"(pipeline+maven) MySQL database support available in 3.6.0 .[~xed] Can you use a MySQL database with the Pipeline Maven Plugin instead of the embedded H2 database as documented in "[Pipeline Maven Plugin Setup > Using a MySQL Database (since 3.6.0)|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-UsingaMySQLDatabase(since3.6.0)]" ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54437) Add support for MySql database
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-54437 Re: Add support for MySql database Delivered in 3.6.0 Setup documented in [Pipeline Maven Plugin Setup > Using a MySQL Database (since 3.6.0)|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-UsingaMySQLDatabase(since3.6.0)] ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54711) jenkins-jobs.mv.db failed
Title: Message Title Cyrille Le Clerc commented on JENKINS-54711 Re: jenkins-jobs.mv.db failed The filesystem of your jenkins home (/u01/jenkins/jenkins_home/) seem to cause problems to the embedded H2 database. Can you use a MySQL database with the Pipeline Maven Plugin instead of the embedded H2 database as documented in Pipeline Maven Plugin Setup > Using a MySQL Database (since 3.6.0) ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54711) jenkins-jobs.mv.db failed
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-54711
jenkins-jobs.mv.db failed
Change By:
Cyrille Le Clerc
Hi, we got the following problem: we see a problem in the jenkins log, the file update date was more than a day in the system, in a temporary solution, the jenkins was restarted, after a while it continued to appear.Jenkins 2.138.2The log in the attachment{noformat}SELECT ID FROM JENKINS_BUILD WHERE JOB_ID=? AND NUMBER=? [5-196]SELECT ID FROM JENKINS_BUILD WHERE JOB_ID=? AND NUMBER=? [5-196] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:168) at org.h2.message.DbException.convert(DbException.java:295) at org.h2.command.Command.executeQuery(Command.java:215) at org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111) at org.jenkinsci.plugins.pipeline.maven.dao.PipelineMavenPluginH2Dao.getOrCreateBuildPrimaryKey(PipelineMavenPluginH2Dao.java:400) ... 19 moreCaused by: java.lang.IllegalStateException: Reading from nio:/u01/jenkins/jenkins_home/jenkins-jobs/jenkins-jobs.mv.db failed; file length -1 read length 512 at 99917712 [1.4.196/1] at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:765) at org.h2.mvstore.DataUtils.readFully(DataUtils.java:435) at org.h2.mvstore.FileStore.readFully(FileStore.java:98) at org.h2.mvstore.Page.read(Page.java:190) at org.h2.mvstore.MVStore.readPage(MVStore.java:1952) at org.h2.mvstore.MVMap.readPage(MVMap.java:741) at org.h2.mvstore.Page.getChildPage(Page.java:217) at org.h2.mvstore.Cursor.min(Cursor.java:129) at org.h2.mvstore.Cursor.hasNext(Cursor.java:36) at org.h2.mvstore.db.TransactionStore$TransactionMap$1.fetchNext(TransactionStore.java:1392) at org.h2.mvstore.db.TransactionStore$TransactionMap$1.(TransactionStore.java:1388) at org.h2.mvstore.db.TransactionStore$TransactionMap.keyIterator(TransactionStore.java:1383) at org.h2.mvstore.db.TransactionStore$TransactionMap.keyIterator(TransactionStore.java:1371) at org.h2.mvstore.db.MVSecondaryIndex.find(MVSecondaryIndex.java:309) at org.h2.mvstore.db.MVSecondaryIndex.find(MVSecondaryIndex.java:254) at org.h2.index.BaseIndex.find(BaseIndex.java:128) at org.h2.index.IndexCursor.find(IndexCursor.java:169) at org.h2.table.TableFilter.next(TableFilter.java:468) at org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452) at org.h2.result.LazyResult.hasNext(LazyResult.java:79) at org.h2.result.LazyResult.next(LazyResult.java:59) at org.h2.command.dml.Select.queryFlat(Select.java:519) at org.h2.command.dml.Select.queryWithoutCache(Select.java:625) at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114) at org.h2.command.dml.Query.query(Query.java:371) at org.h2.command.dml.Query.query(Query.java:333) at org.h2.command.CommandContainer.query(CommandContainer.java:113) at org.h2.command.Command.executeQuery(Command.java:201)
[JIRA] (JENKINS-54711) jenkins-jobs.mv.db failed
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-54711
jenkins-jobs.mv.db failed
Change By:
Cyrille Le Clerc
Hi, we got the following problem: we see a problem in the jenkins log, the file update date was more than a day in the system, in a temporary solution, the jenkins was restarted, after a while it continued to appear.Jenkins 2.138.2The log in the attachment{noformat}SELECT ID FROM JENKINS_BUILD WHERE JOB_ID=? AND NUMBER=? [5-196]SELECT ID FROM JENKINS_BUILD WHERE JOB_ID=? AND NUMBER=? [5-196] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:168) at org.h2.message.DbException.convert(DbException.java:295) at org.h2.command.Command.executeQuery(Command.java:215) at org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111) at org.jenkinsci.plugins.pipeline.maven.dao.PipelineMavenPluginH2Dao.getOrCreateBuildPrimaryKey(PipelineMavenPluginH2Dao.java:400)... 19 moreCaused moreCaused by: java.lang.IllegalStateException: Reading from nio:/u01/jenkins/jenkins_home/jenkins-jobs/jenkins-jobs.mv.db failed; file length -1 read length 512 at 99917712 [1.4.196/1] at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:765) at org.h2.mvstore.DataUtils.readFully(DataUtils.java:435) at org.h2.mvstore.FileStore.readFully(FileStore.java:98) at org.h2.mvstore.Page.read(Page.java:190) at org.h2.mvstore.MVStore.readPage(MVStore.java:1952) at org.h2.mvstore.MVMap.readPage(MVMap.java:741) at org.h2.mvstore.Page.getChildPage(Page.java:217) at org.h2.mvstore.Cursor.min(Cursor.java:129) at org.h2.mvstore.Cursor.hasNext(Cursor.java:36) at org.h2.mvstore.db.TransactionStore$TransactionMap$1.fetchNext(TransactionStore.java:1392) at org.h2.mvstore.db.TransactionStore$TransactionMap$1.(TransactionStore.java:1388) at org.h2.mvstore.db.TransactionStore$TransactionMap.keyIterator(TransactionStore.java:1383) at org.h2.mvstore.db.TransactionStore$TransactionMap.keyIterator(TransactionStore.java:1371) at org.h2.mvstore.db.MVSecondaryIndex.find(MVSecondaryIndex.java:309) at org.h2.mvstore.db.MVSecondaryIndex.find(MVSecondaryIndex.java:254) at org.h2.index.BaseIndex.find(BaseIndex.java:128) at org.h2.index.IndexCursor.find(IndexCursor.java:169) at org.h2.table.TableFilter.next(TableFilter.java:468) at org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452) at org.h2.result.LazyResult.hasNext(LazyResult.java:79) at org.h2.result.LazyResult.next(LazyResult.java:59) at org.h2.command.dml.Select.queryFlat(Select.java:519) at org.h2.command.dml.Select.queryWithoutCache(Select.java:625) at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114) at org.h2.command.dml.Query.query(Query.java:371) at org.h2.command.dml.Query.query(Query.java:333) at org.h2.command.CommandContainer.query(CommandContainer.java:113) at org.h2.command.Command.executeQuery(Command.java:201) ... 21 moreCaused by: java.nio.channels.ClosedChannelException at
[JIRA] (JENKINS-54711) jenkins-jobs.mv.db failed
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-54711
jenkins-jobs.mv.db failed
Change By:
Cyrille Le Clerc
Hi, we got the following problem: we see a problem in the jenkins log, the file update date was more than a day in the system, in a temporary solution, the jenkins was restarted, after a while it continued to appear.Jenkins 2.138.2The log in the attachment { code:java noformat }SELECT ID FROM JENKINS_BUILD WHERE JOB_ID=? AND NUMBER=? [5-196]SELECT ID FROM JENKINS_BUILD WHERE JOB_ID=? AND NUMBER=? [5-196]at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)at org.h2.message.DbException.get(DbException.java:168)at org.h2.message.DbException.convert(DbException.java:295)at org.h2.command.Command.executeQuery(Command.java:215)at org.h2.jdbc.JdbcPreparedStatement.executeQuery(JdbcPreparedStatement.java:111)at org.jenkinsci.plugins.pipeline.maven.dao.PipelineMavenPluginH2Dao.getOrCreateBuildPrimaryKey(PipelineMavenPluginH2Dao.java:400) ... 19 moreCaused by: java.lang.IllegalStateException: Reading from nio:/u01/jenkins/jenkins_home/jenkins-jobs/jenkins-jobs.mv.db failed; file length -1 read length 512at 99917712 [1.4.196/1]at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:765)at org.h2.mvstore.DataUtils.readFully(DataUtils.java:435)at org.h2.mvstore.FileStore.readFully(FileStore.java:98)at org.h2.mvstore.Page.read(Page.java:190)at org.h2.mvstore.MVStore.readPage(MVStore.java:1952)at org.h2.mvstore.MVMap.readPage(MVMap.java:741)at org.h2.mvstore.Page.getChildPage(Page.java:217)at org.h2.mvstore.Cursor.min(Cursor.java:129)at org.h2.mvstore.Cursor.hasNext(Cursor.java:36)at org.h2.mvstore.db.TransactionStore$TransactionMap$1.fetchNext(TransactionStore.java:1392)at org.h2.mvstore.db.TransactionStore$TransactionMap$1.(TransactionStore.java:1388)at org.h2.mvstore.db.TransactionStore$TransactionMap.keyIterator(TransactionStore.java:1383)at org.h2.mvstore.db.TransactionStore$TransactionMap.keyIterator(TransactionStore.java:1371)at org.h2.mvstore.db.MVSecondaryIndex.find(MVSecondaryIndex.java:309)at org.h2.mvstore.db.MVSecondaryIndex.find(MVSecondaryIndex.java:254)at org.h2.index.BaseIndex.find(BaseIndex.java:128)at org.h2.index.IndexCursor.find(IndexCursor.java:169)at org.h2.table.TableFilter.next(TableFilter.java:468)at org.h2.command.dml.Select$LazyResultQueryFlat.fetchNextRow(Select.java:1452)at org.h2.result.LazyResult.hasNext(LazyResult.java:79)at org.h2.result.LazyResult.next(LazyResult.java:59)at org.h2.command.dml.Select.queryFlat(Select.java:519)at org.h2.command.dml.Select.queryWithoutCache(Select.java:625)at org.h2.command.dml.Query.queryWithoutCacheLazyCheck(Query.java:114)at org.h2.command.dml.Query.query(Query.java:371)at org.h2.command.dml.Query.query(Query.java:333)at org.h2.command.CommandContainer.query(CommandContainer.java:113)at
[JIRA] (JENKINS-44715) Pipeline plugin won't get updated PR github title
Title: Message Title Gordon Shieh updated JENKINS-44715 Jenkins / JENKINS-44715 Pipeline plugin won't get updated PR github title Change By: Gordon Shieh Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-44715) Pipeline plugin won't get updated PR github title
Title: Message Title Gordon Shieh started work on JENKINS-44715 Change By: Gordon Shieh Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Flemming Steffensen commented on JENKINS-54729 Re: jenkins dashboard displays stacktrace I just upgraded the ssh-slave from 1.28.1 to 1.29.1, and immediately got the same stack-trace. Downgrading to 1.29.0 also produced the stack-trace. Finally, back on 1.28.1, everything is back to normal. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Flemming Steffensen commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core I just upgraded the ssh-slave from 1.28.1 to 1.29.1, and immediately got the same stack-trace. Downgrading to 1.29.0 also produced the stack-trace. Finally, back on 1.28.1, everything is back to normal. On each of the above mentioned versions, I've tested both trilead-api 1.0.0 and 1.0.1 - but this plugin version does not seem to affect the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-44715) Pipeline plugin won't get updated PR github title
Title: Message Title Gordon Shieh commented on JENKINS-44715 Re: Pipeline plugin won't get updated PR github title Joe Harte I've created a pull request that addresses this issue. https://github.com/jenkinsci/github-branch-source-plugin/pull/192 we'll see how the review process goes, and if it makes it into master... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Flemming Steffensen commented on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 I just upgraded the ssh-slave from 1.28.1 to 1.29.1, and immediately got the same stack-trace. Downgrading to 1.29.0 also produced the stack-trace. Finally, back on 1.28.1, everything is back to normal. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54738) Unable to view console because of Jelly error
Title: Message Title
Keith Bertelsen updated an issue
Jenkins / JENKINS-54738
Unable to view console because of Jelly error
Change By:
Keith Bertelsen
I am unable to view console logs in Jenkins itself (though getting the raw logs works fine). The stack trace error is: {{ org.apache.commons.jelly.JellyTagException: jar: [ file:/Users/bertelsk/.jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/hudson/model/Run/console.jelly:65:27: |file:///Users/bertelsk/.jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/hudson/model/Run/console.jelly:65:27:] com/trilead/ssh2/crypto/Base64 }} {{ at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) }} {{ at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) }} {{ at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) }} {{ at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) }} {{ at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) }} {{ at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) }} {{ at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at
[JIRA] (JENKINS-54738) Unable to view console because of Jelly error
Title: Message Title
Keith Bertelsen updated an issue
Jenkins / JENKINS-54738
Unable to view console because of Jelly error
Change By:
Keith Bertelsen
I am unable to view console logs in Jenkins itself (though getting the raw logs works fine). The stack trace error is: ``` {{ org.apache.commons.jelly.JellyTagException: jar:file:/Users/bertelsk/.jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/hudson/model/Run/console.jelly:65:27: com/trilead/ssh2/crypto/Base64 at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-54738) Unable to view console because of Jelly error
Title: Message Title
Keith Bertelsen updated an issue
Jenkins / JENKINS-54738
Unable to view console because of Jelly error
Change By:
Keith Bertelsen
I am unable to view console logs in Jenkins itself (though getting the raw logs works fine). The stack trace error is: {{org.apache.commons.jelly.JellyTagException: jar: [ file:/Users/bertelsk/.jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/hudson/model/Run/console.jelly:65:27: |file:///Users/bertelsk/.jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/hudson/model/Run/console.jelly:65:27:] com/trilead/ssh2/crypto/Base64 }} {{ at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) }} {{ at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) }} {{ at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) }} {{ at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) }} {{ at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) }} {{ at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) }} {{ at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) }} {{ at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) }} {{ at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) }} {{ at
[JIRA] (JENKINS-54738) Unable to view console because of Jelly error
Title: Message Title Keith Bertelsen created an issue Jenkins / JENKINS-54738 Unable to view console because of Jelly error Issue Type: Bug Assignee: Praqma Support Components: logging-plugin Created: 2018-11-20 21:18 Environment: macOS 10.14; Java 1.8.0_192; Jenkins 2.152 with default plugins Labels: consoleoutput Priority: Minor Reporter: Keith Bertelsen I am unable to view console logs in Jenkins itself (though getting the raw logs works fine). The stack trace error is: ``` org.apache.commons.jelly.JellyTagException: jar:file:/Users/bertelsk/.jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/hudson/model/Run/console.jelly:65:27: com/trilead/ssh2/crypto/Base64 at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title Ulli Hafner commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config The warnings-ng plugin uses a different library now (it replaces analysis-core). It would be great if you can check the beta if it resolves your problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54736) Show errors of pmd.xml file
Title: Message Title Ulli Hafner commented on JENKINS-54736 Re: Show errors of pmd.xml file I see, I never encountered a PMD error in my code The parser currently reads only violations... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54736) Show errors of pmd.xml file
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-54736 Show errors of pmd.xml file Change By: Ulli Hafner Component/s: analysis-model Component/s: warnings-ng-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54711) jenkins-jobs.mv.db failed
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-54711 jenkins-jobs.mv.db failed Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54159) Support configuration as code plugin
Title: Message Title Tim Jacomb commented on JENKINS-54159 Re: Support configuration as code plugin Jie Shen are you working on this? / any updates? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17116) gracefull job termination
Title: Message Title Victor Magana commented on JENKINS-17116 Re: gracefull job termination Hello, I'm seeing an error in the hudson.util.ProcessTree logger, "External Ctrl+C execution failed for process pid=3872. Ctrl+C process exited with code -1073741515: Failed to attach to the console". Is there any option/parameter that needs to be set for this to attach and send the Ctrl+C signal. I'm running Jenkins Server on Windows 7x64 version 2.150. Running a Windows batch job on the local master that executes a python script. Also ran as Execute Python Script job, same error. Thanks for any help. Failed to send CTRL+C to pid=3872 org.jvnet.winp.WinpException: External Ctrl+C execution failed for process pid=3872. Ctrl+C process exited with code -1073741515: Failed to attach to the console (see the AttachConsole WinAPI call). error=0 at winp.cpp:59 at org.jvnet.winp.Native.sendCtrlC(Native Method) at org.jvnet.winp.Native.sendCtrlC(Native.java:90) at org.jvnet.winp.WinProcess.sendCtrlC(WinProcess.java:93) at hudson.util.ProcessTree$WindowsOSProcess.killSoftly(ProcessTree.java:538) at hudson.util.ProcessTree$WindowsOSProcess.killRecursively(ProcessTree.java:517) at hudson.util.ProcessTree.killAll(ProcessTree.java:168) at hudson.Proc$LocalProc.destroy(Proc.java:384) at hudson.Proc$LocalProc.join(Proc.java:357) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1810) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-54289) Create year-round GSoC schedule
Title: Message Title Lloyd Chang commented on JENKINS-54289 Re: Create year-round GSoC schedule re: Org Admin entries, they should be in the Org Admin guidelines (in a Google Doc that Oleg Nenashev is writing), hence I removed them from the AsciiDoc. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54289) Create year-round GSoC schedule
Title: Message Title Lloyd Chang edited a comment on JENKINS-54289 Re: Create year-round GSoC schedule I created an AsciiDoc for Jenkins year round GSoC schedule via https://github.com/ jenkins-infra/jenkins.io # /pull/ 1898 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Mashrur mia commented on JENKINS-54729 Re: jenkins dashboard displays stacktrace while I do get the exact same stacktrace on console out, the plaintext output shows everything as normal. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54289) Create year-round GSoC schedule
Title: Message Title Lloyd Chang commented on JENKINS-54289 Re: Create year-round GSoC schedule I created an AsciiDoc for Jenkins year round GSoC schedule via jenkins-infra/jenkins.io#1898 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54289) Create year-round GSoC schedule
Title: Message Title Lloyd Chang updated JENKINS-54289 Jenkins / JENKINS-54289 Create year-round GSoC schedule Change By: Lloyd Chang Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54289) Create year-round GSoC schedule
Title: Message Title Lloyd Chang updated an issue Jenkins / JENKINS-54289 Create year-round GSoC schedule Change By: Lloyd Chang A year - round GSoC schedule would help direct efforts both outside and during the GSoC official timeline. For example, this "schedule" should associate a time of year to each one of these: * Org Admins ** setup a regular meeting with mentors to check on progress and on the process *** ensure mentors follow the mentor guidelines *** make sure mentors have what they need *** ensure all mentors are still engaged ** setup regular (once per coding period? every other week?) meeting of all students and all mentors ** ensure this "schedule" aligns with timeline published by Google at [ https://developers.google.com/open-source/gsoc/timeline ] * Mentor and project champion recruitment ** period of the year when we actively search for mentors from various sources like SIGs and mailing list * Call for GSoC project proposals/mentors ** period of year where we pro-actively seek for project proposals ** pre-book SMEs, ask them to make a few hours per coding phase in their schedule (even more so if their SIG participates in GSoC) ** Form mentor groups * Community bounding ** have co-mentors agree on project general direction before talking to students ** Explicitly state that design work needs to happen during this phase ** Do pair coding to get student going * A schedule of communications to students and mentors ** List of what mentors need to discuss with students (e.g. eligibility check such as CPT) ** When to send deadline reminders ** When to send expectation reminders ** When to setup office hours * Post GSoC activities schedule ** review and retrospective ** keeping the student engaged by giving more responsibilities and more ownership ** create epic of remaining work (perhaps do this at end of last coding phase) ** create a path for students to become mentors, and see their project continue in next GSoC * Presence at Jenkins World Conferences * Swag shipping schedule * Personalized thank you letters to all participants schedule (at end of application period, at end of last coding period) Add Comment
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Adam Lock commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Any update on this? The workaround seems like it could become a concern. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54596) can't parse argument number: changelog.url
Title: Message Title Paul Deauna assigned an issue to Paul Deauna Jenkins / JENKINS-54596 can't parse argument number: changelog.url Change By: Paul Deauna Assignee: Paul Deauna Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54289) Create year-round GSoC schedule
Title: Message Title Lloyd Chang updated an issue Jenkins / JENKINS-54289 Create year-round GSoC schedule Change By: Lloyd Chang Summary: Create year - round GSoC schedule Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Quinn Mikelson commented on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Same issue using Jenkins ver. 2.138.3 and Bitbucket plugin version 2.2.14 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title
Nikolas Falco edited a comment on JENKINS-54668
Re: Unable to provide NodeJS path to Jenkins plugin
is /usr/local/nodejs accessible by jenkins user?How PATH and NODEJS-HOME environment variable are setup inside a shell script step? Did you tick the "provide Node & npm bin/ folder to PATH" ? Are the node and npm command marked as executable attribute (try with 755)? You had wrote node is already in the your PATH so if you run from an ssh shell:{{/usr/local/bin/node -v}}or{{/usr/local/nodejs/bin/node -v}}I expect it works and wrote the version.In jenkins create a new Freestyle job and add a shell step that execute both command with full path, if not work than something from in Jenkins not related with nodejs plugin When you ask help it is useful any detailed explanation.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Nikolas Falco commented on JENKINS-54668 Re: Unable to provide NodeJS path to Jenkins plugin I spent some minutes to perform a test. I have download the windows zip distribution node-v10.13.0-win-x64.zip unzip it in download folder D:\Downloads\node-v10.13.0-win-x64 add a new NodeJS tool definition in Manage Jenkins installation without disabling "Automatic install" and provide D:\Downloads\node-v10.13.0-win-x64 as installation folder. Create a new Freestyle Job tick "Provide Node & npm bin/ folder to PATH" add a windows batch shell step put set %PATH% set %NODEJS_HOME%" node -v and the node executable was of the expected version 10.13.0 because I have installed in the system NodeJS 8.11.1, but the specified as jenkins tools wins over installed. Started by user anonymous Building in workspace D:\git\nodejs-plugin\work\workspace\node [node] $ cmd /c call C:\Users\NIKOLA~1\AppData\Local\Temp\jenkins8164397220893305286.bat D:\git\nodejs-plugin\work\workspace\node>echo C:\Program Files\Java\jdk1.8.0/bin;D:\Downloads\node-v10.13.0-win-x64;C:\Program Files\Java\jdk1.8.0/bin;C:/Program Files/Java/bin/server;C:/Program Files/Java/bin;C:/Program Files/Java/lib/amd64;C:\Program Files\Docker\Docker\Resources\bin;C:\ProgramData\Oracle\Java\javapath;D:\Programs\Python3 D:\git\nodejs-plugin\work\workspace\node>echo D:\Downloads\node-v10.13.0-win-x64 D:\Downloads\node-v10.13.0-win-x64 D:\git\nodejs-plugin\work\workspace\node>node -v v10.13.0 D:\git\nodejs-plugin\work\workspace\node>exit 0 Finished: SUCCESS Add Comment
[JIRA] (JENKINS-54729) jenkins dashboard displays stacktrace
Title: Message Title Kurt Routley edited a comment on JENKINS-54729 Re: jenkins dashboard displays stacktrace I also saw this issue on [CloudBees Jenkins Enterprise 2.121.1.2-rolling|https://release-notes.cloudbees.com/product/CloudBees+Jenkins+Enterprise] , upgrading to SSH Slaves Plugin 1.29.1 at [https://updates.jenkins.io/download/plugins/ssh-slaves/1.29.1/ssh-slaves.hpi] resolved it. We observed this issue after attempting to update to Pipeline Plugin 2.33 and restarting Jenkins. Likely a new SSH Slaves plugin had been uploaded previously and we didn't notice in the pending updates requiring restart. Uncertain what the SSH Slaves plugin version was that would have caused the issues, but 1.29.1 resolves it for certain.Initial attempt to fix was to rollback Pipeline Plugin to 2.32, this does not resolve the issue, so can rule out that plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Kurt Routley updated an issue Jenkins / JENKINS-54729 jenkins dashboard displays stacktrace Change By: Kurt Routley Component/s: ssh-slaves-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Kurt Routley commented on JENKINS-54729 Re: jenkins dashboard displays stacktrace I also saw this issue on CloudBees Jenkins Enterprise 2.121.1.2-rolling , upgrading to SSH Slaves Plugin 1.29.1 at https://updates.jenkins.io/download/plugins/ssh-slaves/1.29.1/ssh-slaves.hpi resolved it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Nikolas Falco commented on JENKINS-54668 Re: Unable to provide NodeJS path to Jenkins plugin is /usr/local/nodejs accessible by jenkins user? How PATH and NODEJS-HOME environment variable are setup inside a shell script step? Did you tick the "provide Node & npm bin/ folder to PATH" ? When you ask help it is useful any detailed explanation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54737) Internal post stages are not reported in the stage view
Title: Message Title
Ben Goldsmith created an issue
Jenkins / JENKINS-54737
Internal post stages are not reported in the stage view
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2018-11-20 18:13
Priority:
Minor
Reporter:
Ben Goldsmith
If you have nested post blocks within a declarative pipeline, none of them are included in the overall timing for the stage view, which can be confusing if there is a particularly long internal post block that runs. For example, see the below declarative pipeline JenkinsFile I would expect to get a break down for the post stages indicating how much time was spent in them, especially if there are a number of post stages that take some time (such as running sonarQube).
pipeline {
agent any
stages {
stage ('Common Environment Setup') {
steps {
echo 'common setup'
}
}
stage ('Parallel Stage Execution') {
parallel {
stage('Parallel Stage 1') {
steps {
echo 'in parallel stage 1'
}
post {
failure {
echo 'alert that parallel stage 1 failed'
}
}
}
stage ('Parallel Stage 2') {
steps {
echo 'in parallel stage 2'
}
post {
failure {
echo 'alert that parallel stage 2 failed'
}
}
}
}
post {
[JIRA] (JENKINS-54628) Poll error when no view in Manual workspace for stream
Title: Message Title Dave Miller commented on JENKINS-54628 Re: Poll error when no view in Manual workspace for stream Checkout step: checkout ( changelog: false, poll: false, scm: perforce( credential: 'p4svcacct', populate: forceClean( have: true, revert: true, parallel: [ enable: true, minbytes: '1024', minfiles: '1', threads: '4' ], pin: env.BUILD_CHANGELIST, quiet: false ), workspace: manualSpec( charset: 'none', name: env.BUILD_WORKSPACE_NAME, syncID: env.JOB_NAME, pinHost: false, spec: clientSpec( allwrite: true, line: 'UNIX', streamName: '//depot/dev_jenkins_build', view: '' ) ) ) ) Step log: ... p4 client -o jenkins-mac-build-1-polling-testing-2 + ... p4 info + ... p4 info + ... p4 client -i + P4: Unable to setup workspace: java.lang.NullPointerException ... p4 counter change + ... p4 changes -m1 -ssubmitted //jenkins-mac-build-1-polling-testing-2/... + ... p4 repos -C + Building on Node: mac-build-1 ... p4 client -o jenkins-mac-build-1-polling-testing-2 + ... p4 info + ... p4 info + ... p4 client -i + P4: Unable to setup workspace: java.lang.NullPointerException P4 Task: establishing connection. ... server: perforce.example.com:1666 ... node: MAC-BUILD-1.local P4 Task: reverting all pending and shelved revisions. ... p4 revert /jenkins/workspace/polling-testing/... + ... rm [abandoned files] duration: (13ms) ... p4 sync /jenkins/workspace/polling-testing/...#none + ... rm -rf /jenkins/workspace/polling-testing P4 Task: syncing files at change: 65549 ... p4 sync --parallel=threads=4,min=1,minsize=1024 -f /jenkins/workspace/polling-testi___ + duration: 0m 50s Add Comment
[JIRA] (JENKINS-46882) Scripts not permitted to use new java.lang.Exception java.lang.String
Title: Message Title Richard Lee commented on JENKINS-46882 Re: Scripts not permitted to use new java.lang.Exception java.lang.String Using script-security 1.44, but getting org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.lang.IllegalArgumentException java.lang.String Shouldn't that be allowed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54736) Show errors of pmd.xml file
Title: Message Title Jordi Llach created an issue Jenkins / JENKINS-54736 Show errors of pmd.xml file Issue Type: Improvement Assignee: Ulli Hafner Attachments: pmd.xml Components: warnings-ng-plugin Created: 2018-11-20 17:46 Priority: Major Reporter: Jordi Llach When using pmd, pmd-jsp, we often encounter JSPs that are so broken that can not even be parsed. Those errors are contained in the pmd.xml file but are not shown in the ui, I attach a sample pmd.xml file Add Comment
[JIRA] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
Steve Mokris edited a comment on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
A workaround in the meantime: { { code} retry(5) { }} {{ ret = sh returnStatus: true, script: 'some-failure-prone-script' }} {{ if (ret) { }} {{ sleep time: 30, unit: 'SECONDS' }} {{ error ' }}{{ some-failure-prone-script failed' }} {{ } }} {{ } {code } } …but there's no way to know when we're on the last retry attempt (see JENKINS-49341), so it unnecessarily waits 30 seconds when after the last retry attempt fails.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
Steve Mokris commented on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
A workaround in the meantime: retry(5) { ret = sh returnStatus: true, script: 'some-failure-prone-script' if (ret) { sleep time: 30, unit: 'SECONDS' error 'some-failure-prone-script failed' {{ }}} {{ }}} …but there's no way to know when we're on the last retry attempt (see JENKINS-49341), so it unnecessarily waits 30 seconds when the last retry attempt fails.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-54311) Create user with . in name doesn't work
Title: Message Title Alba Mendez commented on JENKINS-54311 Re: Create user with . in name doesn't work Okay it's from design. This is the relevant security change in 2.121 that restricts usernames: Setting the mentioned hudson.security.HudsonPrivateSecurityRealm.ID_REGEX system property at startup to ^[a-zA-Z0-9_.-]+$ works An error message like "Invalid username. By default, usernames must only contain alphanumeric characters, underscore and dash." should be shown. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title Steve Mokris created an issue Jenkins / JENKINS-54735 Pipeline retry clause: optionally delay between retries Issue Type: Improvement Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2018-11-20 17:24 Labels: pipeline Priority: Major Reporter: Steve Mokris I use a retry block to perform requests on a remote server that I don't control (e.g., Apple's Code Signing or Notarization service), and sometimes that remote server is offline. Currently retry immediately retries upon failure, so when the remote server is offline for an extended period of time, my pipeline project quickly retries and then the build fails. It would be nice to have the ability to make retry wait after each failure, with optional exponential backoff (doubling the wait time after each failure), to give these builds a greater chance of success. For example: retry(tries:5, waitSecondsBetweenFailures:30, doubleWaitTimeAfterEachFailure:true) Add Comment
[JIRA] (JENKINS-54731) Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-54731 Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts Change By: Ramon Leon Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54731) Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts
Title: Message Title Ramon Leon edited a comment on JENKINS-54731 Re: Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts Link to the [Pull Request #3768| [http://example.com| https://github.com/jenkinsci/jenkins/pull/3768] ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54731) Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts
Title: Message Title Ramon Leon commented on JENKINS-54731 Re: Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts Link to the [Pull Request #3768|http://example.com] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54731) Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts
Title: Message Title Ramon Leon updated JENKINS-54731 Jenkins / JENKINS-54731 Rename hudson.PluginManager.CHECK_UPDATE_ATTEMPTS property to hudson.PluginManager.checkUpdateAttempts Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Vitalii Lisovych commented on JENKINS-54729 Re: jenkins dashboard displays stacktrace Updating SSH Slaves plugin to 1.28.1 helped me as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54734) Blue Ocean view for pipeline doesn't show strings which contain any job parameter value
Title: Message Title Gennady Krasnikov created an issue Jenkins / JENKINS-54734 Blue Ocean view for pipeline doesn't show strings which contain any job parameter value Issue Type: Bug Assignee: Unassigned Attachments: image-2018-11-20-20-14-03-949.png Components: blueocean-plugin Created: 2018-11-20 17:17 Environment: Jenkins ver. 2.138.1 Priority: Minor Reporter: Gennady Krasnikov For a Pipeline job mark This project is parameterized and add any string parameter with a given value, say secret1 example_string=secret1 add pipeline description #!groovy def specialPlatformTestDir specialPlatformTestDir = 'secret2' echo specialPlatformTestDir specialPlatformTestDir = 'secret1' echo specialPlatformTestDir
[JIRA] (JENKINS-54729) jenkins dashboard displays stacktrace
Title: Message Title Vitalii Lisovych assigned an issue to Vitalii Lisovych Jenkins / JENKINS-54729 jenkins dashboard displays stacktrace Change By: Vitalii Lisovych Assignee: Sven Schoenung Vitalii Lisovych Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Vitalii Lisovych assigned an issue to Sven Schoenung Jenkins / JENKINS-54729 jenkins dashboard displays stacktrace Change By: Vitalii Lisovych Assignee: Vitalii Lisovych Sven Schoenung Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Jesse Glick commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. There we go at last. The visual appearance can probably be improved by someone more familiar with CSS. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
