[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook
Title: Message Title Christian Köberl commented on JENKINS-58919 Re: DateTimeParseException on MR web hook the fixed version is now released: https://github.com/gitlab4j/gitlab4j-api/releases/tag/gitlab4j-api-4.12.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201262.156577292.3771.1565932620111%40Atlassian.JIRA.
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title
Dan Alvizu commented on JENKINS-53427
Re: Agent creation failure because of concurrent attempts to schedule a pod
Looking through the code base I'm unclear where this could be happening. This is where things are first being terminated: org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate So this must be called incorrectly somewhere. However it can only be called by: AbstractCloudSlave.terminate() (hudson.slaves) Which in turn can only be called from one of three places – I hope I'm missing something here:
KubernetesLauncher.launch(SlaveComputer, TaskListener) (org.csanchez.jenkins.plugins.kubernetes)
CloudRetentionStrategy.check(AbstractCloudComputer) (hudson.slaves)
AbstractCloudComputer.doDoDelete() (hudson.slaves) DeleteNodeCommand.run() (hudson.cli)
#1 can't happen because that requires a log statement {{"Error in provisioning; agent=%s, template=%s" }}to happen before the observed log statement, where instead it appears after (on the second termination). #2 can't be happening, as i logs a "Disconnecting {0}" with computer.name() – these only appear for "jnlp-" computers #3 can't be happening as I'm not running any CLI commands at the time
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193618.1536147614000.3765.1565929500314%40Atlassian.JIRA.
[JIRA] (JENKINS-58958) Use the same Jenkins workspace on a Change basis
Title: Message Title isaac mann assigned an issue to lucamilanesio Jenkins / JENKINS-58958 Use the same Jenkins workspace on a Change basis Change By: isaac mann Assignee: Daniel Beck lucamilanesio Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201305.1565917678000.3762.1565918160172%40Atlassian.JIRA.
[JIRA] (JENKINS-58958) Use the same Jenkins workspace on a Change basis
Title: Message Title isaac mann moved an issue Jenkins / JENKINS-58958 Use the same Jenkins workspace on a Change basis Change By: isaac mann Project: Infrastructure Jenkins Key: INFRA JENKINS - 2215 58958 Workflow: classic default workflow JNJira + In-Review Component/s: gerrit-code-review-plugin Component/s: github Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201305.1565917678000.3759.1565917740138%40Atlassian.JIRA.
[JIRA] (JENKINS-58915) Change timeout
Title: Message Title
Clark Kromenaker edited a comment on JENKINS-58915
Re: Change timeout
I came here to create a ticket for this issue. I noticed that I'd frequently (but not always) get this output for my Jenkins jobs: {code:java}Creating an upload resource. Upload resource successful. Uploading app to resource. Upload app unsuccessful. java.net.SocketTimeoutException: timeout io.jenkins.plugins.appcenter.AppCenterException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: timeout Build step 'Upload app to AppCenter' changed build result to FAILURE {code}You might say it's a network connection issue...but the HockeyApp plugin I used previously would very consistently upload without failure or timeout.Please resolve, since it makes my Jenkins builds fail about 80% of the time! I'm uploading an app that is about 80MB, if that makes any difference.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201258.1565762652000.3755.1565915340171%40Atlassian.JIRA.
[JIRA] (JENKINS-58915) Change timeout
Title: Message Title Clark Kromenaker edited a comment on JENKINS-58915 Re: Change timeout I came here to create a ticket for this issue. I noticed that I'd frequently (but not always) get this output for my Jenkins jobs: Creating an upload resource.Upload resource successful.Uploading app to resource.Upload app unsuccessful.java.net.SocketTimeoutException: timeoutio.jenkins.plugins.appcenter.AppCenterException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: timeoutBuild step 'Upload app to AppCenter' changed build result to FAILURE You might say it's a network connection issue...but the HockeyApp plugin I used previously would very consistently upload without failure or timeout.Please resolve, since it makes my Jenkins builds fail about 80% of the time! I'm uploading an app that is about 80MB, if that makes any difference. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201258.1565762652000.3752.1565915280447%40Atlassian.JIRA.
[JIRA] (JENKINS-58915) Change timeout
Title: Message Title Clark Kromenaker commented on JENKINS-58915 Re: Change timeout I came here to create a ticket for this issue. I noticed that I'd frequently (but not always) get this output for my Jenkins jobs: Creating an upload resource. Upload resource successful. Uploading app to resource. Upload app unsuccessful. java.net.SocketTimeoutException: timeout io.jenkins.plugins.appcenter.AppCenterException: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: timeout Build step 'Upload app to AppCenter' changed build result to FAILURE You might say it's a network connection issue...but the HockeyApp plugin I used previously would very consistently upload without failure or timeout. Please resolve, since it makes my Jenkins builds fail about 80% of the time! I'm uploading an app that is about 80MB, if that makes any difference. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201258.1565762652000.3749.1565915280406%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number Using some fairly wide-reaching changes, the following test failures will need to be investigated: hudson.PluginTest.doDynamic hudson.cli.CLITest.interrupt hudson.cli.CLITest.strictHostKey hudson.model.AbstractProjectTest.configDotXmlSubmissionToDifferentType hudson.model.UsageStatisticsTest.roundtrip jenkins.I18nTest.test_baseName_plugin There were also some test errors in UDPBroadcastThreadTest, but that randomly happens to me anyways. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3743.1565908380238%40Atlassian.JIRA.
[JIRA] (JENKINS-58957) trap and report login failure; no stack trace
Title: Message Title Ian Williams created an issue Jenkins / JENKINS-58957 trap and report login failure; no stack trace Issue Type: Improvement Assignee: Félix Belzunce Arcos Attachments: jenkins-activedir-login-fail.txt Components: active-directory-plugin Created: 2019-08-15 22:02 Environment: Jenkins 2.176.2 active-directory:2.8 Priority: Minor Reporter: Ian Williams Connecting to active directory a failed login produces two stack traces in the logs. They are not required and just clutter the logs. It should simply record the login failure. eg: BadCredentialsException: Either no such user 'x...@mydomain.com' or incorrect password Instead we get: Aug 15, 2019 12:41:19 AM hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl bind WARNING: Failed to authenticate while binding to btwn000265.corp.ads:3268 javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090400, comment: AcceptSecurityContext error, data 52e, v1db1^@] Aug 15, 2019 12:41:19 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser WARNING: Credential exception trying to authenticate against corp.ads domain org.acegisecurity.BadCredentialsException: Either no such user 'x...@mydomain.com' or incorrect password Complete error attached. I see Kohsuke Kawaguchi previously closed a similar issue JENKINS-14298 in 2013 as "Won't Fix", but would ask to revisit. Evidently, we have a lot of people in the org who can't type their passwords properly. What value is provided by the stack trace over the simple
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number Still running tests, but as long as nothing relies on programmatic access to the version number without authentication, this shouldn't be an incompatible change. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3736.1565902560234%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number That's good news! Now for more things I've found: Jenkins.getApi() has no permission check. Several other getApi() methods likely also don't do this. I think that Api.setHeaders() can also do a permission check before adding that as a header. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3731.1565900520187%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Jeff Thompson commented on JENKINS-56217 Re: allow to hide version number TcpSlaveAgentListener provides the version but I'm pretty confident it doesn't actually need to. That particular response, https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/TcpSlaveAgentListener.java#L306 , provides a little bit of troubleshooting info. Very little. We should have a flag to disable that whole response and make that the default. There is already a system property to disable UDPBroadcastThread. Auto-discovery of Jenkins on the network is hardly a necessary feature and should probably be disabled by anyone who is paranoid enough about security to hide the version elsewhere. We could ignore this one in favor of the existing property or we could include version suppression here. Inbound TCP agents use a different header here, https://github.com/jenkinsci/remoting/blob/master/src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java#L208 , which contains the minimum supported Remoting version but not the Jenkins version. It may at times be possible to extract some Jenkins version info from this but we haven't updated that in well over two years so it's not very useful. I wouldn't bother with this one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3726.1565900220198%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number I'm running some experiments on this to see what (if anything) breaks by removing the version number when lacking the Overall/Read permission in those files. I do not know what the version number is used for in each of these, so they may require some additional changes to avoid unauthorized leaking of the version number. Both TcpSlaveAgentListener and UDPBroadcastThread seem like they need to provide the Jenkins version, though perhaps that's not necessary anymore with remoting? Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3713.1565898060495%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker edited a comment on JENKINS-56217 Re: allow to hide version number I don't see how that's going to help finding method calls in Jelly. I could look into that for checking what references Jenkins.VERSION to see if I missed anything, though.If we go the route of requiring Overall/Read to view a version number, then this will decrease the surface area of what needs to be updated somewhat significantly.* HudsonAuthenticationEntryPoint* TcpSlaveAgentListener* UDPBroadcastThread* IncompatibleVMDetected* l:layout and l:html* Other plugins TBD Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3704.1565897520172%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title William Gillaspy commented on JENKINS-58862 Re: Github Branch Source Plugin always references https://api.github.com Looks good. Thanks for the help! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201177.1565278734000.3699.1565897160477%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number I'm not finding any direct references to AbstractBuild.getHudsonVersion() other than in various plugins. Some of those plugins use it to display, though permissions involved are unknown. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3697.1565897160435%40Atlassian.JIRA.
[JIRA] (JENKINS-58956) Manual Promotion doesn't work thorugh API
Title: Message Title
Brandon Johnson created an issue
Jenkins / JENKINS-58956
Manual Promotion doesn't work thorugh API
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
promoted-builds-plugin
Created:
2019-08-15 19:24
Environment:
Jenkins v 2.183
Priority:
Minor
Reporter:
Brandon Johnson
getting this stack trace why trying to promote a build that is manual approval. Is there a different endpoint to hit to do an approval on a manual promotion job created using the promoted-builds-plugin? code for request: headers includes Jenkins-Crumb only
>>> renodata
'json={"parameters": [{"_class": "hudson.plugins.jira.listissuesparameter.JiraIssueParameterValue", "name": "SR", "value": "SR-6970"}, {"_class": "hudson.model.StringParameterValue", "name": "ENVIRONMENT", "value": "prod-dc2"}, {"_class": "hudson.model.StringParameterValue", "name": "GIT_TAG", "value": "DEPLOY-10-prod-dc2_42"}]}'
>>> requests.post('https://your-jenkins.com/job/reno-obac/62/promotion/promotionProcess/Promote-Consul-Env/promotionCondition/hudson.plugins.promoted_builds.conditions.ManualCondition/approve', auth=auth, headers=headers, data="">
Error:
java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
at
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number I don't see how that's going to help finding method calls in Jelly. I could look into that for checking what references Jenkins.VERSION to see if I missed anything, though. If we go the route of requiring Overall/Read to view a version number, then this will decrease the surface area of what needs to be updated somewhat significantly. HudsonAuthenticationEntryPoint TcpSlaveAgentListener UDPBroadcastThread IncompatibleVMDetected l:layout and l:html Other plugins TBD Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.3689.1565896920288%40Atlassian.JIRA.
[JIRA] (JENKINS-58862) Github Branch Source Plugin always references https://api.github.com
Title: Message Title Karl Shultz updated JENKINS-58862 The above mentioned pull request has been merged and released as GitHub Branch Source 2.5.6. Jenkins / JENKINS-58862 Github Branch Source Plugin always references https://api.github.com Change By: Karl Shultz Status: In Review Closed Resolution: Fixed Released As: github-branch-source-2.5.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58955) Can't connect with slaves via API
Title: Message Title
Lucas Messina created an issue
Jenkins / JENKINS-58955
Can't connect with slaves via API
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-08-15 19:05
Environment:
Jenkins: 2.189 Working EC2 plugin: 1.39 Working EC2 plugin: 1.45
Priority:
Major
Reporter:
Lucas Messina
Hello everybody, We have the plugin up and running good, but when updating the version of the plugin we can't start slaves via API. We don't have any problems with the plugin if a slave is started due a new job running, but we have a job with the following script: @NonCPS def submmitCleanJob(slave){ println "Going to submmit task to node: ${slave.name}" def computer = slave.toComputer() def connection = computer.connect(false) connection.get() build job: 'slave-clean', wait: false, propagate: false, parameters: [[$class: 'StringParameterValue', name: 'slave', value: "${slave.name}"]] } This job was working fine with plugin version 1.39, but now if the slave is stopped we can not start it from the script, and entering to see the logs of the slave we see that the connection is trying without success giving the following error "Failed to connect via ssh: The kexTimeout (1 ms) expired."
[JIRA] (JENKINS-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder Shashank Kulshrestha Did you read the comment before yours? there you have the solution *--extractedFilesFolder=c:\TMP-FOLDER-PATH* Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153867.1394206051000.3680.1565895181592%40Atlassian.JIRA.
[JIRA] (JENKINS-58910) [security] ssh slave hardening - ssh slave weak Key Exchange Algorithms/Message Authentication Codes
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58910 Re: [security] ssh slave hardening - ssh slave weak Key Exchange Algorithms/Message Authentication Codes please read How to report an issue, for questions you should use the google groups, also you do not provide Jenkins core version or ssh-slaves version number you are using nor the encryption settings you are using, however, I guess you are using ed25519 that it is supported in the latest versions of the Jenkins core (trilead-ssh2 module on jenkins-2.189) see https://issues.jenkins-ci.org/browse/JENKINS-55133 and https://github.com/jenkinsci/jenkins/pull/3827 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201249.1565708856000.3645.1565895000405%40Atlassian.JIRA.
[JIRA] (JENKINS-58910) [security] ssh slave hardening - ssh slave weak Key Exchange Algorithms/Message Authentication Codes
Title: Message Title Ivan Fernandez Calvo closed an issue as Fixed Jenkins / JENKINS-58910 [security] ssh slave hardening - ssh slave weak Key Exchange Algorithms/Message Authentication Codes Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201249.1565708856000.3647.1565895000432%40Atlassian.JIRA.
[JIRA] (JENKINS-58896) Dynamic kubernetes agents not registering to master
Title: Message Title matt c updated JENKINS-58896 Jenkins / JENKINS-58896 Dynamic kubernetes agents not registering to master Change By: matt c Status: Open Fixed but Unreleased Assignee: matt c Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201233.156562127.3642.1565894760117%40Atlassian.JIRA.
[JIRA] (JENKINS-58896) Dynamic kubernetes agents not registering to master
Title: Message Title matt c commented on JENKINS-58896 Re: Dynamic kubernetes agents not registering to master I believe this is the source of my issue: https://github.com/rancher/rancher/issues/21740 Rancher 2.2.5 and 2.2.6 have cross-site scripting exploit denials that are affecting the plugin. We upgraded to 2.2.7 and the plugin works again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201233.156562127.3641.1565894700066%40Atlassian.JIRA.
[JIRA] (JENKINS-58866) Splunk plugin not sending json files
Title: Message Title Sophie Lan commented on JENKINS-58866 Re: Splunk plugin not sending json files Thanks, it works now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201183.1565289754000.3639.1565892240201%40Atlassian.JIRA.
[JIRA] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title pjdarton closed an issue as Won't Do Looks like it wasn't as "in progress" as shown. If I'm wrong, feel free to re-open this and submit a PR that does this. Jenkins / JENKINS-28870 allow specifying target host when cloning a VM Change By: pjdarton Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163328.1434024869000.3636.1565891280351%40Atlassian.JIRA.
[JIRA] (JENKINS-28870) allow specifying target host when cloning a VM
Title: Message Title pjdarton stopped work on JENKINS-28870 Change By: pjdarton Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163328.1434024869000.3633.1565891160239%40Atlassian.JIRA.
[JIRA] (JENKINS-43823) Create post build-action to cleanup my environment
Title: Message Title pjdarton closed an issue as Won't Do Jenkins / JENKINS-43823 Create post build-action to cleanup my environment Change By: pjdarton Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181341.1493126274000.3631.1565891100290%40Atlassian.JIRA.
[JIRA] (JENKINS-43823) Create post build-action to cleanup my environment
Title: Message Title pjdarton commented on JENKINS-43823 Re: Create post build-action to cleanup my environment Use https://wiki.jenkins.io/display/JENKINS/PostBuildScript+Plugin That lets you run arbitrary build steps as part of the post-build process, so you could put step 4 in that and it'll always get run. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181341.1493126274000.3629.1565891040123%40Atlassian.JIRA.
[JIRA] (JENKINS-38568) vSphere Nodes are never started when in demand
Title: Message Title pjdarton closed an issue as Cannot Reproduce I've been using the vSphere plugin for a few years now and, while it had issues before I started, it's now perfectly capable of creating new slave nodes "on demand" (we use it for exactly this). I think this is a non-issue these days. Jenkins / JENKINS-38568 vSphere Nodes are never started when in demand Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174755.1475063063000.3625.1565890680356%40Atlassian.JIRA.
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Andrey Babushkin commented on JENKINS-53752 Re: Block PRs from forks from untrusted users I'm sorry Brian J Murrell, It seems I've just screwed the config of my GitHub Organization folder. I've set "Build strategies" like on the picture you've provided and "Trust" to "Nobody". Jenkins creates jobs for PRs opened by untrusted persons, but doesn't run them. That's exactly what I've needed, thank you Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194259.1537809356000.3618.1565890320370%40Atlassian.JIRA.
[JIRA] (JENKINS-51758) Register new vsphere template under vsphere plugin via groovy/jenkinsfile
Title: Message Title pjdarton closed an issue as Not A Defect Jenkins / JENKINS-51758 Register new vsphere template under vsphere plugin via groovy/jenkinsfile Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191205.1528346029000.3614.1565890200374%40Atlassian.JIRA.
[JIRA] (JENKINS-54213) MAC OS linked clone
Title: Message Title pjdarton closed an issue as Cannot Reproduce I'd guess from the lack of response that you got to the bottom of this and sorted it. If that's not the case, feel free to re-open and provide more information. Jenkins / JENKINS-54213 MAC OS linked clone Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194850.1540338042000.3612.1565890140199%40Atlassian.JIRA.
[JIRA] (JENKINS-56811) vSphere plugin instant clone support
Title: Message Title pjdarton commented on JENKINS-56811 Re: vSphere plugin instant clone support This plugin pre-dates "instance clone" - when it was written, vSphere didn't support it. Linked clones was about as close as you'd get (and even that is tricky). To do this, we'd need to work out if this isn't just sales-hype re-describing what a linked clone is already if there's anyone willing and able to implement this if the yavijava library supports the API calls required After that, I'd guess the design process would be to determine: what configuration data the Jenkins plugin would need for this use case how best to distinguish between "clone from template" and "instant clone" in the configuration UI if we'd also need different build steps to support it (e.g. we've got "template to vm" and "vm to template" but would we also need new stuff for "instant clones"?) how best to "plug in" to the existing "create a new VM on demand" functionality when the configuration is set to "instant clone". Having someone both willing and able to do it is key tho' - this is free software; it isn't anyone's "job" to implement features that other people are asking for; if you need it, you learn everything you need to learn to do that, and do it yourself (or you pay someone else to do that). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) --
[JIRA] (JENKINS-56884) Vsphere plugin : Convert Template to a VM
Title: Message Title pjdarton commented on JENKINS-56884 Re: Vsphere plugin : Convert Template to a VM I'd suggest that you log the following at Log level "ALL": vsphere-cloud org.jenkinsci.plugins.folder.FolderVSphereCloudProperty org.jenkinsci.plugins.vsphere org.jenkinsci.plugins.vSphereCloud org.jenkinsci.plugins.vSphereCloudLauncher org.jenkinsci.plugins.vSphereCloudProvisionedSlave org.jenkinsci.plugins.vSphereCloudRunListener org.jenkinsci.plugins.vSphereCloudSlave org.jenkinsci.plugins.vSphereCloudSlaveComputer org.jenkinsci.plugins.vSphereCloudSlaveTemplate org.jenkinsci.plugins.workflow.vSphereStep FYI logging on this plugin is a bit odd "for historical reasons", i.e. it was like that well before I ever got involved and I (and everyone else who's contributed since) have left that bit alone. Fixing it would be non-trivial, as it would mean moving all the code into a deeper package (e.g. org.jenkinsci.plugins.vsphere) and renaming the classes so they're called "VSphere..." instead of "vSphere...", but then there'd be hell to pay w.r.t. handling the upgrade path and (thus far) nobody's had the courage, the skill and the inclination to do that. Note: It's not a known bug - we turn VMs to templates and templates to VMs where I work and "it works for us" - but there is a known bug whereby most (all?) of the build steps will declare "success" if they fail- my guess is that it's failing silently and you'll see the real error once you've got more logging enabled. Add Comment
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Brian J Murrell commented on JENKINS-53752 Re: Block PRs from forks from untrusted users Andrey Babushkin That's not at all how the item description or help text reads. It very specifically says it will only build a change request / pull request ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194259.1537809356000.3600.1565888640492%40Atlassian.JIRA.
[JIRA] (JENKINS-42808) matrix-project support for pipeline jobs
Title: Message Title sv savage commented on JENKINS-42808 Re: matrix-project support for pipeline jobs I have a matrix of test data and configuration parameters that I would like to use a pipeline to test. . I can run a shell, but how to I get it to run a pipleline? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179806.1489589538000.3577.1565888280571%40Atlassian.JIRA.
[JIRA] (JENKINS-35371) Please add option to deploy ova file using vSphere Cloud Plugin
Title: Message Title pjdarton commented on JENKINS-35371 Re: Please add option to deploy ova file using vSphere Cloud Plugin These are two independent enhancements - the CDrom stuff would probably be an enhancement to the "reconfigure VM" build step. As for ova/ovf stuff, that really doesn't fit with the way vSphere & Jenkins communicate, e.g. what would "host" the ova/ovf files to provide them to vSphere? They'd really need to already be on the vSphere server to start with ... and if an end-user is able to arrange for that, they can also turn that into a vSphere template that vSphere is then able to use ... and which this plugin is able to tell vSphere to use. FYI there is no "ETA" on this because nobody seems to want it badly enough to implement support for it. This is free open-source software and you "get what you pay for" If you (or anyone else who wants this) can come up with a good design for how this would fit into the existing plugin functionality and, ultimately, create a pull-request that implements it, I'd be willing to help review the design/implementation and merge it into the code (as long as the demands on my time are kept to a minimum). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171162.1465210496000.3572.1565888220272%40Atlassian.JIRA.
[JIRA] (JENKINS-35371) Please add option to deploy ova file using vSphere Cloud Plugin
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-35371 Please add option to deploy ova file using vSphere Cloud Plugin Change By: pjdarton Assignee: jswager Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171162.1465210496000.3568.1565887440393%40Atlassian.JIRA.
[JIRA] (JENKINS-58136) vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration
Title: Message Title pjdarton commented on JENKINS-58136 Re: vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration I think I've found the error: The code was changed to say checked="false" I'd guess that removing that attribute should fix the issue ... but I'm not an expert on Jenkins "jelly" code so this would require a bit of trial-and-error to be 100% sure. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200181.1561105641000.3565.1565887380182%40Atlassian.JIRA.
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Andrey Babushkin commented on JENKINS-53752 Re: Block PRs from forks from untrusted users Brian J Murrell, no, it isn't because it blocks only Jenkinsfile changes (it will be taken from PR's target branch, not source) and still executes it. Therefore any user who can open a PR in your repository can easily modify build scripts/CMake files and gain access to your build systems Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194259.1537809356000.3558.1565887320277%40Atlassian.JIRA.
[JIRA] (JENKINS-58866) Splunk plugin not sending json files
Title: Message Title Ted commented on JENKINS-58866 Re: Splunk plugin not sending json files it will be fixed by https://github.com/jenkinsci/splunk-devops-plugin/pull/8 you can use https://repo.jenkins-ci.org/snapshots/com/splunk/splunkins/splunk-devops/1.8.1-SNAPSHOT/splunk-devops-1.8.1-20190815.162126-1.hpi for testing Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201183.1565289754000.3552.1565886420142%40Atlassian.JIRA.
[JIRA] (JENKINS-30009) Generates Dockerfile programmatically from DockerContainer
Title: Message Title Jesse Glick commented on JENKINS-30009 Re: Generates Dockerfile programmatically from DockerContainer Which reminds me, we should consider deprecating docker-fixtures altogether and moving everything over to testcontainers.org. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164588.1439905919000.3548.1565886180236%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title pjdarton assigned an issue to pjdarton Jenkins / JENKINS-46375 vSphere template definition doesn't allow environment variables to be defined Change By: pjdarton Issue Type: Bug Improvement Assignee: pjdarton Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184639.1503478575000.3542.1565885101175%40Atlassian.JIRA.
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title pjdarton assigned an issue to pjdarton Jenkins / JENKINS-41428 Tool Location Configuration Removed when Configuring System Change By: pjdarton Assignee: pjdarton Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178210.1485355044000.3544.1565885101210%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title pjdarton started work on JENKINS-46375 Change By: pjdarton Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184639.1503478575000.3539.1565885101114%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title pjdarton commented on JENKINS-46375 Re: vSphere template definition doesn't allow environment variables to be defined It looks like there's a problem in the WebUI "jelly" code that binds the UI to the data that's preventing folks from doing this. While I don't see why the code doesn't work as-is (as it's doing the same stuff as works elsewhere), I think it's a fairly trivial fix (especially as the docker plugin has a working example we can use for inspiration). I've started work to fix this in PR#105. Those changes will likely go into the next release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184639.1503478575000.3535.1565885040148%40Atlassian.JIRA.
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title pjdarton commented on JENKINS-41428 Re: Tool Location Configuration Removed when Configuring System It looks like there's a problem in the WebUI "jelly" code that binds the UI to the data. While I don't see why the code doesn't work as-is (as it's doing the same stuff as works elsewhere), I think it's a fairly trivial fix (especially as the docker plugin has a working example we can use for inspiration). I've started work to fix this in PR#105. Those changes will likely go into the next release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178210.1485355044000.3531.1565884980286%40Atlassian.JIRA.
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title pjdarton started work on JENKINS-41428 Change By: pjdarton Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178210.1485355044000.3528.1565884740514%40Atlassian.JIRA.
[JIRA] (JENKINS-42258) Parallel vSphere VM Creation Support
Title: Message Title pjdarton closed an issue as Cannot Reproduce Having used (and worked on) this plugin for a few years now, I'm pretty sure that, when it's configured to allow more than one VM of a particular template to be active, it'll create multiple VMs of that type, allowing builds to run on multiple VMs in parallel. i.e. I think this is a non-bug - the plugin already allows this. If that's not the case, feel free to add additional information here regarding the repro-case and re-open the issue. Jenkins / JENKINS-42258 Parallel vSphere VM Creation Support Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on
[JIRA] (JENKINS-58954) Durable-task-plugin Powershell step returnStdOut no longer working
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-58954 Durable-task-plugin Powershell step returnStdOut no longer working Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-08-15 15:52 Environment: Jenkins 2.176.2 Durable Task Plugin 1.30 Priority: Minor Reporter: Jon Starbird Not sure if this started in 1.30 as I didn't notice it until today. Is returnStdOut no longer supported? I didn't find any mention anywhere of it being removed. Scripts still run of course but nothing is printed out from the script run even if the Powershell script has write statements. Now getting this warning - WARNING: Unknown parameter(s) found for class type 'org.jenkinsci.plugins.workflow.steps.durable_task.PowershellScriptStep': returnStdOut Add Comment
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title Dan Alvizu reopened an issue re-opening as requested in previous comment Jenkins / JENKINS-53427 Agent creation failure because of concurrent attempts to schedule a pod Change By: Dan Alvizu Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193618.1536147614000.3514.1565883540602%40Atlassian.JIRA.
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title Dan Alvizu commented on JENKINS-53427 Re: Agent creation failure because of concurrent attempts to schedule a pod During our incident, deleting 1-3 pods would result in more pods coming up with the same error from the JNLP container. However, when we deleted all 100 of them, the next pods to start did not have this error. Script used to delete all the failed slaves in our 'cicd' namespace: for pod in $(kubectl get pods -n cicd -ojson -ljenkins=slave | jq '.items[].metadata.name' -r); do kubectl delete -n cicd pod "$pod" --wait=false; done I will try to reproduce this issue, but I believe that the high number of running pods is critical here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193618.1536147614000.3507.1565883480240%40Atlassian.JIRA.
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title Dan Alvizu commented on JENKINS-53427 Re: Agent creation failure because of concurrent attempts to schedule a pod We observed this in version 1.17.2 of the kubernetes-plugin. We had reached our maximum pod limit (100) in our kubernetes cluster, all of which had failing JNLP containers. They all had the same error: the master had refused the connection as it had an 'unknown client name' Agent JNLP container logs: Aug 14, 2019 9:51:40 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Protocol JNLP4-connect encountered an unexpected exception java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: proteus-apply-central-v95mf 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: proteus-apply-central-v95mf 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 org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: java.nio.channels.ClosedChannelException ... 7 more "Local headers refused by remote: Unknown client name:" Here is the jenkins master log of a single one of these failing pods (ui-pipeline-shared-7sdt7). Apologies I did not discover[ the debug logging settings|https://github.com/jenkinsci/kubernetes-plugin#debugging] during our incident so I do not have much logs: k logs jenkins-icecream-68c6d8497d-xhl9x -n cicd | grep ui-pipeline-shared-7sdt7 (central/ping-services) INFO: Terminating Kubernetes instance for agent ui-pipeline-shared-7sdt7 WARNING: Failed to delete pod for agent cicd/ui-pipeline-shared-7sdt7: not found INFO: Disconnected computer ui-pipeline-shared-7sdt7 ERROR: Failed to delete pod for agent cicd/ui-pipeline-shared-7sdt7: not found Disconnected computer ui-pipeline-shared-7sdt7 INFO: Created Pod: cicd/ui-pipeline-shared-7sdt7 INFO: Pod is running: cicd/ui-pipeline-shared-7sdt7 WARNING: Error in provisioning; agent=KubernetesSlave name: ui-pipeline-shared-7sdt7,
[JIRA] (JENKINS-58953) ConfigFileProvider throws exception after update
Title: Message Title
Michael Akinde created an issue
Jenkins / JENKINS-58953
ConfigFileProvider throws exception after update
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
config-file-provider-plugin, script-security-plugin
Created:
2019-08-15 14:49
Environment:
Oracle Linux
Priority:
Minor
Reporter:
Michael Akinde
Recently upgraded our internal Jenkins installation to 2.189, which also involved updating the script security plugin from 1.44 to v1.61. This caused a host of issues with scripts not running for various not easily identifiable reasons. Following the docs, it would appear one should be able to approve signatures and classpaths to resolve most of these issues, but nothing turns up in the GUI for approval in the current installation. Currently, the problem we're facing is this: Adding a configFileProvider to any script instantly breaks it. I.e., straight up code generated by the snippet generator like this:
steps {
configFileProvider([configFile(fileId: 'elapses-properties', targetLocation: 'elapses.properties')]) {
// some block
}
}
Results in this:
org.parboiled.errors.GrammarException: No constructor found for class org.jenkinsci.plugins.tokenmacro.Parser$$parboiled and the given 5 arguments
at
[JIRA] (JENKINS-58952) sh labels can't be used in post stages
Title: Message Title Brian J Murrell commented on JENKINS-58952 Re: sh labels can't be used in post stages If I put the label after the script sh script: '''set -ex ...''', label: "Collect artifacts and tear down" it parses fine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201299.1565879837000.3495.1565880180053%40Atlassian.JIRA.
[JIRA] (JENKINS-58952) sh labels can't be used in post stages
Title: Message Title
Brian J Murrell created an issue
Jenkins / JENKINS-58952
sh labels can't be used in post stages
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline-build-step-plugin
Created:
2019-08-15 14:37
Priority:
Major
Reporter:
Brian J Murrell
When I try to assign a label to an sh step in a post stage I get an error. I.e.:
post {
always {
sh label: "Collect artifacts and tear down",
script '''set -ex
I get the error:
WorkflowScript: 1078: Expected a step @ line 1078, column 29.
sh label: "Collect artifacts and tear down",
^
This works in a build step though:
stage('Build') {
when {
beforeAgent true
_expression_ { return env.QUICKBUILD == '1' }
}
agent {
dockerfile {
filename 'Dockerfile'
dir 'utils/docker'
label 'docker_runner'
additionalBuildArgs '--build-arg
[JIRA] (JENKINS-58951) Add YAML Configurator for folders in JCasC
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-58951 Add YAML Configurator for folders in JCasC Change By: Oleg Nenashev Assignee: Francisco Fernández Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201298.1565877288000.3488.1565877360298%40Atlassian.JIRA.
[JIRA] (JENKINS-58951) Add YAML Configurator for folders in JCasC
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-58951 Add YAML Configurator for folders in JCasC Issue Type: New Feature Assignee: Francisco Fernández Components: cloudbees-folder-plugin, configuration-as-code-plugin Created: 2019-08-15 13:54 Labels: jcasc-compatibility Priority: Minor Reporter: Oleg Nenashev Currently it is possible to configure folders in JCasC using Groovy syntax via JobDSL. It would be cool if the Folders Plugin had a native configurator so that JCasC could configure objects using YAML definition. Acceptance criteria: There is a way to define folder structure using JCasC It is possible to define folders and folder properties in YAML It is possible to define ComputedFolders via JCasC (e.g. GitHub Org Folder) Nice2have: The implementation allows configuring jobs inside folders in the future. Likely in YAML, see the examples for Pipeline in https://github.com/jenkinsci/simple-pull-request-job-plugin
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Karl Wirth commented on JENKINS-58949 Re: If job fails in cleanup further triggering fails Note: Cause on customers site was manually aborted job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201296.1565876577000.3484.1565877180066%40Atlassian.JIRA.
[JIRA] (JENKINS-58950) When trying to deploy with v2.0.0 of this plugin got error unable to find valid certification path to requested target.
Title: Message Title Mikhail K. created an issue Jenkins / JENKINS-58950 When trying to deploy with v2.0.0 of this plugin got error unable to find valid certification path to requested target. Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-08-15 13:50 Environment: Jenkins v2.176.2 ace-editor 1.1 true allure-jenkins-plugin 2.28.1 true ansicolor 0.6.2 true ant 1.9 true antisamy-markup-formatter 1.5 true apache-httpcomponents-client-4-api 4.5.5-3.0 true authentication-tokens 1.3 true authorize-project 1.3.0 true azure-commons 1.0.4 true bouncycastle-api 2.17 true branch-api 2.5.4 true build-pipeline-plugin 1.5.8 true build-timeout 1.19 true built-on-column 1.1 true cloudbees-folder 6.9 true command-launcher 1.3 true conditional-buildstep 1.3.6 true config-file-provider 3.6.2 true credentials 2.2.1 true credentials-binding 1.20 true dashboard-view 2.11 true display-url-api 2.3.2 true docker-commons 1.15 true docker-java-api 3.0.14 true docker-plugin 1.1.7 true docker-slaves 1.0.7 true docker-workflow 1.19 true durable-task 1.30 true email-ext 2.66 true embeddable-build-status 2.0.2 true envinject 2.2.0 true envinject-api 1.6 true external-monitor-job 1.7 true git 3.11.0 true git-client 2.8.0 true git-server 1.8 true global-variable-string-parameter 1.2 true handlebars 1.1.1 true icon-shim 2.0.3 true jackson2-api 2.9.9.1 true javadoc 1.5 true jdk-tool 1.3 true jenkins-multijob-plugin 1.32 true jquery 1.12.4-0 true jquery-detached 1.2.1 true jsch 0.1.55.1 true junit 1.28 true kubernetes 1.18.1 true kubernetes-cd 1.0.0 true kubernetes-cli 1.7.0 true kubernetes-credentials 0.4.1 true ldap 1.20 true locale 1.4 true lockable-resources 2.5 true mailer 1.24 true mapdb-api 1.0.9.0 true matrix-auth 2.4.2 true matrix-project 1.14 true maven-plugin 3.4 true mercurial 2.8 true momentjs 1.1.1 true pam-auth 1.5.1 true parameterized-trigger 2.35.2 true pipeline-build-step 2.9 true pipeline-graph-analysis 1.10 true pipeline-input-step 2.10 true pipeline-milestone-step 1.3.1 true pipeline-model-api 1.3.9 true pipeline-model-declarative-agent 1.1.1 true pipeline-model-definition 1.3.9 true pipeline-model-extensions 1.3.9 true pipeline-rest-api 2.12 true pipeline-stage-step 2.3 true pipeline-stage-tags-metadata 1.3.9 true pipeline-stage-view 2.12 true pipeline-utility-steps 2.3.0 true plain-credentials 1.5 true promoted-builds 3.3 true publish-over 0.22 true publish-over-ftp 1.15 true publish-over-ssh 1.20.1 true rancher 1.0.13-SNAPSHOT (private-12/31/2018 16:31-yunlong) true rebuild 1.31 true resource-disposer 0.13 true
[JIRA] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title javydreamercsw updated an issue Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: javydreamercsw Environment: Jenkins 1.651.2 , Jenkins 2.176.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170406.1463047354000.3441.1565876761314%40Atlassian.JIRA.
[JIRA] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title javydreamercsw commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects I believe this is still the case on 2.176.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170406.1463047354000.3353.1565876703937%40Atlassian.JIRA.
[JIRA] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title javydreamercsw updated an issue Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: javydreamercsw Environment: Jenkins 1.651.2 Jenkins 2.176.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170406.1463047354000.3397.1565876704844%40Atlassian.JIRA.
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-58949 If job fails in cleanup further triggering fails Issue Type: Bug Assignee: Unassigned Attachments: build.xml, log Components: p4-plugin Created: 2019-08-15 13:42 Environment: Jenkins 2.176.1 P4-Plugin 1.10.3 Labels: P4_VERIFY Priority: Blocker Reporter: Karl Wirth Reproduction Steps: Created Triggered Pipeline AutoClean job Add Trigger to Perforce server Submit a file to trigger path. Job runs. Allow it to run to completion. Submit a file to trigger path. Jobs runs. Press X on job before it gets to the sync stage. Result of job will be ABORTED. Submit a file to trigger path. Job DOES NOT run.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Mario Nitsch commented on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
I'm really happy with our solution that is based on a LinkedBlockingQueue.
def test = ["a","b","c","d","e","f"]
parallelLimitedBranches(test) {
echo "processing ${it.value} on branch ${it.branch}
}
def parallelLimitedBranches(Collection
[JIRA] (JENKINS-58551) Add support for Chinese Lunar calendar
Title: Message Title Jack Shen updated JENKINS-58551 Jenkins / JENKINS-58551 Add support for Chinese Lunar calendar Change By: Jack Shen Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200701.1563457668000.3308.1565874720268%40Atlassian.JIRA.
[JIRA] (JENKINS-30009) Generates Dockerfile programmatically from DockerContainer
Title: Message Title Oliver Gondža closed an issue as Won't Do I am closing this with as something we will not implement. Jenkins / JENKINS-30009 Generates Dockerfile programmatically from DockerContainer Change By: Oliver Gondža Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164588.1439905919000.3304.1565874600897%40Atlassian.JIRA.
[JIRA] (JENKINS-30859) Add support for Apache Mesos/Marathon
Title: Message Title Oliver Gondža commented on JENKINS-30859 Re: Add support for Apache Mesos/Marathon Is there still a need (and a will to implement) for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165473.1444387038000.3301.1565874540436%40Atlassian.JIRA.
[JIRA] (JENKINS-33107) ATH Docker Fixtures might fail using Docker-Machine
Title: Message Title Oliver Gondža resolved as Fixed Jenkins / JENKINS-33107 ATH Docker Fixtures might fail using Docker-Machine Change By: Oliver Gondža Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168474.1456245225000.3298.1565874480294%40Atlassian.JIRA.
[JIRA] (JENKINS-34411) Horizontal scrolling & overflow issues
Title: Message Title Oliver Gondža commented on JENKINS-34411 Re: Horizontal scrolling & overflow issues Is there something else to do? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169996.1461421897000.3294.1565874420174%40Atlassian.JIRA.
[JIRA] (JENKINS-40770) Take into account optional dependencies during plugins installation
Title: Message Title Oliver Gondža updated JENKINS-40770 I am afraid this issue is outdated after we have switched to update center proxy and delegate the dependency resolution to Jenkins update center fully. Jenkins / JENKINS-40770 Take into account optional dependencies during plugins installation Change By: Oliver Gondža Status: In Review Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177476.1483443708000.3292.1565874360259%40Atlassian.JIRA.
[JIRA] (JENKINS-54295) Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium
Title: Message Title Oliver Gondža updated JENKINS-54295 Jenkins / JENKINS-54295 Firefox version in newer jenkins/ath docker image is not compatible with ATH selenium Change By: Oliver Gondža Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194943.1540749992000.3290.1565874060267%40Atlassian.JIRA.
[JIRA] (JENKINS-56950) ATH container does not build because java 8 package is missing
Title: Message Title Oliver Gondža updated JENKINS-56950 Fixed by switching to centos a while ago. Jenkins / JENKINS-56950 ATH container does not build because java 8 package is missing Change By: Oliver Gondža Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198638.1554871727000.3288.1565874000457%40Atlassian.JIRA.
[JIRA] (JENKINS-58758) React Plugin Develop Boilerplate
Title: Message Title Jack Shen updated JENKINS-58758 Jenkins / JENKINS-58758 React Plugin Develop Boilerplate Change By: Jack Shen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201062.1564665164000.3286.1565874000388%40Atlassian.JIRA.
[JIRA] (JENKINS-58449) Fix reporting of Core/acceptance-test-harness
Title: Message Title Oliver Gondža resolved as Fixed This is working for a while: https://ci.jenkins.io/job/Core/job/acceptance-test-harness/job/master/167/testReport/junit/plugins/DashboardViewPluginTest/java_8_split0___jobsGridPortlet_numberOfColumns/ Jenkins / JENKINS-58449 Fix reporting of Core/acceptance-test-harness Change By: Oliver Gondža Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186519.151060657.3283.1565873940406%40Atlassian.JIRA.
[JIRA] (JENKINS-58932) Unable to Login After Upgrade from 2.176.1 to 2.176.2
Title: Message Title Jim Duffield updated an issue Jenkins / JENKINS-58932 Unable to Login After Upgrade from 2.176.1 to 2.176.2 Change By: Jim Duffield Environment: Upgrading from 2.176.1 to 2.176.2| Plugin | Version | Enabled ||---|---|---||apache-httpcomponents-client-4-api|4.5.5-3.0|true | |bouncycastle-api|2.17|true | |build-timestamp|1.0.3|true | |command-launcher|1.3|true | |conditional-buildstep|1.3.6|true | |credentials|2.2.1|true | |display-url-api|2.3.2|true | |email-ext|2.66|true | |git| 3.11.0|true | |git-client|2.8.0|true | |greenballs|1.15|true | |jackson2-api|2.9.9.1|true | |javadoc|1.5|true | |jdk-tool|1.3|true | |job-dsl|1.75|true | |jquery|1.12.4-0|true | |jquery-ui|1.0.2|true | |jsch|0.1.55.1|true | |junit|1.28|true | |ldap|1.20|true | |mailer|1.24|true | |matrix-auth|2.4.2|true | |matrix-project|1.14|true | |maven-plugin|3.4| true | |mesos|0.18.1|true | |metrics|4.0.2.5|true | |monitoring|1.79.0|true | |parameterized-trigger|2.35.2|true | |postbuildscript|2.8.1|true|role-strategy|2.13| true|run-condition|1.2|true|saferestart|0.3|true|scm-api|2.6.3|true|script-security|1.62|true|ssh-credentials|1.17.1|true|strict-crumb-issuer|2.0.1|true|structs|1.20|true|token-macro|2.8|true|variant|1.3|true|workflow-api|2.36|true|workflow-job|2.33|true|workflow-scm-step|2.9|true|workflow-step-api|2.20|true|workflow-support|3.3|true Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58948) Easy way to downgrade Blue Ocean
Title: Message Title Unknown Unknown created an issue Jenkins / JENKINS-58948 Easy way to downgrade Blue Ocean Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2019-08-15 12:31 Priority: Major Reporter: Unknown Unknown Blue Ocean has 22 dependant plugins. If you upgrade Blue Ocean and there is a bug in the release that makes it impossible to use Blue Ocean, you have to downgrade. Downgrading doesn't work the same as upgrading where you only upgrade the Blue Ocean plugin and all dependencies are automatically upgraded as well. You have to downgrad all 22 plugins manually. I had to do this more than once. The quality of Blue Ocean is really not that great. We need a way to downgrad in an easier way. Add Comment
[JIRA] (JENKINS-58947) Vault credentials not found secret/
Title: Message Title Kristiyan Kalugerov updated an issue Jenkins / JENKINS-58947 Vault credentials not found secret/ Change By: Kristiyan Kalugerov I'm using HashCorp Vault pluging in Jenkins multibranch pipeline with Vault Token Credential configuration. Everything was fine until the newest version 2.3.0. When I updated the version from 2.2.0 to 2.3.0 all of my pipelines using vault wrapper settings start showing me in the console output of every Jenkins job the message from the summary of the issue -> ` * Vault credentials not found secret/ ` * . When I go back to 2.2.0 everything works fine again. Before revert back to 2.2.0 I have changed all the steps as it is described here -> [ https://wiki.jenkins.io/display/JENKINS/HashiCorp+Vault+Plugin ] for version 2.3.0 but nothing changed.. again the same message. Do you guys have any ideas why this may happen ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201293.1565870178000.3273.1565870280224%40Atlassian.JIRA.
[JIRA] (JENKINS-58947) Vault credentials not found secret/
Title: Message Title Kristiyan Kalugerov created an issue Jenkins / JENKINS-58947 Vault credentials not found secret/ Issue Type: Task Assignee: Peter Tierno Components: hashicorp-vault-plugin Created: 2019-08-15 11:56 Labels: plugin jenkins pipeline vault not-found Priority: Major Reporter: Kristiyan Kalugerov I'm using HashCorp Vault pluging in Jenkins multibranch pipeline with Vault Token Credential configuration. Everything was fine until the newest version 2.3.0. When I updated the version from 2.2.0 to 2.3.0 all of my pipelines using vault wrapper settings start showing me in the console output of every Jenkins job the message from the summary of the issue -> `Vault credentials not found secret/ `. When I go back to 2.2.0 everything works fine again. Before revert back to 2.2.0 I have changed all the steps as it is described here -> https://wiki.jenkins.io/display/JENKINS/HashiCorp+Vault+Plugin for version 2.3.0 but nothing changed.. again the same message. Do you guys have any ideas why this may happen ? Add
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Unknown Unknown commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" After reading through all the comments I came to the conclusion that Blue Ocean must be dead and abandoned. The issue is over 2 months old and breaks Blue Ocean completly. How is it possible that nobody has fixed this the minute after it was reported. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.3265.1565866620996%40Atlassian.JIRA.
[JIRA] (JENKINS-58459) Add User documentation to Folder Auth README
Title: Message Title Abhyudaya Sharma updated JENKINS-58459 Jenkins / JENKINS-58459 Add User documentation to Folder Auth README Change By: Abhyudaya Sharma Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/folder-auth-plugin/releases/tag/folder-auth-1.0-beta-1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200593.1562916638000.3268.1565866621038%40Atlassian.JIRA.
[JIRA] (JENKINS-55798) Performance: Offer Enum APIs instead of String APIs in RoleBasedAuthorizationStrategy
Title: Message Title Abhyudaya Sharma updated JENKINS-55798 Jenkins / JENKINS-55798 Performance: Offer Enum APIs instead of String APIs in RoleBasedAuthorizationStrategy Change By: Abhyudaya Sharma Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/role-strategy-plugin/releases/tag/role-strategy-2.12 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197187.1548591082000.3243.1565866560269%40Atlassian.JIRA.
[JIRA] (JENKINS-58486) Add help files and meta information to Folder Auth plugin
Title: Message Title Abhyudaya Sharma updated JENKINS-58486 Jenkins / JENKINS-58486 Add help files and meta information to Folder Auth plugin Change By: Abhyudaya Sharma Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/folder-auth-plugin/releases/tag/folder-auth-1.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200624.1563172016000.3240.1565866500219%40Atlassian.JIRA.
[JIRA] (JENKINS-58293) Introduce folder based authorization
Title: Message Title Abhyudaya Sharma updated JENKINS-58293 1.0 Released: plugins.jenkins.io/folder-auth Jenkins / JENKINS-58293 Introduce folder based authorization Change By: Abhyudaya Sharma Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/folder-auth-plugin/releases/tag/folder-auth-1.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58723) Make Folder Authorization Strategy Immutable
Title: Message Title Abhyudaya Sharma updated JENKINS-58723 Jenkins / JENKINS-58723 Make Folder Authorization Strategy Immutable Change By: Abhyudaya Sharma Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/folder-auth-plugin/releases/tag/folder-auth-1.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201016.1564473649000.3238.1565866440425%40Atlassian.JIRA.
[JIRA] (JENKINS-58485) Do not serialize ConcurrentHashMap$KeySetView
Title: Message Title Abhyudaya Sharma updated JENKINS-58485 Jenkins / JENKINS-58485 Do not serialize ConcurrentHashMap$KeySetView Change By: Abhyudaya Sharma Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/folder-auth-plugin/releases/tag/folder-auth-1.0-beta-1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200623.1563168055000.3233.1565866380316%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Unknown Unknown updated an issue Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Unknown Unknown Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.3231.1565862842107%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Unknown Unknown commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Same here. No input steps are shown. We are not able to finish a pipeline. This is a desaster. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.3189.1565862780512%40Atlassian.JIRA.
[JIRA] (JENKINS-58145) Blue Ocean pipeline shows no progress
Title: Message Title Unknown Unknown commented on JENKINS-58145 Re: Blue Ocean pipeline shows no progress I have the same problem. I also updated from 164 to 176. Every pipeline with an input step is not able to complete because the input step just doesn't show up in the Blue Ocean view. The log says "Input requested" and I can click on that link and it also shows me the proceed and abort buttons. I also updated several plugins so I don't know which version caused the error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200190.156113573.3187.1565862600178%40Atlassian.JIRA.
[JIRA] (JENKINS-58921) Extremly slow build after connection to network
Title: Message Title Michal Zajac updated an issue Jenkins / JENKINS-58921 Extremly slow build after connection to network Change By: Michal Zajac Hi, When I changed network settings of my Virtual Machine to "Bridged: Connected directly to the physical network", jobs is done extremely slow.I have Jenkins server which is installed on Virtual Machine, when the IP of virtual machine is "local" (e.g. 192.168.1.20) jobs are done quite OK (~6minutes per build).But when I changed IP to domain IP (e.g. 3.194.15.23) build are s slow (up to 15 hours!). I changed IP due to fact, that I want to connect with server (from web browser) from every computer in network (not only from VM host computer)I tried almost everything, changed proxy setting, changed Java proxy settings, increase Java buffers, turn off the antyvirus and still nothing.This is not compiler/computer issue, because when I start compiling from command prompt (directly where the Makefile is), clean is perform quick, via Jenkins it stuck first time at:_mkdir -p XmlConfig_and take ~3minutes when in "normal" build it take ~100msany ideas where is the bug? UPDATE: When I change the IP settings in windows, and when there is no communication to e.g. SVN, compilation works fine (of course its not solve my problem)So my guessing is that this is some buffer in Jenkins after connection to WAN? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-39207) "RSS for all" shows only a few builds
Title: Message Title Steven Murphy commented on JENKINS-39207 Re: "RSS for all" shows only a few builds I know this is an old issue but this still appears to be the case. The rssAll only goes back 7 days. Is this the intention or is it returning an incomplete list? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175634.1477293546000.3181.1565861100153%40Atlassian.JIRA.
[JIRA] (JENKINS-58946) Use p4 changes @date instead of @change when finding CL to sync
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-58946 Use p4 changes @date instead of @change when finding CL to sync Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-08-15 09:08 Environment: 1.10.3 Labels: P4_VERIFY Priority: Minor Reporter: Karl Wirth Background This is a side effect of the way P4-Plugin now correctly only builds code that existed when the job was triggered. Imagine the following stream: Steam: //helix/dev Paths: share ... import+ imports/bin/... //builds-server/main/bin/... # A REMOTE DEPOT PATH import+ doc/html/... //doc/main/html/... # A LOCAL DEPOT PATH P4-Jenkins runs 'p4 changes' to determine the correct changelist to build and then 'p4 sync' to get the code at that changelist. In the above scenario 'p4 changes -m1 ws' will only return the highest changelist for the local depot paths '//helix/dev/...' and '//doc/main/html/...'. Problem This is fine unless the '//builds-server/main/bin/...' has been updated after the other two paths. In that case we will not sync any newer changes from the remote depot until a local depot change occurs even if you click 'Build Now'. This is because we are running that 'p4 changes' first to figure out what to build. Solution A possible
[JIRA] (JENKINS-54776) Node stays suspended after node is started
Title: Message Title nicholas robinson commented on JENKINS-54776 Re: Node stays suspended after node is started We have a similar issue to this. In our log there are a number of "agent XXX is always shut down" messages however the agent is still running. It seems the omsagent will not allow the plugin to shutdown the vm during updates/patching the plugin then marks the vm as eligibleforreuse even though its not shutdown please consider adding a try/catch here https://github.com/jenkinsci/azure-vm-agents-plugin/blob/46658bae2f22df3c8aaeb73d707816d766ca9dbc/src/main/java/com/microsoft/azure/vmagent/AzureVMAgent.java#L492 to see if the vm actually shutsdown Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195583.1542901223000.3171.1565859720380%40Atlassian.JIRA.
[JIRA] (JENKINS-56661) Add suppot to discover tags
Title: Message Title John V commented on JENKINS-56661 Re: Add suppot to discover tags I think that this might already be working? At least in my pipeline log all tags are discovered and checked for a Jenkinsfile (don't have any tags with a Jenkinsfile so cannot say if it actually works). Maybe we could get the "Discover branches" and "Discover tags" options like in the git source? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198295.155316814.3167.1565857140295%40Atlassian.JIRA.
[JIRA] (JENKINS-58943) Kubernetes plugin missing dependency on variant-plugin?
Title: Message Title Ian Williams assigned an issue to Unassigned Jenkins / JENKINS-58943 Kubernetes plugin missing dependency on variant-plugin? Change By: Ian Williams Assignee: Ian Williams Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201288.1565825229000.3164.1565855880077%40Atlassian.JIRA.
[JIRA] (JENKINS-58943) Kubernetes plugin missing dependency on variant-plugin?
Title: Message Title
Ian Williams updated an issue
Jenkins / JENKINS-58943
Kubernetes plugin missing dependency on variant-plugin?
Change By:
Ian Williams
Using install_plugins.sh (decker model) to mange plugins.Updated list to include: kubernetes:1.18.1 (assuming all dependencies are pulled in so only lsit list top-level plugins)Startup Jenkins, get alert:{quote} Kubernetes plugin version 1.18.1Variant Plugin version 1.2 is older than required. To fix, install version 1.3 or later.{quote}No record of that dependency for the plugin.[https://plugins.jenkins.io/kubernetes-credentials] shows dependencies:Apache HttpComponents Client 4.x API v.4.5.5-3.0 (required)Credentials v.2.1.7 (required)Plain Credentials v.1.3 (required)Command Agent Launcher v.1.0 (implied) (what's this?)Oracle Java SE Development Kit Installer v.1.0 (implied) (what's this?)JAXB v.2.3.0 (implied) (what's this?)Trilead API v.1.0.4 (implied) (what's this?)Jenkins.instance.pluginManagerplugins..getDependencies() reports:[apache-httpcomponents-client-4-api (4.5.5-3.0), credentials (2.1.7), plain-credentials (1.3), command-launcher (1.0), jdk-tool (1.0)]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-58943) Kubernetes plugin missing dependency on variant-plugin?
Title: Message Title Ian Williams assigned an issue to Ian Williams Jenkins / JENKINS-58943 Kubernetes plugin missing dependency on variant-plugin? Change By: Ian Williams Assignee: Ian Williams Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201288.1565825229000.3162.1565855700141%40Atlassian.JIRA.
[JIRA] (JENKINS-58943) Kubernetes plugin missing dependency on variant-plugin?
Title: Message Title Ian Williams updated an issue Jenkins / JENKINS-58943 Kubernetes plugin missing dependency on variant-plugin? Change By: Ian Williams Summary: Kubernets Kubernetes plugin missing dependency on varaint variant -plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201288.1565825229000.3161.1565855700103%40Atlassian.JIRA.
