[JIRA] (JENKINS-59736) No new commits used if LocalBranch checked in same workspace
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59736 No new commits used if LocalBranch checked in same workspace Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202454.1570741853000.5308.1570772820171%40Atlassian.JIRA.
[JIRA] (JENKINS-59149) 'Test Connection' succesfully sends a message, but build-event notifications don't get sent
Title: Message Title Daniel Bocksteger commented on JENKINS-59149 Re: 'Test Connection' succesfully sends a message, but build-event notifications don't get sent Martin Reinhardt when will be this update available via the Update-Center? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201585.1567146235000.5305.1570769820235%40Atlassian.JIRA.
[JIRA] (JENKINS-59243) When build is in Queue, it shows all the available labels instead specified label.
Title: Message Title Shiva Kumar assigned an issue to Unassigned Jenkins / JENKINS-59243 When build is in Queue, it shows all the available labels instead specified label. Change By: Shiva Kumar Assignee: jenkins admin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201701.1567674683000.5303.1570767780266%40Atlassian.JIRA.
[JIRA] (JENKINS-59739) Thin backup is not taking backup of all jobs
Title: Message Title Shiva Kumar created an issue Jenkins / JENKINS-59739 Thin backup is not taking backup of all jobs Issue Type: Bug Assignee: Thomas Fürer Components: thinbackup-plugin Created: 2019-10-11 04:20 Priority: Critical Reporter: Shiva Kumar Thin backup is not taking backup of all jobs only 30Gb is backed up, but we have more than 100GB data in .jenkins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59738) how to change jenkins jnpl slave resource limit
Title: Message Title xiaoping huang created an issue Jenkins / JENKINS-59738 how to change jenkins jnpl slave resource limit Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-10-11 04:13 Priority: Minor Reporter: xiaoping huang resources: limits: memory: "512Mi" cpu: "512m" requests: memory: "512Mi" cpu: "512m" I want to change 512to 2048 ，how to Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-55953) JCasC compability with RocketChat Notifier Plugin
Title: Message Title Martin Reinhardt assigned an issue to Uwe Hanisch Could you give version 1.4.6 a try? Jenkins / JENKINS-55953 JCasC compability with RocketChat Notifier Plugin Change By: Martin Reinhardt Assignee: Martin Reinhardt Uwe Hanisch Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197363.1549289231000.5296.1570767120211%40Atlassian.JIRA.
[JIRA] (JENKINS-56087) Chanel name case sensitive error ignored
Title: Message Title Martin Reinhardt assigned an issue to Lionel FÉLICITÉ Could you retry with version 1.4.6? Jenkins / JENKINS-56087 Chanel name case sensitive error ignored Change By: Martin Reinhardt Assignee: Martin Reinhardt Lionel FÉLICITÉ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197516.1549893316000.5294.1570766940144%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Martin Reinhardt resolved as Fixed Fixed in Version 1.4.6 Jenkins / JENKINS-59503 Plugin does not save settings Change By: Martin Reinhardt Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-42365) Test Connection fails with Rocket.Chat API 0.46.0
Title: Message Title Martin Reinhardt resolved as Fixed Fixed in Version 1.4.6 Jenkins / JENKINS-42365 Test Connection fails with Rocket.Chat API 0.46.0 Change By: Martin Reinhardt Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59149) 'Test Connection' succesfully sends a message, but build-event notifications don't get sent
Title: Message Title Martin Reinhardt resolved as Fixed Fixed in Version 1.4.6 Jenkins / JENKINS-59149 'Test Connection' succesfully sends a message, but build-event notifications don't get sent Change By: Martin Reinhardt Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on
[JIRA] (JENKINS-59149) 'Test Connection' succesfully sends a message, but build-event notifications don't get sent
Title: Message Title Martin Reinhardt commented on JENKINS-59149 Re: 'Test Connection' succesfully sends a message, but build-event notifications don't get sent I was able to reproduce the error locally and provide a fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201585.1567146235000.5281.1570766400220%40Atlassian.JIRA.
[JIRA] (JENKINS-56562) Parallel downstream jobs are not linked correctly
Title: Message Title Jiefu Zheng commented on JENKINS-56562 Re: Parallel downstream jobs are not linked correctly We're having a hard time without downstream jobs linked(more switching between blue ocean/classic, opening huge build log to find links), would really appreciate this issue to be fixed, and sorry for the spam. Orz Orz Orz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198177.1552574352000.5276.1570760880336%40Atlassian.JIRA.
[JIRA] (JENKINS-59737) sshUserPrivateKey's "KeyFileVariable" is missing drive letter on windows
Title: Message Title
p cowlinator created an issue
Jenkins / JENKINS-59737
sshUserPrivateKey's "KeyFileVariable" is missing drive letter on windows
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2019-10-10 22:16
Environment:
Master: Jenkins v 2.176.1 from docker image jenkins/jenkins:lts Credential binding plugin v 1.19 Node: Windows Server 2019 (amd64)
Labels:
plugin credentials Credentials
Priority:
Major
Reporter:
p cowlinator
I am seeing a bug when using withCredentials([sshUserPrivateKey(credentialsId: 'myCred', keyFileVariable: 'privateSshKey')]){} Documentation for keyFileVariable states that it is "an environment variable to be set to the temporary path of the SSH key file". The problem is that the value of the variable is a nearly, but not quite, absolute path. On Windows specifically, it is missing the drive letter and colon. This causes it to fail with commands such as "ssh -i ${privateSshKey} myUrl". Example: If the actual path is `C:\home\jenkins\agent\workspace\myjob@abc\def\ghi-privateSshKey`, then the environment variable is incorrectly set to `/home/jenkins/agent/workspace/myjob@abc/def/ghi-privateSshKey` This was very difficult to debug because the plugin masks/censors all output containing the path. There should be a way to opt out of the masking of logs.
[JIRA] (JENKINS-59725) Bump to HikariCP 3.4.1
Title: Message Title Cyrille Le Clerc closed an issue as Fixed fixed in 3.8.2 Jenkins / JENKINS-59725 Bump to HikariCP 3.4.1 Change By: Cyrille Le Clerc Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59583) JunitTestsPublisher: Also set stage result
Title: Message Title Cyrille Le Clerc closed an issue as Fixed fixed in 3.8.2 Jenkins / JENKINS-59583 JunitTestsPublisher: Also set stage result Change By: Cyrille Le Clerc Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Alex Earl commented on JENKINS-59734 Re: mailer/email-ext settings persist after removing from JCasC yaml You would need to clean your JENKINS_HOME, configuration as code will not remove anything as far as I know. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202452.1570740669000.5269.1570743900118%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier commented on JENKINS-59707 Re: Give more details in the connection success panel Maybe something like cc Ryan Campbell (it's just an idea) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.5254.1570742820052%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Attachment: Screenshot 2019-10-10 23.24.15.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.5253.1570742700064%40Atlassian.JIRA.
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Jonathan B commented on JENKINS-59734 Re: mailer/email-ext settings persist after removing from JCasC yaml The expectation is that, by omitting the files from configuration-as-code, the plugin's configuration files on disk should be removed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202452.1570740669000.5247.1570742460259%40Atlassian.JIRA.
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Jonathan B edited a comment on JENKINS-59734 Re: mailer/email-ext settings persist after removing from JCasC yaml The expectation is that, by omitting the files from configuration-as-code yaml , the plugin's configuration files on disk should be removed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202452.1570740669000.5249.1570742460290%40Atlassian.JIRA.
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Alex Earl closed an issue as Not A Defect Jenkins / JENKINS-59734 mailer/email-ext settings persist after removing from JCasC yaml Change By: Alex Earl Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202452.1570740669000.5241.1570742220381%40Atlassian.JIRA.
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Alex Earl commented on JENKINS-59734 Re: mailer/email-ext settings persist after removing from JCasC yaml If the files exist then they will be deserialized and the configuration will be populated. This is expected behavior. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202452.1570740669000.5239.1570742220348%40Atlassian.JIRA.
[JIRA] (JENKINS-59736) No new commits used if LocalBranch checked in same workspace
Title: Message Title
vladislav piskunov updated an issue
Jenkins / JENKINS-59736
No new commits used if LocalBranch checked in same workspace
Change By:
vladislav piskunov
Reproduce steps: * Create branch * Execute pipeline with LocalBranch * Add commits to branch * Repeat pipeline in same workspace - no new commits will be used from originalCriteria to reproduce: * Usage of LocalBranch extension * Usage of original branch name containig '/' symbolProblem in class:{code:java}hudson.plugins.git.util.DefaultBuildChooser#getCandidateRevisions{code}Example Pipeline:{code:java}node('master') {stage('Checkout'){script {String url = ''//: Branch name containing `/` symbolString branch = 'feature/branch'String credentialsId = 'secret-credentials'//: Checkout originalcheckout scm: [$class: 'GitSCM',userRemoteConfigs: [[ url: url, credentialsId: credentialsId]],extensions: [[$class: 'LocalBranch']],branches: [[name: branch]]]//: Change local historysh('git reset --hard HEAD^')//: Checkout one more time - local history will be usedcheckout scm: [$class: 'GitSCM',userRemoteConfigs: [[ url: url, credentialsId: credentialsId]],extensions: [[$class: 'LocalBranch']],branches: [[name: branch]]]}}} {code} Workaround:Execute before checkout {code :java } sh('rm -rf .git/refs/heads/*'){code}To remove local branches refs
Add Comment
[JIRA] (JENKINS-59736) No new commits used if LocalBranch checked in same workspace
Title: Message Title
vladislav piskunov created an issue
Jenkins / JENKINS-59736
No new commits used if LocalBranch checked in same workspace
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-10-10 21:10
Environment:
Any version from
Priority:
Minor
Reporter:
vladislav piskunov
Reproduce steps:
Create branch
Execute pipeline with LocalBranch
Add commits to branch
Repeat pipeline in same workspace - no new commits will be used from original
Criteria to reproduce:
Usage of LocalBranch extension
Usage of original branch name containig '/' symbol
Problem in class:
hudson.plugins.git.util.DefaultBuildChooser#getCandidateRevisions
Example Pipeline:
node('master') {
[JIRA] (JENKINS-59735) Tee step intermittently truncates output
Title: Message Title
Jonathan B created an issue
Jenkins / JENKINS-59735
Tee step intermittently truncates output
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2019-10-10 20:56
Environment:
Jenkins 2.190.1 pipeline-utility-steps 2.3.1
Priority:
Minor
Reporter:
Jonathan B
We have a pipeline with code along the lines of ``` tee('output.log') { sh 'terraform plan' } ``` and we've noticed that output.log is occasionally truncated (the end of the file has a predictable pattern, so we alert on when it's missing), while stdout, as shown in the Jenkins console log, is not truncated. We've seen this happen even when output.log was not a large file (just a few kilobytes). It seems to happen the most when there's a lot of build congestion (many jobs running concurrently). It doesn't happen often and we haven't found a way to reproduce the issue at will.
Add Comment
[JIRA] (JENKINS-59735) Tee step intermittently truncates output
Title: Message Title
Jonathan B updated an issue
Jenkins / JENKINS-59735
Tee step intermittently truncates output
Change By:
Jonathan B
We have a pipeline with code along the lines of ``` {code} tee('output.log') { sh 'terraform plan'} ``` {code} and we've noticed that output.log is occasionally truncated (the end of the file has a predictable pattern, so we alert on when it's missing), while stdout, as shown in the Jenkins console log, is not truncated.We've seen this happen even when output.log was not a large file (just a few kilobytes). It seems to happen the most when there's a lot of build congestion (many jobs running concurrently). It doesn't happen often and we haven't found a way to reproduce the issue at will.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Jonathan B created an issue Jenkins / JENKINS-59734 mailer/email-ext settings persist after removing from JCasC yaml Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin, mailer-plugin Created: 2019-10-10 20:51 Environment: Jenkins 2.190.1 mailer-plugin 1.29 email-ext 2.66 Priority: Minor Reporter: Jonathan B We recently switched our existing Jenkins server over to configuration-as-code. Prior to the change, we had mailer and email-ext configured in a certain way. The new configuration yaml omits any configuration for those plugins because we no longer wish to configure them. However, the Jenkins settings page (in the web UI) still shows the configuration that existed before, for both plugins. The files hudson.plugins.emailext.ExtendedEmailPublisher.xml and hudson.tasks.Mailer.xml in the Jenkins home directory both still exist and are populated. Is this expected behavior? Add Comment
[JIRA] (JENKINS-58383) Disable aggregated analysis results
Title: Message Title Stefan Thurnherr commented on JENKINS-58383 Re: Disable aggregated analysis results Ulli Hafner Thanks for fixing this - I've tried chart type "None" and it works fine to disable the aggregated graphs! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200507.1562597544000.5220.1570740667284%40Atlassian.JIRA.
[JIRA] (JENKINS-59732) SSH agent descriptors shouldn't say "agent agents"
Title: Message Title Nick Jones commented on JENKINS-59732 Re: SSH agent descriptors shouldn't say "agent agents" See https://github.com/jenkinsci/ssh-slaves-plugin/pull/159 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202450.1570725387000.5205.1570734900375%40Atlassian.JIRA.
[JIRA] (JENKINS-59732) SSH agent descriptors shouldn't say "agent agents"
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-59732 SSH agent descriptors shouldn't say "agent agents" Change By: Nick Jones Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202450.1570725387000.5203.1570734900340%40Atlassian.JIRA.
[JIRA] (JENKINS-59713) Glassfish 4 Failed deployment: org.codehaus.cargo.util.CargoException: Deployment has failed: null
Title: Message Title Robin Jansohn commented on JENKINS-59713 Re: Glassfish 4 Failed deployment: org.codehaus.cargo.util.CargoException: Deployment has failed: null I'm no GlassFish user so I can't reproduce this on my machine at the moment. I checked the code mentioned in the stack trace and the problem seems to be that the GlassFish deployment step returns failed instead of success. Maybe you can try deployment interactively to see if that is not working either? Otherwise you need to give some more information, e.g. has it ever worked before, have you tried different different WAR locations (I see you are using drive D), are you using Jenkins slaves/agents, etc. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202422.157062835.5201.1570733400239%40Atlassian.JIRA.
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title William Brode commented on JENKINS-52806 Re: Pipeline: Parallel syncs don't set environment variables properly. Yeah, we basically do the same. I can't promise anything but I'll do my best to get to this in 2 weeks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192727.153298856.5199.1570731360413%40Atlassian.JIRA.
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title Matthew Dews commented on JENKINS-52806 Re: Pipeline: Parallel syncs don't set environment variables properly. That'd be great. Currently we maintain separate Jenkinsfiles for CI jobs across different platform's CI so that they can run at the same time, while avoiding this bug. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192727.153298856.5185.1570730340273%40Atlassian.JIRA.
[JIRA] (JENKINS-4859) Slaves cannot be started using Windows Service on Windows Server 2008 x64
Title: Message Title Mark Waite commented on JENKINS-4859 Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64 paul hendley with Windows Server 2019 and with the most recent Windows 10 service packs Microsoft now provides the Microsoft OpenSSH Server. If you're using new enough operating systems, it is much simpler to manage the Windows agents with ssh than to fight with the DCOM approach used by the windows slaves plugin. Refer to the windows section of the ssh-slaves plugin for more information. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.134932.1258346923000.5166.1570729140575%40Atlassian.JIRA.
[JIRA] (JENKINS-4859) Slaves cannot be started using Windows Service on Windows Server 2008 x64
Title: Message Title paul hendley commented on JENKINS-4859 Re: Slaves cannot be started using Windows Service on Windows Server 2008 x64 Encountering same thing. no upvotes so adding support of others comments. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.134932.1258346923000.5147.1570728660584%40Atlassian.JIRA.
[JIRA] (JENKINS-59733) Changing JENKINS_DEBUG_LEVEL does not affect log level
Title: Message Title Ali H created an issue Jenkins / JENKINS-59733 Changing JENKINS_DEBUG_LEVEL does not affect log level Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-10 16:54 Priority: Minor Reporter: Ali H Changing JENKINS_DEBUG_LEVEL to either "1" or "9" does not affect log level. With either, I still see the same logs, INFO level logs. Jenkins v2.190.1 on CentOS 7.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59388) Broken formatting for Boolean parameters
Title: Message Title Josh Soref commented on JENKINS-59388 Re: Broken formatting for Boolean parameters It's by design. It will look better when we switch away from the table layout. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201944.1568631629000.5124.1570726270265%40Atlassian.JIRA.
[JIRA] (JENKINS-59480) Automatically label SUSE Linux Enterprise Server agents
Title: Message Title Mark Waite updated JENKINS-59480 Jenkins / JENKINS-59480 Automatically label SUSE Linux Enterprise Server agents Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202095.1569240565000.5122.1570725900515%40Atlassian.JIRA.
[JIRA] (JENKINS-59480) Automatically label SUSE Linux Enterprise Server agents
Title: Message Title Mark Waite started work on JENKINS-59480 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202095.1569240565000.5120.1570725900491%40Atlassian.JIRA.
[JIRA] (JENKINS-59480) Automatically label SUSE Linux Enterprise Server agents
Title: Message Title Mark Waite assigned an issue to Markus Winter Jenkins / JENKINS-59480 Automatically label SUSE Linux Enterprise Server agents Change By: Mark Waite Assignee: Markus Winter Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202095.1569240565000.5118.1570725900454%40Atlassian.JIRA.
[JIRA] (JENKINS-59732) SSH agent descriptors shouldn't say "agent agents"
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-59732 SSH agent descriptors shouldn't say "agent agents" Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2019-10-10 16:36 Priority: Trivial Reporter: Nick Jones This is a leftover artifact from when this used to say "slave agents", but now results in redundant/nonsensical text like "Launch agent agents via SSH". This should be cleaned up. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-59567) Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Title: Message Title red der commented on JENKINS-59567 Re: Server Credentials created from Jenkins credentials don't show up in maven settings.xml this can be closed. I gave up and just used a secret file to store my entire config instead. I realized I dont really need this plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202202.1569618942000.5100.1570724220137%40Atlassian.JIRA.
[JIRA] (JENKINS-59730) text-finder sets whole matrix job to "not built" even if only one configuration matched
Title: Message Title
Basil Crow commented on JENKINS-59730
Re: text-finder sets whole matrix job to "not built" even if only one configuration matched
Thanks for reporting this, Christoph Berg. Would you be willing to write a unit test that reproduces the issue, marked with @Ignore and @Issue("JENKINS-59730")? The existing tests should serve as a good example to follow, modulo using using MatrixProject instead of FreestyleProject via something like MatrixProject createMatrixProject = jenkins.createProject(MatrixProject.class, "mp"). This would greatly facilitate getting the issue fixed.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202448.1570712752000.5088.1570722780104%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title
tapvir virk commented on JENKINS-59633
Re: EC2 Plguin: Windows EC2 instances are not launching
Below is the cli request and the response aws ec2 get-password-data --instance-id i-xx --region ca-central-1 { "InstanceId": "i-x", "Timestamp": "2019-10-10T15:48:21.000Z", "PasswordData": "\r\nPdbgYc5e0hJZAxqgrcGSPdEGmrno+6kCXej8hApQC2f05pfjCnUZVb/vG/57K42oN8skN6OLE5WGGBaKsYzjAl1qoXq0pw1WBANbsqJgeZWJLKG6O4B9XKog2YPHtb4+aaxnbWK+gU84cBGbGmrEbs5XSnpt54/WA5MOqi0iNV4LTnYc3DfEpGHR4Ir6Zjl0qo9FFOUD5KbA0BMiiRXD9/JguIKGHlES12G/0ko8pJhD3g7GMykWWjt2AAL52UlvUd/pxqzQZHbszrQ1xqKD12XDVs1ewJcl7pzCPKbRYg0hOrAeih4gVCcWNneTf27VObj0v4PSOQAFv3lfTB2jMA==\r\n" }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.5086.1570722660160%40Atlassian.JIRA.
[JIRA] (JENKINS-58193) EC2 Plugin: EC2 instances are getting terminated right away on initializing in 1.44 version
Title: Message Title tapvir virk commented on JENKINS-58193 Re: EC2 Plugin: EC2 instances are getting terminated right away on initializing in 1.44 version I already created below ticket JENKINS-59633 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200248.1561491352000.5078.1570721760773%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title
tapvir virk edited a comment on JENKINS-59633
Re: EC2 Plguin: Windows EC2 instances are not launching
Hi [~raihaan]As per your comment in JENKINS-58193 ,I can see the getPasswordData cli returning \r\n prefixing the content. I haven't set any password in the ami. I'm just running below script in the userdata,# Disable Credssp for Jenkins master to login via WinRM.winrm set winrm/config/service/auth '@\{CredSSP="false"}'$osString = wmic os get caption | Out-Stringecho "Windows OS: $osString"
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.5075.1570721700185%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Hi Raihaan Shouhell As per your comment in JENKINS-58193 , I can see the getPasswordData cli returning \r\n prefixing the content. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.5072.1570721340190%40Atlassian.JIRA.
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title
Mykhailo Zolotarenko edited a comment on JENKINS-53427
Re: Agent creation failure because of concurrent attempts to schedule a pod
Additional logs to the previous comment from Dan Alvizu Full JNLP container logs:{code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: ui-pipeline-shared-jbr6lOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 09, 2019 8:58:32 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.29Oct 09, 2019 8:58:32 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://jenkins-icecream.some.tools/]Oct 09, 2019 8:58:32 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, some]Oct 09, 2019 8:58:32 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins-icecream-agent.some.tools Agent port: 5 Identity: 11:11:11:11:11:11:11:11:11:11:11:11:11Oct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins-icecream-agent.some.tools:5Oct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 54:90:09:b3:21:36:c7:d1:0d:3f:a6:b4:51:2c:12:61Oct 09, 2019 8:58:32 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to jenkins-icecream-agent.some.tools/10.75.115.45:5] Local headers refused by remote: Unknown client name: ui-pipeline-shared-jbr6lOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-jbr6l at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-jbr6l at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at
[JIRA] (JENKINS-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
Title: Message Title
Yauheni Bobich edited a comment on JENKINS-54275
Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
We can reproduce that with enabled Advanced Configuration->Force Authentication. Our IdP - G Suite. After some investigation, I found out that that G Suite ignores ForceAuthn = "true". Change Maximum Authentication Lifetime is not suitable for us. We want to our session was as short as it can. Too long lifetime makes the availability of the Jenkins a long time after removing an account from IdP (G Suite). [~ifernandezcalvo] can you have any ideas about this? Plugin version: 1.1.3{code:java}org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old or in the future at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateAuthenticationStatements(SAML2DefaultResponseValidator.java:620) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateAssertion(SAML2DefaultResponseValidator.java:393) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateSamlSSOResponse(SAML2DefaultResponseValidator.java:302) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validate(SAML2DefaultResponseValidator.java:138) at org.pac4j.saml.sso.impl.SAML2WebSSOMessageReceiver.receiveMessage(SAML2WebSSOMessageReceiver.java:77) at org.pac4j.saml.sso.impl.SAML2WebSSOProfileHandler.receive(SAML2WebSSOProfileHandler.java:35) at org.pac4j.saml.client.SAML2Client.retrieveCredentials(SAML2Client.java:225) at org.pac4j.saml.client.SAML2Client.retrieveCredentials(SAML2Client.java:60) at org.pac4j.core.client.IndirectClient.getCredentials(IndirectClient.java:106) at org.jenkinsci.plugins.saml.SamlProfileWrapper.process(SamlProfileWrapper.java:55) at org.jenkinsci.plugins.saml.SamlProfileWrapper.process(SamlProfileWrapper.java:35) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:64) at org.jenkinsci.plugins.saml.SamlSecurityRealm.doFinishLogin(SamlSecurityRealm.java:311) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:219) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies commented on JENKINS-51581 Re: Add option to override tool config for slave nodes created by EC2 plugin Pull request created: https://github.com/jenkinsci/ec2-plugin/pull/410 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.5054.1570719060188%40Atlassian.JIRA.
[JIRA] (JENKINS-59686) MicroFocus Build Report Publish Error
Title: Message Title Ricardo Nazareth edited a comment on JENKINS-59686 Re: MicroFocus Build Report Publish Error Hi, So I discover that this Slave machines had an installed Jenkins. I delete the old folders.I also delete the folder C:\Jenkins at salve machines so it creates a new one. Until now its Its works, and Jenkins keep was running and saving the evidences at master. So i start running all pipelines and jobs by order. Cloud be some conflict whit After the folders or can be a problem handling whit the evidences when it reaches some capacity, dunno 5º pipeline starts to crash again . Anyway just a update Dunno what i could do until now to more . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202384.1570454666000.5051.1570719000108%40Atlassian.JIRA.
[JIRA] (JENKINS-59611) Symlink target update fails when "noclobber" set
Title: Message Title
Charusheela Bopardikar updated an issue
Jenkins / JENKINS-59611
Symlink target update fails when "noclobber" set
Change By:
Charusheela Bopardikar
If the contents of the target of a symlink is updated and noclobber is set on the workspace the next sync fails. For example:{code:java}P4 Task: syncing files at change: 1980... p4 sync /var/lib/jenkins/workspace/Symlinks/...@1980P4 Task: attempt: 1ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s):Can't clobber writable file /var/lib/jenkins/workspace/Symlinks/aLinux/target/F1{code}The permission on the target is OK. P4-Plugin does set the symlink permission to be 'w':{code:java}lrwxrwxrwx 1 jenkins jenkins 12 Oct 1 14:13 ./aLinux/links/F1_link -> ../target/F1-r--r--r-- 1 jenkins jenkins 89 Oct 1 14:13 ./aLinux/target/F1{code}P4 command line would set the same permissions but will correctly sync the files with the same permission. For example:{code:java}$ ls -ld $(find .)drwxr-xr-x 4 kwirth kwirth 4096 Jul 2 11:16 .drwxr-xr-x 2 kwirth kwirth 4096 Oct 1 15:33 ./linkslrwxrwxrwx 1 kwirth kwirth 12 Oct 1 15:33 ./links/F1_link -> ../target/F1drwxr-xr-x 3 kwirth kwirth 4096 Oct 1 15:34 ./target-r--r--r-- 1 kwirth kwirth 134 Oct 1 15:34 ./target/F1$ p4 sync ...//depot/symlink/aLinux/target/F1#3 - updating /ws/symlink/aLinux/target/F1{code}*Reproduction Steps:* # Add a target and symlink to Perforce from your Linux Perforce workspace. # Create a freestyle job to sync the path containing the symlink. # Before saving the job untick 'clobber'. # Set the job to only build on one Linux node and set the populate option to 'Auto Cleanup And Sync'. # Save the job. # Run the job. # Make an edit to the target of the symlink to point to a new target and submit it from your Linux workspace. # Run the job.*Result:* The "Can't clobber writable file" error is seen.*Expected Result:* Target is synced without error.
Add Comment
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Jesse Glick commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Ad that is indeed a missing feature in Pipeline. I have hijacked JENKINS-44847 to discuss this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4973.1570717561506%40Atlassian.JIRA.
[JIRA] (JENKINS-44847) add functionality to pipeline
Title: Message Title
Jesse Glick commented on JENKINS-44847
Re: add functionality to pipeline
More broadly, we strongly encourage users to minimize the number of distinct steps in a Pipeline build, so that
node {
stage('Checkout') {
checkout scm
}
stage('Build') {
sh 'mvn -DskipTests package'
}
stage('Test') {
sh 'mvn surefire:test'
}
}
should be reduced to
node {
stage('Checkout') {
checkout scm
}
stage('Main') {
sh 'mvn package'
}
}
or even moving the details to an external versioned file in whatever language is most convenient, so that the Pipeline script itself stays short enough to not need testing or frequent patching:
node {
stage('Checkout') {
checkout scm
}
stage('Main') {
sh 'bash ci.sh'
}
}
(For now, the checkout cannot be easily moved to an external script, since Jenkins SCM plugins do some complex things with authentication, PR merging, changelog generation, and polling which are tricky to replace with a plain git clone, not to mention that you need to bootstrap a checkout just to get an external script to run!) The problem is that when you do this, you lose some richness of detail in build visualizations. From the text console, this is not so visible, but from Blue Ocean it is. In this case, you lose the ability to see quickly which “stage” the build is in, even if ci.sh is running multiple long-running subcommands. What we would like is for your ci.sh to look something like
echo === Building
mvn -DskipTests package
echo === Testing
mvn surefire:test
where the visualization layers would automatically pick up the section headers (you could also use https://en.wikipedia.org/wiki/Page_break etc.) and display them just like stage or other labels present in Pipeline script. (Delimiters could even be made to match built-in output of various build tools. For example using [INFO] --- would allow a one-line script mvn test to show structure in the Jenkins UI.)
[JIRA] (JENKINS-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
Title: Message Title Yauheni Bobich commented on JENKINS-54275 Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old We can reproduce that with enabled Advanced Configuration->Force Authentication. Plugin version: 1.1.3 org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old or in the future at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateAuthenticationStatements(SAML2DefaultResponseValidator.java:620) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateAssertion(SAML2DefaultResponseValidator.java:393) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validateSamlSSOResponse(SAML2DefaultResponseValidator.java:302) at org.pac4j.saml.sso.impl.SAML2DefaultResponseValidator.validate(SAML2DefaultResponseValidator.java:138) at org.pac4j.saml.sso.impl.SAML2WebSSOMessageReceiver.receiveMessage(SAML2WebSSOMessageReceiver.java:77) at org.pac4j.saml.sso.impl.SAML2WebSSOProfileHandler.receive(SAML2WebSSOProfileHandler.java:35) at org.pac4j.saml.client.SAML2Client.retrieveCredentials(SAML2Client.java:225) at org.pac4j.saml.client.SAML2Client.retrieveCredentials(SAML2Client.java:60) at org.pac4j.core.client.IndirectClient.getCredentials(IndirectClient.java:106) at org.jenkinsci.plugins.saml.SamlProfileWrapper.process(SamlProfileWrapper.java:55) at org.jenkinsci.plugins.saml.SamlProfileWrapper.process(SamlProfileWrapper.java:35) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:64) at org.jenkinsci.plugins.saml.SamlSecurityRealm.doFinishLogin(SamlSecurityRealm.java:311) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:219) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at
[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Chris Knight commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs "Include @Library changes in job recent changes" did fix this issue for us. However, importantly, we had to restart our Jenkins server for this to take effect. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176175.1478690005000.4912.1570716961147%40Atlassian.JIRA.
[JIRA] (JENKINS-44847) add functionality to pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-44847 add functionality to pipeline Change By: Jesse Glick Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182909.1497354553000.4908.1570716607988%40Atlassian.JIRA.
[JIRA] (JENKINS-59731) Moving pipeline job to folder causes loss of "Recent changes"
Title: Message Title Anders Hammar created an issue Jenkins / JENKINS-59731 Moving pipeline job to folder causes loss of "Recent changes" Issue Type: Bug Assignee: Unassigned Attachments: packager-config.yml Components: pipeline Created: 2019-10-10 13:33 Environment: Jenkins 2.176.2 on RHEL7 with OpenJDK 1.8. All used plugins can be seen in attached yaml file. Git 2.9 OS client Priority: Minor Reporter: Anders Hammar Issue: A pipeline build job which has been built and has changes listed for builds (seen by accessing ./changes on the job URL) as well as the number of commits for each build shown in the Stage View UI. When that pipeline job then is moved to a folder, all recent changes are lost. Also, it now says "No changes" in the Staeg View for all builds. If then a change is committed to the git repo a new build is triggered, that change is listed in "Recent changes" and it says "1 commit" for that build in the Stage view. All older builds says "No Changes". No stack trace or problem indication in the log. If I move the build back to where it was from the beginning, the changes are back again! (But then any changes recorden when the job was in the folder is lost instead.) I have tested the same procedure with a Maven project build job and then recent changes are still there after moving to a folder.
[JIRA] (JENKINS-56037) SCM Polling with p4-plugin triggers builds several times
Title: Message Title Paul Allen updated JENKINS-56037 Jenkins / JENKINS-56037 SCM Polling with p4-plugin triggers builds several times Change By: Paul Allen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197457.1549569383000.4898.1570714501735%40Atlassian.JIRA.
[JIRA] (JENKINS-56037) SCM Polling with p4-plugin triggers builds several times
Title: Message Title Paul Allen commented on JENKINS-56037 Re: SCM Polling with p4-plugin triggers builds several times Karl Wirth - I think this issue is now fixed in release 1.10.5 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197457.1549569383000.4890.1570714442659%40Atlassian.JIRA.
[JIRA] (JENKINS-56187) manually provided key verification strategy crashes
Title: Message Title Ivan Fernandez Calvo updated JENKINS-56187 Jenkins / JENKINS-56187 manually provided key verification strategy crashes Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197736.1550529573000.4886.1570714441971%40Atlassian.JIRA.
[JIRA] (JENKINS-56187) manually provided key verification strategy crashes
Title: Message Title Ivan Fernandez Calvo updated JENKINS-56187 Jenkins / JENKINS-56187 manually provided key verification strategy crashes Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.30.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197736.1550529573000.4888.1570714442350%40Atlassian.JIRA.
[JIRA] (JENKINS-59728) Bump Jenkins core to 2.190.1
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59728 Jenkins / JENKINS-59728 Bump Jenkins core to 2.190.1 Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.31.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202445.1570705008000.4884.1570713660117%40Atlassian.JIRA.
[JIRA] (JENKINS-58639) pipeline job runs every two minutes
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.10.5 Jenkins / JENKINS-58639 pipeline job runs every two minutes Change By: Paul Allen Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59698) file crippled during deploy
Title: Message Title Peter Niederlag commented on JENKINS-59698 Re: file crippled during deploy nodejs, git deployment strategy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202398.1570524247000.4851.1570712940583%40Atlassian.JIRA.
[JIRA] (JENKINS-59730) text-finder sets whole matrix job to "not built" even if only one configuration matched
Title: Message Title Christoph Berg created an issue Jenkins / JENKINS-59730 text-finder sets whole matrix job to "not built" even if only one configuration matched Issue Type: Bug Assignee: Basil Crow Attachments: not-built.png Components: text-finder-plugin Created: 2019-10-10 13:05 Priority: Major Reporter: Christoph Berg When using the Text Finder Plugin with matrix jobs, if one configuration was set to "not built" from this plugin, the whole build will be marked as "not built", even if there were other configurations that passed successfully. My expectation would be that matrix jobs should be blue/green if there's any configurations that passed, and only be "not built" themselves if all configurations had that result. Add Comment
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title Mykhailo Zolotarenko commented on JENKINS-53427 Re: Agent creation failure because of concurrent attempts to schedule a pod I can reproduce this issue when I disable “Do not allow concurrent builds” and run pipeline job for couple times at the same time Our agent using kub2iam and I don’t know when and why Jenkins-master had refused the connection as it had an 'unknown client name’… maybe this is due to kub2iam, which we use for our agent… maybe something else... 1. Enable option “Do not allow concurrent builds” - this should help prevent this issue. 2. Deleting Error pods - should help prevent reaching the maximum pod limit in the kubernetes cluster 3. Stop current job - should prevent to generate Error pods… I hope this helps Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193618.1536147614000.4840.1570712640398%40Atlassian.JIRA.
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Arnaud Héritier updated JENKINS-59695 Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-plugin-2.12 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.4817.1570711500253%40Atlassian.JIRA.
[JIRA] (JENKINS-59686) MicroFocus Build Report Publish Error
Title: Message Title Ricardo Nazareth commented on JENKINS-59686 Re: MicroFocus Build Report Publish Error Hi, So I discover that this Slave machines had an installed Jenkins. I delete the old folders. I also delete the folder C:\Jenkins at salve machines so it creates a new one. Until now its works, and Jenkins keep running and saving the evidences at master. Cloud be some conflict whit the folders or can be a problem handling whit the evidences when it reaches some capacity, dunno. Anyway just a update what i could do until now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202384.1570454666000.4695.1570707420213%40Atlassian.JIRA.
[JIRA] (JENKINS-59729) SEVERE: http://jenkins2.jenkins2.svc.cluster.local:8080 provided port:50000 is not reachable
Title: Message Title xiaoping huang created an issue Jenkins / JENKINS-59729 SEVERE: http://jenkins2.jenkins2.svc.cluster.local:8080 provided port:5 is not reachable Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-10-10 11:33 Priority: Major Reporter: xiaoping huang jenkins/jnlp-agent-maven:latest execute has errors [root@dev7 jenkins]# kubectl logs default-8bsmg -c jnlp-mvn -n jenkins2 Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior Oct 10, 2019 11:06:51 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: default-8bsmg Oct 10, 2019 11:06:51 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Oct 10, 2019 11:06:51 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.29 Oct 10, 2019 11:06:51 AM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /root/.jenkins/cache/jars Oct 10, 2019 11:06:52 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://jenkins2.jenkins2.svc.cluster.local:8080 Oct 10, 2019 11:06:52 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Oct 10, 2019 11:06:57 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible WARNING: connect timed out Oct 10, 2019 11:06:57 AM hudson.remoting.jnlp.Main$CuiListener error SEVERE: http://jenkins2.jenkins2.svc.cluster.local:8080 provided port:5 is not reachable java.io.IOException: http://jenkins2.jenkins2.svc.cluster.local:8080 provided port:5 is not reachable at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:287) at hudson.remoting.Engine.innerRun(Engine.java:523) at hudson.remoting.Engine.run(Engine.java:474)
[JIRA] (JENKINS-59728) Bump Jenkins core to 2.190.1
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-59728 Re: Bump Jenkins core to 2.190.1 other dependencies bumped: credentials to 2.30.0 ssh-credentials to 1.18 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202445.1570705008000.4583.1570705560060%40Atlassian.JIRA.
[JIRA] (JENKINS-59728) Bump Jenkins core to 2.190.1
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-59728 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202445.1570705008000.4573.1570705200181%40Atlassian.JIRA.
[JIRA] (JENKINS-59728) Bump Jenkins core to 2.190.1
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59728 Jenkins / JENKINS-59728 Bump Jenkins core to 2.190.1 Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202445.1570705008000.4574.1570705200347%40Atlassian.JIRA.
[JIRA] (JENKINS-59728) Bump Jenkins core to 2.190.1
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-59728 Bump Jenkins core to 2.190.1 Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin Created: 2019-10-10 10:56 Priority: Minor Reporter: Ivan Fernandez Calvo because Jenkins core 2.190.1 no longer has trilead-ssh2, I've to bump the core to 1.90.1 and include trilead-api-plugin as dependency. I will maintain 1.30.x versions for previous cores for awhile. Add Comment This message was
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel commented on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target Hello, Aleksi Simell Thanks for quick answer Yes, seems it was broken since upgrade from 1.X to 2.X a) ... influxDbPublisher(selectedTarget: 'Preprod InfluxDB', customData: influxDbCustomData) ... b) I created a new target via /configure UI Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.4567.1570703940140%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Denis Bel updated an issue Jenkins / JENKINS-59724 no known implementation of class java.lang.String is named Target Change By: Denis Bel Attachment: image-2019-10-10-13-36-10-271.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.4564.1570703820423%40Atlassian.JIRA.
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-51581 Add option to override tool config for slave nodes created by EC2 plugin Change By: George Cimpoies Environment: Jenkins 2.107.3, Amazon EC2 Plugin 1. 39 46.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.4559.1570703704058%40Atlassian.JIRA.
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title
George Cimpoies edited a comment on JENKINS-51581
Re: Add option to override tool config for slave nodes created by EC2 plugin
This is a show-stopper for us as we want to rely solely on aws for our build agents, but we can't define global tool locations since we have many different jobs and configurations on Jenkins.With hardware nodes we use swarm plugin + a script like this:{code:java}"$($env:JDK8_PATH)\bin\java.exe" `-cp "$($env:USERPROFILE)\slave.jar" `-jar "$($env:USERPROFILE)\swarm-client.jar" `- deleteExistingClients `-name "$($env:HOSTNAME)" `-disableClientsUniqueId `- fsroot "$($env:USERPROFILE)" `-description "$($env:JENKINS_NODE_DESCRIPTION)" `-master "$($env:JENKINS_MASTER)" `-executors "$($env:JENKINS_NUMBER_OF_EXECUTORS)" `-labels "$($env:JENKINS_NODE_LABELS)" `--toolLocation "jdk7=$($env:JDK7_PATH)" `--toolLocation "jdk8=$($env:JDK8_PATH)" `--toolLocation "jdk9=$($env:JDK9_PATH)" `--toolLocation "jdk10=$($env:JDK10_PATH)" `--toolLocation "jdk11=$($env:JDK11_PATH)" `{code}to add the tool locations on the node that's connecting to Jenkins.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.4551.1570703703400%40Atlassian.JIRA.
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-51581 Add option to override tool config for slave nodes created by EC2 plugin Change By: George Cimpoies Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.4556.1570703703958%40Atlassian.JIRA.
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies commented on JENKINS-51581 Re: Add option to override tool config for slave nodes created by EC2 plugin This is a show-stopper for us as we want to rely solely on aws for our build agents, but we can't define global tool locations since we have many different jobs and configurations on Jenkins. With hardware nodes we use swarm plugin + a script like this: "$($env:JDK8_PATH)\bin\java.exe" ` -cp "$($env:USERPROFILE)\slave.jar" ` -jar "$($env:USERPROFILE)\swarm-client.jar" ` -deleteExistingClients ` -name "$($env:HOSTNAME)" ` -disableClientsUniqueId ` -fsroot "$($env:USERPROFILE)" ` -description "$($env:JENKINS_NODE_DESCRIPTION)" ` -master "$($env:JENKINS_MASTER)" ` -executors "$($env:JENKINS_NUMBER_OF_EXECUTORS)" ` -labels "$($env:JENKINS_NODE_LABELS)" ` --toolLocation "jdk7=$($env:JDK7_PATH)" ` --toolLocation "jdk8=$($env:JDK8_PATH)" ` --toolLocation "jdk9=$($env:JDK9_PATH)" ` --toolLocation "jdk10=$($env:JDK10_PATH)" ` --toolLocation "jdk11=$($env:JDK11_PATH)" ` to add the tool locations on the node that's connecting to Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin
Title: Message Title George Cimpoies updated an issue Jenkins / JENKINS-51581 Add option to override tool config for slave nodes created by EC2 plugin Change By: George Cimpoies Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190974.1527594894000.4542.1570703460398%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Ad commented on JENKINS-49278 Re: cat command in docker agents not detected correctly For specialized use cases like this you should not use withDockerContainer. Just run whatever docker commands you need directly from a sh (or indirectly via some script). We are revisiting our use of docker agents in our CI pipeline. Jesse Glick we are considering following your advice above, thus removing the docker agents and instead run `docker` commands in `sh` steps directly on the master. Yet, our current setup is that we have a stage with many steps running on the agent (having the different steps showing nicely in Jenkins UI). How could we get the same result by executing the docker command directly? (i.e. executing discrete Jenkins `steps` in the same docker container, without restarting the container since it would loose its state). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4506.1570702621287%40Atlassian.JIRA.
[JIRA] (JENKINS-59727) Exception 'Could not initialize class sun.security.ssl.SSLContextImpl$TLSContext' after openJDK upgrade
Title: Message Title David Aldrich created an issue Jenkins / JENKINS-59727 Exception 'Could not initialize class sun.security.ssl.SSLContextImpl$TLSContext' after openJDK upgrade Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-10 10:05 Environment: Jenkins 2.190.1 Centos 7 java-1.8.0-openjdk.x86_64 1:1.8.0.222.b10-1.el7_7 Priority: Minor Reporter: David Aldrich I have a simple freestyle project that checks out a small Subversion repository and executes a small shell script. This is running on a Centos 7 machine. It runs fine with: java-1.8.0-openjdk.x86_64 1:1.8.0.181-7.b13.el7 java-1.8.0-openjdk-headless.x86_64 1:1.8.0.181-7.b13.el7 However, I see exceptions if I run with: java-1.8.0-openjdk.x86_64 1:1.8.0.222.b10-1.el7_7 java-1.8.0-openjdk-headless.x86_64 1:1.8.0.222.b10-1.el7_7 Here is the exception trace: Checking out https://172.29.68.12/subversion/tools at revision '2019-10-10T10:52:49.103 +0100' --quiet Also: hudson.remoting.Channel$CallSiteStackTrace:
[JIRA] (JENKINS-59726) P4IGNORE on windows uses p4ignore.txt
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-59726 P4IGNORE on windows uses p4ignore.txt Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-10-10 10:01 Environment: P4-Plugin 1.10.4 Jenkins 2.176.1 Labels: P4_VERIFY Priority: Minor Reporter: Karl Wirth On Windows build slaves 'p4ignore.txt' is used for P4IGNORE files based on the following code: https://github.com/jenkinsci/p4-plugin/blob/2d15b39ddc1e03b901c844b330b93779c56ee856/src/main/java/org/jenkinsci/plugins/p4/client/ConnectionHelper.java#L170 This should either be configurable (if not already) or at least documented. Add Comment
[JIRA] (JENKINS-59725) Bump to HikariCP 3.4.1
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-59725 Bump to HikariCP 3.4.1 Issue Type: Improvement Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2019-10-10 10:00 Priority: Minor Reporter: Cyrille Le Clerc Bump to HikariCP 3.4.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59567) Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-59567 Server Credentials created from Jenkins credentials don't show up in maven settings.xml Change By: Cyrille Le Clerc Assignee: Dominik Bartholdi Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202202.1569618942000.4501.1570701540222%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Aleksi Simell commented on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target Are you trying to a) write stuff to InfluxDB b) create a new target? In both cases, how are you trying to do that? Did your job work previously and broke when you updated the plugin? And from which version did you update? As described in https://wiki.jenkins.io/display/JENKINS/InfluxDB+Plugin, after version 2.0 you need to make the password a hudson.util.Secret instead of String. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.4498.1570701481713%40Atlassian.JIRA.
[JIRA] (JENKINS-59567) Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-59567
Re: Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Cross posting answer already made on [https://groups.google.com/forum/#!topic/jenkinsci-users/7P1Wd2W-OcA] Hello,This is one of the most broadly used feature of the pipeline-maven-plugin, I think it works for most user, there is probably a glitch somewhere.Can you please share your testing Jenkinsfile and the details reported by withMaven in the build logs?The troubleshooting pipeline script should look like{code}withMaven(...) { sh "mvn help:effective-settings"}{code}The build logs line that reports the credentials injected in the settings looks like{ code noformat }[withMaven] using Maven global settings.xml 'global-settings-for-pipeline-maven-plugin' with Maven servers credentials provided by Jenkins (replaceAll: false): [mavenServerId: 'github', jenkinsCredentials: 'github-credentials', username: 'cyrille-leclerc', type: 'UsernamePasswordCredentialsImpl'], [mavenServerId: 'nexus3.example.com', jenkinsCredentials: 'api-team-nexus-deployment-credentials', username: 'api-team', type: 'UsernamePasswordCredentialsImpl']{ code noformat }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59567) Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-59567
Re: Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Cross posting answer already made on [https://groups.google.com/forum/#!topic/jenkinsci-users/7P1Wd2W-OcA] Hello,This is one of the most broadly used feature of the pipeline-maven-plugin, I think it works for most user, there is probably a glitch somewhere.Can you please share your testing Jenkinsfile and the details reported by withMaven in the build logs?The troubleshooting pipeline script should look like{code}withMaven(...) { sh "mvn help:effective-settings"}{code}The build logs line that reports the credentials injected in the settings looks like{ noformat code }[withMaven] using Maven global settings.xml 'global-settings-for-pipeline-maven-plugin' with Maven servers credentials provided by Jenkins (replaceAll: false): [mavenServerId: 'github', jenkinsCredentials: 'github-credentials', username: 'cyrille-leclerc', type: 'UsernamePasswordCredentialsImpl'], [mavenServerId: 'nexus3.example.com', jenkinsCredentials: 'api-team-nexus-deployment-credentials', username: 'api-team', type: 'UsernamePasswordCredentialsImpl']{ noformat code }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59567) Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Title: Message Title
Cyrille Le Clerc commented on JENKINS-59567
Re: Server Credentials created from Jenkins credentials don't show up in maven settings.xml
Cross posting answer already made on https://groups.google.com/forum/#!topic/jenkinsci-users/7P1Wd2W-OcA Hello, This is one of the most broadly used feature of the pipeline-maven-plugin, I think it works for most user, there is probably a glitch somewhere. Can you please share your testing Jenkinsfile and the details reported by withMaven in the build logs? The troubleshooting pipeline script should look like
withMaven(...) {
sh "mvn help:effective-settings"
}
The build logs line that reports the credentials injected in the settings looks like
[withMaven] using Maven global settings.xml 'global-settings-for-pipeline-maven-plugin' with Maven servers credentials provided by Jenkins (replaceAll: false): [mavenServerId: 'github', jenkinsCredentials: 'github-credentials', username: 'cyrille-leclerc', type: 'UsernamePasswordCredentialsImpl'], [mavenServerId: 'nexus3.example.com', jenkinsCredentials: 'api-team-nexus-deployment-credentials', username: 'api-team', type: 'UsernamePasswordCredentialsImpl']
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title
Denis Bel created an issue
Jenkins / JENKINS-59724
no known implementation of class java.lang.String is named Target
Issue Type:
Bug
Assignee:
Aleksi Simell
Components:
influxdb-plugin
Created:
2019-10-10 09:46
Environment:
Jenkins ver. 2.190.1 Plugin version: 2.0.1
Priority:
Minor
Reporter:
Denis Bel
Jenkins log contains a lot of such warnings with password as a plain text:
2019-10-10 08:24:15.380+ [id=40232] WARNING o.j.p.s.d.DescribableModel#uninstantiate2: Cannot create control version of class org.jenkinsci.plugins.workflow.steps.CoreStep using {delegate=$InfluxDbPublisher(customData={version=null, endpoint=null, scmrevision=c2cb16},customDataMap=null,customDataMapTags=null,customDataTags=null,customPrefix=null,customProjectName=null,jenkinsEnvParameterField=null,jenkinsEnvParameterTag=null,measurementName=null,replaceDashWithUnderscore=false,selectedTarget=Preprod InfluxDB,target=$Target(database=grafana,description=Preprod InfluxDB,exposeExceptions=false,globalListener=true,globalListenerFilter=,jobScheduledTimeAsPointsTimestamp=false,password=***,retentionPolicy=autogen,url="" class="code-comment" style="color: #808080">//influxdb-ci.***.com,username=jenkins,usingJenkinsProxy=false))}
java.lang.UnsupportedOperationException: no known implementation of class java.lang.String is named Target
at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:549)
at org.jenkinsci.plugins.structs.describable.UninstantiatedDescribable.instantiate(UninstantiatedDescribable.java:207)
at
[JIRA] (JENKINS-57108) Pipeline-Maven-Plugin - UNSTABLE build with downstream list of parent job
Title: Message Title benjamin tocquec commented on JENKINS-57108 Re: Pipeline-Maven-Plugin - UNSTABLE build with downstream list of parent job Thanks a lot Stefan Sedelmaier ! Hope this PR will be merged soon Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198853.18956.4481.1570700700195%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-59311 Poor performance when using 'grep' Change By: Christoph Fetzer Environment: jenkins ver 2.176.3 jenkins ver 2.190.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.4482.1570700700212%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance when using 'grep' This jenkins installation is driving me nuts - the slow behaviour came back.The last quick run was on September, 27th. After that the build failed for some days due to issues with the code and the libraries used. The first completing build after that on Oct. 9th was slow again (same times - ~45min vs 3:40hours). OK, I noticed, there are failed builds with indicatino of slow behaviour since October, 2nd. The builds before failed after only 6mins.I implemented every updates in that time as soon as I realised them. There were a number of them in that time frame. Is there a log that shows the plugins updated and the version change? With that I could restore the state of September 27th and apply all the updates step by step until the build gets slower again. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.4478.1570700640113%40Atlassian.JIRA.
[JIRA] (JENKINS-58911) Jira Plugin does not create new version in existing project
Title: Message Title Radek Antoniuk commented on JENKINS-58911 Re: Jira Plugin does not create new version in existing project Oh, I just noticed you are on Jira (Server) 5.2.10. Indeed, Jira 5.2.10 doesn't know the startDate field that the current version of Jenkins Jira plugin is using. https://docs.atlassian.com/software/jira/docs/api/5.2.10/index.html?com/atlassian/jira/rest/v2/issue/version/VersionBean.html https://docs.atlassian.com/software/jira/docs/api/7.3.2/com/atlassian/jira/rest/v2/issue/version/VersionBean.html We need to think how we can achieve backward compatibility with older Jira versions for cases like this, for now I guess you can only try using an older version of Jenkins Jira plugin or consider upgrading your Jira instance... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201251.1565711807000.4469.1570700400327%40Atlassian.JIRA.
[JIRA] (JENKINS-59723) Missing Delay Setting in Performance Signature Plugin
Title: Message Title rachel lee created an issue Jenkins / JENKINS-59723 Missing Delay Setting in Performance Signature Plugin Issue Type: Bug Assignee: Raphael Pionke Attachments: plugin.JPG Components: performance-signature-dynatrace-plugin Created: 2019-10-10 09:32 Priority: Minor Reporter: rachel lee Hi Support, We had setup Dynatrace Performance Signature Plugin in Jenkins. We are looking for a setting to configure delay but we couldn't find it. Can help to advice? https://github.com/jenkinsci/performance-signature-dynatrace-plugin/tree/master/dynatrace Thank you. Add Comment
[JIRA] (JENKINS-58628) jira-plugin not working from pipeline job: jiraIssueSelector doesn't find any issues
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-58628 jira-plugin not working from pipeline job: jiraIssueSelector doesn't find any issues Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200796.1563944957000.4454.1570699442748%40Atlassian.JIRA.
[JIRA] (JENKINS-58911) Jira Plugin does not create new version in existing project
Title: Message Title Radek Antoniuk commented on JENKINS-58911 Re: Jira Plugin does not create new version in existing project It seems that the API is now not accepting startDate field? What Jira type (Server or Cloud) and version are you using? Also, you should remove quotes from your version string, as you can see in the log they are double-quoted. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201251.1565711807000.4451.1570699380141%40Atlassian.JIRA.
[JIRA] (JENKINS-58714) Cannot save System Settings or update Jobs with latest JIRA Plugin versions
Title: Message Title Radek Antoniuk commented on JENKINS-58714 Re: Cannot save System Settings or update Jobs with latest JIRA Plugin versions Can you check with the current version, as this might be related to JENKINS-57899? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201006.1564423788000..1570699080818%40Atlassian.JIRA.
[JIRA] (JENKINS-59003) JENKINS and JIRA integration
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-59003 JENKINS and JIRA integration Change By: Radek Antoniuk Component/s: jira-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201355.1566272905000.4447.1570699141137%40Atlassian.JIRA.
