[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Bart Devriendt commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file We are having this issue as well since we upgraded from 3.8.0 to 3.9.1. At random times we have workspaces that cannot be cleaned anymore and the only solution seems to be to restart the Jenkins agent service. This only occurs on our windows slaves, Linux slaves are not impacted. 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-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Javier Delgado updated JENKINS-47643 Jenkins / JENKINS-47643 Allow [ci skip] to work for non-pull request changes Change By: Javier Delgado 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-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Javier Delgado updated JENKINS-47643 Jenkins / JENKINS-47643 Allow [ci skip] to work for non-pull request changes Change By: Javier Delgado 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Pavel Novak commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error joe ferr Yes, I can confirm that, once we upgraded to the latest ( git plugin to 4.0.0-rc and git client plugin to 3.0.0-rc), git operations were not working correctly. Downgrade to 3.9.1 and 2.7.2 solved the issue, but it seems (of course) busy file persist. 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-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title Stuart Rowe edited a comment on JENKINS-55497 Re: BlueOcean Pipeline View sometimes shows No Changes Visiting the activity page for the project seems to populate the changeset: * blue/organizations/jenkins//activity However, if you return to the classic UI from the top navigation bar and then re-enter the BlueOcean pipeline view, the changeset is empty 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-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title Stuart Rowe commented on JENKINS-55497 Re: BlueOcean Pipeline View sometimes shows No Changes Visiting the activity page for the project seems to populate the changeset: blue/organizations/jenkins//activity 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-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title
Stuart Rowe updated an issue
Jenkins / JENKINS-55497
BlueOcean Pipeline View sometimes shows No Changes
Change By:
Stuart Rowe
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset.The changeset for a run doesn't get populated until the next run of a project starts. The changeset doesn't appear to be populated when a run completes either.Navigation is to the BlueOcean pipeline view is from the classic run page by following the {{Open Blue Ocean}} link from the left hand navigation bar. This is occurring for standard pipeline jobs using {{checkout}} steps with the {{perforce}} scm configured (p4-plugin). The pipelines are defined using scripted pipeline. This issue applies to, but is not limited to, all of the following pages: * blue/organizations/jenkins//detail///pipeline * blue/organizations/jenkins//detail///pipeline/changes
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title
Stuart Rowe updated an issue
Jenkins / JENKINS-55497
BlueOcean Pipeline View sometimes shows No Changes
Change By:
Stuart Rowe
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset.The changeset for a run doesn't get populated until the next run of a project starts. The changeset doesn't appear to be populated when a run completes either.Navigation is to the BlueOcean pipeline view is from the classic run page by following the \ {{Open Blue Ocean}} link from the left hand navigation bar. This is occurring for standard pipeline jobs using {{checkout}} step steps with the {{perforce}} scm configured (p4-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-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title
Stuart Rowe updated an issue
Jenkins / JENKINS-55497
BlueOcean Pipeline View sometimes shows No Changes
Change By:
Stuart Rowe
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. The changeset for a run doesn't get populated until the next run of a project starts. The changeset doesn't appear to be populated when a run completes either.Navigation is to the BlueOcean pipeline view is from the classic run page by following the \{{Open Blue Ocean}} link from the left hand navigation bar. This is occurring for standard pipeline jobs using {{checkout}} step with the {{perforce}} scm (p4-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-55497) BlueOcean Pipeline View sometimes shows No Changes
Title: Message Title Stuart Rowe updated an issue Jenkins / JENKINS-55497 BlueOcean Pipeline View sometimes shows No Changes Change By: Stuart Rowe In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. 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-53053) Add support for readCSV / writeCSV pipeline steps
Title: Message Title Stuart Rowe updated JENKINS-53053 https://github.com/jenkinsci/pipeline-utility-steps-plugin/commit/113be3be3e76f48ea886f841cac57789724ce5ae Jenkins / JENKINS-53053 Add support for readCSV / writeCSV pipeline steps Change By: Stuart Rowe Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick resolved as Won't Fix Suemiao Rossignol please do not reopen. If necessary, file a separate (but linked) bug report with complete steps to reproduce from scratch as well as FINE logs from jenkins.branch.WorkspaceLocatorImpl. Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Jesse Glick Status: Reopened Resolved 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-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt edited a comment on JENKINS-55453 Re: Github PR creating job but not building This might be related to [https://github.com/jenkinsci/github-branch-source-plugin/pull/183] and the fact that the change was not applied to the GitHubPullRequestFilter class. edit: adding this here for posterity as well - https://issues.jenkins-ci.org/browse/JENKINS-46202 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-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt edited a comment on JENKINS-55453 Re: Github PR creating job but not building This might be related to [https://github.com/jenkinsci/github-branch-source-plugin/pull/183] and the fact that the change was not applied to the GitHubPullRequestFilter class. edit: adding this here for posterity as well - https://issues.jenkins-ci.org/browse/JENKINS-46202 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-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt commented on JENKINS-55453 Re: Github PR creating job but not building This might be related to https://github.com/jenkinsci/github-branch-source-plugin/pull/183 and the fact that the change was not applied to the `GitHubPullRequestFilter` class. 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-55453) Github PR creating job but not building
Title: Message Title Stephen Schmidt edited a comment on JENKINS-55453 Re: Github PR creating job but not building This might be related to [https://github.com/jenkinsci/github-branch-source-plugin/pull/183] and the fact that the change was not applied to the ` GitHubPullRequestFilter ` class. 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-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title Joseph Petersen commented on JENKINS-55927 Re: Jenkins multibranch pipeline scan is triggered in case of remote pull request merge Antonio Muñiz or Stephen Connolly perhaps either of you can speak to the reason for reindexing? Doing a quick look at gitea and github plugins none of them forces the reindex Should we perhaps remove 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-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Alex Simenduev commented on JENKINS-47643 Re: Allow [ci skip] to work for non-pull request changes Thanks a lot Javier Delgado. Works as expected! 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-19413) StaplerRequest.getAncestor does not work for lazy block
Title: Message Title Jesse Glick commented on JENKINS-19413 Re: StaplerRequest.getAncestor does not work for lazy block @ContextInPath as defined by Stephen Connolly might be useful here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55986) “Restart Parallel Stages” appears on the screen even when the user has no permissions
Title: Message Title Nicolae Pascu assigned an issue to Nicolae Pascu Jenkins / JENKINS-55986 “Restart Parallel Stages” appears on the screen even when the user has no permissions Change By: Nicolae Pascu Assignee: BlueOcean Security Nicolae Pascu 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-55986) “Restart Parallel Stages” appears on the screen even when the user has no permissions
Title: Message Title BlueOcean Security assigned an issue to BlueOcean Security Jenkins / JENKINS-55986 “Restart Parallel Stages” appears on the screen even when the user has no permissions Change By: BlueOcean Security Assignee: BlueOcean Security 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-55986) “Restart Parallel Stages” appears on the screen even when the user has no permissions
Title: Message Title BlueOcean Security assigned an issue to BlueOcean Security Jenkins / JENKINS-55986 “Restart Parallel Stages” appears on the screen even when the user has no permissions Change By: BlueOcean Security Assignee: BlueOcean Security 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-55986) “Restart Parallel Stages” appears on the screen even when the user has no permissions
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-55986 “Restart Parallel Stages” appears on the screen even when the user has no permissions Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2019-02-05 at 17.56.01.png Components: blueocean-plugin Created: 2019-02-05 23:05 Environment: BlueOcean 1.10.2 Jenkins 2.150.2 Priority: Minor Reporter: Oleg Nenashev “Restart Parallel Stages” appears on the screen even when the user has no permissions. See the attached screenshot CC Nicolae Pascu Add Comment
[JIRA] (JENKINS-55878) JEP-200 in System Groovy scripts
Title: Message Title Oleg Nenashev commented on JENKINS-55878 Re: JEP-200 in System Groovy scripts Jackie Hammell Although I understand your frustration and concerns, I believe you confuse JEP-200 and method whitelists in Script Security plugins. All your comments are about Script Security from what I see. JEP-200 is not related to blacklisting of methods in Script Security Plugin. JEP-200 introduces a whitelist for objects being serialized to the disk or over Remoting. If you use a non-whitelisted class for that purpose, it will fail in any language (Java, Groovy, Kotlin, whatever). https://github.com/jenkinsci/jep/tree/master/jep/200 > I am of the school of thought that an administrator should NEVER not be able to call a method that prohibits them from performing their duties https://wiki.jenkins.io/display/JENKINS/Permissive+Script+Security+Plugin , it will help. The default behavior is designed for protecting non-experienced users from shooting in their feet, but there are many ways to workaround the default behavior. Also, as an administrator, you can disable Sandbox for Pipeline jobs. Then you will be automatically getting your scripts approved as an administrator. > The answer you gave me 'Rewrite it in Java' It's not my answer. My answer was that you should avoid using Groovy classes and object wrappers when you write Groovy scripts. If you provide your script samples, I can give you more detailed suggestions > large corporation that uses CloubBees Jenkins There is no such thing like CloudBees Jenkins. There are products like CloudBees Jenkins Enterprise or CloudBees Jenkins Platform. Jenkins is Jenkins. https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage > I have raised my concerns with the CoudBees folks, and I would like to explain my concerns to you as well. FYI I work for CloudBees. If there is a question about JEP-200, you can ask the support team to escalate it to me on my teammates. But again, the feedback here does not look to be related to JEP-200. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title
krizleebear updated an issue
Jenkins / JENKINS-55985
Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Change By:
krizleebear
After upgrading P4 plugin from 1.9.4 to the latest version 1.9.6 the following error occurs in Jobs that use multi configuration parameters in client spec: {code:java}P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.Error detected at line 18.Null directory (//) not allowed in '//depot/dev//...'. at com.perforce.p4java.impl.mapbased.server.cmd.ResultMapParser.handleErrorStr(ResultMapParser.java:145)at com.perforce.p4java.impl.mapbased.server.cmd.ResultMapParser.parseCommandResultMapIfIsInfoMessageAsString(ResultMapParser.java:96)at com.perforce.p4java.impl.mapbased.server.cmd.ClientDelegator.updateClient(ClientDelegator.java:192)at com.perforce.p4java.impl.mapbased.server.Server.updateClient(Server.java:1506)at com.perforce.p4java.impl.mapbased.client.Client.update(Client.java:507)at org.jenkinsci.plugins.p4.client.ClientHelper.updateClient(ClientHelper.java:181)at org.jenkinsci.plugins.p4.client.ClientHelper.clientLogin(ClientHelper.java:159)at org.jenkinsci.plugins.p4.client.ClientHelper.(ClientHelper.java:101)at org.jenkinsci.plugins.p4.tasks.CheckoutTask.initialise(CheckoutTask.java:61)at org.jenkinsci.plugins.p4.PerforceScm.checkout(PerforceScm.java:477)at hudson.scm.SCM.checkout(SCM.java:504)at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)at hudson.model.Run.execute(Run.java:1810)at hudson.matrix.MatrixBuild.run(MatrixBuild.java:323)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429) ERROR: P4: Unable to initialise CheckoutTask: hudson.AbortException: Error in client specification.Error detected at line 18.Null directory (//) not allowed in '//depot/dev//…'. {code} I attached a repro case as Jenkins config.xml file. The relevant part of the client spec:{code:java}//depot/dev/${VARIANT}/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}/... {code}The parameter ${VARIANT} is defined as matrix job axis but is replaced with 'empty string' by version 1.9.6 of the plugin.I've also seen there have been changes regarding to multi branch config with this release, maybe this is a hint.
[JIRA] (JENKINS-55985) Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6
Title: Message Title krizleebear created an issue Jenkins / JENKINS-55985 Matrix params lead to Null directory (//) not allowed in '//depot/dev//...'. after upgrading to P4 plugin 1.9.6 Issue Type: Bug Assignee: Unassigned Attachments: config.xml Components: p4-plugin Created: 2019-02-05 22:49 Environment: Ubuntu 16.04, Jenkins LTS 2.150.2, P4 Plugin 1.9.6, various Perforce Helix server versions Priority: Blocker Reporter: krizleebear After upgrading P4 plugin from 1.9.4 to the latest version 1.9.6 the following error occurs in Jobs that use multi configuration parameters in client spec: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Error detected at line 18. Null directory (//) not allowed in '//depot/dev//...'. at com.perforce.p4java.impl.mapbased.server.cmd.ResultMapParser.handleErrorStr(ResultMapParser.java:145) at com.perforce.p4java.impl.mapbased.server.cmd.ResultMapParser.parseCommandResultMapIfIsInfoMessageAsString(ResultMapParser.java:96) at com.perforce.p4java.impl.mapbased.server.cmd.ClientDelegator.updateClient(ClientDelegator.java:192) at com.perforce.p4java.impl.mapbased.server.Server.updateClient(Server.java:1506) at com.perforce.p4java.impl.mapbased.client.Client.update(Client.java:507) at org.jenkinsci.plugins.p4.client.ClientHelper.updateClient(ClientHelper.java:181) at
[JIRA] (JENKINS-55878) JEP-200 in System Groovy scripts
Title: Message Title Jackie Hammell edited a comment on JENKINS-55878 Re: JEP-200 in System Groovy scripts Hi Oleg, Thanks for getting back to me. I would like to express my concerns regarding JEP200. It SCARES ME! I work for a large corporation that uses CloubBees Jenkins, I have raised my concerns with the CoudBees folks, and I would like to explain my concerns to you as well. I will let you know that I am an avid coder, with more years under my belt than I would like to admit anymore :). In the shop that I work in we have a "Self service" model with 13 people manning the helm of JIRA, Jenkins, Artifactory and Bitbucket, out of which 3-4 of us are hands on with regards to the Jenkins infrastructure supporting 4K+ developers. Additionally, the infrastructure I work in has 9 masters and 1 JOC, we push over 20K jobs through the infrastructure daily and at a guesstimate over 150K job configurations.1) My biggest concern is that Jenkins is the critical CI/CD backbone to all development work happening in the organization I work in, and there are many jobs that have heavy groovy scripts driving them, and not knowing what is being Blacklisted (until we hit the wall), and can no longer be Approved though the admin GUI has the potential of bring high visability visibility critical jobs to a grinding halt and catch fire state. We are currently testing in UAT, but it's impossible to test every job that has custom groovy code driving the pipeline.2) I am of the school of thought that an administrator should NEVER not be able to call a method that prohibits them from performing their duties. In my particular case, in the UAT environment the Node configurations need to be updated to ensure that the JDK can be found in the Tool Locations, in the use cases where the slaves don't have JAVA in their paths (yes, this happens more than you'd think). I don't believe in having to click on every /computer/ to get my job done when a simple groovy script will do it for me. I will quote Viktor Farcic, whom I believe you know 'GUI's are for managers and executive, not software engineers' - DevOps/Jenkins World San Francisco 2018.3) The answer you gave me 'Rewrite it in Java' is most doable, but my burning question is why can I accomplish my task in Java, yet the open source community has Blacklisted the method in Groovy? It seems counter productive to my rational brain. Is it up to the Jenkins project to try and save us from ourselves? I get and see the value of users not being able to access public static calls without being approved (we don't entirely trust them either), but Blacklisting an administrator from any call they choose to make out of necessity goes against the grain of everything I believe in.I hope this gives you some food for thought and I'm looking forward to your response. Cheers,Jackie Add Comment
[JIRA] (JENKINS-55673) Support SonarQube Generic Issues
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-55673 Support SonarQube Generic Issues Change By: Ulli Hafner Assignee: 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-55707) SpotBug: Unknown bug pattern
Title: Message Title Ulli Hafner commented on JENKINS-55707 Re: SpotBug: Unknown bug pattern Are these detectors of SpotBugs? Or are you using a plugin or custom detectors? 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-55878) JEP-200 in System Groovy scripts
Title: Message Title Jackie Hammell edited a comment on JENKINS-55878 Re: JEP-200 in System Groovy scripts Hi Oleg, Thanks for getting back to me. I would like to express my concerns regarding JEP200. It SCARES ME! I work for a large corporation that uses CloubBees Jenkins, I have raised my concerns with the CoudBees folks, and I would like to explain my concerns to you as well. I will let you know that I am an avid coder, with more years under my belt than I would like to admit anymore :). In the shop that I work in we have a "Self service" model with 13 people manning the helm of JIRA, Jenkin Jenkins , Artifactory and Bitbucket, out of which 3-4 of us are hands on with regards to the Jenkins infrastructure supporting 4K+ developers. Additionally, the infrastructure I work in has 9 masters and 1 JOC, we push over 20K jobs through the infrastructure daily and at a guesstimate over 150K job configurations.1) My biggest concern is that Jenkins is the critical CI/CD backbone to all development work happening in the organization I work in, and there are many jobs that have heavy groovy scripts driving them, and not knowing what is being Blacklisted (until we hit the wall), and can no longer be Approved though the admin GUI has the potential of bring high visability critical jobs to a grinding halt and catch fire state. We are currently testing in UAT, but it's impossible to test every job that has custom groovy code driving the pipeline.2) I am of the school of thought that an administrator should NEVER not be able to call a method that prohibits them from performing their duties. In my particular case, in the UAT environment the Node configurations need to be updated to ensure that the JDK can be found in the Tool Locations, in the use cases where the slaves don't have JAVA in their paths (yes, this happens more than you'd think). I don't believe in having to click on every /computer/ to get my job done when a simple groovy script will do it for me. I will quote Viktor Farcic, whom I believe you know 'GUI's are for managers and executive, not software engineers' - DevOps/Jenkins World San Francisco 2018.3) The answer you gave me 'Rewrite it in Java' is most doable, but my burning question is why can I accomplish my task in Java, yet the open source community has Blacklisted the method in Groovy? It seems counter productive to my rational brain. Is it up to the Jenkins project to try and save us from ourselves? I get and see the value of users not being able to access public static calls without being approved (we don't entirely trust them either), but Blacklisting an administrator from any call they choose to make out of necessity goes against the grain of everything I believe in.I hope this gives you some food for thought and I'm looking forward to your response. Cheers,Jackie Add Comment
[JIRA] (JENKINS-55679) XML source files not displayed in warnings-ng
Title: Message Title Ulli Hafner updated JENKINS-55679 Jenkins / JENKINS-55679 XML source files not displayed in warnings-ng Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55715) TagList parser should present files as file names, not classes.
Title: Message Title Ulli Hafner updated JENKINS-55715 Jenkins / JENKINS-55715 TagList parser should present files as file names, not classes. Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55733) Wrong parsing of CppCheck results
Title: Message Title Ulli Hafner commented on JENKINS-55733 Re: Wrong parsing of CppCheck results sunblack what do you think? Is there something I can do here? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55878) JEP-200 in System Groovy scripts
Title: Message Title Jackie Hammell edited a comment on JENKINS-55878 Re: JEP-200 in System Groovy scripts Hi Oleg, Thanks for getting back to me. I would like to express my concerns regarding JEP200. It SCARES ME! I work for a large corporation that uses CloubBees Jenkins, I have raised my concerns with the CoudBees folks, and I would like to explain my concerns to you as well. I will let you know that I am an avid coder, with more years under my belt than I would like to admit anymore :). In the shop that I work in we have a "Self service" model with 13 people manning the helm of JIRA, Jenkin, Artifactory and Bitbucket, out of which 3-4 of us are hands on with regards to the Jenkins infrastructure supporting 4K+ developers. Additionally, the infrastructure I work in has 9 masters and 1 JOC, we push over 20K jobs through the infrastructure daily and at a guesstimate over 150K job configurations.1) My biggest concern is that Jenkins is the critical CI/CD backbone to all development work happening in the organization I work in, and there are many jobs that have heavy groovy scripts driving them, and not knowing what is being Blacklisted (until we hit the wall), and can no longer be Approved though the admin GUI has the potential of bring high viability visability critical jobs to a grinding halt and catch fire state. We are currently testing in UAT, but it's impossible to test every job that has custom groovy code driving the pipeline.2) I am of the school of thought that an administrator should NEVER not be able to call a method that prohibits them from performing their duties. In my particular case, in the UAT environment the Node configurations need to be updated to ensure that the JDK can be found in the Tool Locations, in the use cases where the slaves don't have JAVA in their paths (yes, this happens more than you'd think). I don't believe in having to click on every /computer/ to get my job done when a simple groovy script will do it for me. I will quote Viktor Farcic, whom I believe you know 'GUI's are for managers and executive, not software engineers' - DevOps/Jenkins World San Francisco 2018.3) The answer you gave me 'Rewrite it in Java' is most doable, but my burning question is why can I accomplish my task in Java, yet the open source community has Blacklisted the method in Groovy? It seems counter productive to my rational brain. Is it up to the Jenkins project to try and save us from ourselves? I get and see the value of users not being able to access public static calls without being approved (we don't entirely trust them either), but Blacklisting an administrator from any call they choose to make out of necessity goes against the grain of everything I believe in.I hope this gives you some food for thought and I'm looking forward to your response. Cheers,Jackie Add Comment
[JIRA] (JENKINS-55878) JEP-200 in System Groovy scripts
Title: Message Title Jackie Hammell edited a comment on JENKINS-55878 Re: JEP-200 in System Groovy scripts Hi Oleg, Thanks for getting back to me. I would like to express my concerns regarding JEP200. It SCARES ME! I work for a large corporation that uses CloubBees Jenkins, I have raised my concerns with the CoudBees folks, and I would like to explain my concerns to you as well. I will let you know that I am an avid coder, with more years under my belt than I would like to admit anymore :). In the shop that I work in we have a "Self service" model with 13 people manning the helm of JIRA, Jenkin, Artifactory and Bitbucket, out of which 3-4 of us are hands on with regards to the Jenkins infrastructure supporting 4K+ developers. Additionally, the infrastructure I work in has 9 masters and 1 JOC, we push over 20K jobs through the infrastructure daily and at a guesstimate over 150K job configurations. 1) My biggest concern is that Jenkins is the critical CI/CD backbone to all development work happening in the organization I work in, and there are many jobs that have heavy groovy scripts driving them, and not knowing what is being Blacklisted (until we hit the wall), and can no longer be Approved though the admin GUI has the potential of bring high viability critical jobs to a grinding halt and catch fire state. We are currently testing in UAT, but it's impossible to test every job that has custom groovy code driving the pipeline. 2) I am of the school of thought that an administrator should NEVER not be able to call a method that prohibits them from performing their duties. In my particular case, in the UAT environment the Node configurations need to be updated to ensure that the JDK can be found in the Tool Locations, in the use cases where the slaves don't have JAVA in their paths (yes, this happens more than you'd think). I don't believe in having to click on every /computer/ to get my job done when a simple groovy script will do it for me. I will quote Viktor Farcic, whom I believe you know 'GUI's are for managers and executive, not software engineers' - DevOps/Jenkins World San Francisco 2018. 3) The answer you gave me 'Rewrite it in Java' is most doable, but my burning question is why can I accomplish my task in Java, yet the open source community has Blacklisted the method in Groovy? It seems counter productive to my rational brain. Is it up to the Jenkins project to try and save us from ourselves? I get and see the value of users not being able to access public static calls without being approved (we don't entirely trust them either), but Blacklisting an administrator from any call they choose to make out of necessity goes against the grain of everything I believe in. I hope this gives you some food for thought and I'm looking forward to your response. Cheers, Jackie
[JIRA] (JENKINS-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Change By: Ulli Hafner Assignee: 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-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Change By: Ulli Hafner Labels: help-wanted 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-55855) Possibility to Exclude certain parsers from quality gates
Title: Message Title Ulli Hafner resolved as Won't Fix Jenkins / JENKINS-55855 Possibility to Exclude certain parsers from quality gates Change By: Ulli Hafner Status: Open Resolved 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title
Aaron Nelson edited a comment on JENKINS-55836
Re: Unable to delete workspace due to locked git .pack file
Same issue here. We run our Jenkins master on a Windows Server 2008 R2 server and anytime a freestyle job has the "Build Environment" check box checked for "Delete workspace before build starts", there is a lock that Jenkins has on a .pack file in the git directory. Our work-around is to add an advanced configuration to the "Delete workspace before build starts" which specifically excludes {code:java} * * /.git/* *{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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Aaron Nelson commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Same issue here. We run our Jenkins master on a Windows Server 2008 R2 server and anytime a freestyle job has the "Build Environment" check box checked for "Delete workspace before build starts", there is a lock that Jenkins has on a .pack file in the git directory. Our work-around is to add an advanced configuration to the "Delete workspace before build starts" which specifically excludes "/.git/*" 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-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Aaron Nelson edited a comment on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Same issue here. We run our Jenkins master on a Windows Server 2008 R2 server and anytime a freestyle job has the "Build Environment" check box checked for "Delete workspace before build starts", there is a lock that Jenkins has on a .pack file in the git directory. Our work-around is to add an advanced configuration to the "Delete workspace before build starts" which specifically excludes " * * /.git/* *" 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-55976) Missing error log
Title: Message Title Jeff Thompson updated JENKINS-55976 Jenkins / JENKINS-55976 Missing error log Change By: Jeff Thompson Status: In Review Resolved Resolution: Fixed Released As: Remoting 3.29 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 assigned an issue to Ulli Hafner Jenkins / JENKINS-55442 Need filter by message text Change By: Ulli Hafner Assignee: Michael Keppler 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-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 updated JENKINS-55442 Jenkins / JENKINS-55442 Need filter by message text Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Javier Delgado commented on JENKINS-47643 Re: Allow [ci skip] to work for non-pull request changes This should be included on the 0.2.0 released plugin. Should appear at the update center shortly. Could you provide feedback, in order to close this ticket? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title
Claes Buckwalter edited a comment on JENKINS-50429
Re: Shell command are really slower than before
I am trying to understand what you guys think is the root cause of the issue. [~mrjgreen] are you saying that commenting out the [env variable setting|https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/ContainerExecDecorator.java#L342-L364] only reduced the container time by 1s, or reduced it down to 1s?I think my team is facing the same issue. When comparing an almost identical Pipeline running on Docker Swarm vs Kubernetes, we find that in _our setup_ it consistently takes 1s on Docker Swarm and 37s on Kubernetes. Each {{sh}} build step takes about 12s. We are using: - Jenkins 2.138.4 - Kubernetes plugin 1.13.5 - Kubernetes 1.11.2 - Docker plugin 1.1.5 * Kubernetes build (uses JNLP agent): * {code:java}pipeline { agent {kubernetes { label "${Utils.getTimestamp()}" inheritFrom 'k8s-build' containerTemplate {name 'build'image "aado-docker-releases.${ARTIFACTORY_URL}/build_centos7:latest"alwaysPullImage trueworkingDir '/home/jenkins'ttyEnabled truecommand 'cat'args '' }} }options {timestamps()disableConcurrentBuilds()buildDiscarder(logRotator(daysToKeepStr: '1', artifactDaysToKeepStr: '2'))timeout(time: 5, unit: 'MINUTES') } stages {stage('shell steps') { steps{container('build') { sh 'date --iso-8601=ns && pwd' sh "date --iso-8601=ns && whoami" sh ''' date --iso-8601=ns pwd whoami date --iso-8601=ns '''} }} }}{code}!clabu609-k8s-steps.png|thumbnail!{code:java}[Pipeline] {[Pipeline] container[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] timeout21:11:03 Timeout set to expire in 5 min 0 sec[Pipeline] {[Pipeline] stage[Pipeline] { (shell steps)[Pipeline] container[Pipeline] {[Pipeline] sh21:11:16 + date --iso-8601=ns21:11:16 2019-02-05T21:11:16,397400542+21:11:16 + pwd21:11:16 /home/jenkins/workspace/CTO/DevOps/sandbox/DO-5721/test-sh-k8s[Pipeline] sh21:11:29 + date --iso-8601=ns21:11:29 2019-02-05T21:11:28,906771174+21:11:29 + whoami21:11:29 root[Pipeline] sh21:11:41 + date --iso-8601=ns21:11:41 2019-02-05T21:11:41,347653982+21:11:41 + pwd21:11:41 /home/jenkins/workspace/CTO/DevOps/sandbox/DO-5721/test-sh-k8s21:11:41 + whoami21:11:41 root21:11:41 + date --iso-8601=ns21:11:41 2019-02-05T21:11:41,350677503+[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // timestamps[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] End of PipelineFinished: SUCCESS {code} * Docker build (uses SSH agent): * {code:java}pipeline { agent { label 'build_rhel7_jdk1.7_maven3_latest_candidate' } options {timestamps()disableConcurrentBuilds()buildDiscarder(logRotator(daysToKeepStr: '1', artifactDaysToKeepStr: '2'))timeout(time: 5, unit: 'MINUTES') } stages {stage('shell steps') { steps{ sh 'date --iso-8601=ns && pwd' sh "date --iso-8601=ns && whoami" sh ''' date --iso-8601=ns pwd whoami date --iso-8601=ns ''' }} }}{code}!clabu609-docker-steps.png|thumbnail!{code:java}[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] timeout21:20:14 Timeout set to expire in 5 min 0 sec[Pipeline] {[Pipeline] stage[Pipeline] { (shell steps)[Pipeline] sh21:20:14
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title
Claes Buckwalter commented on JENKINS-50429
Re: Shell command are really slower than before
I am trying to understand what you guys think is the root cause of the issue. Joseph Green are you saying that commenting out the env variable setting only reduced the container time by 1s, or reduced it down to 1s? I think my team is facing the same issue. When comparing an almost identical Pipeline running on Docker Swarm vs Kubernetes, we find that in our setup it consistently takes 1s on Docker Swarm and 37s on Kubernetes. Each sh build step takes about 12s. We are using:
Jenkins 2.138.4
Kubernetes plugin 1.13.5
Kubernetes 1.11.2
Docker plugin 1.1.5
Kubernetes build (uses JNLP agent):
pipeline {
agent {
kubernetes {
label "${Utils.getTimestamp()}"
inheritFrom 'k8s-build'
containerTemplate {
name 'build'
image "aado-docker-releases.${ARTIFACTORY_URL}/build_centos7:latest"
alwaysPullImage true
workingDir '/home/jenkins'
ttyEnabled true
command 'cat'
args ''
}
}
}
options {
timestamps()
disableConcurrentBuilds()
buildDiscarder(logRotator(daysToKeepStr: '1', artifactDaysToKeepStr: '2'))
timeout(time: 5, unit: 'MINUTES')
}
stages {
stage('shell steps') {
steps{
container('build') {
sh 'date --iso-8601=ns && pwd'
sh "date --iso-8601=ns && whoami"
sh '''
date --iso-8601=ns
pwd
whoami
date --iso-8601=ns
'''
}
}
}
}
}
[Pipeline] {
[Pipeline] container
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] timeout
21:11:03 Timeout set to expire in 5 min 0 sec
[Pipeline] {
[Pipeline] stage
[Pipeline] { (shell steps)
[Pipeline] container
[Pipeline] {
[Pipeline] sh
21:11:16 + date --iso-8601=ns
21:11:16 2019-02-05T21:11:16,397400542+
21:11:16 + pwd
21:11:16 /home/jenkins/workspace/CTO/DevOps/sandbox/DO-5721/test-sh-k8s
[Pipeline] sh
21:11:29 + date --iso-8601=ns
21:11:29 2019-02-05T21:11:28,906771174+
21:11:29 + whoami
21:11:29 root
[Pipeline] sh
21:11:41 + date --iso-8601=ns
21:11:41 2019-02-05T21:11:41,347653982+
21:11:41 + pwd
21:11:41 /home/jenkins/workspace/CTO/DevOps/sandbox/DO-5721/test-sh-k8s
21:11:41 + whoami
21:11:41 root
21:11:41 + date --iso-8601=ns
21:11:41 2019-02-05T21:11:41,350677503+
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
Finished: SUCCESS
Docker
[JIRA] (JENKINS-52770) started.FATAL: Log statements out of sync: current test suite 'Target_Test.xctest' not exists
Title: Message Title Spin Selling commented on JENKINS-52770 Re: started.FATAL: Log statements out of sync: current test suite 'Target_Test.xctest' not exists Kazuhide Takahashi: Any updates ? I am facing the similar issue. Xcode that am using is 10.1 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-55984) Unable to perform Unit tests due to error "started.FATAL: Log statements out of sync: current test suite not exists
Title: Message Title Spin Selling commented on JENKINS-55984 Re: Unable to perform Unit tests due to error "started.FATAL: Log statements out of sync: current test suite not exists Xcode used to compile : Version 10.1 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-55775) Warning reports does not show absolute file path.
Title: Message Title Ulli Hafner commented on JENKINS-55775 Re: Warning reports does not show absolute file path. I see. For non-java files I added a folder tab now. Hope that helps in your case as well. 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-50429) Shell command are really slower than before
Title: Message Title Claes Buckwalter updated an issue Jenkins / JENKINS-50429 Shell command are really slower than before Change By: Claes Buckwalter Attachment: clabu609-docker-steps.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Claes Buckwalter updated an issue Jenkins / JENKINS-50429 Shell command are really slower than before Change By: Claes Buckwalter Attachment: clabu609-k8s-steps.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Suemiao Rossignol reopened an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Suemiao Rossignol Resolution: Won't Fix Status: Resolved Reopened 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Suemiao Rossignol edited a comment on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I am using Jenkins 2.150.2 version but still hitting this issue?I also install short workspace pluginswithout plugins without any luck.Is this truly 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Suemiao Rossignol commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I am using Jenkins 2.150.2 version but still hitting this issue? I also install short workspace pluginswithout any luck. Is this truly 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-55984) Unable to perform Unit tests due to error "started.FATAL: Log statements out of sync: current test suite not exists
Title: Message Title Spin Selling created an issue Jenkins / JENKINS-55984 Unable to perform Unit tests due to error "started.FATAL: Log statements out of sync: current test suite not exists Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 2019-02-05 21:06 Priority: Blocker Reporter: Spin Selling Jenkins Version : 2.150.2 Xcode Plugin Version : 2.0.10 Issue: Unit test job on jenkins stops with started.FATAL: Log statements out of sync: current test suite '.XX.xctest' not exists The same build, if i try unit test with command line it succeeds. Add
[JIRA] (JENKINS-55983) need mechanism to clear GitHubHookRegisterProblemMonitor errors without restart
Title: Message Title Joshua Hoblitt created an issue Jenkins / JENKINS-55983 need mechanism to clear GitHubHookRegisterProblemMonitor errors without restart Issue Type: Improvement Assignee: Kirill Merkushev Components: github-plugin Created: 2019-02-05 20:43 Environment: jenkins core 2.150.1 Priority: Minor Reporter: Joshua Hoblitt Errors managing github webhooks are recorded and displayed by GitHubHookRegisterProblemMonitor even if no job that currently exists references the listed repos (the warn may even reference to a repo that doesn't exist). There is no administrative mechanism to clear these errors short of restarting the jenkins master. This is sub-optimal as an ops team needs to either ignore these errors or keep track of which are bogus between master restarts. Add Comment
[JIRA] (JENKINS-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Ulli Hafner updated JENKINS-55873 Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55817) Support Credentials store for SSH Steps
Title: Message Title
Naresh Rayapati updated an issue
Jenkins / JENKINS-55817
Support Credentials store for SSH Steps
Change By:
Naresh Rayapati
Currently we need to use ` {code:java} withCredentials ` {code} to map the credentials to all the steps, it would nice to have credentials store integrated to read the credentials from store.
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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Naresh Rayapati commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging Yes, as I mentioned before that is something being printed by dependent library. so I have little control over that one. Thank you. 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Naresh Rayapati closed an issue as Fixed Jenkins / JENKINS-55194 Add logLevel to support debugging and also reduce default excessive logging Change By: Naresh Rayapati Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Karl Shultz commented on JENKINS-55972 Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master OK, thanks for that. Next questions: 1. Did this job work correctly before you updated to the rc levels of the plugin? 2. Can you provide more details as far as the job? When you say "clone git repository" in the description of this bug report, do you mean: As part of a Jenkins Pipeline job? If yes, is it Declarative or Scripted? As part of a Freestyle job? As part of something else? 3. Let's assume it's a Multibranch Pipeline job for the moment. Did you use Git as your SCM provider, or GitHub? That's a mistake I've made before. I'm talking about this pulldown:4. Any idea where the port number 1080 came from? Is that the port that your own Git server is listening on? 5. Is it possible that some other service is blocking port 1080? For my environments, that could be a security group setting in AWS, or a firewall setting who-knows-where, etc. Basically, some steps to recreate the issue would really help pin down what's wrong. 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-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Change By: Karl Shultz Attachment: screenshot-2.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40805) Workspace not available when a slave is created by the Kubernetes plugin
Title: Message Title suryatej yaramada commented on JENKINS-40805 Re: Workspace not available when a slave is created by the Kubernetes plugin May be we use of https://github.com/jenkinsci/external-workspace-manager-plugin/blob/master/README.md this plugin to get view the workspace form GUI if some configurations changes happen in both kubernetes plugin and as well Jenkins 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-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Adam vonNieda commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines I've got the same issue when running sh step without parallel, on ssh slave with Jenkins 2.150.2 LTS, I'm not running on docker. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55982) JIRA Plugin does not respect proxy in some requests
Title: Message Title Diogo Valente updated an issue Jenkins / JENKINS-55982 JIRA Plugin does not respect proxy in some requests Change By: Diogo Valente Labels: jira-plugin-3.0.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55982) JIRA Plugin does not respect proxy in some requests
Title: Message Title Diogo Valente created an issue Jenkins / JENKINS-55982 JIRA Plugin does not respect proxy in some requests Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2019-02-05 19:27 Environment: Windows Server 2008, Jenkins 2.121.2, Jira Plugin 3.0.0 Priority: Minor Reporter: Diogo Valente Jira plugin seems not to respect proxy settings (both JVM and Jenkins Plugins) on some requests, namely getVersions (endpoint /rest/api/2/project/LAPSIS/versions). Add Comment
[JIRA] (JENKINS-55846) No issues found when parsing Error-Prone output from console log during gradle build
Title: Message Title Ulli Hafner updated JENKINS-55846 Jenkins / JENKINS-55846 No issues found when parsing Error-Prone output from console log during gradle build Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54668) Unable to provide NodeJS path to Jenkins plugin
Title: Message Title Nikolas Falco closed an issue as Done Jenkins / JENKINS-54668 Unable to provide NodeJS path to Jenkins plugin Change By: Nikolas Falco Status: Reopened Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55961) Nodejs plugin installs wrong platform package when using parallel pipeline
Title: Message Title Nikolas Falco commented on JENKINS-55961 Re: Nodejs plugin installs wrong platform package when using parallel pipeline Philip Adams your analysis was very very good. Thank a lot. The platform is taken from system property gather by the EnvVars for that node (JENKINS-14807). I should check if NodeJSInstall is instantiated just one time but run in parallel by the parallel task (so I have to check it must be thread safe) or there is an issue in the EnvVars given by the node. 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-55775) Warning reports does not show absolute file path.
Title: Message Title Omar Lopesino updated an issue Jenkins / JENKINS-55775 Warning reports does not show absolute file path. Change By: Omar Lopesino Summary: Warning reports does not show absolute urls file path . Attachment: report-screenshot.jpg When I access the reports generated by the plugin I can see the list of files affected but I don't see the absolute file path. This was working with the older warning plugin. This is happening with a php project. What could be happening? 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-55775) Warning reports does not show absolute file path.
Title: Message Title Omar Lopesino edited a comment on JENKINS-55775 Re: Warning reports does not show absolute file path. Maybe is late, but my explanation was not precise. I expand some details: I need this for php projects where is not clear where the php file reported is.I've also attached a screenshot to this issue. In that screenshot only appears the file name instead the complete path. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55775) Warning reports does not show absolute file path.
Title: Message Title Omar Lopesino commented on JENKINS-55775 Re: Warning reports does not show absolute file path. Maybe is late, but my explanation was not precise. I expand some details: I need this for php projects where is not clear where the php file reported is. I've also attached a screenshot to this issue. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55981) Execute Scripts on Matrix steps are performed after email is sent
Title: Message Title John David created an issue Jenkins / JENKINS-55981 Execute Scripts on Matrix steps are performed after email is sent Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2019-02-05 18:08 Environment: Jenkins 2.89.4 PostBuildScript 2.5.1 Email Extension 2.61 Priority: Major Reporter: John David Email is supposed to let all post-build steps run before it gets sent. I have an number of post-build 'Execute Scripts on Matrix' Execute shell steps that run. These jobs were added later so came after the Editable email step. I am getting mail saying the build succeeded when it, in fact, failed on the post build matrix steps. Looking at the build log of the top level matrix job confirms this. At first, I thought it was the order and deleted the Editable email step and tried adding it last. No matter what I do, it always gets placed as the first post build step. Add Comment
[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Priyanka Rathi updated an issue Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Change By: Priyanka Rathi Attachment: image-2019-02-05-23-28-19-792.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Priyanka Rathi commented on JENKINS-55972 Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Karl Shultz its same as yours. 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title juan perez commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once We are using lots of python code called from the shared library, is a pain sh only returns an error code we would need a way to bubble the error message. Those solutions sounds good. 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-55453) Github PR creating job but not building
Title: Message Title
Tyler Pickett edited a comment on JENKINS-55453
Re: Github PR creating job but not building
Thanks, I realized that after digging in a bit further and didn't come back to update this. Sorry for the trouble. Leaving this for posterity: After reading through the code it looks like the problem may actually be in the \ {{github-branch-source }}plugin I'll retag this to that plugin and work on adding some logging around where that trigger is happening to get better insight into what's going on.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-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 Component/s: github-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-55948) Git client plug-in crash
Title: Message Title
Karl Shultz edited a comment on JENKINS-55948
Re: Git client plug-in crash
[~carlosgarcia] - what version of the {{git}} and {{git-client}} plugins are you running right now? You can see this by looking at https://your-jenkins:jenkins-port/pluginManager/installed. Should look something like this: !image-2019-02-05-12-46-05-024.png|thumbnail!I ask because there is currently a release-candidate version of both of these plugins, on the experimental update center.
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-55948) Git client plug-in crash
Title: Message Title
Karl Shultz edited a comment on JENKINS-55948
Re: Git client plug-in crash
[~carlosgarcia] - what version of the {{git}} and {{git-client}} plugins are you running right now? You can see this by looking at https://your-jenkins:jenkins-port/pluginManager/installed. Should look something like this: !image-2019-02-05-12-46-05-024.png|thumbnail! I ask because there is currently a release-candidate version of both of these plugins, on the experimental update center. I'd like to know if you're running this early-release version, or the current version. Thanks!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55453) Github PR creating job but not building
Title: Message Title
Tyler Pickett commented on JENKINS-55453
Re: Github PR creating job but not building
After reading through the code it looks like the problem may actually be in the {{github-branch-source }}plugin I'll retag this to that plugin and work on adding some logging around where that trigger is happening to get better insight into what's going on.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-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 Component/s: github-branch-source-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-55948) Git client plug-in crash
Title: Message Title Karl Shultz commented on JENKINS-55948 Re: Git client plug-in crash Carlos Garcia - what version of the git and git-client plugins are you running right now? You can see this by looking at https://your-jenkins:jenkins-port/pluginManager/installed. Should look something like this: I ask because there is currently a release-candidate version of both of these plugins, on the experimental update center. 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-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Karl Shultz commented on JENKINS-55972 Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Priyanka Rathi - what version of the git and git-client plugins are you running right now? You can see this by looking at https://your-jenkins:jenkins-port/pluginManager/installed. For example, here is one of mine. I've got it set up to use the experimental update center, meaning it's running beta-level code, including (but not limited to) these release-candidate versions of git and git-client. 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-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Change By: Karl Shultz Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title
Priyanka Rathi commented on JENKINS-55972
Re: Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
new error now .It is not giving me any error related to port Cloning the remote Git repositoryCloning the remote Git repositoryCloning repository https://.git > /usr/bin/git init /AutoCSA/${workspace} # timeout=10Fetching upstream changes from https://.git > /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials Bitbucket service user > /usr/bin/git fetch --tags --progress https://.git +refs/heads/:refs/remotes/origin/ # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://.git +refs/heads/:refs/remotes/origin/" returned status code 128:stdout: stderr: error: cannot run /AutoCSA//AutoCSA//AutoCSA/${workspace}@tmp/jenkins-gitclient-pass7876213394703629191.sh: No such file or directoryfatal: could not read Username for 'https://.com': terminal prompts disabled at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1905) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:81) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:488) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:712) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) 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:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to csa-automation-node1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor865.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy79.execute(Unknown Source) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1135) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1175) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1810) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at
[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Priyanka Rathi updated JENKINS-55972 Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Change By: Priyanka Rathi Resolution: Not A Defect Status: Fixed but Unreleased Reopened 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title joe ferr commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Mark Waite After installing beta4 our gitlab integration from jenkins to gitlab stopped working. There seem to be lots of reported issues w. the gitlab plugin so I'm not sure what broke it (e.g may be unrelated to your stuff)...here's a ticket that we found https://github.com/jenkinsci/gitlab-plugin/issues/893. We have hundreds of pipeline jobs that use this and they all stopped reporting pipeline status back to gitlab. I turned on logging for the gitlab plugin and I'm seeing this. If you do think it's related to your changes let me know if I can do any testing for you to help troubleshoot. Build does not contain build data. Feb 05, 2019 9:46:44 AM INFO com.dabsquared.gitlabjenkins.util.CommitStatusUpdater retrieveGitlabProjectIds 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-55190) Support "List of parameters to check" in Throttle Concurrent Builds Plugin
Title: Message Title Uwe Hanisch edited a comment on JENKINS-55190 Re: Support "List of parameters to check" in Throttle Concurrent Builds Plugin It is confusing the diffence The difference between build in and dynamic DSL is confusing .Nonetheless job-dsl-plugin should support the configuration of the following two Throttle Concurrent Build parameters natively: - boolean limitOneJobWithMatchingParams - String paramsToUseForLimitThese two parameters were introduced with Throttle Concurrent Build version 1.8.5Files which needed to adjust: * Code ** [job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/Job.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/Job.groovy#L84] ** [job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/toplevel/ThrottleConcurrentBuildsContext.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/toplevel/ThrottleConcurrentBuildsContext.groovy] * examples ** [job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/Job/throttleConcurrentBuilds.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/Job/throttleConcurrentBuilds.groovy] * Tests ** [job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/JobSpec.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/JobSpec.groovy#L340] ** [job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/jobs/MatrixJobSpec.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/jobs/MatrixJobSpec.groovy#L102] 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
[JIRA] (JENKINS-55190) Support "List of parameters to check" in Throttle Concurrent Builds Plugin
Title: Message Title Uwe Hanisch edited a comment on JENKINS-55190 Re: Support "List of parameters to check" in Throttle Concurrent Builds Plugin It is confusing the diffence between build in and dynamic DSL.Nonetheless job-dsl-plugin should support the configuration of following two Throttle Concurrent Build parameters natively: - boolean limitOneJobWithMatchingParams- String paramsToUseForLimitThese two parameters were introduced with Throttle Concurrent Build version 1.8.5Files which needed to adjust:* Code** [job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/Job.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/Job.groovy#L84]** [job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/toplevel/ThrottleConcurrentBuildsContext.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/toplevel/ThrottleConcurrentBuildsContext.groovy]* examples** [job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/Job/throttleConcurrentBuilds.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/Job/throttleConcurrentBuilds.groovy]* Tests** [job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/JobSpec.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/JobSpec.groovy#L340]** [job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/jobs/MatrixJobSpec.groovy|https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/jobs/MatrixJobSpec.groovy#L102] 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-55980) Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-55980 Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-02-05 17:11 Priority: Minor Reporter: Oleg Nenashev This is a follow-up to JENKINS-55562. Once JENKINS-55575 is integrated into Lib Version Number, we can use new generic classes for robust Java version comparison in the core. It should prevent issues if any other plugin ships something unexpected in the metadata (like "8" instead of "1.8") Add Comment
[JIRA] (JENKINS-55980) Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-55980 Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-55980) Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata
Title: Message Title Oleg Nenashev started work on JENKINS-55980 Change By: Oleg Nenashev 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-55980) Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55980 Make Jenkins tolerant against incorrect minimum Java version specifications in plugin metadata Change By: Oleg Nenashev Labels: java11 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-55575) Move JavaSpecificationVersion from the Update Center codebase to the Version Number Lib
Title: Message Title Oleg Nenashev updated JENKINS-55575 Jenkins / JENKINS-55575 Move JavaSpecificationVersion from the Update Center codebase to the Version Number Lib Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Version Number Lib 1.6 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-55736) Support proxy logins
Title: Message Title Jonathan Whitby commented on JENKINS-55736 Re: Support proxy logins Fernando Boaglio 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-55979) Jenkins doesn't update moved tags
Title: Message Title Jussi Lind updated an issue Jenkins / JENKINS-55979 Jenkins doesn't update moved tags Change By: Jussi Lind The issue is simply that Jenkins doesn't seem to update moved Git tags:1) Make your Multibranch Pipeline project discover also tags2) Create a tag and push3) Observe the tag in Jenkins -> -[PROJECT] -> Tags4) Move the same tag to a new commit (e.g. `git tag -f`) and push5) Rescan the multibranch pipeline6) Observe the tag in Jenkins -> -[PROJECT] -> Tags. The tag is still pointing to the original Revision / commit hash after scan and it won't update . It is showing the build results of the original revision, which is misleading. 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-55979) Jenkins doesn't update moved tags
Title: Message Title Jussi Lind created an issue Jenkins / JENKINS-55979 Jenkins doesn't update moved tags Issue Type: Bug Assignee: Denis Saponenko Components: pipeline-multibranch-defaults-plugin Created: 2019-02-05 16:59 Environment: Jenkins 2.150.1 Labels: pipeline git-tag Priority: Minor Reporter: Jussi Lind The issue is simply that Jenkins doesn't seem to update moved Git tags: 1) Make your Multibranch Pipeline project discover also tags 2) Create a tag and push 3) Observe the tag in Jenkins -> -[PROJECT] -> Tags 4) Move the same tag to a new commit (e.g. `git tag -f`) and push 5) Rescan the multibranch pipeline 6) Observe the tag in Jenkins -> -[PROJECT] -> Tags. The tag is still pointing to the original Revision / commit hash after scan and it won't update Add Comment
