[JIRA] (JENKINS-55462) "shelve project" button missing for all non-admin users
Title: Message Title Pierre Beitz updated JENKINS-55462 Jenkins / JENKINS-55462 "shelve project" button missing for all non-admin users Change By: Pierre Beitz 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-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz started work on JENKINS-56181 Change By: Pierre Beitz 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-7004) cause not working in parameterized projects
Title: Message Title Colathur Vijayan commented on JENKINS-7004 Re: cause not working in parameterized projects My intent is to figure out if there is a way to monitor a job invocation accurately by either using the Queue ID returned as part of the Location and then retrieving the Build ID OR by passing a unique identifier to the Cause parameter. What I find weird is that when there is a Quiet period in effect neither the Queue ID nor the Cause parameter behave as expected. Please see the attached sample test harness and its output. There are 3 jobs invoked in parallel each a unique identifier for cause. This is is the outcome. A. First job gets a successful build, the other 2 don't (presumably because of the Quiet period). B. The First job is queryable through the Queue ID and the response does have the unique identifier passed in Cause. C. However the second and third invocations get a status of 201 and have the same Queue ID of the first, with the response having all the 3 causes. 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-7004) cause not working in parameterized projects
Title: Message Title Colathur Vijayan updated an issue Jenkins / JENKINS-7004 cause not working in parameterized projects Change By: Colathur Vijayan Attachment: jenkinstestharness.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7004) cause not working in parameterized projects
Title: Message Title Colathur Vijayan commented on JENKINS-7004 Re: cause not working in parameterized projects Should I open a new ticket or reopen this ticket ? 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-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz updated JENKINS-56181 Jenkins / JENKINS-56181 Shelve project plugin broken backward compatibility Change By: Pierre Beitz 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-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz commented on JENKINS-52781 Re: tar function is breaking symlinks Brian J Murrell Review is stalled, the changes are a bit touchy and would need to be reviewed/discussed with more people. PR is linked to the ticket: https://github.com/jenkinsci/jenkins/pull/3569 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-56495) build is completed
Title: Message Title divya katike created an issue Jenkins / JENKINS-56495 build is completed Issue Type: Task Assignee: divya katike Components: artifactory-plugin Created: 2019-03-10 10:18 Priority: Minor Reporter: divya katike 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-55971) SSH Host key matches, Authentication failed, Slaves failed to reconnect
Title: Message Title divya katike updated JENKINS-55971 Jenkins / JENKINS-55971 SSH Host key matches, Authentication failed, Slaves failed to reconnect Change By: divya katike Resolution: Duplicate Status: Resolved In 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-43610) Split Trilead out from Core
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / JENKINS-43610
Split Trilead out from Core
Change By:
Ivan Fernandez Calvo
Jenkins core currently bundles version 8 of the Jenkins fork of Trilead to provide SSH client functionality. Multiple plugins depend on this provision to utilize Trilead classes, so don't bundle Trilead directly. A new version of Trilead has recently been released containing a number of security enhancements (strong MAC algorithms, strong key exchange methods, curve based cryptographic keys etc), but this requires one of the following: # Jenkins core to update the bundled Trilead library. This means anyone using the weekly release from the point we include a new bundled library gets the new features, but users who only upgrade plugins or who are on an LTS release are stuck with an old Trilead version # Any plugin that wants hardened SSH capabilities bundles Trilead directly, but then potentially breaks functionality shared between plugins: SSH credentials uses `Class.isAssignableFrom` to check it can provide credentials, which stops this plugin working if the plugin needing credentials hasn't loaded Trilead from the same classloader (currently core).Since nothing in Jenkins core actually needs Trilead or the supporting classes that have been added to core for it, the logical change would be # Copy the Trilead library and supporting classes into a plugin # Update plugins that require Trilead so they depend on this new plugin # Remove Trilead from the core and bundle the new Trilead plugin as a detached pluginMore plugins will be added to the components list for this issue as investigation is performed into what plugins depend on Trilead. Some plugins may be updated to remove references to Trilead classes where they're only using utility methods from Trilead, such as Base64 methods and `IOUtils.closeQuitely`.Current changes required:||Component||Changes||PR Raised||PR Merged||Change Released|||Jenkins Core (Phase 1)| # Replace Trilead Base64 references with java.util.Base64 references (various classes) # Replace Trilead MD5 reference with MessageDigest.getInstance("MD5") (ConsistentHash.java)| No Yes | n/a Yes | n/a Yes ||Jenkins Core (Phase 2)| # Move SFTP client into Trilead plugin and remove from core # Update sshd-module and ssh-cli-module dependencies to latest version # Remove Trilead dependency from core # Set Trilead dependency in CLI project to 'optional' to prevent core visibility # Set Trilead API Plugin as a detached plugin| Yes| No| n/a No | n/a| |Token Macro Plugin|Remove unused import to com.trilead.ssh2.crypto.digest.MAC from JobDescriptionMacro|[Yes|https://github.com/jenkinsci/token-macro-plugin/pull/29]|Yes| No Yes ||SSHD Module| # Upgrade SSH CLI Module dependency to a new version (1.2 or above) # Remove direct references to Trilead classes, instead using SSH CLI Auth Module's key comparison functionality found in newer versions|[Yes|https://github.com/jenkinsci/ssh-cli-auth-module/pull/5]|No|No||SSH CLI Auth Module| # Replace referen
[JIRA] (JENKINS-56495) build is completed
Title: Message Title divya katike updated JENKINS-56495 Jenkins / JENKINS-56495 build is completed Change By: divya katike Status: Open Fixed but Unreleased Resolution: Done 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-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-55809 Missing Logout Url in SAML metadata XML for ADFS Change By: Ivan Fernandez Calvo Issue Type: Bug 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-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-55809 Missing Logout Url in SAML metadata XML for ADFS Change By: Ivan Fernandez Calvo Issue Type: Bug 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-55809) Missing Logout Url in SAML metadata XML for ADFS
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-55809 Re: Missing Logout Url in SAML metadata XML for ADFS I reviewed the code and the SingleLogoutService is never loaded from the IdP metadata, it is not implemented, so it is a new feature to implement. 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-56325) Device config is not enclosed between " " in multiConfig matrix job which fails the job
Title: Message Title Gaurav Dalal updated an issue Jenkins / JENKINS-56325 Device config is not enclosed between " " in multiConfig matrix job which fails the job Change By: Gaurav Dalal Component/s: android-emulator-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-56402) Declarative Pipeline shows SUCCESS even though job FAILED
Title: Message Title Christoph Amshoff commented on JENKINS-56402 Re: Declarative Pipeline shows SUCCESS even though job FAILED I've installed 1.3.7-beta-1 version of all four pipeline plugins (Pipeline: Declarative, Pipeline: Declarative Extension Points API, Pipeline: Model API and Pipeline: Stage Tags Metadata) and can confirm that it works! Status in post action is correcct now, mails are sent with proper status and Claims plugin's icon shows up again for unstable or failed builds. So, thanks for the fix! I really appreciate your efforts, and can imagine it's hard to fix this messy status implementation without breaking any functionality... 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-7004) cause not working in parameterized projects
Title: Message Title Daniel Beck commented on JENKINS-7004 Re: cause not working in parameterized projects The behavior described above is as designed, queue items are combined when they're considered identical, and causes combined as well. So if you pass the same build parameters (the Magic "cause" is not one of them) they will be combined. 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-56496) use blueocean tests results as pass/fail/unstable criteria
Title: Message Title Vlad Aginsky created an issue Jenkins / JENKINS-56496 use blueocean tests results as pass/fail/unstable criteria Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-03-10 13:01 Priority: Minor Reporter: Vlad Aginsky Hi, my use case: in blueocean there is very nice parser that summarizes new/still failed tets from xunit test results. I am aware that i can use xunit tresholds to set build color(red/yellow/green) but it will be better just to use blueocean "New failing" detection. is it possible? Add Comment
[JIRA] (JENKINS-55353) Upgrade Jenkins core to 2.121.3
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-55353 Upgrade Jenkins core to 2.121.3 Change By: Ivan Fernandez Calvo After tested the plugin to compile against different Jenkins core versions, I have detected some changes that I have to make to test it.* Update Jenkins file to compile an test on Jenkins core 2.121.3, 2.138.4, 2.150.1, and 2.156 (3 LTS and last weekly)* Compile and test weekly with JDK 11* Upgrade Jenkins core to 2.121.3, I will support 3 LTS versions* Remove JDKInstaler references, is not used in ssh-slaves and it is no longer in Jenkins core, it is in tool-jdk plugin* Remove deprecated constructors, all these constructors were marked with a warning in logs 6 months ago.* Remove unused code* Remove old fields related to deprecated constructors* Fix tests after changes * Remove deprecated package depencency javax.xml.bind 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-55353) Upgrade Jenkins core to 2.121.3
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-55353 Upgrade Jenkins core to 2.121.3 Change By: Ivan Fernandez Calvo After tested the plugin to compile against different Jenkins core versions, I have detected some changes that I have to make to test it.* Update Jenkins file to compile an test on Jenkins core 2. 121.3, 2. 138.4, 2.150. 1 4 , and 2. 156 164 ( 3 2 LTS and last weekly)* Compile and test weekly with JDK 11* Upgrade Jenkins core to 2. 121 138 . 3 4 , I will support 3 2 LTS versions* Remove JDKInstaler references, is not used in ssh-slaves and it is no longer in Jenkins core, it is in tool-jdk plugin* Remove deprecated constructors, all these constructors were marked with a warning in logs 6 months ago.* Remove unused code* Remove old fields related to deprecated constructors* Fix tests after changes* Remove deprecated package depencency javax.xml.bind 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 Guy Arad commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites Mark Waite it didn't resolved the issue for me. Blue Ocean 1.13.2 Autofavorite 1.2.3 Jenkins 2.150.3 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-56496) use blueocean tests results as pass/fail/unstable criteria
Title: Message Title Vlad Aginsky updated an issue Jenkins / JENKINS-56496 use blueocean tests results as pass/fail/unstable criteria Change By: Vlad Aginsky Attachment: image-2019-03-10-16-30-39-840.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56496) use blueocean tests results as pass/fail/unstable criteria
Title: Message Title Vlad Aginsky updated an issue Jenkins / JENKINS-56496 use blueocean tests results as pass/fail/unstable criteria Change By: Vlad Aginsky Hi, my use case:in blueocean there is very nice parser that summarizes new/still failed tets from xunit test results.I am aware that i can use xunit tresholds thresholds to set build color(red/yellow/green) but it will be better just to use blueocean "New failing" detection. i will illustrate:i have a build that ended with 7 new failed tests. there is some logic in blueocean that correctly detected all new faulures:!image-2019-03-10-16-30-39-840.png|width=740,height=211! I want to use this logic to set build result. is it possible? P.S: xunit parser is not sophisticated enough, and in this same build it reports:7 failures (+4) , 3 skipped (±0), It ignores the fact that some test got fixed and some new got broken, and while in total the number went up only by 4, but 7 new tests got broken. 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz updated JENKINS-55244 Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Change By: Pierre Beitz 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz updated JENKINS-55244 Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Change By: Pierre Beitz 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Change By: Pierre Beitz Labels: 2.3-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-20922) Progress bar links to nonexistant console
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-20922 Progress bar links to nonexistant console Change By: Pierre Beitz Labels: 2.3-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-20922) Progress bar links to nonexistant console
Title: Message Title Pierre Beitz updated JENKINS-20922 Jenkins / JENKINS-20922 Progress bar links to nonexistant console Change By: Pierre Beitz 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-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz updated JENKINS-55331 Jenkins / JENKINS-55331 Shelving fails if the optional Folder plugin is absent Change By: Pierre Beitz 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-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-55331 Shelving fails if the optional Folder plugin is absent Change By: Pierre Beitz Labels: 2.3-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-38417) chef-identity-plugin to support pipeline builds
Title: Message Title Tyler Fitch commented on JENKINS-38417 Re: chef-identity-plugin to support pipeline builds Hey everyone - the battle right now is that Jenkins and more so Java has moved forward leaving this plugin in the dust. For me, in its current state the project doesn't even build with Java 10. I'm trying to make some updates to the POM and if needed be the code to get the publish command to even work. My current error is [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 6.216 s [INFO] Finished at: 2019-03-10T16:15:15-07:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:javadoc (default) on project chef-identity: Execution default of goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:javadoc failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-javadoc-plugin:2.10.4:javadoc: java.lang.ExceptionInInitializerError: null [ERROR] - I've opened PR to see if I can get some help debugging the plugin from someone more regularly developing them. https://github.com/jenkinsci/chef-identity-plugin/pull/3 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://gr
[JIRA] (JENKINS-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum updated an issue Jenkins / JENKINS-56376 remoting kakfa plugin creates too many threads and takes too much cpu time Change By: Federico Naum Attachment: s-l640.jpg 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-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum updated an issue Jenkins / JENKINS-56376 remoting kakfa plugin creates too many threads and takes too much cpu time Change By: Federico Naum Attachment: s-l640.jpg 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-38417) chef-identity-plugin to support pipeline builds
Title: Message Title Tyler Fitch commented on JENKINS-38417 Re: chef-identity-plugin to support pipeline builds Okay, installed JDK 8 on my machine and I think I got it now and it's published as version 2.0.3 of the plugin. [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ chef-identity --- Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3.hpi Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3.hpi (21 kB at 17 kB/s) Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3.pom Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3.pom (3.5 kB at 3.4 kB/s) Downloading from maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/maven-metadata.xml Downloaded from maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/maven-metadata.xml (545 B at 2.8 kB/s) Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/maven-metadata.xml Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/maven-metadata.xml (497 B at 878 B/s) Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3.jar Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3.jar (21 kB at 33 kB/s) Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3-sources.jar Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3-sources.jar (17 kB at 27 kB/s) Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3-javadoc.jar Uploaded to maven.jenkins-ci.org: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/chef-identity/2.0.3/chef-identity-2.0.3-javadoc.jar (76 kB at 112 kB/s) [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 29.512 s [INFO] Finished at: 2019-03-10T17:44:37-07:00 [INFO]
[JIRA] (JENKINS-38417) chef-identity-plugin to support pipeline builds
Title: Message Title Tyler Fitch resolved as Fixed I see the plugin here: https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/chef-identity/2.0.3 Looking good, marking issue as fixed. Jenkins / JENKINS-38417 chef-identity-plugin to support pipeline builds Change By: Tyler Fitch Status: Open 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-38417) chef-identity-plugin to support pipeline builds
Title: Message Title Tyler Fitch resolved as Fixed I see the plugin here: https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/chef-identity/2.0.3 Looking good, marking issue as fixed. Jenkins / JENKINS-38417 chef-identity-plugin to support pipeline builds Change By: Tyler Fitch Status: Open 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-38417) chef-identity-plugin to support pipeline builds
Title: Message Title
Tyler Fitch commented on JENKINS-38417
Re: chef-identity-plugin to support pipeline builds
Also, if you're looking at the requested syntax in the ticket, this hasn't been solved this way but instead as described in the README.
node {
wrap([$class: 'ChefIdentityBuildWrapper', jobIdentity: 'my-chef']) {
sh 'knife node list -c .chef/knife.rb'
}
}
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-52024) Can't compile/test under Java 10/11 with mvn
Title: Message Title Mark Waite commented on JENKINS-52024 Re: Can't compile/test under Java 10/11 with mvn Solution in my case (and I believe the general case) to compile with Java 11 needs to use Jenkins version 2.164 or later (slightly older versions can compile with Java 11, Jenkins 2.150 cannot compile with Java 11). My command line to compile with Java 11 was: $ java -version openjdk version "11.0.2" 2019-01-15 OpenJDK Runtime Environment 18.9 (build 11.0.2+9) OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode) $ mvn --version Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T18:41:47Z) Maven home: /home/jagent/tools/apache-maven-3.6.0 Java version: 11.0.2, vendor: Oracle Corporation, runtime: /mnt/xvdba/home/jagent/tools/jdk-11.0.2 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "2.6.32-754.6.3.el6.x86_64", arch: "amd64", family: "unix" $ mvn -Djenkins.version=2.164 clean install 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-54072) extension point to write comments to SCM pull request
Title: Message Title Jean-Christophe Morin commented on JENKINS-54072 Re: extension point to write comments to SCM pull request Hi Jeremy Marshall, have you progressed on this? On my side I'd be interested into publishing comments to Bitbucket. Maybe we could join our forces to come up with working solution (if you don't have a working solution yet) ? When I look at your GitHub profile, I see that you already started (https://github.com/JeremyMarshall/warnings-ng-plugin/tree/extension and https://github.com/JeremyMarshall/github-violations-warnings-plugin). Would you be up for some collaboration on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56482) custom name variable seems to not working
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-56482 custom name variable seems to not working Change By: Jie Shen Assignee: Azure DevOps Jie Shen 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-56482) custom name variable seems to not working
Title: Message Title Jie Shen commented on JENKINS-56482 Re: custom name variable seems to not working Hi Omega BK, how do you set back Environment variables in Jenkins before? You current problem is that you cannot fetch the variables in the withCredentials block? 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-56386) File handles are not release by java process after running OWASP Dependency-Check Plugin
Title: Message Title Steve Springett commented on JENKINS-56386 Re: File handles are not release by java process after running OWASP Dependency-Check Plugin This is a common problem with Windows. Nothing I can do to fix. There are a lot of workarounds for this type of behavior including disabling Windows services that read recently modified files (Windows search, anti-virus, etc). Since the Jenkins plugin doesn't actually have code that performs scanning, workarounds would need to be implemented in the Dependency-Check core module. 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-56386) File handles are not release by java process after running OWASP Dependency-Check Plugin
Title: Message Title Steve Springett closed an issue as Won't Fix Jenkins / JENKINS-56386 File handles are not release by java process after running OWASP Dependency-Check Plugin Change By: Steve Springett 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-55935) adding template without credentials results in multiple devil pages
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-55935 adding template without credentials results in multiple devil pages Change By: Jie Shen Status: In Progress Resolved Resolution: Fixed Released As: 0.9.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-56482) custom name variable seems to not working
Title: Message Title Azure DevOps started work on JENKINS-56482 Change By: Azure DevOps 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-53182) Uncaught TypeError: Cannot read property 'firstChild' of undefined
Title: Message Title fei wang commented on JENKINS-53182 Re: Uncaught TypeError: Cannot read property 'firstChild' of undefined I also have the same issue, my jenkins is installed on centos 6 with version 2.150.3 and java 8. when I open a maven project after a new creation, the issue came out. 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-36798) Status icon for specific build in queue
Title: Message Title Renato Chencinski commented on JENKINS-36798 Re: Status icon for specific build in queue Thanks Thomas Döring. How should I do to display a "Queued" badge while build is queued, and have it automatically change to Running and Success/Failed once it's finished? Cheers 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-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum updated an issue Jenkins / JENKINS-56376 remoting kakfa plugin creates too many threads and takes too much cpu time Change By: Federico Naum Attachment: ChannelReaderThreads_prouction_instance.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum updated an issue Jenkins / JENKINS-56376 remoting kakfa plugin creates too many threads and takes too much cpu time Change By: Federico Naum Attachment: HighCPUUsage_test_instance.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum updated an issue Jenkins / JENKINS-56376 remoting kakfa plugin creates too many threads and takes too much cpu time Change By: Federico Naum Attachment: ChannelReaderThreads_test_instance.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum updated an issue Jenkins / JENKINS-56376 remoting kakfa plugin creates too many threads and takes too much cpu time Change By: Federico Naum Attachment: HighCPUUsage_production_instance.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56376) remoting kakfa plugin creates too many threads and takes too much cpu time
Title: Message Title Federico Naum updated an issue Jenkins / JENKINS-56376 remoting kakfa plugin creates too many threads and takes too much cpu time Change By: Federico Naum Attachment: ProducerThreads_test_instance_900_threads.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53067) Android App Bundle upload support
Title: Message Title Praveen Kumar commented on JENKINS-53067 Re: Android App Bundle upload support Hello. Any time-frame to have this please? I'm really waiting for this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55939) git-plugin v4.0.0-rc not returning "lastBuiltRevision" in BuildData
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-55939 git-plugin v4.0.0-rc not returning "lastBuiltRevision" in BuildData Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56257) Git clone/fetch filtering user:password from git https://user:pwd@path-2-git
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-56257 Git clone/fetch filtering user:password from git https://user:pwd@path-2-git Change By: Mark Waite Component/s: git-client-plugin Component/s: git-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-56257) Git clone/fetch filtering user:password from git https://user:pwd@path-2-git
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56257 Git clone/fetch filtering user:password from git https://user:pwd@path-2-git Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56359) Unable to load http://localhost:8080/ from my system,
Title: Message Title Mark Waite updated JENKINS-56359 Jenkins / JENKINS-56359 Unable to load http://localhost:8080/ from my system, Change By: Mark Waite Status: Fixed but Unreleased Closed 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-56359) Unable to load http://localhost:8080/ from my system,
Title: Message Title Mark Waite updated JENKINS-56359 Insufficient information to understand if there is a bug or not. Jenkins / JENKINS-56359 Unable to load http://localhost:8080/ from my system, Change By: Mark Waite Status: Open Fixed but Unreleased 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-7004) cause not working in parameterized projects
Title: Message Title Colathur Vijayan commented on JENKINS-7004 Re: cause not working in parameterized projects In the above case when the queue items are combined is there any way to know that they are combined from the response when tehy are invoked ? All of them return the same http status code of 201, so for sure this doesn't help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56311) github-coverage-reporter-plugin missing pipeline instructions
Title: Message Title Idan Adar commented on JENKINS-56311 Re: github-coverage-reporter-plugin missing pipeline instructions Jack Newcombe would love to help with the documentation, but for that to happen I need to know if it is at all possible to use this plug-in in a Pipeline. What is the Step that needs to be added into the Jenkinsfile? 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-7004) cause not working in parameterized projects
Title: Message Title Colathur Vijayan edited a comment on JENKINS-7004 Re: cause not working in parameterized projects In the above case when the queue items are combined is there any way to know that they are combined from the response when tehy are invoked ? All of them return the same a http status code of 201 (= Resource Created) , so for sure this doesn't help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7004) cause not working in parameterized projects
Title: Message Title Colathur Vijayan edited a comment on JENKINS-7004 Re: cause not working in parameterized projects In the above case when the queue items are combined is there any way to know that they are combined from the response when tehy they are invoked ? All of them return a http status code of 201 (= Resource Created), so for sure this doesn't help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52292) Support Multiple Vault IDs
Title: Message Title Marek Vesely commented on JENKINS-52292 Re: Support Multiple Vault IDs +1 for this 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-52292) Support Multiple Vault IDs
Title: Message Title Marek Vesely updated an issue Jenkins / JENKINS-52292 Support Multiple Vault IDs Change By: Marek Vesely Priority: Minor Major 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-56392) blue-ocean links from classic do not use https
Title: Message Title Björn Pedersen commented on JENKINS-56392 Re: blue-ocean links from classic do not use https Even so with setting the proxy header to https explicitly the request will use https, it still fails with a 404. Note that the redirect actually happens inside jenkins (server: jetty), not on the apache side. It seems like adding a slash at the end of the URL actually will load the right page, maybe that is the missing part. (I still consider relying on the incoming request headers to determine the host/protocol a security flaw, absolute urls should always use the configured Jenkins URL independent from the incoming request). Can you point me to the code where these urls are compute, then I'll try to find a patch for 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-56453) git command line fails with http 502
Title: Message Title Carsten Hilber commented on JENKINS-56453 Re: git command line fails with http 502 Hi Mark, thanks for your answer. I have checked most of the things that you are suggesting, let me file what I did so far by answering the questions: Is the server actually speaking HTTP on port 7990 or is it https? > http. there is no https configured on bitbucket Is there a proxy server between the Jenkins agent and the Bitbucket server? > There is a proxy configured, but the server is on the ignore proxy list. Is that proxy server configured in Jenkins the same as it is in your shell? > It is configured the same Does the agent have any surprising or different text in the .gitconfig file for the user that runs the agent? > I checked the git config because I found quite some issues with GIT_ASKPASS when hunting down the issue, but there is nothing special configured, only https_verify=false Is there a different version of curl installed on the agent than on your computer where the clone works? > No, it is the same box where I ran success with command line and unsuccess with a job. Are there relevant differences in values of the environment variables between the working case and the failing case? > The only difference I came across is that Jenkins is using git_askpass from the tmp dir to do the authentication on Bitbucket. I don't really know how to test this scenario from the command line. Does ssh private key based clone work with command line git from the Bitbucket server? > ssh is disabled for bitbucket. There are two things that look suspicious to me: 1. Why is the request from bitbucket taking 6 Minutes and then answers with 502? Bitbucket didn't even log an access. 2. When I change the used git implementation from command line to jgit, it works. Do you still think this is a local configuration thing? Could this also be realted to a bug with git_askpass? Thanks in advance Carsten
