[JIRA] (JENKINS-60535) Getting IOException when Jenkins is trying to connect to Slaves in Azure Cloud
Title: Message Title anil dugar commented on JENKINS-60535 Re: Getting IOException when Jenkins is trying to connect to Slaves in Azure Cloud Thanks Jie, we are also working on an optimistic solution of having a retry logic, hopefully that will work and also we will have a loot at the above mentioned feature. 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.203638.1576734671000.8576.1581578520202%40Atlassian.JIRA.
[JIRA] (JENKINS-60708) Only one cause is shown in list view
Title: Message Title Pekka Mäki-Asiala commented on JENKINS-60708 Re: Only one cause is shown in list view In case "someone" is using plugin with jenkins jobs executing automated tests to gather statistics on test failure causes it would be extremely beneficial to be able to list all failure causes (defined in the Failure Cause Management section). 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.203955.1578559543000.8573.1581578460250%40Atlassian.JIRA.
[JIRA] (JENKINS-54445) Add more common tags for all measurements
Title: Message Title Aleksi Simell updated JENKINS-54445 Jenkins / JENKINS-54445 Add more common tags for all measurements Change By: Aleksi Simell Status: Fixed but Unreleased Closed Released As: 2.1 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.195207.1541406402000.8567.1581573600453%40Atlassian.JIRA.
[JIRA] (JENKINS-49343) Version 1.0.5 fails to test unit test assemblies specified with a relative path
Title: Message Title sharath Kumar edited a comment on JENKINS-49343 Re: Version 1.0.5 fails to test unit test assemblies specified with a relative path This is the Is this issue fixed? I thought of using workaround but how to we create logger.trx and use the post-build publish to create a report, can someone guild me 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.188207.1517570683000.8563.1581573360222%40Atlassian.JIRA.
[JIRA] (JENKINS-49343) Version 1.0.5 fails to test unit test assemblies specified with a relative path
Title: Message Title sharath Kumar commented on JENKINS-49343 Re: Version 1.0.5 fails to test unit test assemblies specified with a relative path This is the issue fixed? I thought of using workaround but how to we create logger.trx and use the post-build publish to create a report, can someone guild me 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.188207.1517570683000.8555.1581573300174%40Atlassian.JIRA.
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror / . This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround. It is mentioned in the release note that Stackoverlflow issue is solved in https://github.com/microsoft/team-explorer-everywhere/releases/tag/v14.0.3. If we have a look at [the source code of the SDK|https://github.com/microsoft/team-explorer-everywhere/blob/releases/14.0.3/source/com.microsoft.tfs.core/src/com/microsoft/tfs/core/TFSTeamProjectCollection.java#L261-L276]) however, the TFSConfigurationServer is closed after the TFSTeamProjectCollection and (while the workaround is to close it before).We can see that the TFS plugin [does already this in a way|https://github.com/jenkinsci/tfs-plugin/blob/tfs-5.157.0/tfs/src/main/java/hudson/plugins/tfs/model/Server.java#L274-L290]. But there is some legacy code using reflection that could be cleaned up. Proposed https://github.com/jenkinsci/tfs-plugin/pull/230 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
[JIRA] (JENKINS-61074) Allow Git plugin to give variable branch specifiers along with other hardcoded branch specifiers.
Title: Message Title Akashdeep Thakur updated an issue Jenkins / JENKINS-61074 Allow Git plugin to give variable branch specifiers along with other hardcoded branch specifiers. Change By: Akashdeep Thakur Priority: Minor Major 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.204564.1581565527000.8540.1581566220226%40Atlassian.JIRA.
[JIRA] (JENKINS-61074) Allow Git plugin to give variable branch specifiers along with other hardcoded branch specifiers.
Title: Message Title
Akashdeep Thakur created an issue
Jenkins / JENKINS-61074
Allow Git plugin to give variable branch specifiers along with other hardcoded branch specifiers.
Issue Type:
Task
Assignee:
Mark Waite
Attachments:
issue.png
Components:
git-plugin
Created:
2020-02-13 03:45
Labels:
git-plugin
Priority:
Minor
Reporter:
Akashdeep Thakur
I have provided branch specifiers as shown in the attached image. If I remove the branch specifier with $BRANCH in it, job works perfectly(gets triggered) as anyone commits to develop or feature branches. Now I also want that same job should also be able to build the project on any specific branch of choice. So I added a branch specifier and put $BRANCH in it. I have defined BRANCH as a string parameter and the user can give branch value as input when triggering the job manually. But in this scenario even if the user gives a "bugfix112" job is still building develop branch. Or if earlier poll action had built the job on feature branch than even after providing user-input, the job will still build feature branch. It seems like manual input has no effect. How can I configure a Jenkins job that can be triggered on poll SCM and also with user input for the branch parameter? I also tried giving /$BRANCH,/${BRANCH} but no success.
[JIRA] (JENKINS-61073) SMTP authentication details not stored properly
Title: Message Title D P created an issue Jenkins / JENKINS-61073 SMTP authentication details not stored properly Issue Type: Bug Assignee: Adrien Lecharpentier Components: mailer-plugin Created: 2020-02-13 02:59 Priority: Major Reporter: D P I'm trying to setup the email notification in Jenkins to create an alert when a build has failed. I am using Jenkins 2.204.2 and mailer plugin 1.30 I have tried with AWS and Gmail authentication. I encounter exactly the same problem on both. In both cases after I've entered all of my SMTP server details I am able to successfully send a test email. I receive the test email externally as well. If I click apply and then test configuration I still get "Email was successfully sent" However when I click "Save" and then go back to "Manage Jenkins" -> "Configure System" and "Test configuration by sending test e-mail" when I send a test email I get the following error: "Failed to send out e-mail javax.mail.AuthenticationFailedException: 535-5.7.8 Username and Password not accepted. Learn more at 535 5.7.8 https://support.google.com/mail/?p=BadCredentials r8sm514463pjo.22 - gsmtp" or "Failed to send out e-mail javax.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid at com.sun.mail.smtp.SMTPTransport$Authenticator.authenticate(SMTPTransport.java:809) at com.sun.mail.smtp.SMTPTransport.authenticate(SMTPTransport.java:752) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:669)" Additionally what concerns me is whenever I go to the configure page of jenkins it shows the notepad with a pen icon indicating that "One or more fields in this block have been edited". But that is without any edits having been made from my side? I've managed to get it working using gmail's SMTP, but in order to get it working I have to "save" the password when I receive a chrome "would you like to update your password" popup. This password popup should be in relation to my login details for the site, and not for the SMTP log
[JIRA] (JENKINS-60923) Add an option to disable Bitbucket multibranch project.
Title: Message Title Daniel Kjellin closed an issue as Not A Defect Jenkins / JENKINS-60923 Add an option to disable Bitbucket multibranch project. Change By: Daniel Kjellin Status: Open Closed Resolution: Not A Defect 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.204320.1580398726000.8534.1581562260320%40Atlassian.JIRA.
[JIRA] (JENKINS-60923) Add an option to disable Bitbucket multibranch project.
Title: Message Title Daniel Kjellin commented on JENKINS-60923 Re: Add an option to disable Bitbucket multibranch project. Hello Vitaliy Khrystyuk That is not part of this plugin, it comes from the Bitbucket branch source plugin (https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/ ). So if you want that disabled on your instance you can uninstall or disable the Bitbucket branch source plugin. 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.204320.1580398726000.8532.1581562260290%40Atlassian.JIRA.
[JIRA] (JENKINS-60967) Webhook in Bitbucket not being removed on trigger removal or job deletion
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-60967 Webhook in Bitbucket not being removed on trigger removal or job deletion Change By: Daniel Kjellin Assignee: Kristy Hughes 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.204430.1580885674000.8488.1581562141428%40Atlassian.JIRA.
[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-60392 Allow environment variables with Bitbucket Server Integration Pipeline Change By: Daniel Kjellin Assignee: Kristy Hughes 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.203446.157565559.8493.1581562141596%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-60492 Connection with Bitbucket server over SSH Change By: Daniel Kjellin Assignee: Kristy Hughes 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.203581.1576452688000.8527.1581562142035%40Atlassian.JIRA.
[JIRA] (JENKINS-60341) Allow configuring the plugin to use Jenkins domain credentials
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-60341 Allow configuring the plugin to use Jenkins domain credentials Change By: Daniel Kjellin Assignee: Kristy Hughes 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.203355.1575283635000.8502.1581562141746%40Atlassian.JIRA.
[JIRA] (JENKINS-60342) Include support to BitBucket Pull Request
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-60342 Include support to BitBucket Pull Request Change By: Daniel Kjellin Assignee: Kristy Hughes 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.203356.157528517.8514.1581562141878%40Atlassian.JIRA.
[JIRA] (JENKINS-60491) Use credentials from project's storage
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-60491 Use credentials from project's storage Change By: Daniel Kjellin Assignee: Kristy Hughes 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.203580.157645255.8524.1581562141990%40Atlassian.JIRA.
[JIRA] (JENKINS-60340) BitBucket payload information is not injected in the Jenkins build
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-60340 BitBucket payload information is not injected in the Jenkins build Change By: Daniel Kjellin Assignee: Kristy Hughes 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.203354.1575283232000.8520.1581562141943%40Atlassian.JIRA.
[JIRA] (JENKINS-60923) Add an option to disable Bitbucket multibranch project.
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-60923 Add an option to disable Bitbucket multibranch project. Change By: Daniel Kjellin Assignee: Kristy Hughes 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.204320.1580398726000.8496.1581562141668%40Atlassian.JIRA.
[JIRA] (JENKINS-61072) Kubernetes declarative pipeline does not merge initContainer sections
Title: Message Title
Stephane Odul updated an issue
Jenkins / JENKINS-61072
Kubernetes declarative pipeline does not merge initContainer sections
Change By:
Stephane Odul
We use declarative pipelines with ` {{ yamlMergeStrategy merge() ` }} and a yaml entry. Some of the YAMLs have an `initContainers` {{initContainer}} section that is preserved when we do not set the merge strategy but get dropped from the final yaml when we do set the strategy to ` {{ merge() ` }} .[https://kubernetes.io/docs/concepts/workloads/pods/init-containers/] For reference the {{merge()}} option was added to the declarative pipeline in https://github.com/jenkinsci/kubernetes-plugin/pull/638
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 t
[JIRA] (JENKINS-61072) Kubernetes declarative pipeline does not merge initContainer sections
Title: Message Title Stephane Odul created an issue Jenkins / JENKINS-61072 Kubernetes declarative pipeline does not merge initContainer sections Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-02-13 01:47 Environment: kubernetes:1.23.1 Priority: Major Reporter: Stephane Odul We use declarative pipelines with `yamlMergeStrategy merge()` and a yaml entry. Some of the YAMLs have an `initContainers` section that is preserved when we do not set the merge strategy but get dropped from the final yaml when we do set the strategy to `merge()`. https://kubernetes.io/docs/concepts/workloads/pods/init-containers/ Add Comment
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Owen Mehegan commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen Kellie Jos leah antkiewicz Brian Benz I just wanted to ping a few of you since you all seem to be recent contributors to this plugin. At CloudBees, we have a couple of customers who have been affected by the issue described here, and they are forced to restart Jenkins regularly to work around it. We have proposed this PR as a possible solution: https://github.com/jenkinsci/tfs-plugin/pull/230 If there is anything else we can do to work with you on this, please let us know! 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.189378.1521699501000.8481.1581557160634%40Atlassian.JIRA.
[JIRA] (JENKINS-61071) Dynamic loading of @Initializer runs as anonymous user
Title: Message Title Jesse Glick updated JENKINS-61071 Jenkins / JENKINS-61071 Dynamic loading of @Initializer runs as anonymous user Change By: Jesse Glick Status: In Progress Review 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.204561.1581554646000.8468.158140090%40Atlassian.JIRA.
[JIRA] (JENKINS-61071) Dynamic loading of @Initializer runs as anonymous user
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-61071 Dynamic loading of @Initializer runs as anonymous user Issue Type: Bug Assignee: Jesse Glick Components: core Created: 2020-02-13 00:44 Labels: regression lts-candidate Priority: Major Reporter: Jesse Glick Similarly to JENKINS-59775, if a plugin requires permissions in an @Initializer it will fail during dynamic loading in batch mode. Was not covered by previous fix because InitReactorRunner starts separate threads. Add Comment
[JIRA] (JENKINS-61071) Dynamic loading of @Initializer runs as anonymous user
Title: Message Title Jesse Glick started work on JENKINS-61071 Change By: Jesse Glick Status: Open In Progress 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.204561.1581554646000.8467.1581554700231%40Atlassian.JIRA.
[JIRA] (JENKINS-61070) Robot framework publishes red for successful result
Title: Message Title Dennis Chang created an issue Jenkins / JENKINS-61070 Robot framework publishes red for successful result Issue Type: Improvement Assignee: jpiironen Attachments: 179512_robot_column_jelly.png, 179512_robot_v1.6.5.png, 179512_robot_v2.0.1.png Components: robot-plugin Created: 2020-02-13 00:02 Labels: user-experience plugin Priority: Minor Reporter: Dennis Chang See screenshots. Version 1.6.5 did not colour the output. Version 2.0.1 prints a background of red (suggesting that a test result failed). Add Comment
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title John Lengeling commented on JENKINS-52842 Re: xUnit plugin blocks PingThread responses Other than the 1 hung job soon after I loaded xunit-2.3.8-rc831.cbb77af6dfed, the issue looks to be improved. The test job has been running hourly for the past 2 days with 0 hangs versus several hangs per day with 2.3.7. So you might be on the right track. I did also increase the ping thread interval and timeout values to 1500/1200, but I have now restored the ping thread interval/timeout values back to the defaults (300/240). I will let that bake for a few days. 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.192770.1533150138000.8459.1581549060178%40Atlassian.JIRA.
[JIRA] (JENKINS-59487) Startup Trigger doesnt execute jobs in master
Title: Message Title Emory Penney commented on JENKINS-59487 Re: Startup Trigger doesnt execute jobs in master I just installed job-dsl 1.76 on my box and am unable to reproduce this issue. Is this still a problem or has it resolved itself? If it's still a problem it may be a compatibility issue with jenknis-slim which I'm unfamiliar with. 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.202102.1569250479000.8383.1581547980604%40Atlassian.JIRA.
[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Mark Waite commented on JENKINS-55972 Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Gitlab blocking your account is not something that Jenkins or command line git can fix. 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.197383.1549364479000.8338.1581547860757%40Atlassian.JIRA.
[JIRA] (JENKINS-58886) Project base security matrix allows wrong group of users access
Title: Message Title Daniel Beck commented on JENKINS-58886 Re: Project base security matrix allows wrong group of users access Steve Todorov Is this still a problem? My best guess is something is weird about the group memberships, and I would have affected users go to the /whoAmI URL to see what groups they're a member of. 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.201219.1565517127000.8334.1581546240519%40Atlassian.JIRA.
[JIRA] (JENKINS-58538) Support for relative paths in folder view
Title: Message Title Ulli Hafner updated JENKINS-58538 Jenkins / JENKINS-58538 Support for relative paths in folder view Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed 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.200687.1563409751000.8321.1581544980699%40Atlassian.JIRA.
[JIRA] (JENKINS-57556) Path should be stored relative to workspace
Title: Message Title Ulli Hafner updated JENKINS-57556 Jenkins / JENKINS-57556 Path should be stored relative to workspace Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed 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.199467.1558350085000.8322.1581544980723%40Atlassian.JIRA.
[JIRA] (JENKINS-60697) readTrusted does not honor the refspec on Pipeline script from SCM GIT
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60697 readTrusted does not honor the refspec on Pipeline script from SCM GIT Change By: Mark Waite Component/s: workflow-multibranch-plugin Component/s: git-plugin 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.203942.1578497001000.8318.1581544080217%40Atlassian.JIRA.
[JIRA] (JENKINS-60875) branch index scan of multibranch pipeline job fails with GitException on old CLI git (1.8.3)
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60875 branch index scan of multibranch pipeline job fails with GitException on old CLI git (1.8.3) Change By: Mark Waite Summary: branch index scan of multibranch pipeline job fails with hudson.plugins. GitException on old CLI git (1 . GitException 8.3) 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.204257.1580131843000.8316.1581543960153%40Atlassian.JIRA.
[JIRA] (JENKINS-61069) After updating the 'Dependency Graph Viewer' plugin, Jenkins gui would not launch and only listed errors
Title: Message Title TK Asberry updated an issue Jenkins / JENKINS-61069 After updating the 'Dependency Graph Viewer' plugin, Jenkins gui would not launch and only listed errors Change By: TK Asberry Summary: fter After updating the 'Dependency Graph Viewer' plugin, Jenkins gui would not launch and only listed errors 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.204558.1581543548000.8314.1581543780144%40Atlassian.JIRA.
[JIRA] (JENKINS-61069) fter updating the 'Dependency Graph Viewer' plugin, Jenkins gui would not launch and only listed errors
Title: Message Title TK Asberry created an issue Jenkins / JENKINS-61069 fter updating the 'Dependency Graph Viewer' plugin, Jenkins gui would not launch and only listed errors Issue Type: Bug Assignee: Guido Grazioli Components: depgraph-view-plugin Created: 2020-02-12 21:39 Environment: Jenkins 2.204.2 Plugin: Dependency Graph Viewer 0.15 and 1.0.0 Windows Chrome Priority: Major Reporter: TK Asberry After updating the 'Dependency Graph Viewer' plugin, Jenkins gui would not launch and only listed errors. I had to manually replace the 'depgraph-view.jpi' with the previous version (0.13) to get the gui to launch. Add Comment
[JIRA] (JENKINS-61067) Wrong value for GIT_COMMIT after merge?
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61067 Wrong value for GIT_COMMIT after merge? Change By: Mark Waite Labels: newbie-friendly 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.204551.1581508949000.8310.1581543180291%40Atlassian.JIRA.
[JIRA] (JENKINS-61067) Wrong value for GIT_COMMIT after merge?
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61067 Wrong value for GIT_COMMIT after merge? Change By: Mark Waite Assignee: Mark Waite 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.204551.1581508949000.8308.1581543180223%40Atlassian.JIRA.
[JIRA] (JENKINS-61065) Git plugin: infinite build trigger by "SCM change"
Title: Message Title Mark Waite updated JENKINS-61065 Jenkins / JENKINS-61065 Git plugin: infinite build trigger by "SCM change" Change By: Mark Waite Status: In Review Fixed but Unreleased Resolution: Fixed 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.204548.1581498096000.8306.1581543060249%40Atlassian.JIRA.
[JIRA] (JENKINS-61065) Git plugin: infinite build trigger by "SCM change"
Title: Message Title Mark Waite started work on JENKINS-61065 Change By: Mark Waite Status: Open In Progress 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.204548.1581498096000.8302.1581543000303%40Atlassian.JIRA.
[JIRA] (JENKINS-61065) Git plugin: infinite build trigger by "SCM change"
Title: Message Title Mark Waite updated JENKINS-61065 Jenkins / JENKINS-61065 Git plugin: infinite build trigger by "SCM change" Change By: Mark Waite Status: In Progress Review 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.204548.1581498096000.8304.1581543000433%40Atlassian.JIRA.
[JIRA] (JENKINS-61065) Git plugin: infinite build trigger by "SCM change"
Title: Message Title Mark Waite commented on JENKINS-61065 Re: Git plugin: infinite build trigger by "SCM change" Pull request 829 has been merged for the next release of the git plugin. Jobs may optionally choose to ignore multiple candidate revisions. You're welcome to test the latest git plugin build to confirm that change allows you to disable checks for multiple candidate versions. You'll need to download the ".hpi" file from that list of artifacts. 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.204548.1581498096000.8300.1581542940159%40Atlassian.JIRA.
[JIRA] (JENKINS-46988) String.eachLine only reads first line
Title: Message Title Dominique Thornton commented on JENKINS-46988 Re: String.eachLine only reads first line Likewise. Just burned a bit of time on this. Moving to the workaround. 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.185366.1505906799000.8283.1581541380510%40Atlassian.JIRA.
[JIRA] (JENKINS-60856) Breakpad Symbols are not uploaded properly
Title: Message Title Mez Pahlan updated JENKINS-60856 Jenkins / JENKINS-60856 Breakpad Symbols are not uploaded properly Change By: Mez Pahlan Status: In Progress Review 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.204230.157986024.8278.1581541140474%40Atlassian.JIRA.
[JIRA] (JENKINS-60856) Breakpad Symbols are not uploaded properly
Title: Message Title Mez Pahlan updated JENKINS-60856 Jenkins / JENKINS-60856 Breakpad Symbols are not uploaded properly Change By: Mez Pahlan Status: In Review Fixed but Unreleased Resolution: Fixed 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.204230.157986024.8280.1581541140500%40Atlassian.JIRA.
[JIRA] (JENKINS-60856) Breakpad Symbols are not uploaded properly
Title: Message Title Mez Pahlan commented on JENKINS-60856 Re: Breakpad Symbols are not uploaded properly I'm going to move this along and release it. Feel free to raise a new issue if you need. Many thanks for reporting. 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.204230.157986024.8276.1581540660180%40Atlassian.JIRA.
[JIRA] (JENKINS-61058) Checkstyle, PMD and CPD publishers missing after plugin updates
Title: Message Title
Jason Wolf commented on JENKINS-61058
Re: Checkstyle, PMD and CPD publishers missing after plugin updates
Potential docs to update for clarity /plugin/job-dsl/api-viewer/index.html# Interim Resolution I was able to get this working in my project, which is a pipeline project, but only by
Setting the "recordIssues" configs as their own stage, given there is not option to use "publisher" or "post" within a Pipeline job, given the system will throw an error
stage ('Publish Static Analysis Reports') {
steps {
//These settings are called out separately and not included in the preceding stage as it will create a concurrency issue
recordIssues enabledForFailure: true, tool: checkStyle()
recordIssues enabledForFailure: true, tool: spotBugs()
recordIssues enabledForFailure: true, tool: cpd(pattern: '**/target/cpd.xml')
recordIssues enabledForFailure: true, tool: pmdParser(pattern: '**/target/pmd.xml')
}
}
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 f
[JIRA] (JENKINS-61053) submodule checkout randomly fails without failing the job
Title: Message Title Brian J Murrell commented on JENKINS-61053 Re: submodule checkout randomly fails without failing the job Francisco Fernández Total SWAG: 50% or more of the time. i can only SWAG because as soon as it became apparent that it was doing it, I had to disable the feature as it was our production Jenkins server. As for the pairs, at this point in time, I simply don't have the time to be doing roll-backs/forwards and waiting and watching builds to see how many break. I have too many other $day-job tasks that need to get done. I've created a ticket in our local ticketing system to get this debugging done. Either somebody else here might have time to do it, or it will have to wait until I have time. 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.204533.1581430986000.8271.1581536400243%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Adam Gabryś commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL I created a pull request (PR #32) with the fix. Now it works as follow: Code Result Returns ['1:selected', '2', '3', '4', '5'] "1" the default value ['1', '2', '3:selected', '4', '5'] "3" the default value, no difference if it is first or last ['1', '2', '3', '4'] "1" the first element when (no values are marked as default) [] "" empty value (Jenkins cannot handle null) [""] "" the first element (no values are marked as default) ['1:selected', '2', '3:selected', '4'] "1,3" multiple values are checked, so all of them are added (consistent with Build with Parameters behavior) ['1', '2', ':selected', '4'] ""
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site/Server
Title: Message Title Joe Hansche updated JENKINS-47309 Jenkins / JENKINS-47309 Plugin || Confluence Publisher || Not working with confluence cloud site/Server Change By: Joe Hansche Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/confluence-publisher-plugin/releases/tag/confluence-publisher-2.0.5 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.185734.1507283628000.8256.1581534780663%40Atlassian.JIRA.
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Jeff Thompson commented on JENKINS-61051 Re: Jobs are started on master instead of EC2 slaves randomly I'm not familiar with the details of the ec2-plugin, but I know it does some complicated stuff, including with how it manages agents. When I've looked into the code there before, there was some complicated pieces. If you can reproduce the problems without the ec2-plugin then it probably is due to something in the Jenkins server. (Since I'm not familiar with any reports on that, it seems unlikely.) If it only occurs with the ec2-plugin, then it's probably something to do with the custom capabilities it provides. 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.204531.158142564.8250.1581533280157%40Atlassian.JIRA.
[JIRA] (JENKINS-61065) Git plugin: infinite build trigger by "SCM change"
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61065 Git plugin: infinite build trigger by "SCM change" Change By: Mark Waite Exact similar to [https://github.com/jenkinsci/gitlab-plugin/issues/30]It's giving nightmare with infinite builds marked as "Started by an SCM change" even if I start the build myself, one build is triggered on my name followed by infinite triggers by "SCM change" and there is no change in code at all.Seeing these weird new lines ```Multiple candidate revisionsScheduling another build to catch up with``` like https://issues.jenkins-ci.org/browse/ JENKINS-54102 ?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel And this is happening for master branch but we don't have any "origin/master" branch as suggested workaround [here ]( | https://issues.jenkins-ci.org/browse/JENKINS-21464?focusedCommentId=250183&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-250183 ) ] Any fix? **Update** Strangely, while we didn't have origin/master, replacing the wildcard find "*/master" with "master" in "Branches to build" fixes the issue. But, I have been using the same since ages (8 years now) and the wildcard has never given me this issue before. The Git plugin's "Scheduling another build to catch up with" implementation needs to be re-looked. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60994) When using top level agents and timeouts, provisioning time is not accounted for
Title: Message Title Jose Blas Camacho Taboada stopped work on JENKINS-60994 Change By: Jose Blas Camacho Taboada Status: In Progress Open 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.204462.1580984833000.8243.1581529440201%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Adam Gabryś created an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: build-with-parameters.png, parambuild.png Components: active-choices-plugin, build-with-parameters-plugin Created: 2020-02-12 17:20 Environment: Jenkins 2.204.2 Active Choices Plug-in 2.2.2 Build With Parameters 1.4 Priority: Major Reporter: Adam Gabryś Active Choice radio parameter on parambuild page is always visible as text box (which is fine). Unfortunately, the default value is set incorrectly. The plugin always fills the text box with the first value from the script and does not remove :selected suffix. It means that for the following script: ['1', '2', '3:selected', '4', '5'] it returns 1, and for: ['1:selected', '2', '3', '4', '5'] it returns 1:selected. This behavior makes radio button unusable when builds are triggered by Jenkins Pipeline build st
[JIRA] (JENKINS-61053) submodule checkout randomly fails without failing the job
Title: Message Title Francisco Fernández commented on JENKINS-61053 Re: submodule checkout randomly fails without failing the job Brian J Murrell how often do the checkout fail? And could you let us know the result of trying those pairs that Mark mentioned? 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.204533.1581430986000.8239.1581527700266%40Atlassian.JIRA.
[JIRA] (JENKINS-56474) agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8
Title: Message Title Renato Botelho commented on JENKINS-56474 Re: agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8 I believe I saw the same issue here. Jenkins is running on a CentOS 7 box and I'm trying to configure a FreeBSD 13-CURRENT aarch64 as a builder node. Using the default openjdk package (version 8.232.09) I got the same problem. I decided then to go ahead and upgrade it to the latest version available on FreeBSD ports tree, which is 8.242.07.1. After that, it takes like 5 minutes to start, but after that it works. It throws these messages on console: <===[JENKINS REMOTING CAPACITY]===> channel started <===[JENKINS REMOTING CAPACITY]===> channel started Remoting version: 3.36.1This is a Unix agentFeb 12, 2020 11:40:39 AM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:jenkins.slaves.StandardOutputSwapper$channelswap...@4c81d622java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/freebsd-aarch64/libjnidispatch.so) not found in resource path ([]) at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1032) at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:988) at com.sun.jna.Native.(Native.java:195) at hudson.util.jna.GNUCLibrary.(GNUCLibrary.java:115) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.swap(StandardOutputSwapper.java:60) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.call(StandardOutputSwapper.java:45) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.call(StandardOutputSwapper.java:39) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Agent successfully connected and online Add Comment This message was sent by Atlassian Jira (v7
[JIRA] (JENKINS-46260) FileNotFoundExecption when getting info from BitBucket
Title: Message Title
Pavel Li commented on JENKINS-46260
Re: FileNotFoundExecption when getting info from BitBucket
I've tried to look at the Bitbucket OAuth code. Here is the part that causes the error:
...
public UserDetails getUserByUsername(String username) {
InputStreamReaderreader = null;
UserDetailsuserResponce = null;
try {
URLurl = newURL(API2_ENDPOINT + "users/" + username);
...
And as far as I understood the username is provided by Jenksins Core https://javadoc.jenkins.io/hudson/security/SecurityRealm.html So, it could be that username is provided in a wrong form, or plugin uses it incorrectly... But I'm null in Java, so all the above could be completely wrong
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.184508.1502958165000.8232.1581526740162%40Atlassian.JIRA.
[JIRA] (JENKINS-47309) Plugin || Confluence Publisher || Not working with confluence cloud site/Server
Title: Message Title Joe Hansche updated JENKINS-47309 Jenkins / JENKINS-47309 Plugin || Confluence Publisher || Not working with confluence cloud site/Server Change By: Joe Hansche Status: Open Fixed but Unreleased Resolution: Fixed 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.185734.1507283628000.8219.1581525421694%40Atlassian.JIRA.
[JIRA] (JENKINS-60417) Print log if post processing has been skipped
Title: Message Title Ulli Hafner updated JENKINS-60417 Jenkins / JENKINS-60417 Print log if post processing has been skipped Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed 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.203478.1575970934000.8217.1581525240263%40Atlassian.JIRA.
[JIRA] (JENKINS-60417) Print log if post processing has been skipped
Title: Message Title Ulli Hafner started work on JENKINS-60417 Change By: Ulli Hafner Status: Open In Progress 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.203478.1575970934000.8215.1581525181276%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4CLIENT environment variable non-reentrant
Title: Message Title Ralph Ndl updated an issue Jenkins / JENKINS-60213 P4CLIENT environment variable non-reentrant Change By: Ralph Ndl Labels: P4_A P4_CLIENT P4_VERIFY 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.203186.1574180065000.8212.1581524580217%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Brian Ray assigned an issue to Brian Ray Jenkins / JENKINS-57205 Null pointer exception in JGit pre-build merge Change By: Brian Ray Assignee: Brian Ray 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.198962.1556378819000.8205.1581524160597%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Brian Ray commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Yep, happy to track this one down. Between other duties and being a first time contributor, I'm hoping to file a PR by early next week. 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.198962.1556378819000.8202.1581524160526%40Atlassian.JIRA.
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title Ben M commented on JENKINS-60979 Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory Kristin Whetstone it happens when using the plugin installation manager. This does not happen when either not using the liberty feature "transportsecurity" or when not using java >= 9. I think this issue can be closed here, I will open one at openliberty on github instead. 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.204447.1580906476000.8194.1581523860140%40Atlassian.JIRA.
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title Nikolas Falco commented on JENKINS-52842 Re: xUnit plugin blocks PingThread responses I can try to increase the sleep time after 20 processed input files and maybe also try to setup the maximun number of thread used by saxon. By default saxon use the maximun number of thread to make CPU full load. 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.192770.1533150138000.8190.1581523440406%40Atlassian.JIRA.
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Pascal Laporte resolved as Fixed Jenkins / JENKINS-60831 Localisation to non-english is causing a lot of issues, bug and crashes Change By: Pascal Laporte Status: Open Resolved Resolution: Fixed 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.204182.1579617297000.8188.1581523140628%40Atlassian.JIRA.
[JIRA] (JENKINS-60831) Localisation to non-english is causing a lot of issues, bug and crashes
Title: Message Title Pascal Laporte commented on JENKINS-60831 Re: Localisation to non-english is causing a lot of issues, bug and crashes We have updated to 2.220 . Good news! Everything is now working in other language than English. 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.204182.1579617297000.8184.1581523080264%40Atlassian.JIRA.
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title Kristin Whetstone commented on JENKINS-60979 Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory Were you trying to download the plugin using the plugin installation manger tool or is this happening when you're launching Jenkins? If the later, we should change the component to be against core since the `plugin-installation-manager-tool` is a separate thing and under core this would get more attention. 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.204447.1580906476000.8177.1581521580588%40Atlassian.JIRA.
[JIRA] (JENKINS-46260) FileNotFoundExecption when getting info from BitBucket
Title: Message Title
Pavel Li edited a comment on JENKINS-46260
Re: FileNotFoundExecption when getting info from BitBucket
I've also started to experience this issue in logs with Bitbucket OAuth plugin with Role Based plugin. And in newer version with Bitbucket API 2.0: {code:java}java.io.FileNotFoundException: https://api.bitbucket.org/2.0/users/John Doe at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1896){code} I've checked with direct call to API with similar request, it gives following response: {code:java}{"type": "error","error": {"message": "John Doe"}}{code}The problem is that it isn't actual user id which is expected by API.If I use correct user id, i.e. _jdoe_, it works fine.So, something works incorrectly and sends wrong requests to Bitbucket API.Could someone advise where to go with this issue? What would be the right direction if it is not in core? 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.184508.1502958165000.8173.1581521100518%40Atlassian.JIRA.
[JIRA] (JENKINS-46260) FileNotFoundExecption when getting info from BitBucket
Title: Message Title
Pavel Li commented on JENKINS-46260
Re: FileNotFoundExecption when getting info from BitBucket
I've also started to experience this issue in logs with Bitbucket OAuth plugin with Role Based plugin. And in newer version with Bitbucket API 2.0:
java.io.FileNotFoundException: https://api.bitbucket.org/2.0/users/John Doe at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1896)
I've checked with direct call to API with similar request, it gives following response:
{"type": "error","error": {"message": "John Doe"}}
The problem is that it isn't actual user id which is expected by API. If I use correct user id, i.e. jdoe, it works fine. So, something works incorrectly and sends wrong requests to Bitbucket API. Could someone advise where to go with this issue? What would be the right direction if it is not in core?
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 "Jen
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-61009 How to use a reference repository in an organization folder? Change By: Mark Waite Status: Reopened Closed Resolution: Not A Defect 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.204479.1581041026000.8167.1581520920388%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake edited a comment on JENKINS-61009 Re: How to use a reference repository in an organization folder? Mr. [~markewaite] I'm sorry this is the final question, yes I compared .git folders as you said and there is a significant difference of folder sizes. So I'm now going to merge my Pull request into my master branch. I'm sorry this is the final question, could Could you tell me how to resolve this below error sir ? I'm getting below error when I'm building my Pull Request after all changes you explained above. !image-2020-02-12-07-59-42-137.png! !image-2020-02-12-07-58-17-379.png!Please see the below my Jenkinsfile code as well, I hope above issue causing by the refspec as I underlined in below code. !image-2020-02-12-07-57-17-958.png! 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.204479.1581041026000.8164.1581520260157%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake edited a comment on JENKINS-61009 Re: How to use a reference repository in an organization folder? [~markewaite] yes I compared .git folders as you said and there is a significant change difference of folder sizes . So I'm now going to merge my Pull request into my master branch. I'm sorry this is the final question, could you tell me how to resolve this below error sir ? I'm getting below error when I'm building my Pull Request after all changes you explained above. !image-2020-02-12-07-59-42-137.png! !image-2020-02-12-07-58-17-379.png!Please see the below my Jenkinsfile code as well, I hope above issue causing by the refspec as I underlined in below code. !image-2020-02-12-07-57-17-958.png! 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.204479.1581041026000.8161.1581520200361%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake edited a comment on JENKINS-61009 Re: How to use a reference repository in an organization folder? [~markewaite] yes I compared .git folders as you said and there is a significant change. So I 'm now going to merge my Pull request into my master branch. I'm sorry this is the final question, could you tell me how to resolve this below error sir ? We lost our live customer release due to below error. I'm getting below error when I'm building my Pull Request after all changes you explained above. !image-2020-02-12-07-59-42-137.png! !image-2020-02-12-07-58-17-379.png!Please see the below my Jenkinsfile code as well, I hope above issue causing by the refspec as I underlined in below code. !image-2020-02-12-07-57-17-958.png! 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.204479.1581041026000.8158.1581520140475%40Atlassian.JIRA.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title
kamil wezka commented on JENKINS-49794
Re: BooleanParam default value is always true
I just wanted add my comment. Should the script be:
script {
if (params.RUN_TESTS == true) {
echo "true: $RUN_TESTS"
}
else echo "false: $RUN_TESTS"
}
because I think the `params.RUN_TESTS` is just a pointer to parameter reference that is always non null so if you don't use equality operators it is always true. Possibly this is not clear?
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.188745.1519826985000.8154.1581519660186%40Atlassian.JIRA.
[JIRA] (JENKINS-61041) SharedLibrary doesn´t allow git parameter to fetch all branches
Title: Message Title Jon Udaondo updated an issue Jenkins / JENKINS-61041 SharedLibrary doesn´t allow git parameter to fetch all branches Change By: Jon Udaondo Priority: Major Critical 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.204521.1581409996000.8149.1581519120308%40Atlassian.JIRA.
[JIRA] (JENKINS-59776) workflow-basic-steps-plugin "waitUntil" should have a quiet mode
Title: Message Title Terry Lacy edited a comment on JENKINS-59776 Re: workflow-basic-steps-plugin "waitUntil" should have a quiet mode Seriously. The "Will try again after" output is obnoxious and pretty useless. If I really want to see what's happening in the logs I can put my own output in the waitUntil block. One of the reasons I switched from sleep loops was that I was hoping to avoid the output from the sleep command. 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.202500.1571053928000.8109.1581518640198%40Atlassian.JIRA.
[JIRA] (JENKINS-59776) workflow-basic-steps-plugin "waitUntil" should have a quiet mode
Title: Message Title Terry Lacy commented on JENKINS-59776 Re: workflow-basic-steps-plugin "waitUntil" should have a quiet mode Seriously. The "Will try again after" output is obnoxious and pretty useless. If I really want to see what's happening in the logs I can put my own output in the waitUntil block. 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.202500.1571053928000.8104.1581518580827%40Atlassian.JIRA.
[JIRA] (JENKINS-61011) New Feature "Delete / Rename request for entired Folder"
Title: Message Title John Flynn resolved as Fixed Version 2.2.6 has been released with the changes. Jenkins / JENKINS-61011 New Feature "Delete / Rename request for entired Folder" Change By: John Flynn Status: In Progress Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/requests-plugin/blob/requests-2.2.6/CHANGELOG.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60619) Could not initialize class org.boon.Boon
Title: Message Title Mathieu Delrocq started work on JENKINS-60619 Change By: Mathieu Delrocq Status: Open In Progress 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.203850.1577922814000.8000.1581515820770%40Atlassian.JIRA.
[JIRA] (JENKINS-60619) Could not initialize class org.boon.Boon
Title: Message Title Mathieu Delrocq edited a comment on JENKINS-60619 Re: Could not initialize class org.boon.Boon [PR#31| [ https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/31] ] should solve this issue. 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.203850.1577922814000.7996.1581515820655%40Atlassian.JIRA.
[JIRA] (JENKINS-60619) Could not initialize class org.boon.Boon
Title: Message Title Mathieu Delrocq commented on JENKINS-60619 Re: Could not initialize class org.boon.Boon [PR#31|https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/31] should solve this issue. 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.203850.1577922814000.7992.1581515760387%40Atlassian.JIRA.
[JIRA] (JENKINS-61041) SharedLibrary doesn´t allow git parameter to fetch all branches
Title: Message Title Jon Udaondo assigned an issue to Devin Nusbaum Jenkins / JENKINS-61041 SharedLibrary doesn´t allow git parameter to fetch all branches Change By: Jon Udaondo Assignee: Boguslaw Klimas Devin Nusbaum 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.204521.1581409996000.7989.1581514140608%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake reopened an issue Jenkins / JENKINS-61009 How to use a reference repository in an organization folder? Change By: Amila Gunathilake Resolution: Not A Defect Status: Closed Reopened 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.204479.1581041026000.7983.1581513300448%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake edited a comment on JENKINS-61009 Re: How to use a reference repository in an organization folder? I'm sorry this is the final question, could you tell me how to resolve this error sir ? We lost our live customer release due to below error.I'm getting below error when I'm building my Pull Request after all changes you explained above. !image-2020-02-12-07-59-42-137.png! !image-2020-02-12-07-58-17-379.png!Please see the below my Jenkinsfile code as well, I hope above issue causing by the refspec as I underlined in below code. !image-2020-02-12-07-57-17-958.png! 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.204479.1581041026000.7986.1581513300568%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake edited a comment on JENKINS-61009 Re: How to use a reference repository in an organization folder? I'm sorry could you tell me how to resolve this error sir ? We lost our live customer release due to below error.I'm getting below error when I'm building my Pull Request after all changes you explained above. !image-2020-02-12-07-59-42-137.png! !image-2020-02-12-07-58-17-379.png!Please see the below my Jenkinsfile code as well , I hope above issue causing by the refspec as I underlined in below code . !image-2020-02-12-07-57-17-958.png! 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.204479.1581041026000.7979.1581512880166%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake edited a comment on JENKINS-61009 Re: How to use a reference repository in an organization folder? I'm sorry could you tell me how to resolve this error sir ? We lost our live customer release due to below error.I'm getting below error when I'm building my Pull Request after all changes you explained above. !image-2020-02-12-07- 59-42-137.png! !image-2020-02-12-07- 58-17-379.png! Please see the below my Jenkinsfile code as well I hope above issue causing by the refspec. !image-2020-02-12-07-57-17-958.png! 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.204479.1581041026000.7977.1581512400365%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake commented on JENKINS-61009 Re: How to use a reference repository in an organization folder? I'm sorry could you tell me how to resolve this error sir ? We lost our live customer release due to below error. I'm getting below error when I'm building my Pull Request after all changes you explained above. Please see the below my Jenkinsfile code as well I hope above issue causing by the refspec. 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.204479.1581041026000.7973.1581512340660%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-61009 How to use a reference repository in an organization folder? Change By: Amila Gunathilake Attachment: image-2020-02-12-07-58-17-379.png 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.204479.1581041026000.7971.1581512340604%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-61009 How to use a reference repository in an organization folder? Change By: Amila Gunathilake Attachment: image-2020-02-12-07-57-17-958.png 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.204479.1581041026000.7967.1581512280211%40Atlassian.JIRA.
[JIRA] (JENKINS-61067) Wrong value for GIT_COMMIT after merge?
Title: Message Title
Tobias Gruetzmacher updated an issue
Jenkins / JENKINS-61067
Wrong value for GIT_COMMIT after merge?
Change By:
Tobias Gruetzmacher
This issue is just for documentation, since the issue went away with the update to gitlab-branch-source [1.4.4|https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.4.4]. Before that, a merge request would do a "fat" instead a lightweight checkout to read the {{Jenkinsfile}} and I cannot reproduce the issue when just a lightweight checkout is done.Pipeline sample code to have something to talk about:{code:java}def repo = checkout scmecho repo.GIT_COMMIT{code}This works correctly for branch builds, but not for merge request builds and the strategy "Merging the merge request with the current target branch revision" - when using that strategy, {{GIT_COMMIT}} points to a revision which doesn't exist after the merge, but instead to the merge commit from the "temporary" chechout which was done for reading the {{Jenkinsfile}}. Relevant log snippets:{noformat}Branch indexingQuerying the current revision of merge request #3...Current revision of merge request #3 is 367f5bc9835cecaf5929cf9a6a8d3600ad1dae32Checking out git https://.git into /var/lib/jenkins/workspace/SOMETHING_MR-3@script to read Jenkinsfile[...] > git fetch --no-tags --force --progress -- https://.git +refs/merge-requests/3/head:refs/remotes/origin/MR-3 +refs/heads/master:refs/remotes/origin/master # timeout=10Merging remotes/origin/master commit eb6a5804b1a07157304d00562a489437342049e1 into MR head commit 367f5bc9835cecaf5929cf9a6a8d3600ad1dae32[...]Merge succeeded, producing a9473d5a2d79ace679affe37853e74950602b07bChecking out Revision a9473d5a2d79ace679affe37853e74950602b07b (feature/update-slf4j)[...]Commit message: "Merge commit 'eb6a5804b1a07157304d00562a489437342049e1' into HEAD"[GitLab Pipeline Status] Notifying merge request build status: RUNNING tgruetzm/versions/ci/MR-3: Build started...[GitLab Pipeline Status] NotifiedRunning in Durability level: PERFORMANCE_OPTIMIZED[...][GitLab Pipeline Status] Notifying merge request build status: RUNNING tgruetzm/versions/ci/MR-3: Build started...[Pipeline] Start of Pipeline[...][Pipeline] checkout[...]Merging remotes/origin/master commit eb6a5804b1a07157304d00562a489437342049e1 into MR head commit 367f5bc9835cecaf5929cf9a6a8d3600ad1dae32[...]Merge succeeded, producing bdabb0071fa91fe128c037a9f3352b459fcfcde8Checking out Revision bdabb0071fa91fe128c037a9f3352b459fcfcde8 (feature/update-slf4j)[...]Commit message: "Merge commit 'eb6a5804b1a07157304d00562a489437342049e1' into HEAD"First time build. Skipping changelog.[...][Pipeline] echo{GIT_AUTHOR_EMAIL= someid...@inform-software.com xxx , GIT_AUTHOR_NAME= Test-Jenkins xxx , GIT_BRANCH=feature/update-slf4j, GIT_COMMIT=a9473d5a2d79ace679affe37853e74950602b07b, GIT_COMMITTER_EMAIL= someid...@inform-software.com xxx , GIT_COMMITTER_NAME= Test-Jenkins xxx , GIT_LOCAL_BRANCH=feature/update-slf4j, GIT_PREVIOUS_COMMIT=873ac16b7ac3b44ad9b45cdde7479a3dd73a4be
[JIRA] (JENKINS-61067) Wrong value for GIT_COMMIT after merge?
Title: Message Title
Tobias Gruetzmacher updated an issue
Jenkins / JENKINS-61067
Wrong value for GIT_COMMIT after merge?
Change By:
Tobias Gruetzmacher
This issue is just for documentation, since the issue went away with the update to gitlab-branch-source [1.4.4 ]( | https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.4.4 ) ] . Before that, a merge request would do a "fat" instead a lightweight checkout to read the {{Jenkinsfile}} and I cannot reproduce the issue when just a lightweight checkout is done.Pipeline sample code to have somethingto something to talk about:{code:java}def repo = checkout scmecho repo.GIT_COMMIT{code}This works correctly for branch builds, but not for merge request builds and the strategy "Merging the merge request with the current target branch revision" - when using that strategy, {{GIT_COMMIT}} points to a revision which doesn't exist after the merge, but instead to the merge commit from the "temporary" chechout which was done for reading the {{Jenkinsfile}}. Relevant log snippets:{noformat}Branch indexingQuerying the current revision of merge request #3...Current revision of merge request #3 is 367f5bc9835cecaf5929cf9a6a8d3600ad1dae32Checking out git https://.git into /var/lib/jenkins/workspace/SOMETHING_MR-3@script to read Jenkinsfile[...] > git fetch --no-tags --force --progress -- https://.git +refs/merge-requests/3/head:refs/remotes/origin/MR-3 +refs/heads/master:refs/remotes/origin/master # timeout=10Merging remotes/origin/master commit eb6a5804b1a07157304d00562a489437342049e1 into MR head commit 367f5bc9835cecaf5929cf9a6a8d3600ad1dae32[...]Merge succeeded, producing a9473d5a2d79ace679affe37853e74950602b07bChecking out Revision a9473d5a2d79ace679affe37853e74950602b07b (feature/update-slf4j)[...]Commit message: "Merge commit 'eb6a5804b1a07157304d00562a489437342049e1' into HEAD"[GitLab Pipeline Status] Notifying merge request build status: RUNNING tgruetzm/versions/ci/MR-3: Build started...[GitLab Pipeline Status] NotifiedRunning in Durability level: PERFORMANCE_OPTIMIZED[...][GitLab Pipeline Status] Notifying merge request build status: RUNNING tgruetzm/versions/ci/MR-3: Build started...[Pipeline] Start of Pipeline[...][Pipeline] checkout[...]Merging remotes/origin/master commit eb6a5804b1a07157304d00562a489437342049e1 into MR head commit 367f5bc9835cecaf5929cf9a6a8d3600ad1dae32[...]Merge succeeded, producing bdabb0071fa91fe128c037a9f3352b459fcfcde8Checking out Revision bdabb0071fa91fe128c037a9f3352b459fcfcde8 (feature/update-slf4j)[...]Commit message: "Merge commit 'eb6a5804b1a07157304d00562a489437342049e1' into HEAD"First time build. Skipping changelog.[...][Pipeline] echo{GIT_AUTHOR_EMAIL=someid...@inform-software.com, GIT_AUTHOR_NAME=Test-Jenkins, GIT_BRANCH=feature/update-slf4j, GIT_COMMIT=a9473d5a2d79ace679affe37853e74950602b07b, GIT_COMMITTER_EMAIL=someid...@inform-software.com, GIT_COMMITTER_NAME=Test-Jenkins, GIT_LOCAL_BRANCH=feature/update-slf4j, GIT_PREVIOUS_COMMIT=873ac16b7ac3b44ad9b45cdde7479a3dd73a4be
[JIRA] (JENKINS-61058) Checkstyle, PMD and CPD publishers missing after plugin updates
Title: Message Title
Jason Wolf updated an issue
Jenkins / JENKINS-61058
Checkstyle, PMD and CPD publishers missing after plugin updates
Change By:
Jason Wolf
*Issue:* Prior to recently updating a few Jenkins Plugins, we were successfully using the Warnings Next Gen Plug in, and following those plugin updates, the build fails and we are shown the referenced Error Message...which seems to be a net result of changes to the "tools" related to Static Analysis. Legacy plugins which note that Initial review of the functions have stack trace has been removed challenging, but after weeding through, my assumption is that there is a new conflict with the CPS / moved to Warnings Next Gen were previously uninstalled. Script Security Feature *Error =* java.lang.NoSuchMethodError: No such DSL method 'spotBugs *Additional Info* * The reference to .cps workflow tells me that potentially with the plugin update(s), something is potentially an issue with the Workflow CPS plugin, but regrettably I cant seem to find a way to get the config to work, and I dont want to just * * There is a publisher listed below for spot bugs, but it does not match the Warnings Next Gen docs of "spotBugs", the value / method referenced below is, which represents an unexpected change"spotBugsPublisher" * Also noted that there are no publishers available for PMD, CPD or Checkstyle any longer DSL Entry, which previously worked{code:java} steps {// Compile / Static AnalysiswarnError('Static Analysis has FAILED') {sh "mvn install -e -U -DskipTests -Pstatic-analysis -Padobe-public"}archiveArtifacts artifacts: ('**/target/checkstyle-result.xml')archiveArtifacts artifacts: ('**/target/spotbugsXml.xml')archiveArtifacts artifacts: ('**/target/pmd.xml')archiveArtifacts artifacts: ('**/target/cpd.xml')archiveArtifacts artifacts: ('**/target/site/jacoco/jacoco.xml')//Sonarqube analysiswarnError('Sonarqube Analysis has FAILED') {sh "mvn sonar:sonar -Dsonar.branch.name=${env.BRANCH_NAME}"}//Script protocol is needed here, otherwise Pipeline will throw an error//TODO Remediate post build publish issue, as it would not be anticipated that the script variable would be needed here - https://github.com/jenkinsci/job-dsl-plugin/wiki/Script-Securityscript {checkstyle = scanForIssues tool: checkStyle(pattern: '**/target/checkstyle-result.xml')publishIssues issues: [checkstyle]pmd = scanForIssues tool: pmdParser(pattern: '**/target/pmd.xml')publishIssues issues: [pmd]cpd = scanForIssues tool: cpd(pattern: '**/target/cpd.xml')publishIssues issues: [cpd]spotbugs = scanForIssues tool: spotBugs(pattern: '**/target/spotbugsXml.xml')publishIssues issues: [spotbugs]maven = scanForIssues tool: mavenConsole()publishIssues issues: [maven]}}}{code} *Console Error for Spotbugs...but s
[JIRA] (JENKINS-61067) Wrong value for GIT_COMMIT after merge?
Title: Message Title Tobias Gruetzmacher created an issue Jenkins / JENKINS-61067 Wrong value for GIT_COMMIT after merge? Issue Type: Bug Assignee: Mark Waite Components: git-plugin, gitlab-branch-source-plugin Created: 2020-02-12 12:02 Priority: Minor Reporter: Tobias Gruetzmacher This issue is just for documentation, since the issue went away with the update to gitlab-branch-source [1.4.4](https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.4.4). Before that, a merge request would do a "fat" instead a lightweight checkout to read the Jenkinsfile and I cannot reproduce the issue when just a lightweight checkout is done. Pipeline sample code to have somethingto talk about: def repo = checkout scm echo repo.GIT_COMMIT This works correctly for branch builds, but not for merge request builds and the strategy "Merging the merge request with the current target branch revision" - when using that strategy, GIT_COMMIT points to a revision which doesn't exist after the merge, but instead to the merge commit from the "temporary" chechout which was done for reading the Jenkinsfile. Relevant log snippets: Branch indexing Querying the current revision of merge request #3... Current revision of merge request #3 is 367f5bc9835cecaf5929cf9a6a8d3600ad1dae32 Checking out git https://.git into /var/lib/jenkins/workspace/SOMETHING_MR-3@script to read Jenkinsfile [...] > git fetch --no-tags --force --progress -- https://.git +refs/merge-requests/3/head:refs/remotes/origi
[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title ASHOK MOHANTY commented on JENKINS-55972 Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master We are using git-client 3.0 and git plugin 4.0. Facing this error intermittently (inside a JNLP node). For cloning we are using a generic LDAP user without password. And/or please let me know the matching ticket where I can update this issue !! > GitLab: Your account has been blocked. fatal: Could not read from remote repository. 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.197383.1549364479000.7952.1581508080169%40Atlassian.JIRA.
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title Satheesh Kumar commented on JENKINS-55070 Re: "Jenkins.instance is missing" error when restarting Jenkins If you have the backup of the Plugins folder before you did the upgrade of the plugin. Restore the backup folder into the Jenkins home directory and restart the instance, it would work 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.196122.154417045.7941.1581507120397%40Atlassian.JIRA.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Kamil Szuster commented on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration Today the same error occurred again: Jenkins created a ..@2 and ...@3 folder in the .../workspace directory. I had to delete these via SSH and restart the master => back to normal job workspace again. Jenkins ver. 2.176.3 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.164818.1441065243000.7927.1581507000371%40Atlassian.JIRA.
[JIRA] (JENKINS-61066) Schedule Jenkins job using Jenkins Rest API
Title: Message Title Prasanna Rengarajan created an issue Jenkins / JENKINS-61066 Schedule Jenkins job using Jenkins Rest API Issue Type: Improvement Assignee: Martin Spielmann Components: _unsorted, schedule-build-plugin Created: 2020-02-12 11:19 Labels: jenkins plugin Priority: Minor Reporter: Prasanna Rengarajan I have a Jenkins job which is scheduled for a specific time. I want to modify that timing programmatically. I tried to modify the build by installing Schedule Build plugin and modify it using http://jenkins_url/job/jobname/build?delay=3344sec. But this will put the job in quiet period which holds the java thread. I'm looking to modify the Schedule entry without putting it to quiet period. Add Comment
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title João Salavessa commented on JENKINS-60798 Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Vincent Latombe just to confirm that 1.23.3 seems to be working fine. Thanks! 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.204126.1579192576000.7920.1581505020502%40Atlassian.JIRA.
[JIRA] (JENKINS-54594) Add support for credentials binding plugin for ocp bearer token
Title: Message Title Max Laverse stopped work on JENKINS-54594 Change By: Max Laverse Status: In Progress Open 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.195381.1542093616000.7916.1581502560349%40Atlassian.JIRA.
