[JIRA] (JENKINS-55987) Use of when buildingTag does not work in Declarative pipeline
Title: Message Title Krzysztof Malinowski commented on JENKINS-55987 Re: Use of when buildingTag does not work in Declarative pipeline Technically this condition checks for existence of environment variable called TAG_NAME. This is normally contributed by Branch API, for multibranch approach. If you don't use multibranching, you can try to populate TAG_NAME yourself before the condition, or just rework the condition. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197402.1549442533000.1454.1575550800391%40Atlassian.JIRA.
[JIRA] (JENKINS-55987) Use of when buildingTag does not work in Declarative pipeline
Title: Message Title Krzysztof Malinowski commented on JENKINS-55987 Re: Use of when buildingTag does not work in Declarative pipeline Attached log misses the important output of actual cloning so it's impossible to verify, but most times it's because you are not actually building a tag. You need to check out the tag (i.e. by starting build from the Tags tab of a multibranch pipeline) to make those conditions work. It is not enough to just build a commit that happens to have tags applied. Make sure that the Checking out Revision line (not included in attached output) lists a tag, not a branch. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197402.1549442533000.1365.1575541620271%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Krzysztof Malinowski commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data I got that. But plugins may have or may have not used them, as there was no possibility to declare. If core will keep reinstantiating them, we will never be able to get rid of this functionality which was unused. For instance, I may be using Green Balls that only changes icon colors, but it incorporates 14 implied plugins. I am pretty sure it does not use LDAP, JDK installer or Windows agents, yet they keep getting installed, because of the time that the plugin was released, they were part of Jenkins. I don't see any point in re-releasing the plugin or upgrading core requirements as the functionality is quite simple and seems complete, so there is no point in artificial release. I would like to get rid of the functionality I don't need though to reduce the bloat, but the core does not want to let it go. I really believe it should be maintained by people maintaining their Docker images. At least there should be an option I could set to say: 'Yes, I know what I'm doing, thank you.' Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3088.1568379240349%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Krzysztof Malinowski commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Even when disabled, these are still installed and report security issues. As a workaround I am deleting WEB-INF/detached-plugins from jenkins.war, but I believe it should be at least controllable by some property so that one can consciously opt out of that functionality. Apart from that, what's the point of separating functionality into plugins, when the same functionality is injected (in an outdated version) anyway? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.2981.1568376060552%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Krzysztof Malinowski commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Is it possible to somehow skip or remove this behavior? We do not use any of those detached plugins and they keep being instantiated (in rather ancient versions) at service startup. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.8891.1568019360368%40Atlassian.JIRA.
[JIRA] (JENKINS-57516) Bitbucket branch source does not support tag notification
Title: Message Title Krzysztof Malinowski commented on JENKINS-57516 Re: Bitbucket branch source does not support tag notification This is Bitbucket Server 5.12.2. It looks like it falls into check for BRANCH ref change, while the actual notification had a TAG here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199419.1558086229000.16076.1559162820133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57516) Native implementation does not support tag notification
Title: Message Title Krzysztof Malinowski created an issue Jenkins / JENKINS-57516 Native implementation does not support tag notification Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-05-17 09:43 Environment: Jenkins 2.138.2, Bitbucket Branch Source Plugin 2.4.4 Priority: Minor Reporter: Krzysztof Malinowski Upon receipt of Bitbucket native webhook notification no project scan is triggered and the log says: May 17, 2019 9:11:55 AM INFO com.cloudbees.jenkins.plugins.bitbucket.hooks.NativeServerPushHookProcessor$HeadEvent addBranches Received event for unknown ref type TAG of ref TEST_TAG Please add support for tag notifications. Add Comment
[JIRA] (JENKINS-53924) Jenkins 2.136+ is not restartable with GLIBC 2.5
Title: Message Title Krzysztof Malinowski created an issue Jenkins / JENKINS-53924 Jenkins 2.136+ is not restartable with GLIBC 2.5 Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-05 15:20 Environment: Red Hat Enterprise Linux Server release 5.11 (Tikanga) java version "1.8.0_181" Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) Priority: Minor Reporter: Krzysztof Malinowski When Jenkins 2.136 (or newer) starts up, the log lists problem with loading libc library for com.sun.akuma.CLibrary: Oct 05, 2018 4:08:34 PM jenkins.diagnosis.HsErrPidList WARNING: Failed to list up hs_err_pid files java.lang.UnsatisfiedLinkError: /tmp/jna-578977101/jna607378441395487448.tmp: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by /tmp/jna-578977101/jna607378441395487448.tmp) at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1824) at java.lang.Runtime.load0(Runtime.java:809) at java.lang.System.load(System.java:1086) at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:947) at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:922) at com.sun.jna.Native.(Native.java:190) at com.sun.akuma.CLibrary.(CLibrary.java:89) at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:128) at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:116) at com.
