[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Jens Beyer edited a comment on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Regarding the exception:The new workflow-job 2.31 (compared to 2.25) does not write the log files for the individual steps anymore. At least on my system.For new builds started after the upgrade, the individual build step logs seem to work without the individual build step log files.But for builds finished before the upgrade, after the upgrade is done, you are unable to get the full build step logs, and the mentioned exception occurs. Regarding the empty console: I opened JENKINS_55465 JENKINS-55465 which may also be the reason for your issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Jens Beyer edited a comment on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Regarding the exception: The new workflow-job 2.31 (compared to 2.25) does not write the log files for the individual steps anymore. At least on my system.For new builds started after the upgrade, the individual build step logs seem to work without the individual build step log files.But for builds finished before the upgrade, after the upgrade is done, you are unable to get the full build step logs, and the mentioned exception occurs. Regarding the empty console: I opened JENKINS_55465 which may also be the reason for your issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55233) email-ext: PowerMock is not compatible with Java 11
Title: Message Title Adrien Lecharpentier commented on JENKINS-55233 Re: email-ext: PowerMock is not compatible with Java 11 I fixed the problem. Mockito matcher anyMap is not matching null since version 2.1.0, according to the javadoc. Replacing the matcher on the addRecipient in MockUtilities by any solves the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55071) Slow branch scan when using Bitbucket source
Title: Message Title David Kostal commented on JENKINS-55071 Re: Slow branch scan when using Bitbucket source at in my case this was really related to Bitbucket API throttling. However there was no report in Jenkins log. After switch of the biggest and most used repo to dedicated BB user, it's fast again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32308) NoSuchMethodError: hudson.scm.SubversionSCM.getLocations
Title: Message Title David Pärsson assigned an issue to Unassigned Jenkins / JENKINS-32308 NoSuchMethodError: hudson.scm.SubversionSCM.getLocations Change By: David Pärsson Assignee: David Pärsson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title David Pärsson commented on JENKINS-55460 Re: Cleaning of svn workspace broken in 2.157 I'm sorry to let you know that this plugin isn't under active development anymore. If you can provide a pull request that fixes this I'd be happy to review it though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title David Pärsson assigned an issue to Unassigned Jenkins / JENKINS-55460 Cleaning of svn workspace broken in 2.157 Change By: David Pärsson Assignee: David Pärsson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44376) Ability to set variables shared between stages
Title: Message Title Jose Blas Camacho Taboada commented on JENKINS-44376 Re: Ability to set variables shared between stages The fact that a value can be set in an environment and be accessed by child stages lgtm, but setting values for siblings is unclear to be as it breaks the var scope. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Jens Beyer commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs The new workflow-job 2.31 (compared to 2.25) does not write the log files for the individual steps anymore. At least on my system. For new builds started after the upgrade, the individual build step logs seem to work without the individual build step log files. But for builds finished before the upgrade, after the upgrade is done, you are unable to get the full build step logs, and the mentioned exception occurs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55465) Empty console when properties compressBuildLog() is enabled
Title: Message Title Jens Beyer created an issue Jenkins / JENKINS-55465 Empty console when properties compressBuildLog() is enabled Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2019-01-09 07:21 Priority: Critical Reporter: Jens Beyer Had Pipeline Job Plugin 2.25. Our jobs have properties([, compressBuildLog(), ...]) enabled. Upgrade to 2.31 along with a lot of dependencies. With the new plugin, the build console shows the output as long as the build is running. When the build is finished, there is no console anymore for a build (neither default /job//job///console nor .../consoleFull or .../consoleText ). Remove compressBuildLog() from properties, run a build --> issue is gone for the new build. Of course, for the builds which had compressed build logs, the issue persists. Looks like the new console view does not work with compressed build logs. Setting to Critical as this should be mentioned at least in the upgrade notes. I don't have a chance from Classic Jenkins UI to view the logs anymore. Add Comment
[JIRA] (JENKINS-55442) Need filter by message text
Title: Message Title Michael Keppler commented on JENKINS-55442 Re: Need filter by message text I can try that. I guess both the parser library and warnings plugin need to be modified, according to what I saw when I looked at the existing filters. Give me some days. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55464) Increment plugin Jenkins version to 2.89.4
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-55464 Increment plugin Jenkins version to 2.89.4 Issue Type: Improvement Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2019-01-09 07:07 Priority: Major Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55446) Unable to Execute Test in HP Performance Center 12.01
Title: Message Title Pradeepkumar Subramaniam commented on JENKINS-55446 Re: Unable to Execute Test in HP Performance Center 12.01 Thanks Daniel Danan, Please do let me know your availability, so that we can have web meeting. I'm new to Jenkins and Performance Center. it might be configuration too. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55463) Summay report plugin failed to transfer xml to html
Title: Message Title Peng Sun updated an issue Jenkins / JENKINS-55463 Summay report plugin failed to transfer xml to html Change By: Peng Sun Summary: Summay report plugin broken for transfering failed to transfer xml to html Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55463) Summay report plugin broken for transfering xml to html
Title: Message Title Peng Sun created an issue Jenkins / JENKINS-55463 Summay report plugin broken for transfering xml to html Issue Type: Bug Assignee: Unassigned Attachments: 5ASummary.xml, bug.png Components: summary_report-plugin Created: 2019-01-09 05:38 Environment: Jenkins: 2.152 Summary Display Plugin: 1.15 Priority: Major Reporter: Peng Sun For now, it only displays the plain html code on build page not render them. For details, please check the attachment Add Comment
[JIRA] (JENKINS-55462) "shelve project" button missing for all non-admin users
Title: Message Title Roger Wang created an issue Jenkins / JENKINS-55462 "shelve project" button missing for all non-admin users Issue Type: Bug Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2019-01-09 05:28 Environment: jenkins v2.150.1 running on Centos 7 with Project based authorisation Priority: Blocker Reporter: Roger Wang Hello, with project based authorisation, all non-admin user cannot see the Shelve Project button. the button will appear if we grant the administrator privileges to the user in Global Security. I manually created a free style project for testing which behaves the same. Jenkins and plugins are updated to the latest version. Thanks for helping. Roger Add Comment
[JIRA] (JENKINS-55443) Unable to delete Workspace on SSH Slave with Pipeline
Title: Message Title Makson Lee commented on JENKINS-55443 Re: Unable to delete Workspace on SSH Slave with Pipeline workspace cleanup plugin doesn't work in freestyle project now. jenkins: 2.157 ssh slaves: 1.29.4 workspace cleanup: 0.37 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Vipul Madaan commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. ng the exact same issue. Any update on it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55461) Refactor code to conform to log4j style guide
Title: Message Title David Olorundare started work on JENKINS-55461 Change By: David Olorundare Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55461) Refactor code to conform to log4j style guide
Title: Message Title David Olorundare created an issue Jenkins / JENKINS-55461 Refactor code to conform to log4j style guide Issue Type: Task Assignee: David Olorundare Components: audit-log-plugin Created: 2019-01-09 03:36 Labels: audit-logging Priority: Minor Reporter: David Olorundare See - https://logging.apache.org/log4j-audit/latest/javastyle.html - for details on the code style guide the project uses. Add Comment
[JIRA] (JENKINS-54329) Jenkins Does Not Use Private IP Address by Default For VPC+PublicIP Slaves
Title: Message Title Daniel Garzon assigned an issue to Daniel Garzon Jenkins / JENKINS-54329 Jenkins Does Not Use Private IP Address by Default For VPC+PublicIP Slaves Change By: Daniel Garzon Assignee: FABRIZIO MANFREDI Daniel Garzon Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54329) Jenkins Does Not Use Private IP Address by Default For VPC+PublicIP Slaves
Title: Message Title Daniel Garzon commented on JENKINS-54329 Re: Jenkins Does Not Use Private IP Address by Default For VPC+PublicIP Slaves Dustin Brown FABRIZIO MANFREDI I implemented the requested functionality here: https://github.com/jenkinsci/ec2-plugin/pull/329 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Mark Waite commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException If neither of those work, then please open a bug report with the answers to my questions. I don't know if I will have time to help you, but that's probably better than nothing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title Dik Rana created an issue Jenkins / JENKINS-55460 Cleaning of svn workspace broken in 2.157 Issue Type: Bug Assignee: David Pärsson Components: svn-workspace-cleaner Created: 2019-01-09 01:36 Environment: Jenkins 2.157 Windows Server 2012 Priority: Minor Reporter: Dik Rana The following error occurs in the latest Jenkins build when the pipeline script tries to clean the workspace. Reverted back to 2.156 and it works without any issue Checking out svn Environment Control into \workspace@script to read Jenkinsfile Cleaning local Directory . ERROR: Checkout failed jenkins.util.io.CompositeIOException: Unable to delete '\workspace@script\.'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:84) at hudson.Util.deleteContentsRecursive(Util.java:244) at hudson.scm.subversion.CheckoutUpdater$SubversionUpdateTask.perform(CheckoutUpdater.java:93) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:168) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1041) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1017) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:990) at hudson.FilePath.act(FilePath.java:1078) at hudson.FilePath.act(FilePath.java:1061) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:937) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:864) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at
[JIRA] (JENKINS-55459) failFast option for parallel stages should be able to set build result to FAILED
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-55459 failFast option for parallel stages should be able to set build result to FAILED Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-01-09 01:30 Priority: Minor Reporter: Owen Mehegan If a user has a Pipeline script with parallel stages, and they set 'failFast true' for those stages, if one of the stages fails then the build is immediately aborted. The result of the build is set to ABORTED. It would be better if there was a way to optionally have the build result be FAILED in this case. Although it makes a kind of logical sense for it to be ABORTED, because we have told Jenkins to abort the build, we did so because a stage failed. If we didn't failFast, the build's result would always be FAILED. Add Comment
[JIRA] (JENKINS-55458) Unable to create nexus new repo through nexus artifact uploader Plugin
Title: Message Title Tasleem Shaik assigned an issue to nobody Jenkins / JENKINS-55458 Unable to create nexus new repo through nexus artifact uploader Plugin Change By: Tasleem Shaik Assignee: Suresh Kumar nobody Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55458) Unable to create nexus new repo through nexus artifact uploader Plugin
Title: Message Title
Tasleem Shaik created an issue
Jenkins / JENKINS-55458
Unable to create nexus new repo through nexus artifact uploader Plugin
Issue Type:
Task
Assignee:
Suresh Kumar
Components:
nexus-artifact-uploader-plugin
Created:
2019-01-09 01:23
Environment:
jenkins 2.156 on windows using declarative pipeline to upload artifacts
Labels:
pipeline nexus jenkins
Priority:
Blocker
Reporter:
Tasleem Shaik
By using nexus-artifact-uploader-plugin I am able to upload artifacts to existing custom repository in nexus but when I am trying to upload to new repository which is not there in nexus it is throwing error. stage ('upload artifact') { steps { nexusArtifactUploader artifacts: [ [artifactId: 'test', classifier: '', file: 'test.zip', type: 'zip']], credentialsId: 'nexusid', groupId: 'gitlfs', nexusUrl: 'nexus_url', nexusVersion: 'nexus3', protocol: 'http', repository: '', version: "${params.version}" } } NOTE: My requirement is to create new custom repository in nexus repository and upload artifacts to created repository through jenkins Thank you for your help
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Gregor Philp commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException yeah thats the one I sent to and also tried to subscribe like it mentioned. Both failed telling me the group does not exist. Now I guess I have to try gitter Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55277) Icons in html Email are not displayed
Title: Message Title David van Laatum commented on JENKINS-55277 Re: Icons in html Email are not displayed Only thing I can think of is if your using some kind of authenticating reverse proxy in front of jenkins if that is the case and it doesn't have exceptions for images and such that will happen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Mark Waite edited a comment on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException Send an e-mail message to [jenkinsci-us...@googlegroups.com|mailto:jenkinsci-us...@googlegroups.com] . Due to spam, your first posting to the mailing list will be held until it is approved.If that doesn't work, then connect to [Gitter|https://gitter.im/jenkinsci/jenkins] The users mailing list is where users support each other. Internet Relay Chat is also used so that users can support each other.CloudBees also sells support contracts for Jenkins for those that need the power of a commercial support team. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Mark Waite commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException Send an e-mail message to jenkinsci-us...@googlegroups.com . Due to spam, your first posting to the mailing list will be held until it is approved. If that doesn't work, then connect to Gitter Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Gregor Philp commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException Mark Waite ok this is not easy. I've tried contacting both the users and dev email addresses on the Jenkins users mailing list and both just get returned emails saying the group does not exist. What is the jenkins support mailing list? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-54746 Can't connect via SSH on 1.29.1 Change By: Ivan Fernandez Calvo Component/s: ssh-credentials-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Gregor Philp commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException ok I will try that. This was a new bug I filed this morning so I don't know how it got merged onto this one. I created a new issue. It is breaking or production stack with over 700 jobs and over 400 users Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
Title: Message Title
Ke Liu edited a comment on JENKINS-13619
Re: Add ability to throttle number of concurrent builds of matrix configurations per node
Sorry to re-surface such an old thread. I am trying to do exactly the same thing. I have a matrix build of N child jobs, and M nodes. Each node can only execute one child job at the same time, while child jobs on different nodes don't interfere with each other. Child jobs from different builds don't interfere with each other as long as they don't run on the same node.Is there any example that shows how this can be set up? Right now I observe multiple child jobs being scheduled on the same node. My current configuration (in groovy DSL) is like this (I deleted a bunch of unrelated stuff to make it clearer). Thanks. {code:java} def numShards = 5 matrixJob('') { description('') axes { text('SHARD', (0..(numShards - 1)).collect \ { it.toString() }) label('slaves', "some-label") } concurrentBuild() throttleConcurrentBuilds { maxPerNode(1) } steps { shell('some command') }} {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
Title: Message Title
Ke Liu commented on JENKINS-13619
Re: Add ability to throttle number of concurrent builds of matrix configurations per node
Sorry to re-surface such an old thread. I am trying to do exactly the same thing. I have a matrix build of N child jobs, and M nodes. Each node can only execute one child job at the same time, while child jobs on different nodes don't interfere with each other. Child jobs from different builds don't interfere with each other as long as they don't run on the same node. Is there any example that shows how this can be set up? Right now I observe multiple child jobs being scheduled on the same node. My current configuration (in groovy DSL) is like this (I deleted a bunch of unrelated stuff to make it clearer). Thanks. def numShards = 5 matrixJob('') { description('') axes { text('SHARD', (0..(numShards - 1)).collect \{ it.toString() } ) label('slaves', "some-label") } concurrentBuild() throttleConcurrentBuilds { maxPerNode(1) } steps { shell('some command') } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-54746
Re: Can't connect via SSH on 1.29.1
I have tested some configuration to try to replicate the issue, I could not. These are the step I made:
Start vanilla Jenkins core 2.157 + ssh-slaves 1.26 + ssh-credential 1.12
Create 3 SSH credentials "From the Jenkins master ~/.ssh", "From a file on Jenkins master", and "Enter directly"
Create 3 SSH agents using the credential created before
Check that every agent connect
Upgrade to ssh-slaves 1.29.4 + ssh-credential 1.14 (it is a required dependency)
Restart Jenkins
Check every agent connect
Check every credential is migrated to use DirectEntryPrivateKeySource ("Enter directly")
I check the code of ssh-credentials, all the credential source type have the proper method readResolve to migrate to "Enter directly", so there is something I do not see. In any case, the issue is related to ssh-credentials and a deprecated type of credentials, the workaround it is to recreate the credential with the same ID using "Enter directly" for the key, probably if you only save again the credential it will be migrated. I will put a note in the troubleshooting guide and on changelog breaking changes.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-55231) Declarative Docker executors cannot pull from private docker repo
Title: Message Title Jon B updated an issue Jenkins / JENKINS-55231 Declarative Docker executors cannot pull from private docker repo Change By: Jon B Summary: Declarative Docker executors in Declarative pipelines don't seem to work with Artifactory for some reason cannot pull from private docker repo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55436) warnings-ng is not backwards compatible
Title: Message Title Ulli Hafner commented on JENKINS-55436 Re: warnings-ng is not backwards compatible Interesting, on our CI we have both plugins working in parallel without problems: https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/ https://ci.jenkins.io/job/Plugins/job/analysis-model/job/master/ Which version of the workflow cps plugin do you have installed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55408) Configure Quality Gate Thresholds per Tool in post-build action
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55408 Configure Quality Gate Thresholds per Tool in post-build action Change By: Ulli Hafner Comment: [~roufique2]: what is the reason for reopening? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55408) Configure Quality Gate Thresholds per Tool in post-build action
Title: Message Title Ulli Hafner closed an issue as Won't Fix Jenkins / JENKINS-55408 Configure Quality Gate Thresholds per Tool in post-build action Change By: Ulli Hafner Status: Reopened Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55408) Configure Quality Gate Thresholds per Tool in post-build action
Title: Message Title Ulli Hafner assigned an issue to Ulli Hafner Jenkins / JENKINS-55408 Configure Quality Gate Thresholds per Tool in post-build action Change By: Ulli Hafner Assignee: Roufique Hossain Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55408) Configure Quality Gate Thresholds per Tool in post-build action
Title: Message Title Ulli Hafner commented on JENKINS-55408 Re: Configure Quality Gate Thresholds per Tool in post-build action Roufique Hossain: what is the reason for reopening? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Ulli Hafner commented on JENKINS-55368 Re: No issues found when parsing Eclipse ECJ output from console log during maven build I hope that someone will fix our bot that normally adds Jira comments of the associated commits. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55442) Need filter by message text
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55442 Need filter by message text Change By: Ulli Hafner Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55442) Need filter by message text
Title: Message Title Ulli Hafner commented on JENKINS-55442 Re: Need filter by message text In the next release the maven console parser will have an additional `type` property that contains the plugin/goal of the warning. Would that already help? On the other hand, adding another filter should not be hard to add. Interested in providing a PR? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55457) Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-55457 Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55449) Update Jenkins codebase '@since TODO' with actual version
Title: Message Title Baptiste Mathus updated JENKINS-55449 Jenkins / JENKINS-55449 Update Jenkins codebase '@since TODO' with actual version Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55449) Update Jenkins codebase '@since TODO' with actual version
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-55449 Update Jenkins codebase '@since TODO' with actual version Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55449) Update Jenkins codebase '@since TODO' with actual version
Title: Message Title Baptiste Mathus started work on JENKINS-55449 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55434) Enable repository upload permissions for project contributors
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55434 Enable repository upload permissions for project contributors Change By: David Olorundare Upload permissions are required for plugin-contributors in order to upload and deploy release artifacts to the Jenkins Artifactory repository.This task involves enabling those permissions, as cited below for more details. [ https://github.com/jenkins-infra/repository-permissions-updater |https://github.com/jenkins-infra/repository-permissions-updater)] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55434) Enable repository upload permissions for project contributors
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55434 Enable repository upload permissions for project contributors Change By: David Olorundare Upload permissions are required for plugin-contributors in order to upload and deploy release artifacts to the Jenkins Artifactory repository.This task involves enabling those permissions, as cited here below for more details. [https://github.com/jenkins-infra/repository-permissions-updater |https://github.com/jenkins-infra/repository-permissions-updater)] for more details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55434) Enable repository upload permissions for project contributors
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55434 Enable repository upload permissions for project contributors Change By: David Olorundare Upload permissions are required for plugin-contributors in order to upload and deploy release artifacts to the Jenkins Artifactory repository.This task involves enabling those permissions, as cited here - [https://github.com/jenkins-infra/repository-permissions-updater|https://github.com/jenkins-infra/repository-permissions-updater)] for more details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54088) Log audit events for user creation
Title: Message Title David Olorundare updated JENKINS-54088 Jenkins / JENKINS-54088 Log audit events for user creation Change By: David Olorundare Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54965) Create unit tests for code implementations
Title: Message Title David Olorundare updated JENKINS-54965 Jenkins / JENKINS-54965 Create unit tests for code implementations Change By: David Olorundare Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55457) Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building
Title: Message Title Karl Shultz commented on JENKINS-55457 Re: Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building I had a boo-boo in my Jenkinsfile. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55413) [UI] Newly added roles on the 'Manage Roles' page can't be removed by clicking on the cross icon
Title: Message Title Vishal Khanna started work on JENKINS-55413 Change By: Vishal Khanna Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55450) Checkout of library to be used in a Pipeline script with SVN hangs
Title: Message Title Wes Elliott edited a comment on JENKINS-55450 Re: Checkout of library to be used in a Pipeline script with SVN hangs Seems like the same issue but at the very least related . to JENKINS-55448 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55450) Checkout of library to be used in a Pipeline script with SVN hangs
Title: Message Title Wes Elliott commented on JENKINS-55450 Re: Checkout of library to be used in a Pipeline script with SVN hangs Seems like the same issue but at the very least related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55457) Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building
Title: Message Title Mark Waite commented on JENKINS-55457 Re: Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building Thanks for the report and for testing the plugin! The checkout step does not know about the shell step that performed the cd command. Thus all the checkout steps are being performed in parallel in the same working directory. Chaos ensues (interesting test of command line git locking a directory concurrently and jgit locking a directory concurrently). You need to place the checkout (and probably the predecessor steps) in a ws block or a dir block. For an example, refer to the examples in Jenkinsfile 1 Jenkinsfile 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55457) Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-55457
Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building
Change By:
Karl Shultz
*Summary*Declarative Pipeline jobs which use a set of {{parallel}} stages to concurrently download several branches of a different repository via the {{checkout}} step can fail. The appearance is that commit hashes get confused between the two repositories. The Jenkinsfile is stored in SCM, and Git Client is expecting the commit SHA for the Jenkinsfile, but instead reads the commit SHA for one of {{checkout}} steps in the pipeline itself.*Frequency*100% of the time. But this has been a real devil to try and explain...*What this test is doing** This Jenkinsfile ([which can be seen here|https://github.com/kshultzCB/empty-repo/blob/version-for-github-no-submodules/Jenkinsfile]) does a {{checkout}} of each individual branch of [this repository|https://github.com/kshultzCB/repo_without_submodules]. * Of the five branches that get checked out, three are using {{jgit}} as their checkout tool, and two are using {{Default}}. * Each branch that gets checked out is full of little more than a lot of ASCII gibberish. This is to make sure the checkouts take a long enough time that the pipeline stages will actually execute in parallel for more than a fraction of a second.*Steps to recreate*1. Create a new Pipeline job. Use the following settings:* Definition: Pipeline script from SCM* SCM: Git* Repository URL: https://github.com/kshultzCB/empty-repo.git* Credentials: Any credentials you already have set up for public GitHub repos should work fine. These repos are all public.* Branches to build: {{version-for-github-no-submodules}} . This is important , the other branches will do {{checkout}} s on a different repo .* The remaining settings are all left to default:** Git executable: Default** Repository browser: (Auto)** Additional behaviors: (None set)** Script path: Jenkinsfile** Lightweight checkout: checked !image-2019-01-08-14-34-10-612.png|thumbnail! 2. Save the Pipeline3. Click "Build Now"4. Watch the build process via the streaming console log. The first sign of trouble looks to be a {{GitException}}, which reads:{code:none}ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from https://github.com/kshultzCB/repo_without_submodules.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:903) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1130) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1161) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) at hudson.security.ACL.impersonate(ACL.java:290) at
[JIRA] (JENKINS-55457) Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-55457
Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building
Change By:
Karl Shultz
*Summary*Declarative Pipeline jobs which use a set of {{parallel}} stages to concurrently download several branches of a different repository via the {{checkout}} step can fail. The appearance is that commit hashes get confused , because between the two repositories. The Jenkinsfile is stored in SCM, and Git Client looks is expecting the commit SHA for the Jenkinsfile, but instead reads the commit SHA for one of {{checkout}} steps in the pipeline itself.*Frequency*100% of the time. But this has been a real devil to try and explain...*What this test is doing** This Jenkinsfile ([which can be seen here|https://github.com/kshultzCB/empty-repo/blob/version-for-github-no-submodules/Jenkinsfile]) does a {{checkout}} of each individual branch of [this repository|https://github.com/kshultzCB/repo_without_submodules]. * Of the five branches that get checked out, three are using {{jgit}} as their checkout tool, and two are using {{Default}}. * Each branch that gets checked out is full of little more than a lot of ASCII gibberish. This is to make sure the checkouts take a long enough time that the pipeline stages will actually execute in parallel for more than a fraction of a second.*Steps to recreate*1. Create a new Pipeline job. Use the following settings:* Definition: Pipeline script from SCM* SCM: Git* Repository URL: https://github.com/kshultzCB/empty-repo.git* Credentials: Any credentials you already have set up for public GitHub repos should work fine. These repos are all public.* Branches to build: {{version-for-github-no-submodules}} . This is important.* The remaining settings are all left to default:** Git executable: Default** Repository browser: (Auto)** Additional behaviors: (None set)** Script path: Jenkinsfile** Lightweight checkout: checked !image-2019-01-08-14-34-10-612.png|thumbnail! 2. Save the Pipeline3. Click "Build Now"4. Watch the build process via the streaming console log. The first sign of trouble looks to be a {{GitException}}, which reads:{code:none}ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from https://github.com/kshultzCB/repo_without_submodules.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:903) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1130) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1161) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) at hudson.security.ACL.impersonate(ACL.java:290) at
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Mark Waite commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException Gregor Philp the original bug report is related to a large repository and a timeout. The stack trace you're reporting is significantly different from the stack trace in the description of this bug report. The differences are evident because your stack trace does not include the message: ERROR: Timeout after 10 minutes I suspect you'll be better served by first asking for help on one of the chat locations, or on the Jenkins users mailing list. They will tend to ask you questions that will help you identify the problem and will help you decide if a bug report is needed. Some of the questions that they will probably ask in those places will include things like: What versions of Jenkins and plugins were you running when it worked? What versions of Jenkins and plugins were you running after it stopped working? What operating system is running Jenkins? What operating system is running the agent where the failure happens? Is the agent connected to the master with ssh, JNLP, or some other way? Does the failure happen on multiple agents? The chat and the mailing list have many more readers than individual bug reports, especially individual bug reports that are already resolved. If you don't find an answer through chat and the mailing list, you'll need to open a new bug report. If you open a new bug report, please be sure to include answers to those questions and the other items identified in "How to report an issue". Add Comment
[JIRA] (JENKINS-55457) Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-55457 Concurrent git checkouts confuse SHAs between location of Jenkinsfile and the repos its building Change By: Karl Shultz Summary: Concurrent git checkouts confuse SHAs between pipeline code location of Jenkinsfile and what is being checked out the repos its building Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55457) Concurrent git checkouts confuse SHAs between pipeline code and what is being checked out
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-55457 Concurrent git checkouts confuse SHAs between pipeline code and what is being checked out Issue Type: Bug Assignee: Mark Waite Attachments: image-2019-01-08-14-34-10-612.png Components: git-client-plugin, git-plugin Created: 2019-01-08 19:55 Environment: * Jenkins core 2.156 * All experimental update center level plugins, including git and git-client betas Priority: Major Reporter: Karl Shultz Summary Declarative Pipeline jobs which use a set of parallel stages to concurrently download several branches of a repository via the checkout step can fail. The appearance is that commit hashes get confused, because the Jenkinsfile is stored in SCM, and Git Client looks is expecting the commit SHA for the Jenkinsfile, but instead reads the commit SHA for one of checkout steps in the pipeline itself. Frequency 100% of the time. But this has been a real devil to try and explain... What this test is doing This Jenkinsfile (which can be seen here) does a checkout of each individual branch of this repository. Of the five branches that get checked out, three are using jgit as their checkout tool, and two are using Default. Each branch that gets checked out is full of little more than a lot of ASCII gibberish. This is to make sure the checkouts take a long enough time
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title
Gregor Philp commented on JENKINS-47660
Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
This is not to do with a large repository or timeout. The repo is extremely small I am testing with and the job fails in just over 20 seconds. I remove that plugin and the job works fine. timestamps { node ('ECS-CO7-LATEST') { stage ('Checkout') { checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: '***, url: 'g...@github.move.com:IT-Operations/aws-certificates.git']]]) } stage ('sleep') { sh ''' sleep 20 ''' } stage ('Clean') { cleanWs() } } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55456) PowerMock version lock on RC4
Title: Message Title Adrien Lecharpentier created an issue Jenkins / JENKINS-55456 PowerMock version lock on RC4 Issue Type: Bug Assignee: Adrien Lecharpentier Components: plugin-pom Created: 2019-01-08 19:33 Priority: Minor Reporter: Adrien Lecharpentier PowerMock project released the version 2.0.0 so we could upgrade it in the plugin pom. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55455) after upgrading plugins for pipeline: Declarative, pipeline jobs cannot checkout from GHE
Title: Message Title Andrew Bayer commented on JENKINS-55455 Re: after upgrading plugins for pipeline: Declarative, pipeline jobs cannot checkout from GHE What error are you getting? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55451) Use io.jenkins.plugins groupId
Title: Message Title Matt Sicker updated JENKINS-55451 Merged to master. Jenkins / JENKINS-55451 Use io.jenkins.plugins groupId Change By: Matt Sicker Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47660) ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException
Title: Message Title Gregor Philp commented on JENKINS-47660 Re: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException ERROR we get after upgrading these plugins and trying to checkout in a pipeline job 17:52:07 Cloning the remote Git repository 17:52:07 ERROR: Error cloning remote repo 'origin' 17:52:07 hudson.plugins.git.GitException: java.io.IOException: Remote call on JNLP4-connect connection from ip-10-192-23-154.us-west-2.compute.internal/10.192.23.154:23354 failed 17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:169) 17:52:07 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 17:52:07 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 17:52:07 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 17:52:07 at java.lang.reflect.Method.invoke(Method.java:498) 17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) 17:52:07 at com.sun.proxy.$Proxy140.execute(Unknown Source) 17:52:07 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146) 17:52:07 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186) 17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) 17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) 17:52:07 at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) 17:52:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) 17:52:07 at hudson.security.ACL.impersonate(ACL.java:290) 17:52:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48) 17:52:07 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 17:52:07 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 17:52:07 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 17:52:07 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 17:52:07 at java.lang.Thread.run(Thread.java:748) 17:52:07 Caused by: java.io.IOException: Remote call on JNLP4-connect connection from ip-10-192-23-154.us-west-2.compute.internal/10.192.23.154:23354 failed 17:52:07 at hudson.remoting.Channel.call(Channel.java:961) 17:52:07 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) 17:52:07 ... 19 more 17:52:07 Caused by: java.lang.IllegalAccessError: tried to access field hudson.remoting.Channel.executor from class org.jenkinsci.remoting.util.AnonymousClassWarnings 17:52:07 at org.jenkinsci.remoting.util.AnonymousClassWarnings.check(AnonymousClassWarnings.java:65) 17:52:07 at org.jenkinsci.remoting.util.AnonymousClassWarnings$1.annotateClass(AnonymousClassWarnings.java:121) 17:52:07 at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1290) 17:52:07 at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1231) 17:52:07 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1427) 17:52:07 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178) 17:52:07 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) 17:52:07 at hudson.console.ConsoleNote.encodeToBytes(ConsoleNote.java:185) 17:52:07 at hudson.console.ConsoleNote.encode(ConsoleNote.java:211) 17:52:07 at hudson.plugins.timestamper.TimestampNotesOutputStream.eol(TimestampNotesOutputStream.java:70) 17:52:07 at
[JIRA] (JENKINS-55455) after upgrading plugins for pipeline: Declarative, pipeline jobs cannot checkout from GHE
Title: Message Title Gregor Philp created an issue Jenkins / JENKINS-55455 after upgrading plugins for pipeline: Declarative, pipeline jobs cannot checkout from GHE Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-01-08 19:23 Environment: Jenkins 2.150.1 Plugins we have current version of Pipeline: Declarative v1.3.2 (trying to upgrade to 1.3.4) Pipeline: Declarative Extension Points API v1.3.2 (trying to upgrade to 1..3.4) Pipeline: Model API v1.3.2 (trying to upgrade to 1.3.4) Priority: Major Reporter: Gregor Philp Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54893) Error provisioning slaves with ECS plugin 1.18
Title: Message Title Olivier Mignault commented on JENKINS-54893 Re: Error provisioning slaves with ECS plugin 1.18 Thank you Philipp Garbe, I can confirm 1.19 fixed our issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55451) Use io.jenkins.plugins groupId
Title: Message Title David Olorundare updated JENKINS-55451 Jenkins / JENKINS-55451 Use io.jenkins.plugins groupId Change By: David Olorundare Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54329) Jenkins Does Not Use Private IP Address by Default For VPC+PublicIP Slaves
Title: Message Title Daniel Garzon commented on JENKINS-54329 Re: Jenkins Does Not Use Private IP Address by Default For VPC+PublicIP Slaves Dustin Brown FABRIZIO MANFREDI were you able to take a look at this issue? I am experiencing the same problem, and it is a deal breaker. Is there a way to force the plugin to only use the Private IP when SSH'ing? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Chad Williams updated an issue Jenkins / JENKINS-55448 File cleaning failure, old build and plugin update Change By: Chad Williams Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Chad Williams commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update We experience the same/related issues: This is a critical bug for us, since test result parsing via the xUnit plugin fails and successful builds are marked as failures. I can confirm that downgrading to 2.156 fixes the issue. jenkins.util.io.CompositeIOException: Unable to remove directory /foo/bar/generatedJUnitFiles/d87f0d22-c235-43cd-8272-34ce92150592/GoogleTest with directory contents: [/foo/bar/generatedJUnitFiles/d87f0d22-c235-43cd-8272-34ce92150592/GoogleTest/TEST-809dd980-e514-4260-b749-9079e250f828.xml, /foo/bar/generatedJUnitFiles/d87f0d22-c235-43cd-8272-34ce92150592/GoogleTest/TEST-2d8be771-6364-49d8-9573-c51a974a44bc.xml] at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:233) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:191) at jenkins.util.io.PathRemover.forceRemoveFile(PathRemover.java:71) at hudson.Util.deleteFile(Util.java:255) at hudson.FilePath.deleteRecursive(FilePath.java:1305) at hudson.FilePath.access$1600(FilePath.java:213) at hudson.FilePath$DeleteRecursive.invoke(FilePath.java:1274) at hudson.FilePath$DeleteRecursive.invoke(FilePath.java:1270) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3086) at hudson.remoting.UserRequest.perform(UserRequest.java:212) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) java.nio.file.DirectoryNotEmptyException: /foo/bar/generatedJUnitFiles/d87f0d22-c235-43cd-8272-34ce92150592/GoogleTest at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) at java.nio.file.Files.deleteIfExists(Files.java:1165) at jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:220) at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:191) at jenkins.util.io.PathRemover.forceRemoveFile(PathRemover.java:71) at hudson.Util.deleteFile(Util.java:255) at hudson.FilePath.deleteRecursive(FilePath.java:1305) at hudson.FilePath.access$1600(FilePath.java:213) at hudson.FilePath$DeleteRecursive.invoke(FilePath.java:1274) at hudson.FilePath$DeleteRecursive.invoke(FilePath.java:1270) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3086) at hudson.remoting.UserRequest.perform(UserRequest.java:212) 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) java.nio.file.DirectoryNotEmptyException:
[JIRA] (JENKINS-55451) Use io.jenkins.plugins groupId
Title: Message Title David Olorundare updated JENKINS-55451 Jenkins / JENKINS-55451 Use io.jenkins.plugins groupId Change By: David Olorundare Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55408) Configure Quality Gate Thresholds per Tool in post-build action
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-55408 Configure Quality Gate Thresholds per Tool in post-build action Change By: R. Tyler Croy Comment: *Rohit travels & tours* Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55451) Use io.jenkins.plugins groupId
Title: Message Title David Olorundare updated JENKINS-55451 Jenkins / JENKINS-55451 Use io.jenkins.plugins groupId Change By: David Olorundare Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55454) Could not find matching constructor for: hudson.plugins.ec2.AmazonEC2Cloud(java.lang.String, java.lang.Boolean, java.lang.String, java.lang.String, java.lang.String, java.lang.S
Title: Message Title Michal Matyjek commented on JENKINS-55454 Re: Could not find matching constructor for: hudson.plugins.ec2.AmazonEC2Cloud(java.lang.String, java.lang.Boolean, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.util.ArrayList) Exception goes away after downgrading to 1.39 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55451) Use io.jenkins.plugins groupId
Title: Message Title David Olorundare updated JENKINS-55451 Jenkins / JENKINS-55451 Use io.jenkins.plugins groupId Change By: David Olorundare Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55454) Could not find matching constructor for: hudson.plugins.ec2.AmazonEC2Cloud(java.lang.String, java.lang.Boolean, java.lang.String, java.lang.String, java.lang.String, java.lang.S
Title: Message Title Michal Matyjek created an issue Jenkins / JENKINS-55454 Could not find matching constructor for: hudson.plugins.ec2.AmazonEC2Cloud(java.lang.String, java.lang.Boolean, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.util.ArrayList) Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-01-08 17:25 Priority: Major Reporter: Michal Matyjek Seeing the attached in logs, looks new in 1.41, not seeing it in 1.39 ``` groovy.lang.GroovyRuntimeException: Could not find matching constructor for: hudson.plugins.ec2.AmazonEC2Cloud(java.lang.String, java.lang.Boolean, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.util.ArrayList) at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1732) at groovy.lang.MetaClassImpl.invokeConstructor(MetaClassImpl.java:1532) at org.codehaus.groovy.runtime.callsite.MetaClassConstructorSite.callConstructor(MetaClassConstructorSite.java:49) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:60) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:235) at init-ec2.run(init-ec2.groovy:112) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:585) at jenkins.util.groovy.GroovyHookScript.execute(GroovyHookScript.java:136) at jenkins.util.groovy.GroovyHookScript.execute(GroovyHookScript.java:127) at jenkins.util.groovy.GroovyHookScript.run(GroovyHookScript.java:110) at hudson.init.impl.GroovyInitScript.init(GroovyInitScript.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Tyler Pickett updated an issue Jenkins / JENKINS-55453 Github PR creating job but not building Change By: Tyler Pickett Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55433) P4Groovy - P4Groovy fails to run on agent
Title: Message Title Karl Wirth stopped work on JENKINS-55433 Change By: Karl Wirth Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55433) P4Groovy - P4Groovy fails to run on agent
Title: Message Title Karl Wirth started work on JENKINS-55433 Change By: Karl Wirth Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55433) P4Groovy - P4Groovy fails to run on agent
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-55433 P4Groovy - P4Groovy fails to run on agent Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55433) P4Groovy - P4Groovy fails to run on agent
Title: Message Title
Karl Wirth updated an issue
Jenkins / JENKINS-55433
P4Groovy - P4Groovy fails to run on agent
Change By:
Karl Wirth
*Duplication* # Go to an agent's script console (http:///computer//script) # Run this script{code:java}import org.jenkinsci.plugins.p4.workspace.StreamWorkspaceImpl;import org.jenkinsci.plugins.p4.groovy.P4Groovy;def ws = new StreamWorkspaceImpl('none', false, '//Stream_Depot/Main', 'job1-temp-branch1')def p4 = new P4Groovy('credential', null, ws, new FilePath(new File('workspace')))def result = p4.run('status'){code} # Error: 'java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong.' - Can also be duplicated by running the following script in a Jenkinsfile - {code:java} - def ws = [$class: 'StreamWorkspaceImpl', charset: 'none', format: env.JOB_NAME + '-temp-' + env.BRANCH_NAME, pinHost: false, streamName: '//Stream_Depot/' + env.BRANCH_NAME] def p4 = p4(credential: 'credential', workspace: ws) def result = p4.run('streams') {code} - *Expected Result*I can use P4Groovy on an agent with no errors.*Workaround*Run P4Groovy commands in a separate stage running on the master. If data is needed, use Environment Variables to transfer variables to agent.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title Tyler Pickett created an issue Jenkins / JENKINS-55453 Github PR creating job but not building Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2019-01-08 17:04 Environment: Jenkins Version: 1.150.1 (LTS) running in the official docker image Plugins: Amazon EC2 plugin: 1.41 Amazon Elastic Container Service: 1.18 Amazon Web Services SDK: 1.11.457 AnsiColor: 0.6.1 Apache HttpComponents Client 4.x API Plugin: 4.5.5-3.0 Authentication Tokens API Plugin: 1.3 Autofavorite for Blue Ocean: 1.2.2 Basic Branch Build Strategies Plugin: 1.1.1 Bitbucket Branch Source Plugin: 2.3.0 Bitbucket Pipeline for Blue Ocean: 1.10.1 Blue Ocean: 1.10.1 Blue Ocean Core JS: 1.10.1 Blue Ocean Pipeline Editor: 1.10.1 bouncycastle API Plugin: 2.17 Branch API Plugin: 2.1.2 Build Timeout: 1.19 CloudBees AWS Credentials Plugin: 1.24 Command Agent Launcher: 1.2 Common API for Blue Ocean: 1.10.1 Config API for Blue Ocean: 1.10.1 Credentials Binding Plugin: 1.17 Credentials Plugin: 2.1.18 Dashboard for Blue Ocean: 1.10.1 Datadog Plugin: 0.6.5 Design Language: 1.10.1 Display URL API: 2.3.0 Display URL for Blue Ocean: 2.2.0 Docker Commons Plugin: 1.13 Docker Pipeline: 1.17 Durable Task Plugin: 1.28 Events API for Blue Ocean: 1.10.1 Favorite: 2.3.2 Folders Plugin: 6.7 Gerrit Trigger: 2.28.0 Git client plugin: 2.7.5 Git Pipeline for Blue Ocean: 1.10.1 Git plugin: 3.9.1 GIT server Plugin: 1.7 GitHub API Plugin: 1.95 GitHub Branch Source Plugin: 2.4.1 GitHub Pipeline for Blue Ocean: 1.10.1 GitHub plugin: 1.29.3 Global Post Script Plugin: 1.1.4 Handy Uri Templates 2.x API Plugin: 2.1.6-1.0 HTML Publisher plugin: 1.17 i18n for Blue Ocean: 1.10.1 Jackson 2 API Plugin: 2.9.8 JaCoCo plugin: 3.0.4 Javadoc Plugin: 1.4 _javascript_ GUI Lib: ACE Editor bundle plugin: 1.1 _javascript_ GUI Lib: Handlebars bundle plugin: 1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin: 1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin: 1.1.1 JDK Tool Plugin: 1.2 JIRA Integration for Blue Ocean: 1.10.1 JIRA plugin: 3.0.5 Job/Queue/Slaves Monitoring Plugin: 1.4 JSch dependency plugin: 0.1.54.2 JUnit Plugin: 1.26.1 JWT for Blue Ocean: 1.10.1 Lockable Resources plugin: 2.3 Mailer Plugin: 1.23 Matrix Authorization Strategy Plugin: 2.3 Matrix Project Plugin: 1.13 Maven Integration plugin: 3.2 Mercurial plugin: 2.4 Metrics Plugin: 4.0.2.2 Node Iterator API Plugin: 1.5.0 Personalization for Blue Ocean: 1.10.1 Pipeline: 2.6 Pipeline Graph Analysis Plugin: 1.9 Pipeline implementation for Blue Ocean: 1.10.1 Pipeline SCM API for Blue
[JIRA] (JENKINS-55433) P4Groovy - P4Groovy fails to run on agent
Title: Message Title Karl Wirth commented on JENKINS-55433 Re: P4Groovy - P4Groovy fails to run on agent Hi Dylan H - Thanks for getting back to me. I'm going to pass this onto the developers to triage it. They can then decide. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55433) P4Groovy - P4Groovy fails to run on agent
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55433 P4Groovy - P4Groovy fails to run on agent Change By: Karl Wirth Labels: P4_SUPPORT P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55430) P4Groovy - Credential not found error does not propagate
Title: Message Title Charusheela Bopardikar started work on JENKINS-55430 Change By: Charusheela Bopardikar Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53361) Copy files using a regular expresion
Title: Message Title Naresh Rayapati updated JENKINS-53361 Jenkins / JENKINS-53361 Copy files using a regular expresion Change By: Naresh Rayapati Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53361) Copy files using a regular expresion
Title: Message Title Naresh Rayapati commented on JENKINS-53361 Re: Copy files using a regular expresion Merged PR: https://github.com/jenkinsci/ssh-steps-plugin/pull/13 Will release it after further testing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53157) ECS Agents hang during creation never being purged
Title: Message Title Philipp Garbe updated JENKINS-53157 Jenkins / JENKINS-53157 ECS Agents hang during creation never being purged Change By: Philipp Garbe Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53157) ECS Agents hang during creation never being purged
Title: Message Title Philipp Garbe closed an issue as Fixed Jenkins / JENKINS-53157 ECS Agents hang during creation never being purged Change By: Philipp Garbe Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55452) REST API blocked by SECURITY-595
Title: Message Title James Holderness created an issue Jenkins / JENKINS-55452 REST API blocked by SECURITY-595 Issue Type: Bug Assignee: Unassigned Components: next-executions-plugin Created: 2019-01-08 16:24 Environment: Jenkins version 2.157 next-executions plugin version 1.0.12 Priority: Minor Reporter: James Holderness I've been using the REST API exposed by JENKINS-36210, but since the SECURITY-595 fix was applied (I think in Jenkins version 2.154), that API has stopped working. The widgets API link now returns a 404 error, and I see the following warning in the logs: WARNING: New Stapler routing rules result in the URL "/view/all/widgets/2/api/json" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "method hudson.model.View getWidgets". Learn more: [https://jenkins.io/redirect/stapler-routing] I can get the API working again by adding that method to the whitelist, but the documentation here suggests that it would be preferable if the component could be changed to prevent the problem in the first place.
[JIRA] (JENKINS-55436) warnings-ng is not backwards compatible
Title: Message Title Matthias Fuchs commented on JENKINS-55436 Re: warnings-ng is not backwards compatible I updated the story. Of course I have no issues with the design decision as long as I can have both the old and new plugins installed and working side-by-side. Which unfortunately does not seem to be the case, see my updates. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55436) warnings-ng is not backwards compatible
Title: Message Title
Matthias Fuchs updated an issue
Jenkins / JENKINS-55436
warnings-ng is not backwards compatible
Change By:
Matthias Fuchs
Many of the jobs I use have collect static analysis the following way (OLD) :{code}pmd canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '', pattern: "$reports/pmd.xml",unHealthy: '', unstableTotalAll: '0'checkstyle canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '', pattern: "$reports/checkstyle.xml", unHealthy: '', unstableTotalAll: '0'androidLint canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '', pattern: "$reports/lint*.xml", unHealthy: '', unstableTotalAll: '0'{code}Now I want to migrate them to warnings-ng with the following code (NEW) :{code}recordIssues(tools: [androidLint(pattern: "$reports/lint*.xml"), checkStyle(pattern: "$reports/checkstyle.xml"), pmdParser(pattern: "$reports/pmd.xml")], aggregatingResults: true, enabledForFailure: true){code}I face multiple issues though:# warnings-ng is not backwards compatible due to different parameters it accepts# having the Android Lint plugin, the Checkstyle plugin, and the PMD plugin installed alongside warnings-ng breaks builds# This means that I have to transition *all* jobs to warnings-ng which is simply not feasible, given that there are multiple branches that are build and given our policies. Especially I would have to perform the transition at once to avoid failing builds.I think the plugin should be backwards compatible by accepting the additional parameters I listed above. Now when I build a job that uses OLD I get the following error:{noformat}org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 67: Invalid parameter "canComputeNew", did you mean "name"? @ line 67, column 33. pmd canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '', pattern: "$reports/pmd.xml",unHealthy: '', unstableTotalAll: '0' ^WorkflowScript: 67: Invalid parameter "canRunOnFailed", did you mean "name"? @ line 67, column 55. canComputeNew: false, canRunOnFa ^WorkflowScript: 67: Invalid parameter "defaultEncoding", did you mean "reportEncoding"? @ line 67, column 77.false, canRunOnFailed: true, defaultEnc ^WorkflowScript: 67: Invalid parameter "healthy", did you mean "name"? @ line 67, column 98. d: true, defaultEncoding: '', healthy: ' ^WorkflowScript: 67: Invalid parameter "unHealthy", did you mean "name"? @ line 67, column 147. n: "$reports/pmd.xml",unHealthy: ^WorkflowScript: 67: Invalid parameter "unstableTotalAll", did you mean "name"? @ line 67, column 162. d.xml",unHealthy: '', unstableTo ^WorkflowScript: 69: Invalid parameter "canComputeNew", did you mean "name"? @ line 69, column 33.
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Philipp Garbe closed an issue as Fixed Jenkins / JENKINS-54428 ECS plugin fails if task definition ARN is used Change By: Philipp Garbe Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54898) ECS Plugin 1.18 cannot launch slaves
Title: Message Title Philipp Garbe updated JENKINS-54898 Jenkins / JENKINS-54898 ECS Plugin 1.18 cannot launch slaves Change By: Philipp Garbe Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
