[JIRA] (JENKINS-48986) broken if inside table
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-48986) broken if inside table
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-38452) imageName() drops registry prefix outside of withRegistry() block
Title: Message Title Mikhail Sakhnov commented on JENKINS-38452 Re: imageName() drops registry prefix outside of withRegistry() block Christian Höltje but for me, it looks like it doesn't work even if you defy img inside withRegistry block - withRun still ignores the registry prefix in the name. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49687) Failing to write out temporary embedded files - since JEP-200
Title: Message Title Priyesh Patel created an issue Jenkins / JENKINS-49687 Failing to write out temporary embedded files - since JEP-200 Issue Type: Bug Assignee: James Nord Components: cucumber-testresult-plugin Created: 2018-02-22 08:52 Environment: Centos 7 master Centos 7 slaves Jenkins 2.107 Priority: Minor Reporter: Priyesh Patel When the plugin comes across embeddings I believe it is failing to write out the files to the temporary folder, and finally the plugin fails to copy the embed files from the temporary folder with the following exception (The location was checked and no files matching the pattern cuke_* were found in that location): Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to BUILD_MACHINE_1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel.call(Channel.java:952) at hudson.FilePath.act(FilePath.java:998) at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.copyTo(FilePath.java:2079) at hudson.FilePath.copyTo(FilePath.java:2040) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.publishReport(CucumberTestResultArchiver.java:158) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.perform(CucumberTestResultArchiver.java:119) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:290)
[JIRA] (JENKINS-49687) Failing to write out temporary embedded files - since JEP-200
Title: Message Title Priyesh Patel updated an issue Jenkins / JENKINS-49687 Failing to write out temporary embedded files - since JEP-200 Change By: Priyesh Patel When the plugin comes across embeddings I believe it is failing to write out the files to the temporary folder, and finally then the plugin fails to copy the embed files from the temporary folder with the following exception (The location was checked and no files matching the pattern cuke_* were found in that location):Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to BUILD_MACHINE_1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel.call(Channel.java:952) at hudson.FilePath.act(FilePath.java:998) at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.copyTo(FilePath.java:2079) at hudson.FilePath.copyTo(FilePath.java:2040) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.publishReport(CucumberTestResultArchiver.java:158) at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.perform(CucumberTestResultArchiver.java:119) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)java.nio.file.NoSuchFileException: /data/jenkins/workspace/buildx/~/tmp/cuke_8339765699205404139.embed at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.FilePath$41.invoke(FilePath.java:2082) at hudson.FilePath$41.invoke(FilePath.java:2079) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2816) at hudson.remoting.UserRequest.perform(UserRequest.java:210) at hudson
[JIRA] (JENKINS-43050) SSH Agent plugin doesn't work well with docker pipelines
Title: Message Title
Konstantin Ripak commented on JENKINS-43050
Re: SSH Agent plugin doesn't work well with docker pipelines
Well, I think I found how to reproduce the issue. The following code works as expected if running on non-docker agent and does not work inside docker:
agent {
docker {
label 'bsp'
image 'my-registry/my-image'
reuseNode true
}
}
stage("Some stage") {
steps {
sshagent(['some-id']) {
script {
sh "# some code that uses ssh"
}
}
}
}
However, if I put sshagent() inside script {...} block it works:
agent {
docker {
label 'bsp'
image 'my-registry/my-image'
reuseNode true
}
}
stage("Some stage") {
steps {
script {
sshagent(['some-id']) {
sh "# some code that uses ssh"
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins I
[JIRA] (JENKINS-46096) Pipeline stage view rendered at bottom of page, below build history
Title: Message Title Philip Arickx commented on JENKINS-46096 Re: Pipeline stage view rendered at bottom of page, below build history Same issue here, and it is worse because to the right we have graphs for Checkstyle, Duplicate Code, Open Tasks and Test Result trends. As a result, the pipeline is not visible on the screen at all without scrolling down. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49631) git-plugin setup fails
Title: Message Title francesco labate commented on JENKINS-49631 Re: git-plugin setup fails Mark, I reopen the issue as I am available to provide sufficient configuration instructions to allow others to reproduce the issue, ask me the info you still need please, I start answering your questions: 1) there is a mistake in what I wrote in the bug description: from the windows server which guests Jenkins using bash is possible to clone the repository; it is also possible from the node Linux RH using git 2.12.2 command lline. 2) I am using in both cases a couple of private/pubblic ssh keys and they work. 3) there is no other message in the output; 4) the log of the console is attached, apparently it works. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49688) Job Configration page shows Loading... and hangs
Title: Message Title Bettina Bocklage created an issue Jenkins / JENKINS-49688 Job Configration page shows Loading... and hangs Issue Type: Bug Assignee: Stephen Connolly Components: maven-plugin, ssh-credentials-plugin Created: 2018-02-22 09:24 Environment: Jenkins 2.108 ace-editor 1.1 true analysis-collector 1.52 true analysis-core 1.94 true ant 1.8 true antisamy-markup-formatter 1.5 true apache-httpcomponents-client-4-api 4.5.3-2.1 true authentication-tokens 1.3 true bouncycastle-api 2.16.2 true branch-api 2.0.18 true build-blocker-plugin 1.7.3 true build-flow-plugin 0.20 true build-monitor-plugin 1.12+build.201708172343 true build-name-setter 1.6.8 true buildgraph-view 1.8 true categorized-view 1.10 true checkstyle 3.50 true cloudbees-credentials 3.3 true cloudbees-folder 6.3 true command-launcher 1.2 true conditional-buildstep 1.3.6 true config-file-provider 2.17 true configurationslicing 1.47 true copyartifact 1.39 true credentials 2.1.16 true credentials-binding 1.15 true cvs 2.13 true description-setter 1.10 true display-url-api 2.2.0 true docker-commons 1.11 true docker-workflow 1.15.1 true downstream-buildview 1.9 true doxygen 0.18 true durable-task 1.18 true ec2-deployment-dashboard 1.0.10 true email-ext 2.61 true email-ext-recipients-column 1.0 true emotional-jenkins-plugin 1.2 true envinject 2.1.5 true envinject-api 1.5 true exclusive-execution 0.8 true external-monitor-job 1.7 true extra-columns 1.18 true findbugs 4.72 true git 3.7.0 true git-client 2.7.1 true git-server 1.7 true gnat 0.14 true greenballs 1.15 true handlebars 1.1.1 true icon-shim 2.0.3 true ivy 1.28 true ivytrigger 0.34 true jackson2-api 2.8.11.1 true jacoco 2.1.0 true javadoc 1.4 true jira 2.5 true job-dsl 1.68 true jquery 1.12.4-0 true jquery-detached 1.2.1 true jquery-ui 1.0.2 true jsch 0.1.54.2 true junit 1.24 true ldap 1.20 true mailer 1.20 true mapdb-api 1.0.9.0 true matrix-auth 2.2 true matrix-project 1.12 true maven-plugin 3.1 true momentjs 1.1.1 true nexus-artifact-uploader 2.10 true nexus-task-runner 0.9.2 true pam-auth 1.3 true parameterized-trigger 2.35.2 true pipeline-build-step 2.7 true pipeline-graph-analysis 1.6 true pipeline-input-step 2.8 true pipeline-milestone-step 1.3.1 true pipeline-model-api 1.2.7 true pipeline-model-declarative-agent 1.1.1 true pipeline-model-definition 1.2.7 true pipeline-model-extensions 1.2.7 true pipeline-rest-api 2.9 true pipeline-stage-step 2.3 true pipeline-stage-tags-metadata 1.2.7 true pipeline-stage-view 2.9 true plain-credentials 1.4 true plot 2.0.3 true pollscm 1.3.1 true project-des
[JIRA] (JENKINS-49631) git-plugin setup fails
Title: Message Title francesco labate reopened an issue Please let me know which information do you need to reproduce and debug the issue and i will provide you. Jenkins / JENKINS-49631 git-plugin setup fails Change By: francesco labate Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more opt
[JIRA] (JENKINS-49631) git-plugin setup fails
Title: Message Title francesco labate updated an issue Jenkins / JENKINS-49631 git-plugin setup fails Change By: francesco labate Attachment: Output Console.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49671) Can't configure jenkinsfile in subdirectory
Title: Message Title Yair Ogen commented on JENKINS-49671 Re: Can't configure jenkinsfile in subdirectory Cyprian Śniegota I have the same issue. Any workaround? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49671) Can't configure jenkinsfile in subdirectory
Title: Message Title Cyprian Śniegota commented on JENKINS-49671 Re: Can't configure jenkinsfile in subdirectory move jenkinsfiles to the main directory patch sources (one line to change in BitbucketServerAPIClient:120) and build Your version of jenkins plugin until it's fixed in mainstream. We choose first one, so I don't have howto for the second. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49689) Only first repository cloned in a job with multiple repositories.
Title: Message Title francesco labate updated an issue Jenkins / JENKINS-49689 Only first repository cloned in a job with multiple repositories. Change By: francesco labate Environment: Jenkins ver. 2.46.2Git client plugin 2.7.1Git plugin 3.7.0and all related dependencies have been successfully installed as per attached screenshot.Git version on the RedHat node is 2.12.2Bitbucket v4.14.2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49689) Only first repository cloned in a job with multiple repositories.
Title: Message Title francesco labate updated an issue Jenkins / JENKINS-49689 Only first repository cloned in a job with multiple repositories. Change By: francesco labate Attachment: installed git plugins.jpg Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49689) Only first repository cloned in a job with multiple repositories.
Title: Message Title francesco labate created an issue Jenkins / JENKINS-49689 Only first repository cloned in a job with multiple repositories. Issue Type: Bug Assignee: Mark Waite Attachments: Output Console.txt Components: git-client-plugin, git-plugin Created: 2018-02-22 09:33 Priority: Minor Reporter: francesco labate When inside the same Jenkins Multi_Job_Project two or more repositories are specified to be cloned, only the first one is cloned. Workaround: is possible to add the "git clone" commands in the prebuild scripts to have the full project cloned into a different folder on the node, as per attached log. Add Comment
[JIRA] (JENKINS-49688) Job Configration page shows Loading... and hangs
Title: Message Title Oleg Nenashev commented on JENKINS-49688 Re: Job Configration page shows Loading... and hangs Do you have Violations plugin installed? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49688) Job Configration page shows Loading... and hangs
Title: Message Title Oleg Nenashev commented on JENKINS-49688 Re: Job Configration page shows Loading... and hangs Anyway, if you see issues with plugin loading, you need to fix it first. Before that we cannot guarantee stability of Jenkins. If you provide a startup log, I can point you to particular plugins. Though the logs are pretty explicit. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49688) Job Configration page shows Loading... and hangs
Title: Message Title Bettina Bocklage commented on JENKINS-49688 Re: Job Configration page shows Loading... and hangs yes: violation plugin 0.7.11 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49688) Job Configration page shows Loading... and hangs
Title: Message Title Bettina Bocklage commented on JENKINS-49688 Re: Job Configration page shows Loading... and hangs At the moment there are no problems with plugin loading and there are no errors in the log files.The configuration page still shows loading. I did some tests before to find out, to find out the corruped plugin, therefore I downgraded the ssh credential plugin and than there were plugin loading errors. But at the moment a have latest ssh plugins and now I have no errors. Loading ... still hangs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49631) git-plugin setup fails
Title: Message Title francesco labate updated an issue Jenkins / JENKINS-49631 git-plugin setup fails Change By: francesco labate Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49690) Stage view showing wrong pipeline data after build history purge
Title: Message Title Ian Thompson created an issue Jenkins / JENKINS-49690 Stage view showing wrong pipeline data after build history purge Issue Type: Bug Assignee: Sam Van Oort Attachments: after.PNG, before.PNG Components: pipeline-stage-view-plugin, purge-job-history-plugin Created: 2018-02-22 10:22 Environment: Purge Job History Plugin v1.1 Pipeline: Stage view plugin v2.9 Jenkins OS: RHEL 7.3 - 64bit Priority: Minor Reporter: Ian Thompson After performing a build history purge (and reset build number to 1) using the purge job history plugin the stage view shows the stage view from the previous build. Looks like its a similar issue to JENKINS 36865 and the below workaround (listed in the comments session) resolves the issue. import com.cloudbees.workflow.flownode.FlowNodeUtil FlowNodeUtil.CacheExtension ext = FlowNodeUtil.CacheExtension.all().get(0); ext.getRunCache().invalidateAll();
[JIRA] (JENKINS-49691) FilePath.installIfNecessaryFrom always download even if target already exists
Title: Message Title
Cyril MARIN created an issue
Jenkins / JENKINS-49691
FilePath.installIfNecessaryFrom always download even if target already exists
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2018-02-22 10:48
Environment:
2.89.4 (lts)
Labels:
jenkins tools
Priority:
Minor
Reporter:
Cyril MARIN
FilePath.installIfNecessaryFrom, used from ZipExtractionInstaller, is designed to check if target already exists before downloading from remote URL. But I observe that every time I run the build job, the tool is downloaded from remote URL even if the files exists in local $JENKINS_HOME/tools directory. No exception raised while processing. Simple test pipeline to reproduce issue:
pipeline {
agent any
tools {
maven "M3"
jdk "JDK8_161"
}
stages {
stage('Test') {
steps {
echo 'Testing..'
}
}
}
}
*Job output logs for this example *:
[Pipeline] node Running on Jenkins in /var/jenkins_home/workspace/test [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Tool Install) [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] tool Unpacking https://.box.co
[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Ruud P commented on JENKINS-39628 Re: Handle skipped stages and parallels in the Pipeline Graph it is fixed with an update of jenkins, at this moment this works fine for me Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49633) Filenames are no longer shown under Summary of Changes - View Detail
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49633 Re: Filenames are no longer shown under Summary of Changes - View Detail Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/changes/P4ChangeEntry.java src/main/resources/org/jenkinsci/plugins/p4/PerforceScm/global.jelly http://jenkins-ci.org/commit/p4-plugin/549aa7f2d0fed4d999b2adacec9eae907fc99e98 Log: Use DEFAULT_FILE_LIMIT if max file limit is set to 0. JENKINS-49633 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49691) FilePath.installIfNecessaryFrom always download even if target already exists
Title: Message Title Cyril MARIN commented on JENKINS-49691 Re: FilePath.installIfNecessaryFrom always download even if target already exists A little précision : My tools are hosted on a Box.com repository with a public static URL. Maybe there is a trouble with Box hosting. Http headers may not contain "last-modified" for some reason. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49688) Job Configration page shows Loading... and hangs
Title: Message Title Oleg Nenashev commented on JENKINS-49688 Re: Job Configration page shows Loading... and hangs My theory is that it is JENKINS-49630 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title Oleg Nenashev commented on JENKINS-49596 Re: User session memory leak For now I have released 4.1.1 so that we can do some testing on the core's side, but actually I messed up it a bit. It should have been a snapshot release: https://github.com/jenkinsci/winstone/pull/45 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49688) Job Configration page shows Loading... and hangs
Title: Message Title Bettina Bocklage commented on JENKINS-49688 Re: Job Configration page shows Loading... and hangs Great! I removed all Violation plugins and now it works. I don't know why I did not found JENKINS-49630... Thank's a lot. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49596) User session memory leak
Title: Message Title olamy commented on JENKINS-49596 Re: User session memory leak oops sorry I was a bit busy today. But I will do some testing tomorrow. There is still something I don't understand with this issue here and especially with the use of javamelody. for details on Jetty session in 9.4.x please read here https://www.eclipse.org/jetty/documentation/9.4.x/session-management.html Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49631) git-plugin setup fails
Title: Message Title francesco labate commented on JENKINS-49631 Re: git-plugin setup fails Further details about the ssh-key, it has been generated using the command: ssh-keygen -t rsa and enabling the flag: PubkeyAuthentication yes in both files below: /etc/ssh/sshd_config /etc/ssh/config then restarting the service jenkins. As said this key works well using the git clone command from the node. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49105) Can't send data to influx
Title: Message Title Timo Sand commented on JENKINS-49105 Re: Can't send data to influx Aleksi Simell Yet that does not explain why the target object has been preparsed and thus passed in the wrong format to the constructor. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49692 Could not update folder level actions from source Issue Type: Bug Assignee: lucamilanesio Components: gerrit-plugin, workflow-multibranch-plugin Created: 2018-02-22 11:23 Environment: gerrit-plugin-1.1.0 Priority: Major Reporter: Sorin Sbarnea It seems that after configuring a new Multibranch Pipeline project with Gerrit SCM using HTTPS as the source, user would get the exception below while trying to scan for branches: [Thu Feb 22 11:04:09 UTC 2018] Starting branch indexing... ERROR: [Thu Feb 22 11:04:09 UTC 2018] Could not update folder level actions from source dc268e61-3582-471b-97d0-d30b9a99a4a4 java.lang.NullPointerException at jenkins.scm.api.trait.SCMSourceContext.withTraits(SCMSourceContext.java:245) at jenkins.plugins.gerrit.AbstractGerritSCMSource.retrieveActions(AbstractGerritSCMSource.java:214) at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:746) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:591) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:978) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) [Thu Feb 22 11:04:09 UTC 2018] Finished branch indexing. Indexing took 14 ms FATAL: Failed to recompute children of test-jjb-multibranch java.lang.NullPointerEx
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-49692 Could not update folder level actions from source Change By: Sorin Sbarnea Environment: gerrit-plugin-1.1.0 jenkins-2.89.4 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49105) Can't send data to influx
Title: Message Title Aleksi Simell commented on JENKINS-49105 Re: Can't send data to influx Yes, I know that. But I still haven't been able to reproduce this issue. Do you first assign the target as a variable and pass it to the plugin step (I am aware you have the quotation marks around 'telegraf')? I'm just guessing here, since I have never encountered this before. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title Thomas Johansen commented on JENKINS-38383 Re: StackOverflow when loading a large pipeline job I get a similar symptom on startup with Jenkins version 2.102. The stacktrace is now: [...] com.google.common.util.concurrent.ExecutionError: java.lang.StackOverflowError 2018-02-22T11:17:37.589287583Z at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2232) 2018-02-22T11:17:37.589290948Z at com.google.common.cache.LocalCache.get(LocalCache.java:3965) 2018-02-22T11:17:37.589293750Z at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969) 2018-02-22T11:17:37.589296421Z at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4829) 2018-02-22T11:17:37.589299106Z at com.google.common.cache.LocalCache$LocalManualCache.getUnchecked(LocalCache.java:4834) 2018-02-22T11:17:37.589301839Z at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogPrefix(WorkflowRun.java:556) 2018-02-22T11:17:37.589304561Z at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$900(WorkflowRun.java:134) 2018-02-22T11:17:37.589308088Z at org.jenkinsci.plugins.workflow.job.WorkflowRun$6.load(WorkflowRun.java:547) 2018-02-22T11:17:37.589310809Z at org.jenkinsci.plugins.workflow.job.WorkflowRun$6.load(WorkflowRun.java:537) 2018-02-22T11:17:37.589313487Z at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) 2018-02-22T11:17:37.589316198Z at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350) 2018-02-22T11:17:37.589318881Z at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) 2018-02-22T11:17:37.589323997Z at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) 2018-02-22T11:17:37.589326739Z ... 222 more 2018-02-22T11:17:37.589333918Z Caused by: com.google.common.util.concurrent.ExecutionError [...] Jenkins is then irresponsive for some minutes. Is this because I'm having pipeline-jobs using while-loops? Add Comment
[JIRA] (JENKINS-49688) Job Configration page shows Loading... and hangs
Title: Message Title Bettina Bocklage resolved as Duplicate Jenkins / JENKINS-49688 Job Configration page shows Loading... and hangs Change By: Bettina Bocklage Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49693) Add "Only poll using master" option
Title: Message Title Loic Antoine-Gombeaud created an issue Jenkins / JENKINS-49693 Add "Only poll using master" option Issue Type: New Feature Assignee: Unassigned Components: repo-plugin Created: 2018-02-22 11:36 Priority: Minor Reporter: Loic Antoine-Gombeaud When using dynamic nodes, polling the SCM means that there is no available workspace when all nodes are offline. This triggers an extra build (and starts a node) just to poll the SCM. It would be great to be able to either: have the option to only poll the SCM on the master, or (even better) specify node labels on which the SCM polling can run Add Comment
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title
Thomas Johansen edited a comment on JENKINS-38383
Re: StackOverflow when loading a large pipeline job
I get a similar symptom on startup with Jenkins version 2.102. The stacktrace is now:{noformat}[...] com.google.common.util.concurrent.ExecutionError: java.lang.StackOverflowError2018-02-22T11:17:37.589287583Z at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2232)2018-02-22T11:17:37.589290948Z at com.google.common.cache.LocalCache.get(LocalCache.java:3965)2018-02-22T11:17:37.589293750Z at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969)2018-02-22T11:17:37.589296421Z at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4829)2018-02-22T11:17:37.589299106Z at com.google.common.cache.LocalCache$LocalManualCache.getUnchecked(LocalCache.java:4834)2018-02-22T11:17:37.589301839Z at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogPrefix(WorkflowRun.java:556)2018-02-22T11:17:37.589304561Z at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$900(WorkflowRun.java:134)2018-02-22T11:17:37.589308088Z at org.jenkinsci.plugins.workflow.job.WorkflowRun$6.load(WorkflowRun.java:547)2018-02-22T11:17:37.589310809Z at org.jenkinsci.plugins.workflow.job.WorkflowRun$6.load(WorkflowRun.java:537)2018-02-22T11:17:37.589313487Z at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568)2018-02-22T11:17:37.589316198Z at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)2018-02-22T11:17:37.589318881Z at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313)2018-02-22T11:17:37.589323997Z at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228)2018-02-22T11:17:37.589326739Z ... 222 more2018-02-22T11:17:37.589333918Z Caused by: com.google.common.util.concurrent.ExecutionError [...]{noformat}Jenkins is then irresponsive for some minutes , and also it seems like the jobs resumed while in the loop is sometimes stuck after restart . Is this because I'm having pipeline-jobs using while-loops?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49671) Can't configure jenkinsfile in subdirectory
Title: Message Title Yair Ogen commented on JENKINS-49671 Re: Can't configure jenkinsfile in subdirectory option 1 makes sense but something I wanted to avoid Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title Sorin Sbarnea commented on JENKINS-49692 Re: Could not update folder level actions from source It seems that his bug is caused by the missing .git suffix on the git repository URL, something that is optional for git clone command, which works with and without it. Documentation states that the parameter is the same as the one used by git clone. Even Gerrit sample project cloning commands do advertise the URLs without .git prefix, exactly the ones that not working with the plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Simon Wydooghe commented on JENKINS-46068 Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) I can confirm this behaviour after renaming a bunch of our repositories. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Simon Wydooghe edited a comment on JENKINS-46068 Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) I can confirm this behaviour after renaming a bunch of our repositories. What's the easiest workaround to remove the old repo in Jenkins for now? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-49692 Re: Could not update folder level actions from source It seems that his bug is caused by the missing *.git* suffix on the git repository URL, something that is optional for git clone command, which works with and without it.Documentation states that the parameter is the same as the one used by git clone.Even Gerrit sample project cloning commands do advertise the URLs without .git prefix, exactly the ones that not working with the plugin. I also tested with freestyle and pipeline project types, and both of them work well without the .git suffix on the URLs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43427) git-plugin with both LFS and Sparse checkout behaviour pulls too many files
Title: Message Title
Jens Beyer commented on JENKINS-43427
Re: git-plugin with both LFS and Sparse checkout behaviour pulls too many files
As this seems to take a while to be fixed, a heads up on how I solved this for now: Check if the checkout already exists; if not, do a manual sparse checkout configuration. Then do the normal checkout. If the checkout already exists, skip the first part. It is basically something around the following snippet (which may not work directly, you will need to adapt your use case to it). {{ if (!fileExists('.scm/.gitattributes')) {}} bat "git clone --no-checkout $gitrepourl .scm" dir('.scm') { bat "git config core.sparsecheckout true" bat "echo /.gitattributes>.git/info/sparse-checkout" bat "echo /.gitignore>>.git/info/sparse-checkout" bat "echo /$baseDir>>.git/info/sparse-checkout" bat "git checkout $BRANCH_NAME" {{ }}} checkout scm: [$class: 'GitSCM', branches: [[name: "refs/heads/$BRANCH_NAME"]], extensions: [[$class: 'SparseCheckoutPaths', sparseCheckoutPaths: [[path: '/' + baseDir], [path: '/.gitattributes'], [path: '/.gitignore']]], [$class: 'RelativeTargetDirectory', relativeTargetDir: '.scm']], gitTool: 'local', submoduleCfg: [], userRemoteConfigs: [[url: "$gitrepourl"]]] }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39143) Stage view disappears after restarting jenkins
Title: Message Title KS updated an issue Jenkins / JENKINS-39143 Stage view disappears after restarting jenkins Change By: KS Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 The last change in core's registerValidator _javascript_ was 5 years ago. the failing line is here: https://github.com/jenkinsci/jenkins/blame/5c8cc45900bf8d78058cecd471840bdbc88215d3/war/src/main/webapp/scripts/hudson-behavior.js#L424 Apparently, "validation-error-area" is missing, and it causes the code to fail. Since Violations plugin has not been updated for long as well, my theory is that the plugin is a collateral damage as well. Likely recent update in something (e.g. analytics core) contributed an extension point with bogus field. Will see if I can reproduce that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 The last change in core's registerValidator _javascript_ was 5 years ago. the failing line is here: https://github.com/jenkinsci/jenkins/blame/5c8cc45900bf8d78058cecd471840bdbc88215d3/war/src/main/webapp/scripts/hudson-behavior.js#L424Apparently, "validation-error-area" is missing, and it causes the code to fail.Since Violations plugin has not been updated for long as well, my theory is that the plugin is a collateral damage as well. Likely recent update in something (e.g. analytics core) contributed an extension point implementation with a bogus field. Will see if I can reproduce that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev Assignee: mike cirioli Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49694) NPE in io.jenkins.blueocean.preload.PipelineActivityStatePreloader.getFetchData
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-49694 NPE in io.jenkins.blueocean.preload.PipelineActivityStatePreloader.getFetchData Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-02-22 12:17 Priority: Minor Reporter: Oleg Nenashev Spin-off of JENKINS-49630 Caught exception evaluating: preloader.stateJson in /jenkins/blue/organizations/jenkins/js-modules/dashboard-ui/detail/PR-1/19/. Reason: java.lang.reflect.InvocationTargetException java.lang.NullPointerException at io.jenkins.blueocean.preload.PipelineActivityStatePreloader.getFetchData(PipelineActivityStatePreloader.java:67) at io.jenkins.blueocean.commons.RESTFetchPreloader.getStateJson(RESTFetchPreloader.java:64) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1738.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLib
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Oleg Nenashev I upgraded Jenkins to 2.107 yesterday and upgraded all the plugins to their latest version. After that some of our jobs can no longer be configured. The page just shows "Loading" with a blinking icon. In addition, the chrome developer tool shows hudson-behavior.js:424 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (hudson-behavior.js:424) at Array.forEach () at behavior.js:111 at Array.forEach () at behavior.js:107 at Array.forEach () at Object.applySubtree (behavior.js:93) at select.js:269registerValidator @ hudson-behavior.js:424(anonymous) @ behavior.js:111(anonymous) @ behavior.js:107applySubtree @ behavior.js:93(anonymous) @ select.js:269setTimeout (async)(anonymous) @ select.js:263 I am also seeing errors in the logs which may or may not be related. Caught exception evaluating: preloader.stateJson in /jenkins/blue/organizations/jenkins/js-modules/dashboard-ui/detail/PR-1/19/. Reason: java.lang.reflect.InvocationTargetException java.lang.NullPointerException at io.jenkins.blueocean.preload.PipelineActivityStatePreloader.getFetchData(PipelineActivityStatePreloader.java:67) at io.jenkins.blueocean.commons.RESTFetchPreloader.getStateJson(RESTFetchPreloader.java:64) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1738.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) 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.ForEachTag.doTag(ForEachTag.java:150) 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.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapl
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Moved BlueOcean error to JENKINS-49694 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43427) git-plugin with both LFS and Sparse checkout behaviour pulls too many files
Title: Message Title
Jens Beyer edited a comment on JENKINS-43427
Re: git-plugin with both LFS and Sparse checkout behaviour pulls too many files
As this seems to take a while to be fixed, a heads up on how I solved this for now:Check if the checkout already exists; if not, do a manual sparse checkout configuration. Then do the normal checkout. If the checkout already exists, skip the first part.It is basically something around the following snippet (which may not work directly, you will need to adapt your use case to it).{{ if (!fileExists('.scm/.gitattributes')) \{}}{{ bat "git clone --no-checkout $gitrepourl .scm"}}{{ dir('.scm') \{}}{{ bat "git config core.sparsecheckout true"}}{{ bat "echo /.gitattributes>.git/info/sparse-checkout"}}{{ bat "echo /.gitignore>>.git/info/sparse-checkout"}}{{ bat "echo /$baseDir>>.git/info/sparse-checkout"}}{{ bat "git checkout $BRANCH_NAME"}}{{ }}}{{ checkout scm: [$class: 'GitSCM', branches: [[name: "refs/heads/$BRANCH_NAME"]], extensions: [[$class: 'SparseCheckoutPaths', sparseCheckoutPaths: [[path: '/' + baseDir], [path: '/.gitattributes'], [path: '/.gitignore']]], [$class: 'RelativeTargetDirectory', relativeTargetDir: '.scm']], gitTool: 'local', submoduleCfg: [], userRemoteConfigs: [[url: "$gitrepourl"]]]}}{{}}}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper edited a comment on JENKINS-12783 Re: Delete workspace before build starts ignores Exlude patterns (for directories) Jenkins Versions: 2.60.3 & 2.73.3 (WAR deployments on WildFly) Plugin Version: 0.34 Platform: Linux Plugins: Git client plugin 2.6.0 Git plugin 3.6.4Details: No issues when the SCM is CVS. However we are migrating from CVS to GIT. When I configure a freestyle job to use GIT as the SCM and with "Delete workspace before build starts" checked it ignores any "Advanced" options I use (I'm trying to exclude ' **.build.** ' and a 'reports/**' directory) and just deletes everything in the entire workspace.In troubleshooting I also testing the Post Build Action > "Delete workspace when build is done". This half works. I can tell it to "Exclude" specific files, but as soon as the "Apply pattern also on directories" is checked it goes back to the above behavior of deleting everything regardless of excludes.Really hoping someone can have a look at this and find the root cause and a fix.Thanks in advance! Edit:I forgot to add that the GIT install is on a windows machine and the repo is located through a UNC share. Not that I think this has any bearing as the repo pull/clone works fine. Just trying to provide as much info as possible. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49695) Could not fetch branches from source while using Discover open changes
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-49695 Could not fetch branches from source while using Discover open changes Issue Type: Bug Assignee: lucamilanesio Components: gerrit-plugin, workflow-multibranch-plugin Created: 2018-02-22 12:25 Environment: gerrit-plugin-1.1.0 jenkins-2.89.4 Priority: Minor Reporter: Sorin Sbarnea It seems that by default multibranch-pipeline and git-review setup does not discover any branches in gerrit projects, even after adding "Filter by name (with wildcards)" with defaults settings (include *, exclude: ) — which seems to have no effect. Once we add "Discover open changes" to the config, Jenkins starts to discover open branches on gerritbut detection seems to be buggy because I see some failures in the logs: Started [Thu Feb 22 12:15:18 GMT 2018] Starting branch indexing... > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://review.gerrithub.io/pycontribs/powertape > git config remote.origin.url https://review.gerrithub.io/pycontribs/powertape # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://review.gerrithub.io/pycontribs/powertape > git config remote.origin.url https://review.gerrithub.io/pycontribs/powertape # timeout=10 Fetching & pruning origin... Fetching upstream changes from origin > git --version # timeout=10 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --
[JIRA] (JENKINS-49631) git-plugin setup fails
Title: Message Title Mark Waite resolved as Not A Defect Closing. Not a defect. User configuration error that needs to be investigated somewhere other than a bug report. Jenkins / JENKINS-49631 git-plugin setup fails Change By: Mark Waite Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more o
[JIRA] (JENKINS-49689) Only first repository cloned in a job with multiple repositories.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49689 Only first repository cloned in a job with multiple repositories. Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49689) Only first repository cloned in a job with multiple repositories.
Title: Message Title Mark Waite resolved as Won't Fix The Multi-Job plugin was created in 2011 by the Tikal ALM team. It is an initial attempt to solve the same class of problems that are now solved much more effectively by Jenkins Pipeline. Checkout of multiple repositories in a Jenkins Pipeline is well supported and well tested. Please use Jenkins Pipeline instead of the Multi-Job Plugin. Jenkins / JENKINS-49689 Only first repository cloned in a job with multiple repositories. Change By: Mark Waite Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-47166) Not able to use Publish HPE tests result option
Title: Message Title Anton Semenov updated an issue Jenkins / JENKINS-47166 Not able to use Publish HPE tests result option Change By: Anton Semenov Labels: UFT pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49696) Add option to delete views before re-creating them
Title: Message Title Petres Andras created an issue Jenkins / JENKINS-49696 Add option to delete views before re-creating them Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-02-22 12:43 Priority: Minor Reporter: Petres Andras Job DSL does not allow for view type to be changed, throwing an exception when this is attempted. The workaround is deleting the view manually before running the seed job. It would be much nicer if the deletion would be done automatically. I would like to have an option in the plugin which forces the deletion of views before regeneration. When that option (checkbox?) is checked, job-dsl-plugin deletes the view right after if detects that a view with the same name exists and creates it again instead of updating it. Add Comment
[JIRA] (JENKINS-48757) Jenkins Plugin Error - Unable to start the test
Title: Message Title Oren Pelzman updated an issue Jenkins / JENKINS-48757 Jenkins Plugin Error - Unable to start the test Change By: Oren Pelzman Labels: PerformanceCenter jenkins plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47166) Not able to use Publish HPE tests result option
Title: Message Title
Anton Semenov commented on JENKINS-47166
Re: Not able to use Publish HPE tests result option
Evan Chen , I have same problem. Jenkins ver. 2.89.4 But we can execute the plugin by following code: stage('Publish results') { steps { script { step([$class: *'RunResultRecorder'*, archiveTestResultsMode:*'Always archive HP test reports'*]) } } } But it's not working. Here is error text: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.Project at com.hpe.application.automation.tools.results.RunResultRecorder.perform(RunResultRecorder.java:1242) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message beca
[JIRA] (JENKINS-47166) Not able to use Publish HPE tests result option
Title: Message Title Anton Semenov updated an issue Jenkins / JENKINS-47166 Not able to use Publish HPE tests result option Change By: Anton Semenov Labels: RunResultRecorder UFT pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47166) Not able to use Publish HPE tests result option
Title: Message Title
Anton Semenov edited a comment on JENKINS-47166
Re: Not able to use Publish HPE tests result option
[~evanchen] , I have same problem.Jenkins ver. 2.89.4But we can execute the plugin by following code:stage(*'Publish results'*) \{ steps \{ script \{ step([$class: * 'RunResultRecorder' * , archiveTestResultsMode: * 'Always archive HP test reports' * ]) } } }But it's not working. Here is error text:java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.Project at com.hpe.application.automation.tools.results.RunResultRecorder.perform(RunResultRecorder.java:1242) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this messag
[JIRA] (JENKINS-19574) Delete workspace before build starts - does not delete folders in workspace
Title: Message Title Grim Reaper updated an issue Jenkins / JENKINS-19574 Delete workspace before build starts - does not delete folders in workspace Change By: Grim Reaper Environment: OP - workspace cleanup 0.17 Grim - ws-cleanup-plugin 0.34 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19574) Delete workspace before build starts - does not delete folders in workspace
Title: Message Title Grim Reaper updated an issue Jenkins / JENKINS-19574 Delete workspace before build starts - does not delete folders in workspace Change By: Grim Reaper Environment: OP - workspace cleanup 0.17 Grim - ws-cleanup-plugin 0.34 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19574) Delete workspace before build starts - does not delete folders in workspace
Title: Message Title Grim Reaper updated an issue Jenkins / JENKINS-19574 Delete workspace before build starts - does not delete folders in workspace Change By: Grim Reaper Labels: plugin regression workspace Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper updated an issue Jenkins / JENKINS-12783 Delete workspace before build starts ignores Exlude patterns (for directories) Change By: Grim Reaper Labels: bug plugin scm workspace Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Grim Reaper assigned an issue to Oliver Gondža Assigning to you as the plugins page indicates you are the ws-cleanup maintainer. Also for visibility. Jenkins / JENKINS-12783 Delete workspace before build starts ignores Exlude patterns (for directories) Change By: Grim Reaper Assignee: Lucie Votypkova Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41182) Nodes disappear if "# of executors" is set to 0
Title: Message Title Kseniia Nenasheva updated JENKINS-41182 Fixed in PR #3141 and PR #3292 Jenkins / JENKINS-41182 Nodes disappear if "# of executors" is set to 0 Change By: Kseniia Nenasheva Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49048) Optionally disable implict sync when using multibranch
Title: Message Title
Karl Wirth commented on JENKINS-49048
Re: Optionally disable implict sync when using multibranch
Not controlled by P4Jenkins. The pipeline option 'skipDefaultCheckout' will disable implict Sync:
pipeline {
agent any
options { skipDefaultCheckout() }
stages{
stage('Test') {
steps {
echo 'Testing..'
}
}
stage('Deploy') {
steps {
echo 'Deploying'
}
}
}
}
This will need to be clearly documented (possibly in help bubbles).
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49671) Can't configure jenkinsfile in subdirectory
Title: Message Title Cyprian Śniegota commented on JENKINS-49671 Re: Can't configure jenkinsfile in subdirectory Created PR https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/111 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49697) Single quote in credentials password causing job crash
Title: Message Title Ovidiu-Florin Bogdan created an issue Jenkins / JENKINS-49697 Single quote in credentials password causing job crash Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2018-02-22 13:42 Environment: Jenkins 2.89.3 From the official Docker image: jenkins/jenkins:2.89.3 Labels: plugin jenkins Priority: Critical Reporter: Ovidiu-Florin Bogdan Having a (or multiple) single quote(s) in the password of the user used by Artifactory causes the job to crash when using the Conan package manager during the ConanAddUser step. This is the classic SQL injection security hole. I just caught it because I'm running the job in a Docker contaier. I've looked through the plugin code and I found that the single and probably best place where this can be escaped is in https://github.com/JFrogDev/jenkins-artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/util/plugins/PluginsUtils.java#L67 Or just before https://github.com/JFrogDev/jenkins-artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/util/Credentials.java#L43 Since after this the password is scrambled and cannot be escaped anymore. In my desperation I've also asked on StackOverflow about this: https://stackoverflow.com/questions/48907089/jenkins-pipeline-with-docker-and-artifactory
[JIRA] (JENKINS-49698) Show/Enable "Run" button in Jenkins Blue Ocean multibranch pipeline activity tab
Title: Message Title Adrian Vladu created an issue Jenkins / JENKINS-49698 Show/Enable "Run" button in Jenkins Blue Ocean multibranch pipeline activity tab Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-02-22 13:45 Environment: Jenkins ver. 2.73.3, Jenkins Blue Ocean 1.4.1 Priority: Minor Reporter: Adrian Vladu In the normal jobs (freestyle) or the pipeline jobs (non-multibranch), there is the "Run" button in the Jenkins Blue Ocean Pipeline. In the multi-branch pipelines, the "Run" button is missing, and you need to go to the branches tab and press the small "|>" button, which is harder to know what it means. I know that the question would be: to what branch that "Run" button to point at? I suggest having it pointed to the master branch by default and have a pipeline configuration option to change that default behavior. Or reuse the favorite plugin and point to the first favorite. Add Comment
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title Waldek M commented on JENKINS-47026 Re: User not completely set in docker containers Just for the record: Dockerfile workaround worked fine. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Oleg Nenashev commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have tried to reproduce the issue by installing Violations / Warnings and other plugins on 2.108, was unable to do so. From the screenshots I see that it something related to credentials: "select.credentials-select". It comes from Credentials plugin: https://github.com/jenkinsci/credentials-plugin/search?utf8=%E2%9C%93&q=%22credentials-select%22&type= Now the challenge is to find an overlap between Credentials and Violations Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s
Title: Message Title Steve Szabo commented on JENKINS-49660 Re: Unable to configure plugin using ibm k8s I plan to create a service account to manage the namespace from jenkins. Thanks for your help on this one - cheers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49660) Unable to configure plugin using ibm k8s
Title: Message Title Steve Szabo resolved as Not A Defect Jenkins / JENKINS-49660 Unable to configure plugin using ibm k8s Change By: Steve Szabo Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49693) Add "Only poll using master" option
Title: Message Title Loic Antoine-Gombeaud updated an issue Jenkins / JENKINS-49693 Add "Only poll using master" option Change By: Loic Antoine-Gombeaud When using dynamic nodes, polling the SCM means that there is no available workspace when all nodes are offline. This triggers an extra build (and starts a node) just to poll the SCM.It would be great to be able to either:- have the option to only poll the SCM on the master, or- (even better) be able to specify node labels on which the SCM polling can run Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title
Karl Wirth commented on JENKINS-49678
Re: Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Not controlled by P4Jenkins. The pipeline option 'skipDefaultCheckout' will disable this implict Sync:
pipeline {
agent any
options { skipDefaultCheckout() }
stages{
stage('Test') {
steps {
echo 'Testing..'
}
}
stage('Deploy') {
steps {
echo 'Deploying'
}
}
}
}
We are planning to document this in on help pages. Note: Lightweight checkout is not our option so we cant update the help bubble text.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-49678 Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth assigned an issue to Paul Allen Jenkins / JENKINS-49678 Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Change By: Karl Wirth Assignee: Karl Wirth Paul Allen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth started work on JENKINS-49678 Change By: Karl Wirth Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49048) Optionally disable implict sync when using multibranch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49048 Re: Optionally disable implict sync when using multibranch Code changed in jenkins User: Paul Allen Path: MULTI.md WORKFLOW.md docs/images/declarative.png docs/images/lightweight.png http://jenkins-ci.org/commit/p4-plugin/9d17790788a394b73726335cad2b391b7930903d Log: Document lightweight checkout for Pipeline and MultiBranch. JENKINS-49048 JENKINS-49678 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49678 Re: Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Code changed in jenkins User: Paul Allen Path: MULTI.md WORKFLOW.md docs/images/declarative.png docs/images/lightweight.png http://jenkins-ci.org/commit/p4-plugin/9d17790788a394b73726335cad2b391b7930903d Log: Document lightweight checkout for Pipeline and MultiBranch. JENKINS-49048 JENKINS-49678 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49048) Optionally disable implict sync when using multibranch
Title: Message Title
Paul Allen closed an issue as Fixed
Added MultiBranch and Pipeline lightweight checkout documentation for: options { skipDefaultCheckout() }
Jenkins / JENKINS-49048
Optionally disable implict sync when using multibranch
Change By:
Paul Allen
Status:
In Progress Closed
Assignee:
Paul Allen
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title
Paul Allen closed an issue as Fixed
Added MultiBranch and Pipeline lightweight checkout documentation for: options { skipDefaultCheckout() }
Jenkins / JENKINS-49678
Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Change By:
Paul Allen
Status:
In Progress Closed
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-49483) When using Streams, custom view definition seems to be ignored
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49483 When using Streams, custom view definition seems to be ignored Change By: Paul Allen Labels: plugin scm P4_SUPPORT Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters Change By: Paul Allen Labels: P4_SUPPORT Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49658) One JCloud node type can starve another in Jenkins
Title: Message Title Darrel Vuncannon updated an issue Jenkins / JENKINS-49658 One JCloud node type can starve another in Jenkins Change By: Darrel Vuncannon Summary: One JCloud image node type can starve another in Jenkins Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49658) One JCloud image type can starve another in Jenkins
Title: Message Title
Darrel Vuncannon updated an issue
Jenkins / JENKINS-49658
One JCloud image type can starve another in Jenkins
Change By:
Darrel Vuncannon
h5. Problem StatementOn a given Jenkins instance, a desired cloud-node type (e.g. Ubuntu) may not spin up for hours because another image cloud-node type (e.g. Win7) has saturated the cloud's quota. {color:darkred}_Due to node retention times, this can happen even if the existing cloud nodes are idle, resulting in wasted computing power!_{color}h5. Steps to Reproduce* Start with an idle Jenkins and idle cloud quota of 10 nodes* Start 10 builds that require Win7 images* Allow each build to run and complete, e.g. 1 hour* Start 1 build that requires Ubuntuh5. Expected Results* The Ubuntu build enters the build queue* An idle Win7 node should be killed and spin up with Ubuntu* Now the cloud quota of 10 is maxed at 9 idle Win7 nodes and 1 running Ubuntu nodeh5. Actual Results* The Ubuntu build enters the build queue* All 10 Win7 nodes continue to stay idle* No Ubuntu node is spun up because the cloud quota is maxed out at 10* The retention time expires after (default) 30 minutes, and the Win7 nodes are killed* An Ubuntu image spins up and starts building the build requested 30 minutes agoWe prefer a long retention time because we're using our private cloud instead of paying for usage from a 3rd party. We want cloud nodes to live a while so we can avoid spin-up time when reused. But we don't want that behavior at the expense of queuing other builds while cloud nodes are idle .
Add Comment
[JIRA] (JENKINS-36915) Throttle Concurrent Builds on scheduled builds at the same time
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know Jenkins / JENKINS-36915 Throttle Concurrent Builds on scheduled builds at the same time Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48591) Concurrent Builds Plugin Does not work properly
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know Jenkins / JENKINS-48591 Concurrent Builds Plugin Does not work properly Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32888) Throttle Concurrent Builds plugin doesn't work
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know Jenkins / JENKINS-32888 Throttle Concurrent Builds plugin doesn't work Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46858) Comma separated parameters doesn't limit jobs
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know Jenkins / JENKINS-46858 Comma separated parameters doesn't limit jobs Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37938) Throttle Concurrent Builds plugin causing job config web UI to misalign badly
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know Jenkins / JENKINS-37938 Throttle Concurrent Builds plugin causing job config web UI to misalign badly Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48010) Throttling a steps{} or stage{} block has no effect in declarative syntax
Title: Message Title
Oleg Nenashev assigned an issue to Unassigned
Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know
Jenkins / JENKINS-48010
Throttling a steps{} or stage{} block has no effect in declarative syntax
Change By:
Oleg Nenashev
Assignee:
Oleg Nenashev
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37316) After Jenkins restart, concurrent builds only work after clicking 'save' on each job.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know Jenkins / JENKINS-37316 After Jenkins restart, concurrent builds only work after clicking 'save' on each job. Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49006) ConcurrentModificationException in getThrottledPipelineRunsForCategory
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know Jenkins / JENKINS-49006 ConcurrentModificationException in getThrottledPipelineRunsForCategory Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44561) Upgrading throttle-concurrent-builts-plguin från 1.9 -> 2.0 disables ability for nodes to connect in Jenkins LTS
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know Jenkins / JENKINS-44561 Upgrading throttle-concurrent-builts-plguin från 1.9 -> 2.0 disables ability for nodes to connect in Jenkins LTS Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
