[JIRA] (JENKINS-53235) SV Server is not defined shows exception
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53235 SV Server is not defined shows exception Change By: Daniel Gront Environment: Jenkins version 2.121.1 , Micro Focus Application Automation Tools 5.4.3-beta Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53235) SV Server is not defined shows exception
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53235 SV Server is not defined shows exception Issue Type: Bug Assignee: Pavel Chuchma Attachments: SVException.PNG, SVException2.PNG, SVExceptionMessage.txt Components: hp-application-automation-tools-plugin Created: 2018-08-25 06:41 Environment: Jenkins version 2.121.1 Labels: SV Priority: Major Reporter: Daniel Gront As a user that consumes the plugin through freestyle job or in the pipeline snippet generator. If I didn't configure the server, I would like not to see an exception that the server is not defined, but only a message tells me to define it.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-33412 Jenkins locks when started in HTTPS mode on a host with 37+ processors Change By: Olivier Lamy Labels: jenkins jetty winstone Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-33412 Jenkins locks when started in HTTPS mode on a host with 37+ processors Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-51136 Jenkins UI hangs 2.117 - 2.119 Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-52804 Jenkins web GUI hangs when using a computer with more then 70 CPU's Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Olivier Lamy commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Mike Scholze or anyone having the issue can you please the war here http://home.apache.org/~olamy/jenkins/ starting with the option --useQTP use --help for other new jetty options Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Olivier Lamy commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 Marco Jacob or anyone having the issue can you please the war here http://home.apache.org/~olamy/jenkins/ starting with the option --useQTP use --help for other new jetty options Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Olivier Lamy commented on JENKINS-52804 Re: Jenkins web GUI hangs when using a computer with more then 70 CPU's Eric Boehm or anyone having the issue can you please the war here http://home.apache.org/~olamy/jenkins/ starting with the option --useQTP use --help for other new jetty options Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53234) swarm-client fails to connect with 500 error while using Azure AD Plugin
Title: Message Title Steve Bouche created an issue Jenkins / JENKINS-53234 swarm-client fails to connect with 500 error while using Azure AD Plugin Issue Type: Bug Assignee: Azure DevOps Components: azure-ad-plugin Created: 2018-08-24 23:56 Environment: Jenkins 2.121.1 Jenkins Swarm client 3.13 Azure AD Plugin 0.3.0 Priority: Minor Reporter: Steve Bouche Connecting the swarm-client to Jenkins while security is set to Jenkins’ own user database is successful. Attempting to connect the swarm-client to Jenkins while security is set to Azure Active Directory is unsuccessful. $ java -jar swarm-client-3.13.jar -username USER_UPN -password USER_API_TOKEN -master http://JENKINS Aug 24, 2018 11:38:45 PM hudson.plugins.swarm.Client main INFO: Client.main invoked with: [-username USER_UPN -password PASS -master http://JENKINS] Aug 24, 2018 11:38:45 PM hudson.plugins.swarm.Client run INFO: Discovering Jenkins master SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Aug 24, 2018 11:38:45 PM hudson.plugins.swarm.SwarmClient discoverFromMasterUrl SEVERE: Failed to fetch slave info from Jenkins, HTTP response code: 500 Aug 24, 2018 11:38:45 PM hudson.plugins.swarm.Client run SEVERE: RetryException occurred hudson.plugins.swarm.RetryException: Failed to fetch slave info from Jenkins, HTTP response code: 500 at hudson.plugins.swarm.SwarmClient.discoverFromMasterUrl(SwarmClient.java:233) at hudson.plugins.swarm.Client.run(Client.
[JIRA] (JENKINS-42083) Allow Auth Type 'auto'
Title: Message Title Christian McHugh updated JENKINS-42083 This was done in release 3.2.0. Jenkins / JENKINS-42083 Allow Auth Type 'auto' Change By: Christian McHugh Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42083) Allow Auth Type 'auto'
Title: Message Title Christian McHugh updated JENKINS-42083 Jenkins / JENKINS-42083 Allow Auth Type 'auto' Change By: Christian McHugh Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42083) Allow Auth Type 'auto'
Title: Message Title Christian McHugh closed an issue as Done Jenkins / JENKINS-42083 Allow Auth Type 'auto' Change By: Christian McHugh Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title R. Tyler Croy updated JENKINS-53147 Jenkins / JENKINS-53147 Rebrand from Essentials to Evergreen Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53190) Initial admin password regenerated and reset on upgrades
Title: Message Title R. Tyler Croy updated JENKINS-53190 Jenkins / JENKINS-53190 Initial admin password regenerated and reset on upgrades Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Olivier Lamy edited a comment on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors pr here [https://github.com/jenkinsci/winstone/pull/54] I'd like to test that but you need to rebuild winstone and jenkins as well.I can do it for you but not sure how to share with you? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Olivier Lamy commented on JENKINS-52804 Re: Jenkins web GUI hangs when using a computer with more then 70 CPU's pr https://github.com/jenkinsci/winstone/pull/54 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Olivier Lamy commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors pr here https://github.com/jenkinsci/winstone/pull/54 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title jerry wiltse commented on JENKINS-53140 Re: Intermittent Random Stage Failures - No Changes Detected - Parallel Stages Here's the log from one poll cycle. This demonstrates the fact that Jenkins polls one of the SCM URL's once for each stage that exists which is curious. It polls the other SCM URL only once which seems correct: This "Bug" would seem to make more sense to me if it was doing multiple polls on the URL defined in the Jenkinsfile, but it's not. Multiple polls: http://myrepo/mypath/_automation (defined in Jenkins UI: "Jenkinsfile from SCM field") Single poll: http://myrepo/mypath/ (defined in Jenkinsfile "checkout/remote" field) Started on Aug 24, 2018 5:27:00 PM Received SCM poll call on master for myproject on Aug 24, 2018 5:27:00 PM Using sole credentials jenkins/** in realm ‘//myrepo:80> svn’ http://myrepo/mypath/_automation is at revision 52,301 Received SCM poll call on master for myproject on Aug 24, 2018 5:27:00 PM Using sole credentials jenkins/** in realm ‘//myrepo:80> svn’ http://myrepo/mypath/_automation is at revision 52,301 Received SCM poll call on master for myproject on Aug 24, 2018 5:27:00 PM Using sole credentials jenkins/** in realm ‘//myrepo:80> svn’ http://myrepo/mypath is at revision 52,313 Received SCM poll call on master for myproject on Aug 24, 2018 5:27:00 PM Using sole credentials jenkins/** in realm ‘//myrepo:80> svn’ http://myrepo/mypath/_automation is at revision 52,301 Received SCM poll call on master for myproject on Aug 24, 2018 5:27:00 PM Using sole credentials jenkins/** in realm ‘//myrepo:80> svn’ http://myrepo/mypath/_automation is at revision 52,301 Done. Took 98 ms No changes Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-45780) Date parameter not working in pipeline
Title: Message Title Erik Wong edited a comment on JENKINS-45780 Re: Date parameter not working in pipeline - I am experiencing this exact same issue with version 0.0.3 - I got it to work. For me the problem was the syntax suggested by the Pipeline Syntax Snippet Generator, it does not appear to be a problem with the plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title
jerry wiltse commented on JENKINS-53140
Re: Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Sure thing, here it is:
pipeline {
agent none
environment {
SVN_CREDENTIALS = credentials('credentialsid')
}
triggers {
pollSCM('H/2 * * * *')
upstream(
upstreamProjects: 'several/upstream/projects',
threshold: hudson.model.Result.SUCCESS
)
}
stages {
stage('Checkout') {
agent {
label 'docker && windows'
}
steps {
checkout([
$class: 'SubversionSCM',
locations: [[
credentialsId: '{credentialsid}',
local: '.',
remote: '{my_project_url}']],
workspaceUpdater: [$class: 'UpdateUpdater']])
}
}
stage('Build with Conan') {
parallel {
stage('build_mips'){
agent {
label 'docker && windows'
}
steps {
bat 'python build.py'
}
}
stage('build_arm'){
agent {
label 'docker && windows'
}
steps {
bat 'python build.py'
}
}
stage('build_msvc_15'){
agent {
label 'docker && windows'
}
steps {
bat 'python build.py'
}
}
stage('build_gcc_49'){
agent {
label 'docker && windows'
}
steps {
bat 'python build.py'
}
}
}
}
}
}
Add Comment
[JIRA] (JENKINS-51587) frequently Windows JNLP agents can't connect to Master
Title: Message Title Jeff Thompson assigned an issue to Unassigned Jenkins / JENKINS-51587 frequently Windows JNLP agents can't connect to Master Change By: Jeff Thompson Assignee: Jeff Thompson Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51587) frequently Windows JNLP agents can't connect to Master
Title: Message Title Jeff Thompson commented on JENKINS-51587 Re: frequently Windows JNLP agents can't connect to Master Ilya Gorban, you say that there was a high CPU load. Was that on the master? An overloaded system can certainly experience a number of different problems, including slow response causing a loss of connection. Have you been able to determine anything about the cause of that high load? Is it the Jenkins master process itself? Or something else on that system? If it is the Jenkins server, then you should see if you can determine what it is doing and what is causing the load. Perhaps specific jobs, maintenance, or plugins. The first thing to do is to try and isolate something of the cause. Only after that is it possible to try to figure out what needs to be corrected in which component. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53181) Jacoco adapter does not work if Jacoco plugin is installed too
Title: Message Title Jesse Glick commented on JENKINS-53181 Re: Jacoco adapter does not work if Jacoco plugin is installed too there should be a follow-up bug to Pipeline Do not bother—I see no plausible way the current behavior could be changed without a fundamental redesign of Pipeline Groovy syntax. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45780) Date parameter not working in pipeline
Title: Message Title Erik Wong commented on JENKINS-45780 Re: Date parameter not working in pipeline I am experiencing this exact same issue with version 0.0.3 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jeff Thompson commented on JENKINS-46067 Re: Pipeline task scheduled on uninitialized node It sounds like there are possibly a few different, though interacting problems going on here. Agents / nodes fail or otherwise lose their connection at times. I don't see enough information here to suggest any causes, other than system issues such as overload or other lack of resources. Some portions of the system could be more resilient in the face of such failures. Pipeline, for one example, could better handle these failures or provide more tools for handling them. There may be some issue with sequencing of nodes starting up and other things interacting with them, such as pipeline. Again, there isn't sufficient information to determine what the problematic sequencing might be. Possibly other issues, also. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jeff Thompson assigned an issue to Unassigned Jenkins / JENKINS-46067 Pipeline task scheduled on uninitialized node Change By: Jeff Thompson Assignee: Jeff Thompson Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26432) Allow shelving of Pipeline
Title: Message Title Pierre Beitz started work on JENKINS-26432 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Jeff Thompson commented on JENKINS-46067 Re: Pipeline task scheduled on uninitialized node AJ Ferrigno, it would be wise to make sure none of the nodes are overloaded. All sorts of unusual symptoms can occur when systems are overloaded. An overloaded system can cause a node or a connection to fail. Perhaps something needs to be more robust to these conditions, but reducing the load is a good step. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50868) Cannot checkout code via SSH when using blue ocean
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-50868 Cannot checkout code via SSH when using blue ocean Change By: Craig Rodrigues Summary: Cannot checkout code via SHH SSH when using blue ocean Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50868) Cannot checkout code via SSH when using blue ocean
Title: Message Title
Craig Rodrigues updated an issue
Jenkins / JENKINS-50868
Cannot checkout code via SSH when using blue ocean
Change By:
Craig Rodrigues
I use blue ocean to configure and run my build.However, when I switch to checkout over SHH SSH , it will not take the setting and will still checkout via HTTP:{noformat}> git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://bitbucket.SomeCompany.local/scm/~SomeUser/divas.git # timeout=10Cleaning workspace > git rev-parse --verify HEAD # timeout=10No valid HEAD. Skipping the resetting > git clean -fdx # timeout=10Fetching without tagsFetching upstream changes from http://bitbucket.SomeCompany.local/scm/~SomeUser/divas.git > git --version # timeout=10 > git fetch --no-tags --progress http://bitbucket.SomeCompany.local/scm/~SomeUser/divas.git +refs/heads/add-jenkins-file:refs/remotes/origin/add-jenkins-fileERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from http://bitbucket.SomeCompany.local/scm/~SomeUser/divas.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113){noformat} I can also not add another for the SHH SSH checkout, see the small picture.Adding a new one via "Add" will not add them as option in the combobox.
Add Comment
This m
[JIRA] (JENKINS-53166) CLI not filtering out non-optional dependencies of optional dependencies.
Title: Message Title R. Tyler Croy updated JENKINS-53166 Jenkins / JENKINS-53166 CLI not filtering out non-optional dependencies of optional dependencies. Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Mark Laurora created an issue Jenkins / JENKINS-53233 Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2018-08-24 19:53 Environment: Jenkins ver. 2.73.3 HP Performance Center Version 12.53 patch 1 HP Application Automation Tools plugin version 5.4 Priority: Major Reporter: Mark Laurora I am unable to run a performance test via Jenkins. I keep on getting the following message when I try to run a test: Test description: HP PC Test via Jenkins Validating parameters before run OK Trying to login [PCServer='http://SSS.com', User='SSS'] Login succeeded Executing Load Test: Test ID: 122 Test Instance ID: 2401 Timeslot Duration: 0:30(h:mm) Post Run Action: Collate and Analyze Use VUDS: false Error: executeRequest exception: Operation failed. Error code: 1001 Error: Run could not start! Logout succeeded Empty Results Result Status: UNSTABLE - - Build step 'Execute performance test using Performance Center' changed build result to UNSTABLE No results xml File provided Finished: UNSTABLE When I try to run the test in HP Performance Center 12.53, everything is fine. The test completes and I am able to view results. But when I start it in Jenkins it fails with error executeRequest exception: Operation failed. Error code: 1001 I hope you guys can help me with this. Your response is highly appreciated. Thanks in Advance!
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Folder ownership from CLI/REST API
Title: Message Title Michael Vincent commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Folder ownership from CLI/REST API FYI, I had to roll back to 0.11 to work around the createItem() issue. Hopefully it can be resolved soon Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53116) Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)
Title: Message Title Daniel Gront assigned an issue to Roy Lu Jenkins / JENKINS-53116 Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753) Change By: Daniel Gront Assignee: Daniel Gront Roy Lu Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53116) Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53116 Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753) Change By: Daniel Gront Labels: ALM Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52652) Cannot specify single files in workspace mapping
Title: Message Title Richard Lee edited a comment on JENKINS-52652 Re: Cannot specify single files in workspace mapping I think this broke the automatic addition of '/...' to perforce view mappings when using the 'depotPath:' attribute of the p4sync step.This was a breaking, not backwards compatible change. Also, if you will recall, originally, you were *required* to not specify '/...' on the end of your depotPath, or the p4-plugin would add another one itself, messing things up.You guys need to be more careful about testing, maintaining compatibility, and release notes for major breaking changes. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52739) Threads leaked when machine unavailable
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-52739 Re: Threads leaked when machine unavailable I have plans to release it on Sunday, Aug 26th. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52652) Cannot specify single files in workspace mapping
Title: Message Title Richard Lee edited a comment on JENKINS-52652 Re: Cannot specify single files in workspace mapping I think this broke the automatic addition of '/...' to perforce view mappings when using the 'depotPath:' attribute of the p4sync step . This was a breaking, not backwards compatible change. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52652) Cannot specify single files in workspace mapping
Title: Message Title Richard Lee commented on JENKINS-52652 Re: Cannot specify single files in workspace mapping I think this broke the automatic addition of '/...' to perforce view mappings. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title
Devin Nusbaum commented on JENKINS-50199
Re: Failed pipeline jobs stuck running after incorrect resume
Sam Van Oort Any thoughts on adding something like the following patch as a temporary fix in workflow-job to prevent these pipelines from resuming while we continue investigating?
diff --git a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java b/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
index 38e6ac1..70d9474 100644
--- a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
+++ b/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
@@ -752,2 +752,8 @@ public final class WorkflowRun extends Run implements F
if (!completed == Boolean.TRUE) {
+if (execution.isComplete()) {
+LOGGER.log(Level.WARNING, "JENKINS-50199: Run completion inconsistent with execution, defaulting to failure for {0}", this);
+setResult(Result.FAILURE);
+completed = Boolean.TRUE;
+needsToPersist = true;
+} else {
// we've been restarted while we were running. let's get the execution going again.
@@ -757,2 +763,3 @@ public final class WorkflowRun extends Run implements F
Timer.get().submit(() -> Queue.getInstance().schedule(new AfterRestartTask(WorkflowRun.this), 0)); // JENKINS-31614
+}
}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Gr
[JIRA] (JENKINS-51468) Update to npm 6.x
Title: Message Title R. Tyler Croy updated JENKINS-51468 Jenkins / JENKINS-51468 Update to npm 6.x Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53232) Report original commit ID when using "Merge before build"
Title: Message Title Alex Goldberg created an issue Jenkins / JENKINS-53232 Report original commit ID when using "Merge before build" Issue Type: Improvement Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin, git-plugin Created: 2018-08-24 19:08 Priority: Minor Reporter: Alex Goldberg We trigger changes on pushes to feature branches, and want to perform a local merge with master before building (in order to ensure that master will build when the feature is later merged). The "Merge before build" option on the git plugin handles this nicely, but it unfortunately leaves the workspace on a different changeset (if a fast-forward wasn't possible), as it operates by first checking out master and then merging in the feature branch. As a result, the Bitbucket Build Status Notifier plugin sometimes reports success/failure for a nonexistent changeset. We want to report status for the commit on the feature branch that triggered the build (not the throwaway local changeset resulting from merge). We can add a prebuild step to execute the git commands manually (eg. by merging master into feature with --no-commit), but then we have to manually deal with things like updating git LFS (since master may have new git lfs files) Has anyone else found a more graceful solution to this issue? Seems related to this issue: JENKINS-21536
[JIRA] (JENKINS-30328) Execution of UFT tests on the VB.NET desktop application throws an HP Tools Launcher error.
Title: Message Title Daniel Gront closed an issue as Incomplete Please try to update to the latest plugin version, if the issue still persists reopen this ticket and supply with current information. Jenkins / JENKINS-30328 Execution of UFT tests on the VB.NET desktop application throws an HP Tools Launcher error. Change By: Daniel Gront Status: Reopened Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41304) Unable to view trend report with Performance Center integration
Title: Message Title Daniel Gront closed an issue as Incomplete No response from the creator of the issue, please reopen the ticket if the issue still persists. Jenkins / JENKINS-41304 Unable to view trend report with Performance Center integration Change By: Daniel Gront Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45884) Connection to HPE Performance URL
Title: Message Title Daniel Gront closed an issue as Fixed Issue solved, but JENKINS-46678 has appeared instead. Jenkins / JENKINS-45884 Connection to HPE Performance URL Change By: Daniel Gront Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46678) Cannot run test in Performance Centre with v5.2 plugin
Title: Message Title Daniel Gront resolved as Incomplete No response from the creator of the issue, try upgrade to the latest version of the plugin, please reopen the ticket if the issue persists. Jenkins / JENKINS-46678 Cannot run test in Performance Centre with v5.2 plugin Change By: Daniel Gront Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47861) UFT Report is not a unique Build Action
Title: Message Title Daniel Gront updated JENKINS-47861 Hey, If I am not wrong it might be solved in the next release this month, please try to upgrade and if the issue persists please reopen this issue. Jenkins / JENKINS-47861 UFT Report is not a unique Build Action Change By: Daniel Gront Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47828) In case step create tunnel is failed 'Execute tests by SRF' should not begin [AGM #38834]
Title: Message Title Daniel Gront updated JENKINS-47828 No response from the creator of the issue, please reopen the ticket if the issue persists. Jenkins / JENKINS-47828 In case step create tunnel is failed 'Execute tests by SRF' should not begin [AGM #38834] Change By: Daniel Gront Status: In Review Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48001) Project performance test summary report in Jenkins is empty
Title: Message Title Daniel Gront resolved as Fixed No response from the creator of the issue, please reopen the ticket if the issue persists. Jenkins / JENKINS-48001 Project performance test summary report in Jenkins is empty Change By: Daniel Gront Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48192) HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2
Title: Message Title Daniel Gront closed an issue as Incomplete Upgrade to the latest plugin version if the issue is in the plugin, Владислав Ненашев please open another ticket with your specific information. Deep Das, if the issue still occurs reopen this issue. Jenkins / JENKINS-48192 HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2 Change By: Daniel Gront Status: Reopened Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48004) Test result analysis sometimes doesn't proceed after the test run is finished
Title: Message Title Daniel Gront closed an issue as Incomplete No response from the creator of the issue, please reopen the ticket if the issue persists. Jenkins / JENKINS-48004 Test result analysis sometimes doesn't proceed after the test run is finished Change By: Daniel Gront Status: In Progress Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48299) Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
Title: Message Title Daniel Gront closed an issue as Incomplete Upgrade to the latest version of the plugin, if the issue still occurs, please reopen the issue. Jenkins / JENKINS-48299 Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object. Change By: Daniel Gront Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48410) Trend reporting issue with HPE Application Automation Tools plugin
Title: Message Title Daniel Gront closed an issue as Fixed No response for the creator, please reopen the issue if it still persists. Jenkins / JENKINS-48410 Trend reporting issue with HPE Application Automation Tools plugin Change By: Daniel Gront Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48699) Having troubles for setting up Jenkins and ALM LoadRunner integration
Title: Message Title Daniel Gront updated JENKINS-48699 If the solution did not solve your issue, please reopen the ticket so we can find a better solution. Jenkins / JENKINS-48699 Having troubles for setting up Jenkins and ALM LoadRunner integration Change By: Daniel Gront Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50809) error: "executeRequest exception: Exception of type 'HP.PC.API.Common.Exceptions.InvalidAuthenticationDataException' was thrown. Error code: 1100 Login failed"
Title: Message Title Daniel Gront closed an issue as Fixed Jenkins / JENKINS-50809 error: "executeRequest exception: Exception of type 'HP.PC.API.Common.Exceptions.InvalidAuthenticationDataException' was thrown. Error code: 1100 Login failed" Change By: Daniel Gront Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51138) Links inside LoadRunner Analysis Reports not working [Performance Report]
Title: Message Title Daniel Gront closed an issue as Incomplete No response from the creator, If the issue reoccurs please reopen the ticket. Jenkins / JENKINS-51138 Links inside LoadRunner Analysis Reports not working [Performance Report] Change By: Daniel Gront Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51138) Links inside LoadRunner Analysis Reports not working [Performance Report]
Title: Message Title Daniel Gront stopped work on JENKINS-51138 Change By: Daniel Gront Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51265) Run Result Recorder: Didn't find any test results to record
Title: Message Title Daniel Gront commented on JENKINS-51265 Re: Run Result Recorder: Didn't find any test results to record Hey, What Jenkins version, plugin version, UFT version are you using? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53153) REST request failure during test execution if the server is ALM 12.60 p1
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53153 REST request failure during test execution if the server is ALM 12.60 p1 Change By: Daniel Gront Labels: ALM Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume John Arnold Could you upload the whole build folder for one of the zombie builds? I'm most interested in the workflow directory adjacent to build.xml to see if the serialized flow nodes tell us anything interesting, but any exceptions/warnings in the various log files would be interesting as well. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53002) Resource request in declarative pod template ignored
Title: Message Title
Matt Buckland commented on JENKINS-53002
Re: Resource request in declarative pod template ignored
Although the above yaml is wrong, I think this actually doesn't work with correct yaml. Unless mine's wrong too. Maybe I've been staring at it too long, but I think this should work but doesn't:{{}} {{}}
pipeline {
agent {
kubernetes {
label 'moo'
inheritFrom 'default'
yaml """
apiVersion: v1
kind: Pod
spec:
containers:
- name: jnlp
resources:
limits:
cpu: 1
memory: 1Gi
requests:
cpu: 200m
memory: 256Mi
"""
}
}
{{}}I'm on version 1.12.0 btw.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title John Arnold commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Devin Nusbaum Sam Van Oort Is there any additional data I can gather for you. I have lots of repros of this problem. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53231) Detect script/expression usages that can be replaced with pure Declarative and log them
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-53231 Detect script/_expression_ usages that can be replaced with pure Declarative and log them Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-08-24 16:25 Priority: Major Reporter: Andrew Bayer It would be interesting to see if we could inspect script and _expression_ blocks in Declarative validation and look for instances of use cases/patterns/strings that could be replaced by a standard Declarative directive/condition/option, or which served no purpose at all. We'd log those as compiler warnings with a short "hey, don't do that, do this [link to example]", with a page on jenkins.io for the examples. This could look for things like: Setting currentBuild.result = "FAILURE" in a post failure block - that's just totally redundant, why bother. _expression_ blocks that are just if (foo == "bar") (which can be replaced with the equals condition) and other simple if clauses that have direct equivalent conditions. ...ok, need to think of more.
[JIRA] (JENKINS-52636) Gerrit triggered jobs getting delayed
Title: Message Title Fred May commented on JENKINS-52636 Re: Gerrit triggered jobs getting delayed In the situation above, we have found the vast majority of the Gerrit events relate to "git notes" in the git repos. They are not required for triggering Jenkins jobs. A plugin config option that would allow certain events to be ignored by the plugin would be useful. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53230) Add a when condition for "the build hasn't failed or gone unstable etc"
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-53230 Add a when condition for "the build hasn't failed or gone unstable etc" Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-08-24 16:14 Priority: Minor Reporter: Andrew Bayer While poking around GitHub to see if I can find examples that would be broken by the current PR for JENKINS-52114, I'm running across a lot of Jenkinsfiles containing either _expression_ or script with if (currentBuild.result == null || currentBuild.result == 'SUCCESS') or variants thereof. While there is the skipStagesAfterUnstable() option, and any actual failure (i.e., that isn't just something setting currentBuild.result directly) will prevent subsequent stages from being executed, I can see some merit in there being a when condition that just means "Run if the build is still successful/hasn't failed yet/hasn't gone unstable yet". Add Comment
[JIRA] (JENKINS-53229) Regression: Variables set in generateEnv are unset by the SECOND envInject
Title: Message Title Tony Bridges created an issue Jenkins / JENKINS-53229 Regression: Variables set in generateEnv are unset by the SECOND envInject Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 2018-08-24 15:49 Priority: Major Reporter: Tony Bridges Effective in 2.1.5 (and possibly earlier) the behaviour of multiple invocations of envInject has changed. We are experiencing a regression issue in multiple jobs. It appears that the second invocation of envInject "undoes" the settings laid down in the previous invocation, but only for values that we set in GenerateEnv. Prior to this, settings were additive, and in fact, they are for values that are NOT in the generate step. For example : Generate : VAR1=A (works, subsequent steps see VAR=A) EnvInject : VAR1=B VAR2=C (works, subsequent steps see VAR1=B VAR2=C) EnvInject : VAR3=D (fails, subsequent steps see VAR1=A, VAR2=C, VAR3=D) Taking a guess, and assuming that the system keeps a list of variables to playback at the beginning of each step, it feels like the env playback is adding the base env settings from generate before each envInject, > GenList+Inject1 > GenList+Inject1+GenList+Inject2 > GenList+Inject1+GenList+Inject2+GenList+Inject3 and the effect is that settings in Inject1 that overrode GenList will only work after the first inject. We are seeing this behaviour in multiple builds after upgrading to 2.73 Jenkins and 2.1.5 envInject
[JIRA] (JENKINS-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Jesse Glick commented on JENKINS-48050 Re: Replace Declarative Docker agent directive with new implementation Alternate simpler approach: docker PR 681 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53227) evergreen-client should do integrity checking on downloads and gracefully handle errors
Title: Message Title Jesse Glick commented on JENKINS-53227 Re: evergreen-client should do integrity checking on downloads and gracefully handle errors I am seeing this randomly, with different plugins each time, on every startup, and I do not think I am on a poor connection. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53228) RFE: Convert edit window for raw yaml to use a monospace font
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-53228 RFE: Convert edit window for raw yaml to use a monospace font Change By: Karl Shultz Summary: RFE: Convert edit window for raw yaml to use a monospace font Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53228) RFE: Convert edit window for raw yaml use a monospace font
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-53228 RFE: Convert edit window for raw yaml use a monospace font Issue Type: Improvement Assignee: Carlos Sanchez Attachments: image-2018-08-24-10-50-48-669.png, image-2018-08-24-10-52-06-129.png Components: kubernetes-plugin Created: 2018-08-24 14:53 Priority: Minor Reporter: Karl Shultz At present, the edit window for entering raw yaml for a Kubernetes pod template uses a proportional font. Hand-editing this raw yaml could be a lot easier of that edit window used a monospace font. Existing raw yaml editor looks like this: The inline Pipeline editor, for example, looks like this. It even has handy lines in it to show you indentations, etc. Just yesterday, I made an editing mistake that I think could have been avoided had the yaml been easier to see in that edit window. Thanks for your consideration! Add Comment
[JIRA] (JENKINS-53227) evergreen-client should do integrity checking on downloads and gracefully handle errors
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-53227 evergreen-client should do integrity checking on downloads and gracefully handle errors Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-08-24 14:45 Priority: Major Reporter: R. Tyler Croy Denys Digtiar spotted this series of errors when using Evergreen on a poor network connection. It appears that there are a number of invalid respoonses, perhaps from a captive portal or otherwise, which are being saved as .hpi files and then obviously fail to load. The client has the checksums to do integrity checking already, so we should be performing that validation and retrying. If clients are consistently failing to download artifacts, then we're going to have to figure out some reasonable way to inform the user, which is a bit out of the scope for this bug IMO Add Comment
[JIRA] (JENKINS-50097) MavenConsole parser skips duplicate lines
Title: Message Title Ulli Hafner stopped work on JENKINS-50097 Change By: Ulli Hafner Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51383) Jenkinsfile post success condition triggers after NoSuchMethodError Exception
Title: Message Title Andrew Bayer updated JENKINS-51383 Jenkins / JENKINS-51383 Jenkinsfile post success condition triggers after NoSuchMethodError Exception Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51466) Improve description of reference build
Title: Message Title Ulli Hafner updated JENKINS-51466 Jenkins / JENKINS-51466 Improve description of reference build Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51872) Dropdown options appear blank in Declarative Directive Generator
Title: Message Title Andrew Bayer updated JENKINS-51872 Jenkins / JENKINS-51872 Dropdown options appear blank in Declarative Directive Generator Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53181) Jacoco adapter does not work if Jacoco plugin is installed too
Title: Message Title Share Cheng commented on JENKINS-53181 Re: Jacoco adapter does not work if Jacoco plugin is installed too Ramin Baradari You can use `jacocoAdapter` instead of `jacoco` to avoid name conflicts in version 1.0.4. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title Ingmar Karge commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library I think the workaround is too inconvenient to use. I want to include my own library (which I already use in the jenkins pipeline) and not an external lib. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53149) GitHubCommitStatusSetter is not reading proper commit id from a shared library
Title: Message Title Manuel de la Peña commented on JENKINS-53149 Re: GitHubCommitStatusSetter is not reading proper commit id from a shared library It is weird: the commitId used to update the github status is properly captured in pull requests, but not on master branch, where the commitId used is the head commit of the shared library. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Oliver Gondža closed an issue as Fixed Guys, this ticket was resolved year and a half ago. Please, file a separate issue. Jenkins / JENKINS-24824 Asynchronous cleanup not removing renamed workspace directories on slaves Change By: Oliver Gondža Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53163) LR scenario started but no results showing
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-53163 Re: LR scenario started but no results showing Hello vikram, I do not understand exactly this ticket. This is marked as an improvement and you attached some logs (some from 2016/2017). Could you please provide more details. Regards, Rolando Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53181) Jacoco adapter does not work if Jacoco plugin is installed too
Title: Message Title Oleg Nenashev commented on JENKINS-53181 Re: Jacoco adapter does not work if Jacoco plugin is installed too We will need the same fix in Cobertura Plugin before it gets released (CC Jeff Pearce). I believe there should be a follow-up bug to Pipeline, because it's just a matter of time till somebody hits it Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Devin Nusbaum commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Sam Van Oort I have been looking at the issue. Like I commented here I don't think that case is actually a reproduction, because it does complete if you increase the timeout, although I might be misunderstanding the test case. I have been trying to find a way to reproduce the problem, but have been unsuccessful so far. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Marco Jacob commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 No change with reduced amount of GC. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51136) Jenkins UI hangs 2.117 - 2.119
Title: Message Title Marco Jacob commented on JENKINS-51136 Re: Jenkins UI hangs 2.117 - 2.119 I can do this, but that is normal for server jvm on solaris. 2.107.3 is also running with this settings without any problem. Any other suggestions? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38181) withCredentials variables that are extracted are not masked outside of block
Title: Message Title Jesse Glick resolved as Won't Fix As discussed above. Jenkins / JENKINS-38181 withCredentials variables that are extracted are not masked outside of block Change By: Jesse Glick Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Mike Scholze commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors No change with that env var. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24479) The vSphere cloud will not allow this slave to start at this time.
Title: Message Title Artur Szostak commented on JENKINS-24479 Re: The vSphere cloud will not allow this slave to start at this time. We are using Jenkins 2.121.3 and vsphere-cloud-plugin 2.18. Getting "ERROR: The vSphere cloud will not allow this slave to start at this time." randomly for our Jenkins + vSphere cloud setup. Have a single vSphere cloud configured with about 10 different templates (configured automatically with a Groovy script), each template is limited to a max of 50 instances. The total instance count for the cloud is limited to 100. We see between 5% - 30% VMs do not start properly with the above error message in the log. I would say this shows classic symptoms of a race condition in the plugin / Jenkins code. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53194) InfluxDB error failed to collect data after updates
Title: Message Title Grzegorz Dziegielewski commented on JENKINS-53194 Re: InfluxDB error failed to collect data after updates Yes, exactly same error. [InfluxDB Plugin] Failed to collect data. Ignoring Exception:java.lang.NullPointerException ERROR: Build step failed with exception java.lang.NullPointerException at jenkinsci.plugins.influxdb.generators.CustomDataPointGenerator.(CustomDataPointGenerator.java:27) at jenkinsci.plugins.influxdb.InfluxDbPublisher.perform(InfluxDbPublisher.java:341) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.cleanUp(Build.java:196) at hudson.model.Run.execute(Run.java:1845) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Eric Boehm commented on JENKINS-52804 Re: Jenkins web GUI hangs when using a computer with more then 70 CPU's I tried adding JETTY_AVAILABLE_PROCESSORS=32 with 72 processors. It made no difference. I've attached my log. I am using the jul.properties example. Here's how Jenkins was started bash -x ./jenkins.sh start + DESC='Jenkins CI Server' + NAME=jenkins + JENKINS_USER=bcabuild + JENKINS_HOME=/opt/jenkins/mj-dashboard.new/jenkins_runtime + JENKINS_PORT=8288 + JENKINS_HOST=10.75.159.34 + export JETTY_AVAILABLE_PROCESSORS=32 + JETTY_AVAILABLE_PROCESSORS=32 + LOGFILE=/opt/jenkins/mj-dashboard.new/jenkins.log + export JAVA_HOME=/usr/java/jdk1.8.0_144 + JAVA_HOME=/usr/java/jdk1.8.0_144 + JAVA=/usr/java/jdk1.8.0_144/bin/java + CMD='nohup /usr/java/jdk1.8.0_144/bin/java -Xss2048k -Xms4g -Xmx4g -XX:MaxPermSize=1g -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses -Djenkins.upstreamCulprits=true -Dhudson.upstreamCulprits=true -Dhudson.DNSMultiCast.disabled=true -Djava.util.logging.config.file=/opt/jenkins/mj-dashboard.new/jenkins_runtime/jul.properties -DJENKINS_HOME=/opt/jenkins/mj-dashboard.new/jenkins_runtime/ -jar /opt/jenkins/mj-dashboard.new/jenkins_runtime/jenkins.war --httpPort=8288 --httpListenAddress=10.75.159.34 >> /opt/jenkins/mj-dashboard.new/jenkins.log 2>&1 &' + case $1 in + echo -n 'Starting Jenkins CI Server' Starting Jenkins CI Server+ d_start + ulimit -v 12800 + ulimit -c 200 + ulimit -a core file size (blocks, -c) 200 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 1549304 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 1549304 virtual memory (kbytes, -v) 12800 file locks (-x) unlimited + /bin/su -p -c 'nohup /usr/java/jdk1.8.0_144/bin/java -Xss2048k -Xms4g -Xmx4g -XX:MaxPermSize=1g -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses -Djenkins.upstreamCulprits=true -Dhudson.upstreamCulprits=true -Dhudson.DNSMultiCast.disabled=true -Djava.util.logging.config.file=/opt/jenkins/mj-dashboard.new/jenkins_runtime/jul.properties -DJENKINS_HOME=/opt/jenkins/mj-dashboard.new/jenkins_runtime/ -jar /opt/jenkins/mj-dashboard.new/jenkins_runtime/jenkins.war --httpPort=8288 --httpListenAddress=10.75.159.34 >> /opt/jenkins/mj-dashboard.new/jenkins.log 2>&1 &' bcabuild The log shows that I started running curl -I 'http://10.75.159.34:8288/login' at 04:41:24 FINE: isSystemResource==false hudson.slaves.NodeProvisioner$2 jar:file:/opt/jenkins/mj-dashboard.new/jenkins_runtime/war/WEB-INF/lib/jenkins-core-2.117.jar!/hudson/slaves/NodeProvisioner$2.class Aug 24, 2018 4:39:59 AM org.eclipse.jetty.webapp.WebAppClassLoader loadClass FINE: WAP webapp loaded class hudson.slaves.NodeProvisioner$2 Aug 24, 2018 4:41:24 AM org.eclipse.jetty.io.ManagedSelector submit FINE: Queued change org.eclipse.jetty.io.ManagedSelector$Accept@3ce973aa on org.eclipse.jetty.io.ManagedSelector@4c2bb6e0 id=7 keys=0 selected=0 actions=0 I finally killed it 5 minutes later I then tried to access it from a web browser (Chrome, http://10.75.159.34:8288/login). I let it run for 5 minutes, starting at 04:47:12 I also saw the request for a jstack. I ran the following jstack 34908 > jstack.out 2>&1 jstack -F 34908 > jstack.out.F 2>&1 cp jenkins.log jenkins.log.save cat /dev/null > jenkins.log kill -3 34980 cp jenkins.log jenkins.threaddump I've attached jenkins.log.save, jenkins.threaddump, jstack.out, jstack.out.F
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Eric Boehm updated an issue Jenkins / JENKINS-52804 Jenkins web GUI hangs when using a computer with more then 70 CPU's Change By: Eric Boehm Attachment: jenkins.log.save Attachment: jenkins.threaddump Attachment: jstack.out Attachment: jstack.out.F Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53194) InfluxDB error failed to collect data after updates
Title: Message Title
Aleksi Simell commented on JENKINS-53194
Re: InfluxDB error failed to collect data after updates
Grzegorz Dziegielewski Did your configuration also complain about java.lang.NullPointerException {{ at jenkinsci.plugins.influxdb.generators.CustomDataPointGenerator.(CustomDataPointGenerator.java:27)}}? I just tried with a job (not pipeline), that only publishes to InfluxDB, but was not able to reproduce this with version 1.18. I couldn't reproduce with a pipeline job either with customData or null customData.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53226) Incorporate WS Cleanup plugin
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-53226 Incorporate WS Cleanup plugin Issue Type: Improvement Assignee: Scott Hebert Components: foreman-node-sharing-plugin Created: 2018-08-24 11:56 Priority: Major Reporter: Pavel Janoušek It'd be nice to have an ability to remove a garbage before we return a node back to the pool. I think the best solution might be to incorporate WS Cleanup plugin (with all its cfg. options) into the last step before we release a node. Add Comment
[JIRA] (JENKINS-51758) Register new vsphere template under vsphere plugin via groovy/jenkinsfile
Title: Message Title Guillermo Menjivar commented on JENKINS-51758 Re: Register new vsphere template under vsphere plugin via groovy/jenkinsfile Wow thanks alot I will try this! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Olivier Lamy commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors jstack? what happen with env var or sys prop JETTY_AVAILABLE_PROCESSORS=32 (or different value)? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Olivier Lamy commented on JENKINS-52804 Re: Jenkins web GUI hangs when using a computer with more then 70 CPU's is it possible to have a jstack when it hang? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52804 Jenkins web GUI hangs when using a computer with more then 70 CPU's Change By: Oleg Nenashev Component/s: winstone-jetty Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52804 Jenkins web GUI hangs when using a computer with more then 70 CPU's Change By: Oleg Nenashev Labels: jetty regression Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53194) InfluxDB error failed to collect data after updates
Title: Message Title Grzegorz Dziegielewski commented on JENKINS-53194 Re: InfluxDB error failed to collect data after updates After downgrading Jenkins told me that i have some incompatible settings in the InfluxDB part, but i forgot to write it down. And can't reproduce it. It looked for me like there should be an empty array but there was null. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52804) Jenkins web GUI hangs when using a computer with more then 70 CPU's
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52804 Jenkins web GUI hangs when using a computer with more then 70 CPU's Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
