[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job New debug log, and a screenshot of the configuration of the job. Strange how it's complaining about a filter change, given manual FTP commands are showing it works. 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.199458.1558312268000.6172.1558418220084%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Daniel Stratton Attachment: jobConfig.png Attachment: debugLog.20190521.1551.txt 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.199458.1558312268000.6170.1558418100270%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job OK, I decided to give more thought to the relogon logic - seems to be the reason. For now - new dbg version + old SITE command. Kindly retest. 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.199458.1558312268000.6168.1558416780075%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector.hpi 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.199458.1558312268000.6164.1558416720162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector.hpi 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.199458.1558312268000.6166.1558416720189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57574) NO_PROXY enviroment overwrites with side value on slave/JNLP
Title: Message Title Danil Kichay created an issue Jenkins / JENKINS-57574 NO_PROXY enviroment overwrites with side value on slave/JNLP Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-05-21 04:53 Priority: Minor Reporter: Danil Kichay https://hub.docker.com/r/openshift/jenkins-2-centos7 updated jenkins war /usr/lib/jenkins/jenkins.war 2.164.3 updated all plugins Kubernetes plugin 1.15.4 I have a kubernetes cloud plugin with kubernetes pod template configurated. There are HTTP_PROXY, HTTPS_PROXY, NO_PROXY variables is set with "Raw yaml for the Pod" in template configuration. I have a NO_PROXY with "jenkins," value overwriten but not added to the variable. This behavior breaks pipelines with proxy-through routing to a local services with any NO_PROXY configuration in templates. It worked good on old Jenkins 2.138.2 with Kubernetes plugin 1.12.8. I suspected that NO_PROXY enviroment has been overwriten with "Jenkins URL" hostname from configuration when slave nodes running. Sorry for my poor grammar. Add Comment
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar commented on JENKINS-54010 Re: Support two levels of parallelity in stages Could someone from CloudBees Inc. possibly take a look at this? I have seen a few other tickets related to parallel visualization in blue ocean owned by you guys. 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.194623.1539245979000.6158.1558414261939%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57573) Could not download plug ins.
Title: Message Title Md Arshad Qureshi created an issue Jenkins / JENKINS-57573 Could not download plug ins. Issue Type: Bug Assignee: Mark Waite Components: git-plugin, maven-plugin Created: 2019-05-21 04:48 Priority: Major Reporter: Md Arshad Qureshi I am not able to load and download plugins on my machine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52468) Change name of variables in Credential.java
Title: Message Title runze xia started work on JENKINS-52468 Change By: runze xia 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.192297.1531288283000.6097.1558411680484%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52468) Change name of variables in Credential.java
Title: Message Title runze xia stopped work on JENKINS-52468 Change By: runze xia 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.192297.1531288283000.6099.1558411680507%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57572) how to use pipeline sh git add tag?
Title: Message Title
chongjing zhao created an issue
Jenkins / JENKINS-57572
how to use pipeline sh git add tag?
Issue Type:
Patch
Assignee:
Unassigned
Components:
pipeline
Created:
2019-05-21 04:07
Priority:
Minor
Reporter:
chongjing zhao
my jenkins in running k8s i want use pipeline script sh 'git tag' it can't work， error code 127 Here's my pipeline code podTemplate(label: 'docker-pod-git', containers: [ containerTemplate( name: 'docker', image: 'docker:stable', ttyEnabled: true, command: 'cat' ), containerTemplate( name: 'jnlp', image: 'registry.cn-hangzhou.aliyuncs.com/google-containers/jnlp-slave:alpine', args: '${computer.jnlpmac} ${computer.name}', command: '' )], volumes: [ /persistentVolumeClaim(mountPath: '/home/jenkins', claimName: 'jenkins', readOnly: false),/ hostPathVolume(hostPath: '/root/work/jenkins', mountPath: '/home/jenkins'), hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock'), hostPathVolume(hostPath: '/tmp/', mountPath: '/tmp/'), ]) { node ('docker-pod-git') { container('docker') { git url: 'http://*/git/saasvshop.git' , branch: 'release',credentialsId:'**' sh'git tag' } } } here is console log Fetching changes from the remote Git repository > git rev-parse --is-inside-work-tree # timeout=10 > git config remote.origin.url ***# timeout=10 Fetching upstream changes from *** > git --version # timeout=10 using GIT_ASKPASS to set credentials > git fetch --tags --progress *** +refs/heads/:refs/remotes/origin/ Checking out Revision b0381fb26733eaa594ee6f38beb50d94915b31cb (refs/remotes/origin/release) > git rev-parse refs/remotes/origin/release^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/release^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f b0381fb26733eaa594ee6f38beb50d94915b31cb > git branch -a -v --no-abbrev # timeout=10 > git branch -D release # timeout=10 > git checkout -b release b0381fb26733eaa594ee6f38beb50d94915b31cb Commit message:
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar edited a comment on JENKINS-54010 Re: Support two levels of parallelity in stages My set up is also very similar to the one that [~shahafd] has described. A possible solution is to combine all nested stages into one node. When you click on this node, it expands and shows you everything else that was under it. This way the view is fairly clean and intuitive to use. See following images for examples: In the image below lets imagine I clicked on build 1:!Screen Shot 2019-05-14 at 9.49.06 AM.png|width=169,height=304!The UI will then transition to show the following nested pipeline:!Screen Shot 2019-05-20 at 8.55.46 PM.png|width=451,height=198! This basically steps away from only supporting nested parallels to just supporting nested pipelines. Is there anyone who can be considered the owner of this issue? It would be great if we could come up with a plan and start executing. As [~shahafd] said, when you have 50+ builds in parallel, the use is pretty much useless without nesting support. 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.194623.1539245979000.6037.1558411263841%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar commented on JENKINS-54010 Re: Support two levels of parallelity in stages My set up is also very similar to the one that Shahaf Duenyas has described. A possible solution is to combine all nested stages into one node. When you click on this node, it expands and shows you everything else that was under it. This way the view is fairly clean and intuitive to use. See following images for examples: In the image below lets imagine I clicked on build 1: The UI will then transition to show the following nested pipeline: This basically steps away from only supporting nested parallels to just supporting nested pipelines. Is there anyone who can be considered the owner of this issue? It would be great if we could come up with a plan and start executing. As Shahaf Duenyas said, when you have 50+ builds in parallel, the use is pretty much useless without nesting support. 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.194623.1539245979000.5980.1558411263285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar edited a comment on JENKINS-54010 Re: Support two levels of parallelity in stages My set up is also very similar to the one that [~shahafd] has described.A possible solution is to combine all nested stages into one node. When you click on this node, it expands and shows you everything else that was under it. This way the view is fairly clean and intuitive to use. See following images for examples:In the image below lets imagine I clicked on build 1:!Screen Shot 2019-05-14 at 9.49.06 AM.png|width=169,height=304!The UI will then transition to show the following nested pipeline:!Screen Shot 2019-05-20 at 8.55.46 PM.png|width=451,height=198! This basically steps away from only supporting nested parallels to just supporting nested pipelines.Is there anyone who can be considered the owner of this issue? It would be great if we could come up with a plan and start executing. As [~shahafd] said, when you have 50+ builds in parallel, the use UI is pretty much useless without nesting support. 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.194623.1539245979000.6039.1558411263864%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar updated an issue Jenkins / JENKINS-54010 Support two levels of parallelity in stages Change By: Rishi Thakkar Attachment: Screen Shot 2019-05-20 at 8.55.46 PM.png 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.194623.1539245979000.5868.1558411141192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar updated an issue Jenkins / JENKINS-54010 Support two levels of parallelity in stages Change By: Rishi Thakkar Attachment: Screen Shot 2019-05-14 at 9.49.06 AM.png 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.194623.1539245979000.5811.1558411021272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman commented on JENKINS-57371 Re: error message when building PR Audun Halland Formatting: no problem. Yes, one part of Jenkins thinks that definitely believes that the head of master is 7e88, when it is actually 76ff. But it is unclear how that is happening. It sounds like the patch has unblocked you. I'm working on finalizing a new version that includes this 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.199152.155732120.5808.1558404540422%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57565) server.key was unexpected at this time error while building Saleforce using DX
Title: Message Title Owen Mehegan assigned an issue to Unassigned Jenkins / JENKINS-57565 server.key was unexpected at this time error while building Saleforce using DX Change By: Owen Mehegan Assignee: Owen Mehegan 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.199477.1558368443000.5806.1558399860394%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57565) server.key was unexpected at this time error while building Saleforce using DX
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-57565 server.key was unexpected at this time error while building Saleforce using DX Change By: Owen Mehegan Component/s: core Component/s: gitlab-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.199477.1558368443000.5804.1558399860367%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57519) JavaScript: switch to let/const
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-57519 _javascript_: switch to let/const Change By: Josh Soref Summary: _javascript_: switch to let /const 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.199424.1558091187000.5802.1558398780059%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53816) [Blue Ocean] Completed stages appear to be skipped instead of finished
Title: Message Title Josh McDonald updated JENKINS-53816 Fix in master @ 9d8593973dd6c19dc98440effcf8c7abd158ccef Jenkins / JENKINS-53816 [Blue Ocean] Completed stages appear to be skipped instead of finished Change By: Josh McDonald 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.194330.153804945.5798.1558397640644%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job Appreciate the quick turnaround. I've attached the Console Output for the job, and an FTP query to prove the job is completed. I was forced to cancel it as it just sat and spun in the same loop. 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.199458.1558312268000.5796.1558396440085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Daniel Stratton Attachment: debugLog.20190521.0946.txt Attachment: ftpLog.20190521.0946.txt 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.199458.1558312268000.5794.1558396320205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk commented on JENKINS-35435 Re: Test connection doesn't work PR https://github.com/jenkinsci/ec2-fleet-plugin/pull/72 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.171232.146532240.5771.1558396140688%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-35435 Test connection doesn't work Change By: Artem Stasiuk Assignee: Aleksei Besogonov Artem Stasiuk 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.171232.146532240.5787.1558396140912%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk edited a comment on JENKINS-35435 Re: Test connection doesn't work Fix PR https://github.com/jenkinsci/ec2-fleet-plugin/pull/72 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.171232.146532240.5784.1558396140880%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Lakshya Kapoor commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I ran into this right after upgrading to 2.164.2 today. Clearing the /caches folder and restarting Jenkins got rid of 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.197354.1549278137000.5755.1558394761429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57571) Ecutest Plugin: JCasC Compatibility
Title: Message Title Oleg Nenashev resolved as Fixed Released in ecutest-2.7 Jenkins / JENKINS-57571 Ecutest Plugin: JCasC Compatibility Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Released As: ecutest-2.7 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.199485.1558390117000.5753.1558390203969%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57571) Ecutest Plugin: JCasC Compatibility
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57571 Ecutest Plugin: JCasC Compatibility Change By: Oleg Nenashev Labels: jcasc-compatibility 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.199485.1558390117000.5751.1558390201336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57570) Google Oauth: JCasC support
Title: Message Title Oleg Nenashev updated JENKINS-57570 Jenkins / JENKINS-57570 Google Oauth: JCasC support Change By: Oleg Nenashev Status: Resolved Fixed but Unreleased 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.199484.1558389773000.5747.1558390140338%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57571) Ecutest Plugin: JCasC Compatibility
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57571 Ecutest Plugin: JCasC Compatibility Issue Type: Bug Assignee: TraceTronic GmbH Components: ecutest-plugin Created: 2019-05-20 22:08 Priority: Minor Reporter: Oleg Nenashev Placeholder for https://github.com/jenkinsci/ecutest-plugin/pull/23 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57570) Google Oauth: JCasC support
Title: Message Title Oleg Nenashev updated JENKINS-57570 Jenkins / JENKINS-57570 Google Oauth: JCasC support Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199484.1558389773000.5749.1558390140362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57570) Google Oauth: JCasC support
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-57570 Google Oauth: JCasC support Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: Google Oauth 0.8 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.199484.1558389773000.5743.1558390020155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57570) Google Oauth: JCasC support
Title: Message Title Oleg Nenashev started work on JENKINS-57570 Change By: Oleg Nenashev 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.199484.1558389773000.5741.1558389960121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57570) Google Oauth: JCasC support
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57570 Google Oauth: JCasC support Change By: Oleg Nenashev Labels: jcasc-compatibility 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.199484.1558389773000.5739.1558389840116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57570) Google Oauth: JCasC support
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57570 Google Oauth: JCasC support Issue Type: Bug Assignee: Andrey Stroilov Components: google-oauth-plugin Created: 2019-05-20 22:02 Priority: Minor Reporter: Oleg Nenashev Placeholder for https://github.com/jenkinsci/google-oauth-plugin/pull/48 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57547) CWP 1.6 throws error if pom.xml is used for plugins and casc for configuration
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57547 CWP 1.6 throws error if pom.xml is used for plugins and casc for configuration Change By: Oleg Nenashev Labels: jcasc-compatibility regression 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.199455.1558292127000.5735.1558389600157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56684) Config as Code Nullpointer when instanceCapStr is not initialized
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56684 Config as Code Nullpointer when instanceCapStr is not initialized Change By: Oleg Nenashev Labels: configuration-as-code ec2-plugin jcasc-compatibility 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.198321.1553267844000.5734.1558389540240%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57488) build/deploy Vue js project through Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57488 build/deploy Vue js project through Jenkins Change By: Oleg Nenashev Component/s: _unsorted Component/s: core 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.199349.1557937803000.5731.1558388700140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57529) Unable to identify builds run as SYSTEM user
Title: Message Title Oleg Nenashev commented on JENKINS-57529 Re: Unable to identify builds run as SYSTEM user CC Daniel Beck . AFAICT https://github.com/jenkinsci/jenkins/pull/3931 should resolve it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199436.1558108275000.5729.1558388640176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57564) Documentation Update - Jenkins Shared Library Pipeline - Singleton vs On-Demand Singleton
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57564 Documentation Update - Jenkins Shared Library Pipeline - Singleton vs On-Demand Singleton Change By: Oleg Nenashev Component/s: pipeline Component/s: core 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.199476.1558366944000.5724.1558388580155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57564) Documentation Update - Jenkins Shared Library Pipeline - Singleton vs On-Demand Singleton
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57564 Documentation Update - Jenkins Shared Library Pipeline - Singleton vs On-Demand Singleton Change By: Oleg Nenashev Labels: documentation singletons 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.199476.1558366944000.5726.1558388580184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55793) Configuration as Code support for GitHub Pull Request Builder plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55793 Configuration as Code support for GitHub Pull Request Builder plugin Change By: Oleg Nenashev Labels: configuration-as-code jcasc-compatibility 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.197182.1548498736000.5722.1558387860111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Joseph Petersen updated JENKINS-57567 Jenkins / JENKINS-57567 View's description has no setter which is needed for JCasC Change By: Joseph Petersen 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.199481.1558374598000.5720.1558387740233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56422) JCasC doesn't export Github Enterprise Servers added
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56422 JCasC doesn't export Github Enterprise Servers added Change By: Oleg Nenashev Labels: jcasc-compatibility 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.198016.1551822666000.5718.1558387680222%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45473) Running Docker inside docker.image().inside() fails because group is set
Title: Message Title Michael Slattery commented on JENKINS-45473 Re: Running Docker inside docker.image().inside() fails because group is set I just created a pull request that solves the problem. However, it uses a different solution than prescribed in the description. It passes --group-add for all groups the Jenkins user belongs to. The original suggested solution would only work if there was a shared /etc/group between Jenkins and host. https://github.com/jenkinsci/docker-workflow-plugin/pull/174 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.183643.1499862179000.5709.1558385820093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57542) git checkout over ssh fails on windows agents started from msys2 - missing bat file
Title: Message Title T Herzke closed an issue as Won't Fix The problem occurs under special circumstances that are probably outside of the scope of Jenkins. Jenkins / JENKINS-57542 git checkout over ssh fails on windows agents started from msys2 - missing bat file Change By: T Herzke Status: Open Closed Resolution: Won't Fix 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.199450.1558197847000.5703.1558381620181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57542) git checkout over ssh fails on windows agents started from msys2 - missing bat file
Title: Message Title
T Herzke commented on JENKINS-57542
Re: git checkout over ssh fails on windows agents started from msys2 - missing bat file
Workaround recipe: 1) Identify additional environment variables and their values when starting the msys2 bash via start menu vs by invoking bash.exe from cmd.exe. 2) Create bash skript that sets these environment variables in multiple export NAME=value lines, also add the extended PATH value. Store as jenkins.env in msys2 root folder. 3) In the Jenkinsfiles, define custom step windows_bash
def windows_bash(command) {
bat ('C:\\msys64\\usr\\bin\\bash -c "source /jenkins.env && ' + command + ' "')
}
4) In the Jenkinsfiles, define a delegating custom step that forwards to either sh or windows_bash depending on the operating system of the Agent
def bash(command) {
windows() ? windows_bash(command) : sh(command)
}
where windows() has to be defined to return true only for windows agents. 5) In all places in the Jenkinsfile where a shell command could be executed either on windows or on Unix, use bash "command" instead of sh "command"
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
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Martin Weber commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline withEnv takes an array of multiple key-value pairs, one for each variable. Your script passes an array of a single string containing multiple key-value pairs, if I understand your script correctly. Please try with a minimal example. 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.199364.155799447.5699.1558380660359%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-57341 Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.5696.1558380180046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-57560 Export for JCasC is empty Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199471.1558357021000.5694.1558380120261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Mark Waite edited a comment on JENKINS-57560 Re: Export for JCasC is empty I can't duplicate the problem you're describing unless I specifically delete the system provided default git tool. Since it is the system provided default git tool, there is no need to list the default in configuration as code. Whether it is configuration as code or not, there will be a default git implementation.Is that the condition you're seeing?More challenging is the JENKINS-57326 bug which won't allow JGit or JGit with Apache authentication to be represented in JCasC. Can you provide more details on the UI that you use to view the "Tools configuration WebGUI page"? I open the JCasC configuration from "Manage Jenkins" -> "Configuration as Code" -> "View Configuration", then I search for the "tools:" section and the "git:" subsection. 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.199471.1558357021000.5692.1558380060174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Dirk D. commented on JENKINS-49278 Re: cat command in docker agents not detected correctly What about providing a additional switch like "useImageCMD" (default false) which ensures that the CMD from the image is used and is not overwritten with "cat"? 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.188136.1517348633000.5660.1558379880669%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55813) Improve AD/LDAP attribute analysis for locked accounts
Title: Message Title Félix Belzunce Arcos started work on JENKINS-55813 Change By: Félix Belzunce Arcos 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.197207.1548686882000.5651.1558378380528%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55813) Improve AD/LDAP attribute analysis for locked accounts
Title: Message Title Félix Belzunce Arcos stopped work on JENKINS-55813 Change By: Félix Belzunce Arcos 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.197207.1548686882000.5653.1558378380554%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57568) Signature is not trusted errors with Azure AD Configuration
Title: Message Title Ivan Fernandez Calvo closed an issue as Incomplete Jenkins / JENKINS-57568 Signature is not trusted errors with Azure AD Configuration Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Incomplete 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.199482.1558375485000.5647.1558378140246%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57568) Signature is not trusted errors with Azure AD Configuration
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-57568 Re: Signature is not trusted errors with Azure AD Configuration This does not look like a bug, it is mostly something wrong in the configuration, for further questions use the google groups no the Jira see [How ro report an issue|https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue] If the signature is not valid probably the SAMLResponse is not valid because the signature does not match, enable verbose log and check the logs see https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md 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.199482.1558375485000.5645.1558378140214%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57569) Can't boot Jenkins since upgrade to 2.178
Title: Message Title Technology Services created an issue Jenkins / JENKINS-57569 Can't boot Jenkins since upgrade to 2.178 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-20 18:27 Priority: Blocker Reporter: Technology Services I update jenkins.war from 2.177 to 2.178 and restart the service. Then I get below stacktrace in the Jenkins website: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ldapUserSearch': Cannot resolve reference to bean 'initialDirContextFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'initialDirContextFactory': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.acegisecurity.ldap.DefaultInitialDirContextFactory]: Constructor threw exception; nested exception is java.lang.IllegalArgumentException: An LDAP connection URL must be supplied. at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104) at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:495) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:162) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925) at
[JIRA] (JENKINS-57568) Signature is not trusted errors with Azure AD Configuration
Title: Message Title Lester Pimentel created an issue Jenkins / JENKINS-57568 Signature is not trusted errors with Azure AD Configuration Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: Screen Shot 2019-05-20 at 11.03.13 AM.png Components: saml-plugin Created: 2019-05-20 18:04 Environment: Jenkins 2.164.3 LTS saml-plugin 1.1.2 Priority: Minor Reporter: Lester Pimentel Hello - We are having issues when configuring the SAML plugin for Azure AD. After following the [config guide|https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE_AZURE.md] , I'm able to log in via Azure AD/SSO, but then am immediately logged out. I'm seeing the following in the Jenkins logs. I've tried the configuration both with and without Encryption Configuration checked as well. When checked, I followed the instructions in the help dialog to generate a new keystore and referenced that keystore in the config successfully. Still getting the same behavior, either way. Log snippet with exception: jenkins_1 | May 20, 2019 5:30:35 PM org.opensaml.core.config.InitializationService initializejenkins_1 | May 20, 2019 5:30:35 PM org.opensaml.core.config.InitializationService initializejenkins_1 | INFO: Initializing OpenSAML using the Java Services APIjenkins_1 | May 20, 2019 5:30:36 PM org.pac4j.saml.metadata.SAML2ServiceProviderMetadataResolver jenkins_1 | INFO: Using SP entity ID https://jenkins-dev.mycompany.comjenkins_1 | May 20, 2019 5:30:36 PM org.pac4j.saml.metadata.SAML2ServiceProviderMetadataResolver resolvejenkins_1 | INFO:
[JIRA] (JENKINS-45433) NullPointerException in startup trigger
Title: Message Title Emory Penney closed an issue as Cannot Reproduce No feedback for 2 years, cannot reproduce. Assuming issue was a fluke. Jenkins / JENKINS-45433 NullPointerException in startup trigger Change By: Emory Penney 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.183601.149976442.5640.1558375080152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled
Title: Message Title James Tuttle commented on JENKINS-45719 Re: Description for a pipeline run is not compatible and cannot be disabled +1 for supporting HTML in the description. We don't have the complex tables that other mentioned, but just a simple link back to the pull-request. Really miss having this in Blue Ocean, although at least for a link I can copy/paste it go there. 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.183918.1500635641000.5598.1558374840738%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Joseph Petersen started work on JENKINS-57567 Change By: Joseph Petersen 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.199481.1558374598000.5596.1558374720058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Joseph Petersen commented on JENKINS-57567 Re: View's description has no setter which is needed for JCasC Is related to JENKINS-57121 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.199481.1558374598000.5595.1558374660046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-57567 View's description has no setter which is needed for JCasC Issue Type: Bug Assignee: Joseph Petersen Components: core Created: 2019-05-20 17:49 Labels: jcasc-compatibility Priority: Minor Reporter: Joseph Petersen The description in view is missing a databound setter, this affects items ListView too Add Comment
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel This issue is absolutely killing our build server. It's appearing in many different contexts, including getting build configurations, viewing jobs, running executors, routine maintenance tasks like fingerprint cleanup, etc. There have been 4,707 occurrences in just the last three hours: jenkins.log is 32MB (attached compressed jenkins.log.gz). Jenkins is at 2.178. I keep upgrading hoping that this will be fixed but clearly it's not. If there's a single plugin causing the problem, I'd be happy to uninstall it but, as I noted, it's happening for lots of different operations. The biggest problem is that it's blocking the credentials store functionality, so projects that already have credentials configured have a warning "Cannot find any credentials with id ". The only options available in the credentials drop-down list are "current" and "none". If I set the credentials to "none" and save the configuration, then the only option available is "none". At some point the following message is logged: 2019-05-20 14:36:05.974+ [id=10] WARNING hudson.FilePath#_getChannelForSerialization: A FilePath object is being serialized when it should not be, indicating a bug in a plugin. See https://jenkins.io/redirect/filepath-serialization for details. java.io.NotSerializableException: The calling thread Thread[Handling GET /credentials/store/system/domain/_/credential// from __ : __ CredentialsStoreAction/CredentialsWrapper/index.jelly,5,main] has no associated channel. The current object null is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel I've got builds limping along now after dealing with weird conflicts from the authorize project plugin that may or may not be related to this issue, but I would really like a fix to this both so we can configure credentials on projects without having to edit config.xml files and to declutter the log files so that we can see any other issues that may occur. Add Comment This message was sent by
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Joseph Petersen commented on JENKINS-57121 Re: list view jobnames is missing getter and setter for jcasc compliance Please see the down stream PR: https://github.com/jenkinsci/configuration-as-code-plugin/pull/850/files#diff-d4180fbd418102ca8a2290ab285cb17c 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.198871.1555696084000.5586.1558374180125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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.199007.1556619184000.5572.1558373942099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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.199007.1556619184000.5565.1558373941277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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.199007.1556619184000.5579.1558373944205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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.199007.1556619184000.5558.1558373880261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Joseph Petersen commented on JENKINS-57121 Re: list view jobnames is missing getter and setter for jcasc compliance Does not work for jobNames Vi Pl your config uses includeRegex. 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.198871.1555696084000..1558373460176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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.199007.1556619184000.5548.1558372860565%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54208) Groovy compilation error in Splunk Plugin Extension
Title: Message Title Ted updated JENKINS-54208 Jenkins / JENKINS-54208 Groovy compilation error in Splunk Plugin Extension Change By: Ted Status: Open Fixed but Unreleased 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.194845.154031305.5531.1558371780281%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54208) Groovy compilation error in Splunk Plugin Extension
Title: Message Title
Ted commented on JENKINS-54208
Re: Groovy compilation error in Splunk Plugin Extension
pls refer https://plugins.jenkins.io/splunk-devops-extend for declarative syntax
#declarative pipeline
pipeline {
agent any
options {
timeout(time: 1, unit: 'HOURS')
sendSplunkConsoleLog()
}
stages {
stage('Example') {
steps {
echo 'Hello World'
}
}
}
}
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.194845.154031305.5529.1558371780251%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title Ted updated JENKINS-57410 Jenkins / JENKINS-57410 Splunk Plugin Causing threadlock When Testing Connections Change By: Ted Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199215.1557526135000.5527.1558371060931%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title Ted updated JENKINS-57410 fixed in 1.7.2 Jenkins / JENKINS-57410 Splunk Plugin Causing threadlock When Testing Connections Change By: Ted 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.199215.1557526135000.5523.1558371060420%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job I've just uploaded debug version: the issue is somewhat strange and maybe related to relogon logic differing from 2.2.0. The code is in separate branch at GitHub as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.5525.1558371060510%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector.hpi 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.199458.1558312268000.5521.1558371000167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult
Title: Message Title
Tobias Müller updated an issue
Jenkins / JENKINS-57566
Default security prohibits ResultAction's getResult
Change By:
Tobias Müller
The{code:java}post { always { dir("build") { script { def gccIssues = scanForIssues tool: gcc4(name: 'GCC') def action = "" issues: [ gccIssues ], filters: [ excludeFile(".*[/]src[/]external.*") ] def result = action.getResult() def newSize = result.getNewSize() echo newSize echo result.getNewIssues() } } }}{code}fails with{noformat}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method io.jenkins.plugins.analysis.core.model.ResultAction getResultat org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:262){noformat} I also reported this in gitter on 20.05.2019 and was asked to create this bug report 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
[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult
Title: Message Title
Tobias Müller created an issue
Jenkins / JENKINS-57566
Default security prohibits ResultAction's getResult
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-05-20 16:30
Priority:
Minor
Reporter:
Tobias Müller
The
post {
always {
dir("build") {
script {
def gccIssues = scanForIssues tool: gcc4(name: 'GCC')
def action = "" issues: [ gccIssues ], filters: [ excludeFile(".*[/]src[/]external.*") ]
def result = action.getResult()
def newSize = result.getNewSize()
echo newSize
echo result.getNewIssues()
}
}
}
}
fails with
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method io.jenkins.plugins.analysis.core.model.ResultAction getResult
at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:262)
[JIRA] (JENKINS-57565) server.key was unexpected at this time error while building Saleforce using DX
Title: Message Title
Manoj P created an issue
Jenkins / JENKINS-57565
server.key was unexpected at this time error while building Saleforce using DX
Issue Type:
Bug
Assignee:
Owen Mehegan
Components:
gitlab-plugin
Created:
2019-05-20 16:07
Environment:
Local
Priority:
Critical
Reporter:
Manoj P
Hi, While building a Salesforce App using multibranch pipeline, I am getting below error. All configs are correct. Git connection successful. Secret file created and id added to path. Could anyone help whats the issue? Using jenkins-2.164.3 - the latest version C:\Program Files (x86)\Jenkins\workspace\sfdx_>"C:\Program Files\Salesforce CLI\bin\sfdx" force:auth:jwt:grant --instanceurl https://test.salesforce.com --clientid 3MVG91LYYD8O4krRCwFq8CKUq8aUBCOGyPmIM919iQ8.rJw2w.JLmTNmuk_heggv79 --jwtkeyfile --username --setalias UAT \Jenkins\workspace\sfdx_@tmp\secretFiles\f28291d9-e13f-4537-9ef8-b47ea745880c{color:#FF}server.key was unexpected at this time.
Add Comment
[JIRA] (JENKINS-57564) Documentation Update - Jenkins Shared Library Pipeline - Singleton vs On-Demand Singleton
Title: Message Title Brandon Snuggs created an issue Jenkins / JENKINS-57564 Documentation Update - Jenkins Shared Library Pipeline - Singleton vs On-Demand Singleton Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-05-20 15:42 Labels: singletons Priority: Minor Reporter: Brandon Snuggs In the Jenkins documentation, it mentions that all var definitions are on-demand singletons, but does not explain what that means. Documentation reference: https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-global-variables Does this mean that the singleton is determined at the moment the job is called, so its a unique instance for that particular job? And how does this compare to an explicit @Singleton call when placed on a class? I tried setting up my shared pipeline so I could review both sides of it. When I run the code below, I can see in the output that both classes print out the information I expect. They both start as empty strings and then are set equal to the env.BUILD_TAG. My concern is that if I have multiple jobs running concurrently, do they share the same Singleton or is it unique to each build? So far I have not been able to prove this, so I was hoping someone has an answer to this. Structure src - org - utilities - GlobalStateClass.groovy vars - globalStateVar.groovy - main.groovy GlobalStateClass.groovy
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Oleg Nenashev commented on JENKINS-57121 Re: list view jobnames is missing getter and setter for jcasc compliance Same here, works for me 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.198871.1555696084000.5442.1558365480193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57563) Script Security: Add JCACS support to ScriptApproval
Title: Message Title Oleg Nenashev updated JENKINS-57563 Jenkins / JENKINS-57563 Script Security: Add JCACS support to ScriptApproval Change By: Oleg Nenashev 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.199475.155836454.5440.1558365060304%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57563) Script Security: Add JCACS support to ScriptApproval
Title: Message Title Oleg Nenashev started work on JENKINS-57563 Change By: Oleg Nenashev 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.199475.155836454.5438.1558365060279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Mark Waite commented on JENKINS-57560 Re: Export for JCasC is empty I can't duplicate the problem you're describing unless I specifically delete the system provided default git tool. Since it is the system provided default git tool, there is no need to list the default in configuration as code. Whether it is configuration as code or not, there will be a default git implementation. Is that the condition you're seeing? More challenging is the JENKINS-57326 bug which won't allow JGit or JGit with Apache authentication to be represented in JCasC. 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.199471.1558357021000.5436.1558364820166%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57563) Added JCACS support to ScriptApproval
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57563 Added JCACS support to ScriptApproval Issue Type: Bug Assignee: Andrew Bayer Components: script-security-plugin Created: 2019-05-20 15:02 Labels: jcasc-compatibility Priority: Minor Reporter: Oleg Nenashev Placeholder for https://github.com/jenkinsci/script-security-plugin/pull/250 Add Comment
[JIRA] (JENKINS-57563) Script Security: Add JCACS support to ScriptApproval
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57563 Script Security: Add JCACS support to ScriptApproval Change By: Oleg Nenashev Summary: Added Script Security: Add JCACS support to ScriptApproval 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.199475.155836454.5434.1558364580904%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57562) EC2Cloud crashes with NPE when instanceCapStr is not passed from JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57562 EC2Cloud crashes with NPE when instanceCapStr is not passed from JCasC Change By: Oleg Nenashev It is a minor issue in the EC2 Plugin implementation. instanceCapStr in [https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/EC2Cloud.java] is designed to be optional, and it supports empty strings in the constructor. But it still fails with NPE when a field is not passed from the JCasC configuration. I consider it is as an important issue, because the field is not exported by default .The issue can be fixed by a small patch to properly handle nulls in the constructor arguments 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.199473.1558362521000.5428.1558362600114%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57562) EC2Cloud crashes with NPE when instanceCapStr is not passed from JCasC
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57562 EC2Cloud crashes with NPE when instanceCapStr is not passed from JCasC Issue Type: Improvement Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-05-20 14:28 Labels: jcasc-compatibility newbie-friendly Priority: Minor Reporter: Oleg Nenashev It is a minor issue in the EC2 Plugin implementation. instanceCapStr in https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/EC2Cloud.java is designed to be optional, and it supports empty strings in the constructor. But it still fails with NPE when a field is not passed from the JCasC configuration. I consider it is as an important issue, because the field is not exported by default Add Comment
[JIRA] (JENKINS-46579) Maven Event Spy seems to still have a thread safe problem
Title: Message Title Dominik Bartholdi reopened an issue we run version 3.6.11 and still see this from time to time: ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /home/ec2-user/workspace/org_yooture_develop@tmp/withMaven5705f0d0/maven-spy-20190520-135648-9715492809875305253764.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 18407; columnNumber: 263; XML document structures must start and end within the same entity. Jenkins / JENKINS-46579 Maven Event Spy seems to still have a thread safe problem Change By: Dominik Bartholdi Resolution: Fixed Status: Closed Reopened Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-57347 Re: Performance degradation running pipeline step sh on remote agents -Probably related to track credentials, you can disable it - [- https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#threads-stuck-at-credentialsprovidertrackall- ] not related , I was thinking that the time was on the connection to the agent, I will make a test environment but the ssh-slave-plugin only manage the connection process and the way to open the channels, this should not be related to the time consumed by the steps, in any case, I will check it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199122.1557175676000.5419.1558360920291%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-57347 Re: Performance degradation running pipeline step sh on remote agents - Probably related to track credentials, you can disable it https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#threads-stuck-at-credentialsprovidertrackall - not related I was thinking that the time was on the connection to the agent, I will make a test environment but the ssh-slave-plugin only manage the connection process and the way to open the channels, this should not be related to the time consumed by the steps, in any case, I will check it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199122.1557175676000.5417.1558360920255%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57561) Ant plugin exports empty home and then crashes with NPE
Title: Message Title
Oleg Nenashev updated an issue
Jenkins / JENKINS-57561
Ant plugin exports empty home and then crashes with NPE
Change By:
Oleg Nenashev
Export by JCasC:{code:java}ant: defaultProperties: - installSource: installers: - "antFromApache" installations: - name: "Ant 1.10.5" properties: - installSource: installers: - antFromApache: id: "1.10.5"{code} Loading log...{code:java}Caused by: io.jenkins.plugins.casc.ConfiguratorException: ant: Failed to construct instance of class hudson.tasks.Ant$AntInstallation. Constructor: public hudson.tasks.Ant$AntInstallation(java.lang.String,java.lang.String,java.util.List). Arguments: [java.lang.String, null, java.util.ArrayList] at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:149) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:73) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:262) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.check(DataBoundConfigurator.java:97) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:339) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:282) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:347) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:282) at io.jenkins.plugins.casc.ConfigurationAsCode.lambda$checkWith$6(ConfigurationAsCode.java:665) at io.jenkins.plugins.casc.ConfigurationAsCode.invokeWith(ConfigurationAsCode.java:627) ... 18 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:141) ... 27 more Caused by: java.lang.NullPointerException at hudson.tasks.Ant$AntInstallation.launderHome(Ant.java:371) at hudson.tasks.Ant$AntInstallation.(Ant.java:359) ... 32 more{code} Just passing "home" the installation configuration does not help, it keeps crashing with NPE after that
[JIRA] (JENKINS-57561) Ant plugin exports empty home and then crashes with NPE
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57561 Ant plugin exports empty home and then crashes with NPE Change By: Oleg Nenashev Labels: jcasc-compatibility 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.199472.1558359982000.5403.1558360020526%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57561) Ant plugin exports empty home and then crashes with NPE
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57561 Ant plugin exports empty home and then crashes with NPE Change By: Oleg Nenashev Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199472.1558359982000.5401.1558360020492%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57523) Export for JCasC is empty
Title: Message Title Oleg Nenashev commented on JENKINS-57523 Re: Export for JCasC is empty I also discovered JENKINS-57561 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.199428.155809487.5406.1558360020580%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57561) Ant plugin exports empty home and then crashes with NPE
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57561 Ant plugin exports empty home and then crashes with NPE Issue Type: Improvement Assignee: Armando Fernandez Components: ant-plugin Created: 2019-05-20 13:46 Priority: Minor Reporter: Oleg Nenashev Export by JCasC: ant: defaultProperties: - installSource: installers: - "antFromApache" installations: - name: "Ant 1.10.5" properties: - installSource: installers: - antFromApache: id: "1.10.5" Loading log... Caused by: io.jenkins.plugins.casc.ConfiguratorException: ant: Failed to construct instance of class hudson.tasks.Ant$AntInstallation. Constructor: public hudson.tasks.Ant$AntInstallation(java.lang.String,java.lang.String,java.util.List). Arguments: [java.lang.String, null, java.util.ArrayList] at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:149) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:73) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:262) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.check(DataBoundConfigurator.java:97) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:339) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:282) at
[JIRA] (JENKINS-57523) Export for JCasC is empty
Title: Message Title Oleg Nenashev commented on JENKINS-57523 Re: Export for JCasC is empty Pavel Janoušek I have tested it locally, and it works for me well (except known JENKINS-57122). ant: defaultProperties: - installSource: installers: - "antFromApache" installations: - name: "Ant 1.10.5" properties: - installSource: installers: - antFromApache: id: "1.10.5" 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.199428.155809487.5397.1558358580139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57524) JCasC export contains only one record
Title: Message Title Pavel Janoušek commented on JENKINS-57524 Re: JCasC export contains only one record Oleg Nenashev Sure, will do for a new report related to this, thank you for the info. 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.199429.1558095004000.5369.1558357260117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
