[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Supraja Muppala commented on JENKINS-54209 Re: Can't read file: Can't access the file hi hechao, I applied a fix (https://github.com/jenkinsci/cppcheck-plugin/pull/46) for the plugin and it worked. I followed below steps Cppcheck 1.24 version had an issue and the fix was available online but the code was never pushed. Followed the below steps and it picked up the new code. Steps to have new plugin on your jenkins Instance. login to jenkins server cd to /var/lib/jenkins/plugins rename cppcheck.jpi cppcheck.jpi.orig.v1.24 cppcheck cppcheck.orig.v1.24 download cppcheck.hpi file from https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fcppcheck-plugin/detail/PR-46/2/artifacts/ Copy to /var/lib/jenkins/plugins dir and restart the jenkins service == 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57174) List Git Branches Parameter Plugin fetch error
Title: Message Title huang suoyuan commented on JENKINS-57174 Re: List Git Branches Parameter Plugin fetch error hi, it is released already, please refer to https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/list-git-branches-parameter/0.0.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs
Title: Message Title
Napoleon BlownApart updated an issue
Jenkins / JENKINS-57186
New View href is an absolute URL but other menu items are relative URLs
Change By:
Napoleon BlownApart
The href of the "New View" link in the left panel is constructed differently from the other links and is an absolute URL rather than a relative URL. I've only noticed this issue because our Jenkins server is setup behind inside a VPN & SSH, . So we VPN into the university and then SSH to our gateway machine. Thus we use two domain name variants to access Jenkins depending on whether the user is in the lab (thus using "jenkins.int") or outside the lab (thus using "jenkins.vpn").The consequence of this is that when an external user accesses the Jenkins server via VPN/SSH using "jenkins.vpn", the "New View" link points to "jenkins.int/newView" instead of "jenkins.vpn/newView". This means that external users get a 404 error (Server not found) and need to manually correct the url. (Minor/trivial bug.) In core/src/main/java/jenkins/model/NewViewLink.java, starting line 45 {code:java}@Overridepublic String getUrlName() {String urlName = Jenkins.getInstance().getRootUrl() + URL_NAME;return urlName;}{code}the class prepends _Jenkins.getInstance().getRootUrl()_ to _URL_NAME_. If "/" is prepended instead, _urlName_ becomes a relative address, and the "New View" link is fixed.As I am not familiar with the Jenkins codebase, I'm not sure if this is the right way to fix this problem.
Add Comment
This message was sent by Atlassi
[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs
Title: Message Title
Napoleon BlownApart updated an issue
Jenkins / JENKINS-57186
New View href is an absolute URL but other menu items are relative URLs
Change By:
Napoleon BlownApart
The href of the "New View" link in the left panel is constructed differently from the other links and is an absolute URL rather than a relative URL. I've only noticed this issue because our Jenkins server is setup behind a VPN & SSH, and we use two domain name variants to access Jenkins depending on whether the user is in the lab (thus using "jenkins.int") or outside the lab (thus using "jenkins.vpn").The consequence of this is that when an external user accesses the Jenkins server via VPN/SSH using "jenkins.vpn", the "New View" link points to "jenkins.int/newView" instead of "jenkins.vpn/newView". This means that external users get a 404 error (Server not found) and need to manually correct the url. (Minor/trivial bug.) In core/src/main/java/jenkins/model/NewViewLink.java, starting line 45 {code:java} @Overridepublic String getUrlName() {String urlName = Jenkins.getInstance().getRootUrl() + URL_NAME;return urlName;}{code}the class prepends _Jenkins.getInstance().getRootUrl()_ to _URL_NAME_. If "/" is prepended instead, _urlName_ becomes a relative address, and the "New View" link is fixed.As I am not familiar with the Jenkins codebase, I'm not sure if this is the right way to fix this problem.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57192) Digester does try to resolve references
Title: Message Title lanita kuang commented on JENKINS-57192 Re: Digester does try to resolve references Thanks, Can you provide an XML file? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47885) Add Pod Template Button (kubernetes-plugin) in system configuration not working after update matrix-auth plugin
Title: Message Title Daniel Beck commented on JENKINS-47885 Re: Add Pod Template Button (kubernetes-plugin) in system configuration not working after update matrix-auth plugin https://github.com/jenkinsci/matrix-auth-plugin/pull/60/commits/6a788cd3ad07bcdc5bfba252c19d80a8daf4d408 looks promising. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54568) authorizationMatrix does not work in declarative snippet generator
Title: Message Title Daniel Beck commented on JENKINS-54568 Re: authorizationMatrix does not work in declarative snippet generator https://github.com/jenkinsci/matrix-auth-plugin/pull/60/commits/6a788cd3ad07bcdc5bfba252c19d80a8daf4d408 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47885) Add Pod Template Button (kubernetes-plugin) in system configuration not working after update matrix-auth plugin
Title: Message Title Daniel Beck updated JENKINS-47885 Jenkins / JENKINS-47885 Add Pod Template Button (kubernetes-plugin) in system configuration not working after update matrix-auth plugin Change By: Daniel Beck 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54568) authorizationMatrix does not work in declarative snippet generator
Title: Message Title Daniel Beck updated JENKINS-54568 Jenkins / JENKINS-54568 authorizationMatrix does not work in declarative snippet generator Change By: Daniel Beck 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54568) authorizationMatrix does not work in declarative snippet generator
Title: Message Title Daniel Beck started work on JENKINS-54568 Change By: Daniel Beck 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47885) Add Pod Template Button (kubernetes-plugin) in system configuration not working after update matrix-auth plugin
Title: Message Title Daniel Beck started work on JENKINS-47885 Change By: Daniel Beck 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57191) Certificate Problem only with jira-step.plugin
Title: Message Title
Lars Biermanski updated an issue
Jenkins / JENKINS-57191
Certificate Problem only with jira-step.plugin
Change By:
Lars Biermanski
Hi Naresh,i've tried several hours to get start with the jire-step plugin and the internal it infrastructure of my company. It has a self-signed root certificate and the Jira server has an normal one signed with it as shown as follows:{{. |–LEVEL 2–Jenkins}}{{ROOT - |}}{{. |–LEVEL 2--Jira}}First i've had the "*unable to find valid certification path*" - error for all Jira plugins. After importing the server certificate and their root certificates into the keystore and referenced them in /etc/sysconfig/jenkins this error disappeared.For now the jira-step plugin has another error: "*hostname not validated".* The other Jira Plugin can connect to Jira and i could write comments into several tickets.I've also imported the certificates into the /etc/ssl/ca-bundle.crt store and openssl can connect successfully with the server. I downloaded the certificate directly via openssl from the Jira server and include it again into the keystore. The difference between jira-step and openssl is, I see that the jira ssl - step identifies a sha256-fingerprint and openssl a sha512-fingerprint of the Jira server- certificate has not a defined subject alternative name (SAN) field . I don't know actually, if Maybe this is important or not the problem here . I've tried If so, it would be very helpful to override the introduce an option for disabling or lower ssl -check in Jenkins checks at least for testing purposal without success . * Is there any option to override these ssl check in the Jira Step Plugin? * Does the alias-name in the keystore has any impact to the check? * Do you know the difference between Jira PlugIn and Jira Step PlugIn for this handshake? * Any other ideas :) ? I want really use Jira-Step to trigger time-based my jobs. A webhook would be an option, but is not allowed by it security at the moment. This is another story ;)Thanks for any help.GreetingsLars —with *-Djavax.net.debug=ssl*i see that the tls handshake has been done, but then the session is terminated:{code:java}trigger seeding of SecureRandomdone seeding SecureRandomAllow unsafe renegotiation: falseAllow legacy hello messages: trueIs initial handshake: trueIs secure renegotiation: false%% No cached client session*** ClientHello, TLSv1.2[...]*** ECDH ServerKeyExchangeSignature Algorithm SHA512withRSAServer key: Sun EC public key, 256 bits public x coord: public y coord: parameters: secp256r1 [NIST P-256, X9.62 prime256v1] (1.2.840.10045.3.1.7)*** ServerHelloDone*** ECDHClientKeyExchangeECDH Public value: Handling POST /descriptorByName/org.thoughtslive.jenkins.plugins.jira.Site/validateBasic from 10.270.58.12 : qtp992136656-386, WRITE: TLSv1.2 Handshake, length = 70SESSION KEYGEN:PreMaster Secret:CONNECTION KEYGEN:Client Nonce:Server Nonce:Master Secret:Client MAC write Secret:Server MAC write Secret:Client write key:Server write key:... no IV derive
[JIRA] (JENKINS-33666) Error after trying to reload configuration from the SCM plugin
Title: Message Title rajesh cheedalla commented on JENKINS-33666 Re: Error after trying to reload configuration from the SCM plugin I am also getting the same error. Any suggestion? Here is the log : com.thoughtworks.xstream.mapper.CannotResolveClassException: com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.SecurityMapper.realClass(SecurityMapper.java:71) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:379) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:48) at hudson.util.RobustReflectionConverter.determineType(RobustReflectionConverter.java:461) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:327) Caused: jenkins.util.xstream.CriticalXStreamException: com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy : com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy Debugging information message : com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException cause-message : com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy class
[JIRA] (JENKINS-46914) Better indicate implied permissions in the checkbox grid
Title: Message Title Daniel Beck updated JENKINS-46914 Jenkins / JENKINS-46914 Better indicate implied permissions in the checkbox grid Change By: Daniel Beck 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33666) Error after trying to reload configuration from the SCM plugin
Title: Message Title rajesh cheedalla updated an issue Jenkins / JENKINS-33666 Error after trying to reload configuration from the SCM plugin Change By: rajesh cheedalla Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-57201 [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel Change By: Baptiste Mathus Summary: [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Title: Message Title Baptiste Mathus assigned an issue to R. Tyler Croy Jenkins / JENKINS-57201 [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel Change By: Baptiste Mathus Assignee: Baptiste Mathus R. Tyler Croy 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Title: Message Title Baptiste Mathus commented on JENKINS-57201 Re: [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel R. Tyler Croy assigned this to you, after a discussion (yeah, s long ago :|). 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current updateLevel
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-57201
[Evergreen-backend] Expose a publicly accessible endpoint for the current updateLevel
Change By:
Baptiste Mathus
h3. Problem statementTo enableh3. ExpectedThe backend should expose a publicly accessible endpoint returning the current updateLevel. (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel).(This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.)h3. Technical asides{noformat}$ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channelgeneral$ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level188{noformat}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current updateLevel
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-57201 [Evergreen-backend] Expose a publicly accessible endpoint for the current updateLevel Issue Type: Story Assignee: Baptiste Mathus Components: evergreen Created: 2019-04-26 21:42 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-56108) AuditTrail java.nio.file.NoSuchFileException for log file handler
Title: Message Title Sylvia Qi commented on JENKINS-56108 Re: AuditTrail java.nio.file.NoSuchFileException for log file handler I encountered the same issue, but later discovered it had to do with the audit trail log directory. When I had the audit trail log directory set to /var/log/jenkins/audit-%g.log, I got that error. Then I changed it to /var/jenkins_home/logs/audit-%g.log, it worked. The default jenkins log dir of my installation is /var/jenkins_home/logs. Hope this helps. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title
Nofar Bluestein edited a comment on JENKINS-45579
Re: Step to set stage or parallel status
Thank you for the feedback![~saad_azam] I cannot commit to an ETA at the moment, but I can tell you it's a high priority for us,. I will provide additional update soon. [~nancyrobertson2005] in scripted pipelines the following should work: `warnError \{ error() }` would have the same result , but I will consider adding 'unstable' step so it's more elegant and consistent with the 'error' step
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title J P commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites Any plans to fix? Same issue today. Blue Ocean 1.14.0, Autofavorite 1.2.3. This got a lot of people really upset when we found out about it. Not a nice time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-57200 Can't access builds in BlueOcean after updating to 1.15.0 Issue Type: Bug Assignee: Unassigned Attachments: jenkins-thread-dump.log Components: core Created: 2019-04-26 20:44 Environment: Jenkins 2.174 (running in docker container) All BlueOcean plugins at 1.15.0 Labels: jenkins blueocean blueocean-ui Priority: Critical Reporter: Steve Todorov We've upgraded our BlueOcean plugins to the latest 1.15.0 and restarted Jenkins. Afterward, we were unable to access the `activity` tab and some of the builds. Initially we thought it was a browser issue, but after doing a curl request we noticed it's not working as well: $ time curl -I https://domain.com/blue/organizations/jenkins/project%2FjobName/detail/master/2217/pipeline/ ^C real 3m53,812s user 0m0,010s sys 0m0,008s There are no exception logs in Jenkins which can point to what's causing this. However I did make a thread dump which I've attached. I wasn't sure which component this relates to exactly so I've marked `core`.
[JIRA] (JENKINS-32496) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard
Title: Message Title Xaviar Steavenson commented on JENKINS-32496 Re: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard As a bug necro.. Sven Schoenung – if you create a circular reference you'll actually cause a framed version of Jenkins to do this same thing. Followed the stacktrace and ended up here and realized what it was causing it to try and go to / for some reason... Then I went and got coffee and looked again and saw the circular reference Might be nice to watch for that and put a pretty 'Either you need something with caffeine or you've been drinking too much...?' 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site
Title: Message Title Giuliano Campos commented on JENKINS-47309 Re: Plugin || Confluence Publisher || Not working with confluence cloud site Seconding Robert's comment above, this is impacting on the usability for the add-on in Cloud. If possible, any update on the progress would be highly appreciated. CC: Joe Hansche, the assignee of the case. Cheers, Giuliano 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47501) 2 pods are started instead of 1 after update to version 1.1
Title: Message Title Dax Games commented on JENKINS-47501 Re: 2 pods are started instead of 1 after update to version 1.1 I can confirm this is still happening with Kubernetes Plugin 1.15.1 and 1.15.2 on Jenkins 2.150.3. In my case it spins up a new pod every 10 seconds until the first one connects. I just watched a single job spin up 10 pods and the moment the first pod connected the plugin stopped spinning new pods. This is a HUGE problem. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Jesse Glick commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies At least some of the confusing overlap is old. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57199) java.io.IOException: Exception archiving {...list of files...}
Title: Message Title
Robert Baker updated an issue
Jenkins / JENKINS-57199
java.io.IOException: Exception archiving {...list of files...}
Change By:
Robert Baker
*23:11:56* ERROR: [withMaven] WARNING Exception executing Maven reporter 'Generated Artifacts Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at [https://issues.jenkins-ci.org|https://issues.jenkins-ci.org/]*23:11:56* java.io.IOException: Exception archiving \{...removed list of files...}*23:11:56* at org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher.process(GeneratedArtifactsPublisher.java:122)*23:11:56* at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118)*23:11:56* at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050)*23:11:56* at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:366)*23:11:56* at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)*23:11:56* at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)*23:11:56* at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)*23:11:56* at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)*23:11:56* at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)*23:11:56* at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)*23:11:56* at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)*23:11:56* at java.util.concurrent.FutureTask.run(FutureTask.java:266)*23:11:56* at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
[JIRA] (JENKINS-57199) java.io.IOException: Exception archiving {...list of files...}
Title: Message Title
Robert Baker updated an issue
Jenkins / JENKINS-57199
java.io.IOException: Exception archiving {...list of files...}
Change By:
Robert Baker
*23:11:56* ERROR: [withMaven] WARNING Exception executing Maven reporter 'Generated Artifacts Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at [https://issues.jenkins-ci.org|https://issues.jenkins-ci.org/]*23:11:56* java.io.IOException: Exception archiving \{...redacted list of files...}*23:11:56* at org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher.process(GeneratedArtifactsPublisher.java:122)*23:11:56* at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118)*23:11:56* at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050)*23:11:56* at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:366)*23:11:56* at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)*23:11:56* at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)*23:11:56* at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)*23:11:56* at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)*23:11:56* at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)*23:11:56* at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)*23:11:56* at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)*23:11:56* at java.util.concurrent.FutureTask.run(FutureTask.java:266)*23:11:56* at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)*23:11:56* at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)*23:11:5
[JIRA] (JENKINS-57199) java.io.IOException: Exception archiving {...list of files...}
Title: Message Title
Robert Baker created an issue
Jenkins / JENKINS-57199
java.io.IOException: Exception archiving {...list of files...}
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2019-04-26 19:41
Environment:
Jenkins 2.89.4 pipeline-maven-plugin 3.5.9
Priority:
Minor
Reporter:
Robert Baker
23:11:56 ERROR: [withMaven] WARNING Exception executing Maven reporter 'Generated Artifacts Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org 23:11:56 java.io.IOException: Exception archiving {...redacted list of files...}23:11:56 at org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher.process(GeneratedArtifactsPublisher.java:122)23:11:56 at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118)23:11:56 at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050)23:11:56 at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)23:11:56 at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:366)23:11:56 at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)23:11:56 at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)23:11:56 at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)23:11:56 at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)23:11:56 at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)23:11:56 at com.cloudbe
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Steve Collins edited a comment on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations I also have this problem when the docker image has 'no_proxy' set in the image.I had to remove the no_proxy env var from the image to be able to set no_proxy using Env/Node/etc properties.This was not a good workaround as it pushed proxy info back to the user (100's of Jenkins) and not able to use as we hope in other contexts outside of Jenkins without passing in no_proxy env var.thanks. Plugin is really great! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Steve Collins commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations I also have this problem when the docker image has 'no_proxy' set in the image. I had to remove the no_proxy env var from the image to be able to set using Env/Node/etc properties. This was not a good workaround as it pushed proxy info back to the user (100's of Jenkins) and not able to use as we hope in other contexts outside of Jenkins without passing in no_proxy env var. thanks. Plugin is really great! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title
Nofar Bluestein edited a comment on JENKINS-45579
Re: Step to set stage or parallel status
Thank you for the feedback![~saad_azam] I cannot commit to an ETA at the moment, but I can tell you it's a high priority for us, and we intend to start working on it in the next sprint . I will provide additional update soon. [~nancyrobertson2005] in scripted pipelines the following should work: `warnError \{ error() }` would have the same result
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title
Nofar Bluestein commented on JENKINS-45579
Re: Step to set stage or parallel status
Thank you for the feedback! Saad Azam I cannot commit to an ETA at the moment, but I can tell you it's a high priority for us, and we intend to start working on it in the next sprint. Nancy Robertson in scripted pipelines the following should work: `warnError { error() }` would have the same result
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Jesse Glick commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies At least the optionalDependents field was introduced in JENKINS-27177. It seems that the use of dependents to mean all dependencies predated that. Hard to tell what the original intent was, since the Javadoc does not specify; some of this seems to date to Jenkins 2.0. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-33843
It's not possible to disable/uninstall optional dependencies
The following example
Jenkins.instance.pluginManager.plugins.sort(false, {it.shortName}).each {p ->
println(p.shortName);
println(" dependencies:");
println("unspecified: ${p.dependencies*.shortName.sort()}");
println("optional: ${p.optionalDependencies*.shortName.sort()}");
println("mandatory: ${(p.dependencies - p.optionalDependencies)*.shortName.sort()}");
println(" dependents:");
println("unspecified: ${p.dependents.sort()}");
println("optional: ${p.optionalDependents.sort()}");
println("mandatory: ${(p.dependents - p.optionalDependents).sort()}");
}; null
reveals a mess:
antisamy-markup-formatter
dependencies:
unspecified: [bouncycastle-api, command-launcher, jdk-tool, junit]
optional: [bouncycastle-api, command-launcher, jdk-tool, junit]
mandatory: []
dependents:
unspecified: [greenballs, uno-choice]
optional: []
mandatory: [greenballs, uno-choice]
bouncycastle-api
dependencies:
unspecified: [command-launcher, jdk-tool]
optional: [command-launcher, jdk-tool]
mandatory: []
dependents:
unspecified: [antisamy-markup-formatter, credentials, external-monitor-job, greenballs, junit, ldap, mailer, matrix-project, windows-slaves]
optional: []
mandatory: [antisamy-markup-formatter, credentials, external-monitor-job, greenballs, junit, ldap, mailer, matrix-project, windows-slaves]
command-launcher
dependencies:
unspecified: [jdk-tool, script-security]
optional: [jdk-tool]
mandatory: [script-security]
dependents:
unspecified: [antisamy-markup-formatter, bouncycastle-api, config-file-provider, credentials, external-monitor-job, greenballs, junit, ldap, mailer, matrix-project, scm-api, ssh-credentials, structs, uno-choice, windows-slaves]
optional: []
mandatory: [antisamy-markup-formatter, bouncycastle-api, config-file-provider, credentials, external-monitor-job, greenballs, junit, ldap, mailer, matrix-project, scm-api, ssh-credentials, structs, uno-choice, windows-slaves]
config-file-provider
dependencies:
unspecified: [command-launcher, credentials, jdk-tool, ssh-credentials, structs, token-macro]
optional: [cloudbees-folder, command-launcher, jdk-tool]
mandatory: [credentials, ssh-credentials, structs, token-macro]
dependents:
unspecified: [job-dsl]
optional: [job-dsl]
mandatory: []
credentials
dependencies:
unspecified: [bouncycastle-api, command-launcher, jdk-tool, structs]
optional: [bouncycastle-api, command-launcher, jdk-tool]
mandatory: [structs]
dependents:
unspecified: [config-file-provider, ssh-credentials]
optional: []
mandatory: [config-file-provider, ssh-credentials]
display-url-api
dependencies:
unspecified: [jdk-tool]
optional: [jdk-tool]
mandatory: []
dependents:
unspecified: [mailer]
optional: []
mandatory: [mailer]
external-monitor-job
[JIRA] (JENKINS-50246) Blue Ocean github repo naming conflict
Title: Message Title Gavin Mogan closed an issue as Fixed Reading the cloudbees notes, this has been fixed already, so closing Jenkins / JENKINS-50246 Blue Ocean github repo naming conflict Change By: Gavin Mogan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Jesse Glick started work on JENKINS-33843 Change By: Jesse Glick 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46632) Run Details screen has double vertical scrollbar
Title: Message Title Gavin Mogan closed an issue as Fixed I havn't seen it recently, so i'm saying its fixed Jenkins / JENKINS-46632 Run Details screen has double vertical scrollbar Change By: Gavin Mogan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46254) Stapler produces JSON with duplicate property names
Title: Message Title Gavin Mogan closed an issue as Fixed Super stale, and no longer an issue? Jenkins / JENKINS-46254 Stapler produces JSON with duplicate property names Change By: Gavin Mogan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43792) Tidy up a sample plugin repo
Title: Message Title Gavin Mogan updated an issue Jenkins / JENKINS-43792 Tidy up a sample plugin repo Change By: Gavin Mogan Issue Type: Bug Task 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43924) Improve test coverage of blueocean-commons
Title: Message Title Gavin Mogan closed an issue as Not A Defect Jenkins / JENKINS-43924 Improve test coverage of blueocean-commons Change By: Gavin Mogan Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title Gavin Mogan closed an issue as Cannot Reproduce I'm going to close this for now, i don't know if its been fixed, but the pipeline creation UI doesn't ask for a name Jenkins / JENKINS-42990 Pipelines will misbehave if some special symbols are given in the name Change By: Gavin Mogan 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38361) Developing Blue Ocean on Windows
Title: Message Title Gavin Mogan closed an issue as Won't Fix Jenkins / JENKINS-38361 Developing Blue Ocean on Windows Change By: Gavin Mogan 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37876) Notify user of JWT clock skew
Title: Message Title Gavin Mogan updated an issue Jenkins / JENKINS-37876 Notify user of JWT clock skew Change By: Gavin Mogan Issue Type: Bug Improvement 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37841) Unable to open log due to missing JWT token
Title: Message Title Gavin Mogan closed an issue as Fixed Jenkins / JENKINS-37841 Unable to open log due to missing JWT token Change By: Gavin Mogan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37837) Regression: JWT token not present when logged in on blueocean.io
Title: Message Title Gavin Mogan closed an issue as Fixed Jenkins / JENKINS-37837 Regression: JWT token not present when logged in on blueocean.io Change By: Gavin Mogan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54199) Error loading Blue Ocean for Project
Title: Message Title Gavin Mogan closed an issue as Fixed I'm pretty sure this got fixed in later revisions, if you re-open please make sure you have updated Jenkins / JENKINS-54199 Error loading Blue Ocean for Project Change By: Gavin Mogan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54464) Customization for Blue Ocean logo
Title: Message Title Gavin Mogan updated an issue Jenkins / JENKINS-54464 Customization for Blue Ocean logo Change By: Gavin Mogan Issue Type: Bug Improvement 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56474) agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8
Title: Message Title Jeff Thompson commented on JENKINS-56474 Re: agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8 I'm not too surprised that class loading, filtering, and pattern matching would be slow on an interpreted-only JVM. Those can be some intensive operations. Commonly the agent and the operations it needs to perform can be resource intensive. If you're running into that much resource issues just getting it up and going, it may be difficult for it perform the builds, particularly if other plugins are configured for the job. I think your best approach is to figure out how to speed up your processes. If you can get away from an interpreted-only JVM, that would be a good step. Otherwise you may try throwing hardware or other resources at to get it to run faster. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54889) Blue Ocean is throwing an exception in case a Flownode displayname is null
Title: Message Title Gavin Mogan updated JENKINS-54889 Jenkins / JENKINS-54889 Blue Ocean is throwing an exception in case a Flownode displayname is null Change By: Gavin Mogan 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54876) Blueocean doesn't show TestNG Results
Title: Message Title Gavin Mogan updated an issue Jenkins / JENKINS-54876 Blueocean doesn't show TestNG Results Change By: Gavin Mogan Issue Type: Bug Improvement 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56866) Everything is favourite, it is not useful
Title: Message Title Gavin Mogan commented on JENKINS-56866 Re: Everything is favourite, it is not useful Agreed, its pretty busy Apparently it can be disabled per user in the user configuration screen (example https://ci.blueocean.io/user/halkeye/configure), or globally by setting -DBLUEOCEAN_FEATURE_AUTOFAVORITE_ENABLED=true Ideally we'd remove it from being a requirement 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51092) Two Factor Auth in Github Breaks Authentication for Github Organization
Title: Message Title Liam Newman commented on JENKINS-51092 Re: Two Factor Auth in Github Breaks Authentication for Github Organization You can still use two-factor auth login without using the access_token credential type. As a workaround, you use username/password credential type and set the password to the access_key value instead of a password. NOTE: This is the same thing github documentation says to do when accessing github from the command-line with 2FA turned on. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57198) Multibranch pipeline with git tags rebuilds without SCM change
Title: Message Title Zach LaCelle created an issue Jenkins / JENKINS-57198 Multibranch pipeline with git tags rebuilds without SCM change Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-04-26 17:49 Environment: jenkinsci/blueocean 2.164.1 Priority: Major Reporter: Zach LaCelle I've created a multibranch pipeline that gets tags with the "Discover tags" option, and am filtering by name to include two items: "master" and "latest". "master" is the gitlab master branch, and "latest" is a tag pointing to the latest tagged commit (for example, if I have tags 1.0.0, 1.0.1, and 1.0.2, the "latest" tag would point to 1.0.2). Originally, "latest" does not automatically build (as is documented elsewhere). After I tell it to build, however, it continues to build every 10 minutes with the reason "Started by SCM change." There was no SCM change, and the hash of the latest changeset doesn't change between builds. On the other hand, the "master" branch only builds once (correctly). Add Comment
[JIRA] (JENKINS-54476) JNLP Agent disconnected, having issues connecting to master.
Title: Message Title Jeff Thompson commented on JENKINS-54476 Re: JNLP Agent disconnected, having issues connecting to master. Disconnects, particularly with a ChannelClosedException, are typically caused by system, network, or environmental issues. Something external causes the TCP connection to be dropped. From inside the agent or master there is no information on what caused the failure. Tracking down the cause of the disconnections can be difficult. It involves various local troubleshooting activities. The hang is different from usual reports, but there isn't enough information to figure anything out from it. Can you provide any details about how that hang manifests? Does it occur when you try to kill the process? Is something going on at the time? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56555) Remoting error, missing class: hudson/remoting/Channel$IOSyncer
Title: Message Title Jeff Thompson updated JENKINS-56555 An inability to load classes from the remoting (agent) jar likely has the same root causes, even though the class causing problems is different. Closing as a duplicate of the other. Jenkins / JENKINS-56555 Remoting error, missing class: hudson/remoting/Channel$IOSyncer Change By: Jeff Thompson Status: Open Fixed but Unreleased Resolution: Duplicate 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Steven Clark edited a comment on JENKINS-54929 Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin I've submitted a PR that addresses this issue at least for me ([https://github.com/jenkinsci/ansible-plugin/pull/29]).Hopefully someone could accept it and create a bugfix release with it. *EDIT:* ** Looks like there are a very different cases, the patch in that PR seemed to address at least one, but we are still seeing some trimmed output depending on how Anisble might have died from the looks of things. Will keep on looking into the plugin but for now I've pulled the PR. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Steven Clark edited a comment on JENKINS-54929 Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin I've submitted a PR that addresses this issue at least for me ([https://github.com/jenkinsci/ansible-plugin/pull/29]).Hopefully someone could accept it and create a bugfix release with it. *EDIT:* Looks like there are a very few different cases, the patch in that PR seemed to address at least one, but we are still seeing some trimmed output depending on how Anisble Ansible might have died from the looks of things. Will I'll keep on looking into the plugin but for now I've pulled the PR. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Steven Clark edited a comment on JENKINS-54929 Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin I've submitted a PR that addresses this issue at least for me ([https://github.com/jenkinsci/ansible-plugin/pull/29]).Hopefully someone could accept it and create a bugfix release with it. *EDIT:* **Looks like there are a very different cases, the patch in that PR seemed to address at least one, but we are still seeing some trimmed output depending on how Anisble might have died from the looks of things. Will keep on looking into the plugin but for now I've pulled the PR. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43194) Lightweight checkout for PR merge jobs
Title: Message Title Liam Newman updated JENKINS-43194 Released in v2.5.0. Jenkins / JENKINS-43194 Lightweight checkout for PR merge jobs Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48865) JNLP Agents/Slaves Disconnecting Unpredictably
Title: Message Title Alfred Wong closed an issue as Fixed I will update if we find anything more about why the disconnection happen from our IT. Thanks. Jenkins / JENKINS-48865 JNLP Agents/Slaves Disconnecting Unpredictably Change By: Alfred Wong Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57186) New View href is an absolute URL but other menu items are relative URLs
Title: Message Title
Napoleon BlownApart updated an issue
Jenkins / JENKINS-57186
New View href is an absolute URL but other menu items are relative URLs
Change By:
Napoleon BlownApart
Summary:
New View href does not include "${rootURL}/" is an absolute URL but other menu items are relative URLs
The href of the "New View" link in the left panel is constructed differently from the other links and is an absolute URL rather than a relative URL . The sidepanel2.jelly file seems to be missing ${rootURL}/. I've only noticed this issue because our Jenkins server is setup behind a VPN & SSH, and we use two domain name variants to access Jenkins depending on whether the user is in the lab (thus using "jenkins.int") or outside the lab (thus using "jenkins.vpn").The consequence of this is that when an external user accesses the Jenkins server via VPN/SSH using "jenkins.vpn" , the "New View" link points to "jenkins.int/newView" instead of "jenkins.vpn/newView". This means that external users get a 404 error (Server not found) and need to manually correct the url. (Minor/trivial bug.)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
Y
[JIRA] (JENKINS-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman updated JENKINS-54992 Jenkins / JENKINS-54992 Terrifying message makes me think Jenkins will delete my github repo Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57197) Anchore plugin won't connect to self-signed cert
Title: Message Title Jake Remitz created an issue Jenkins / JENKINS-57197 Anchore plugin won't connect to self-signed cert Issue Type: Bug Assignee: Daniel Nurmi Components: anchore-container-scanner-plugin Created: 2019-04-26 15:28 Labels: certificate Priority: Minor Reporter: Jake Remitz We have Anchore Engine running in Kubernetes with a self-signed certificate. Locally, to connect to the remote service we need to use the --insecure flag. However, in the Jenkins Anchore plugin configuration, the "Verify SSL" checkbox appears to have no bearing. We have it deselected, but either way we cannot connect to anchore. The only way to connect to it is to use the internal Cluster IP given Jenkins is deployed also within Kubernetes. Is this a plugin issue or is this something within Kubernetes itself? The error we see is: 2019-04-26T09:51:27.963 ERROR AnchoreWorker Failed to add image(s) to anchore-engine due to an unexpected error javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223) at sun.security.ssl.Handshak
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled Ulli Hafner thanks for pointing me to this ticket in gitter. I tried to whitelist it, but it did not work for me. I also tried io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor (note the $) but this did not work either. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57196) DOC: More description for 'Populate have list'
Title: Message Title Kevin Williamson updated an issue Jenkins / JENKINS-57196 DOC: More description for 'Populate have list' Change By: Kevin Williamson Labels: documentation 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57196) DOC: More description for 'Populate have list'
Title: Message Title Karl Wirth assigned an issue to Kevin Williamson Jenkins / JENKINS-57196 DOC: More description for 'Populate have list' Change By: Karl Wirth Assignee: Karl Wirth Kevin Williamson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57196) DOC: More description for 'Populate have list'
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-57196 DOC: More description for 'Populate have list' Change By: Karl Wirth Assignee: Karl Wirth 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57196) DOC: More description for 'Populate have list'
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-57196 DOC: More description for 'Populate have list' Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-04-26 14:37 Priority: Minor Reporter: Karl Wirth The following section in the documentation assumes that the reader understands the importance of 'Have' lists in Perforce: https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/populate-forced-clean-sync.html?Highlight=%22Populate%20have%20list:%20%22 Populate have list: Overwrites the Perforce "have list". Suggest that it is changed to include a description that includes the impact. For example: Populate have list: Overwrites the Perforce "have list" that records which files have been synced to the workspace. This is usually relevant when you are not force syncing and want the next sync to only transfer changes since the last sync. Note: I am not a documentation expert but you get the idea .
[JIRA] (JENKINS-57099) Configuration of EXAM Installation not loaded
Title: Message Title MicroNova MicroNova resolved as Fixed fixed inconsistend naming of the field and getter Jenkins / JENKINS-57099 Configuration of EXAM Installation not loaded Change By: MicroNova MicroNova Status: In Progress Resolved Resolution: Fixed Released As: 1.0.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-56577
Unable to add Jira Site
Change By:
Radek Antoniuk
Not able to add Jira site in Jenkins. Steps to reproduce:1 Login to Jenkins (localhost:8080)2. Select Manage Jenkins3. Go to JIRA sites and click on Add4. Enter your Jira URL, user name and password5. Click on Test Connection It fails with below error {noformat} java.lang.NoSuchMethodError: okhttp3.HttpUrl.get(Ljava/lang/String;)Lokhttp3/HttpUrl; at retrofit2.Retrofit$Builder.baseUrl(Retrofit.java:458) at org.thoughtslive.jenkins.plugins.jira.service.JiraService.(JiraService.java:49) at org.thoughtslive.jenkins.plugins.jira.Site$DescriptorImpl.doValidateBasic(Site.java:183) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) {noformat}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title Radek Antoniuk commented on JENKINS-56577 Re: Unable to add Jira Site This looks like a conflict with JIRA steps plugin, do you have both plugins jira-plugin and jira-steps-plugin installed and you need them both? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-56577 Unable to add Jira Site Change By: Radek Antoniuk Component/s: jira-steps-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57099) Configuration of EXAM Installation not loaded
Title: Message Title MicroNova MicroNova started work on JENKINS-57099 Change By: MicroNova MicroNova 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57188) EC2 fleet machines fail to spin up.
Title: Message Title Nick Spor edited a comment on JENKINS-57188 Re: EC2 fleet machines fail to spin up. you can close this, increasing the total timeout in seconds allowed me to get passed past this issue. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57188) EC2 fleet machines fail to spin up.
Title: Message Title Nick Spor commented on JENKINS-57188 Re: EC2 fleet machines fail to spin up. you can close this, increasing the total timeout in seconds allowed me to get passed this issue. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57174) List Git Branches Parameter Plugin fetch error
Title: Message Title Yury Komarov commented on JENKINS-57174 Re: List Git Branches Parameter Plugin fetch error huang suoyuan, what is the date of 0.0.7 version release? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Jesse Glick commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies pjdarton Enhance the dependency algorithm to differentiate between hard dependencies and soft dependencies Jenkins has long made that distinction. It just was not being honored in this feature. it'd be nice to have a "I know what I'm doing! Do it anyway." option Would be useless since Jenkins core will refuse to even load a plugin which is missing a hard dependency. NetAppBlueDevil I don't even know why the Green Balls plugin has the LDAP plugin listed as an optional dependency This is because it was a plugin split out of core, and for compatibility reasons these are made implicit optional dependencies of all other plugins which were built against a version of core predating that split. But this brings up an important point. Why are these implicit dependencies optional? Well, in the vast majority of cases the old plugin was not actually using the detached functionality, so we do not want to prevent the split plugin from being disabled or uninstalled if it is obviously unused. There are a few cases where something was detached which a number of other plugins actually relied on—the most prominent cases being maven-plugin, matrix-project, and junit—and so there is some risk that an admin would accidentally disable an “optional” dep that was actually critical to some still-enabled plugin’s functioning, typically seen as a NoClassDefFoundError at runtime. Those cases which are not already mitigated by use of @Extension(optional = true) or other defensive coding patterns can be addressed merely by releasing a downstream plugin update which builds against a newer version of Jenkins core: the Maven build will fail until the split plugin is added as a dependency to the POM, causing it to appear as a hard dependency in the binary plugin’s manifest. Add Comment
[JIRA] (JENKINS-57192) Digester does try to resolve references
Title: Message Title Ulli Hafner edited a comment on JENKINS-57192 Re: Digester does try to resolve references Note that even with the fix you will have a problem: the pattern that you define used (sun_rules) should refer to the xml file that contains the warnings warning results and not to the rules! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57192) Digester does try to resolve references
Title: Message Title Ulli Hafner commented on JENKINS-57192 Re: Digester does try to resolve references Note that even with the fix you will have a problem: the pattern you define should refer to the xml file that contains the warnings and not to the rules! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53415) container image: don't uncompress jenkins.war to /var/jenkins_home
Title: Message Title Michael Düsterhus commented on JENKINS-53415 Re: container image: don't uncompress jenkins.war to /var/jenkins_home I recommend adding this: JENKINS_OPTS="--webroot=/var/cache/jenkins/war --pluginroot=/var/cache/jenkins/plugins" 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-33843 It's not possible to disable/uninstall optional dependencies Change By: Jesse Glick Assignee: Jesse Glick 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56777) Chrome opens, but nothing happens (Selenium)
Title: Message Title Lee Leibke commented on JENKINS-56777 Re: Chrome opens, but nothing happens (Selenium) Per Andrei's comment above, it looks like this was a Chrome bug, not a Jenkins issue. See https://bugs.chromium.org/p/chromium/issues/detail?id=942023 The fix may have been in the v74 release of Chrome, but I haven't verified that using the v74 release of the chromeDriver yet. If the fix isn't in v74 Chrome, it sounds like it would definitely be in v75. There is a workaround that has worked for us noted at: https://bugs.chromium.org/p/chromium/issues/detail?id=942023#c58 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title Jesse Glick updated JENKINS-51638 Fix merged in the 4.x trunk, and a 3.10.x backport is in preparation. Jenkins / JENKINS-51638 No Enum Constant Found - Default PreBuildMerge Failure Change By: Jesse Glick Status: In Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Radek Antoniuk resolved as Fixed Jenkins / JENKINS-25829 Proxy configuration does not work Change By: Radek Antoniuk Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Radek Antoniuk commented on JENKINS-25829 Re: Proxy configuration does not work Li Chang you can set the proxy host and port under Manage > Manage plugins > Advanced tab. If you still have issues when this is configured, please open a new bug report with possible stacktrace included, thanks! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57025) Unable to pull hooks in github organization folder type
Title: Message Title John Mellor commented on JENKINS-57025 Re: Unable to pull hooks in github organization folder type This used to work, but failed sometime in the last 6 months of plugin changes. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44524) Support adding JIRA sites on folder
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-44524 Support adding JIRA sites on folder Change By: Radek Antoniuk Issue Type: Task New Feature 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57025) Unable to pull hooks in github organization folder type
Title: Message Title John Mellor commented on JENKINS-57025 Re: Unable to pull hooks in github organization folder type Job discovery in a github organization folder works correctly. Discovery of the PR and other branches works as expected. Manual builds of these jobs also works as expected. However, the PR verification builds are not being triggered, and instead give the traceback about not being able to find a post-commit hook to download. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57025) Unable to pull hooks in github organization folder type
Title: Message Title John Mellor edited a comment on JENKINS-57025 Re: Unable to pull hooks in github organization folder type It would appear that projects with a dedicated config seem to work ok. However, projects that inherit their config from the parent organization folder always get it wrong, and the hook pulls fail. So, projects that directly have their own config.xml (multibranch builds, ad-hoc builds) function correctly, but github organization type do not. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57025) Unable to pull hooks in github organization folder type
Title: Message Title John Mellor updated an issue Jenkins / JENKINS-57025 Unable to pull hooks in github organization folder type Change By: John Mellor Summary: Unable to pull hooks in github user incorrectly constructed, org name being assumed organization folder type 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55982) JIRA Plugin does not respect proxy in some requests
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-55982 JIRA Plugin does not respect proxy in some requests Change By: Radek Antoniuk Labels: jira-plugin-3.0.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57192) Digester does try to resolve references
Title: Message Title Ulli Hafner updated JENKINS-57192 See https://github.com/jenkinsci/analysis-model/commit/be6000ff3221a847dc62f08f2903bcd19cbe129e Jenkins / JENKINS-57192 Digester does try to resolve references Change By: Ulli Hafner 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53808) Binary compatibility broken between JIRA plugin 3.0.2 and Artifactory plugin 2.16.2
Title: Message Title Radek Antoniuk updated JENKINS-53808 Jenkins / JENKINS-53808 Binary compatibility broken between JIRA plugin 3.0.2 and Artifactory plugin 2.16.2 Change By: Radek Antoniuk 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site
Title: Message Title
Robert Fults commented on JENKINS-47309
Re: Plugin || Confluence Publisher || Not working with confluence cloud site
Per Atlasssian support, SOAP API is deprecated as of April 14, 2019. https://blog.developer.atlassian.com/app-opt-in-api-migration/ This has caused the Confluence Publisher plugin to stop working with Confluence Cloud and is causing production issues for one of our major client projects as there are processes in place that depend on data that is being regularly published to their sites. There is another issue referencing this as well (https://issues.jenkins-ci.org/browse/JENKINS-56987). Jenkins Version: 2.86 Confluence Publisher Plugin version: 2.0.3 Giuliano Campos (Atlassian) advised he can be contacted for more details as needed. Full stack trace from error below: Failed to login AxisFault faultCode: {[http://schemas.xmlsoap.org/soap/envelope/]} Server.userException faultSubcode: faultString: com.atlassian.confluence.rpc.AuthenticationFailedException: Attempt to log in user failed. The maximum number of failed login attempts has been reached. Please log into the web application through the web interface to reset the number of failed login attempts. faultActor: faultNode: faultDetail: {}com.atlassian.confluence.rpc.AuthenticationFailedException:null {[http://xml.apache.org/axis/]} hostname:d7a74d906dd0 com.atlassian.confluence.rpc.AuthenticationFailedException: Attempt to log in user failed. The maximum number of failed login attempts has been reached. Please log into the web application through the web interface to reset the number of failed login attempts. 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 java.lang.Class.newInstance(Class.java:442) at org.apache.axis.encoding.ser.BeanDeserializer.(BeanDeserializer.java:104) at org.apache.axis.encoding.ser.BeanDeserializer.(BeanDeserializer.java:90) at jenkins.plugins.confluence.soap.v1.AuthenticationFailedException.getDeserializer(AuthenticationFailedException.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154) at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84) at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464) at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547) at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157) at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:351) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2784) at com.
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Steven Clark commented on JENKINS-54929 Re: Some final output is missing in Jenkins Pipeline when using the Ansible Plugin I've submitted a PR that addresses this issue at least for me (https://github.com/jenkinsci/ansible-plugin/pull/29).Hopefully someone could accept it and create a bugfix release with 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 Kindly retest with JCL ERR only with latest version. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Attachment: zos-connector-granular-rx.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. For more options, visit https://groups.google.com/d/optout.
