[JIRA] (JENKINS-53630) Error while serving any http://jenkinsURL/configSubmit
Title: Message Title Oleg Nenashev commented on JENKINS-53630 Re: Error while serving any http://jenkinsURL/configSubmit Looks like a binary compat issue in the Jira Test Reporter plugin, similar to what Olivier Lamy fixed for the Jira plugin. Nothing to be done on the core side afaict 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-53630) Error while serving any http://jenkinsURL/configSubmit
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53630 Error while serving any http://jenkinsURL/configSubmit Change By: Oleg Nenashev Component/s: jiratestresultreporter-plugin Component/s: core 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-53630) Error while serving any http://jenkinsURL/configSubmit
Title: Message Title Oleg Nenashev assigned an issue to Catalin Luta Jenkins / JENKINS-53630 Error while serving any http://jenkinsURL/configSubmit Change By: Oleg Nenashev Assignee: Catalin Luta 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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Jon B edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
I just met with [~jglick] who told me that in my case, the underlying mechanism that triggers when I call for "node('general')" selects one of my spot instances. At that moment, an internal ec2 hostname is selected. If, while the work is being performed, that particular node dies, Jenkins intentionally waits for another machine at that hostname to wake up before it will continue. It is for this reason why it appears to hang forever - because my AWS spot/autoscaling does not launch another machine with the same internal hostname.He suggested setting a timeout block which would retry the test run if the work does not complete within a given period.We both agreed this seems to therefore be a new feature request.The new feature would allow Jenkins to re-dispatch the closure of work to any other node that matches the given label if the original executor's host was killed off terminated while the work was being performed .
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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Jon B edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
I just met with [~jglick] who told me that in my case, the underlying mechanism that triggers when I call for "node('general')" selects one of my spot instances. At that moment, an internal ec2 hostname is selected. If, while the work is being performed, that particular node dies, Jenkins intentionally waits for another machine at that hostname to wake up before it will continue. It is for this reason why it appears to hang forever - because my AWS spot/autoscaling does not launch another machine with the same internal hostname.He suggested setting a timeout block which would retry the test run if the work does not complete within a given period.We both agreed this seems to therefore be a new feature request.The new feature would allow Jenkins to re-dispatch the closure of work to any other node that matches the given label if the original executor's host was killed off .
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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Jon B edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
I just met with [~jglick] who told me that in my case, the underlying mechanism that triggers when I call for "node('general')" selects one of my spot instances. At that moment, an internal ec2 hostname is selected. If, while the work is being performed, that particular node does dies , Jenkins intentionally waits for another machine at that hostname to wake up before it will continue. It is for this reason why it appears to hang forever - because my AWS spot/autoscaling does not launch another machine with the same internal hostname.He suggested setting a timeout block which would retry the test run if the work does not complete within a given period.We both agreed this seems to therefore be a new feature request.The new feature would allow Jenkins to re-dispatch the closure of work to any other node that matches the given label.
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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Jon B edited a comment on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
I just met with [~jglick] who told me that in my case, the underlying mechanism that triggers when I call for "node('general')" selects one of my spot instances. At that moment, an internal ec2 hostname is selected. If, while the work is being performed, that particular node does, Jenkins intentionally waits for another machine at that hostname to wake up before it will continue. It is for this reason why it appears to hang forever - because my AWS spot/autoscaling does not launch another machine with the same internal hostname.He suggested setting a timeout block which would retry the test run if the work does not complete within a given period.We both agreed this seems to therefore be a new feature request.The new feature would allow Jenkins to re-dispatch the closure of work to any other node that matches the given label.
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-49707) Auto retry for elastic agents after channel closure
Title: Message Title
Jon B commented on JENKINS-49707
Re: Auto retry for elastic agents after channel closure
I just met with Jesse Glick who told me that in my case, underlying mechanism that triggers when I call for "node('general')" selects one of my spot instances. At that moment, an internal ec2 hostname is selected. If, while the work is being performed, that particular node does, Jenkins intentionally waits for another machine at that hostname to wake up before it will continue. It is for this reason why it appears to hang forever - because my AWS spot/autoscaling does not launch another machine with the same internal hostname. He suggested setting a timeout block which would retry the test run if the work does not complete within a given period. We both agreed this seems to therefore be a new feature request. The new feature would allow Jenkins to re-dispatch the closure of work to any other node that matches the given label.
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-53588) [P4 Plugin] Shelve fails with 'tampered with after resolve' for utf8 files
Title: Message Title Stuart Rowe commented on JENKINS-53588 Re: [P4 Plugin] Shelve fails with 'tampered with after resolve' for utf8 files Paul Allen The Jenkins node has JVM option -Dcom.perforce.p4java.filesys.utf8bom=0 to prevent writing the BOM. However, I added an input step in between the resolve and shelve stages and noticed that the target file does have a BOM after the resolve which is unexpected. 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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title Jie Shen commented on JENKINS-53625 Re: Provisioning an advanced linux image never continues after init.sh Alexander Komarov, thanks for your reporting and investigation. I will look at 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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-53625 Provisioning an advanced linux image never continues after init.sh Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53610) How to use Warnings plugin 5.00 Public Beta in declarative script?
Title: Message Title Ulli Hafner resolved as Fixed See #39a267 Jenkins / JENKINS-53610 How to use Warnings plugin 5.00 Public Beta in declarative script? Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53635) xunit step failure is not displayed
Title: Message Title Owen Wood commented on JENKINS-53635 Re: xunit step failure is not displayed The change now means that a stage failure will be reported correctly as failed. 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-53635) xunit step failure is not displayed
Title: Message Title
Owen Wood updated an issue
Jenkins / JENKINS-53635
xunit step failure is not displayed
Change By:
Owen Wood
Same issue as described in https://issues.jenkins-ci.org/browse/JENKINS-47142, except, for xunit step, not archiveArtifacts step. The issue looks to be that the exception is swallowed here - [https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java#L164] meaning that it's not able to be handled upstream. Not confirmed. The result is that the stage shows as successful, but the build fails.A simple test case that reproduces the issue:{code}node {stage('stage 1') {git 'https://github.com/dantheman213/java-hello-world-maven.git'sh 'mvn clean package'xunit testTimeMargin: '3000', thresholdMode: 1, thresholds: [failed(), passed(), skipped()], tools: [JUnit(deleteOutputFiles: true, failIfNotNew: true, pattern: 'target/failsafe-reports/*.xml', skipNoTestFiles: false, stopProcessingIfError: true)]}stage('stage 2') {echo 'hello from stage 2'}} {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
[JIRA] (JENKINS-53635) xunit step failure is not displayed
Title: Message Title Owen Wood commented on JENKINS-53635 Re: xunit step failure is not displayed Nikolas Falco could you 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-53635) xunit step failure is not displayed
Title: Message Title Owen Wood updated JENKINS-53635 Jenkins / JENKINS-53635 xunit step failure is not displayed Change By: Owen Wood 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-53635) xunit step failure is not displayed
Title: Message Title Owen Wood commented on JENKINS-53635 Re: xunit step failure is not displayed Created https://github.com/jenkinsci/xunit-plugin/pull/64 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-53635) xunit step failure is not displayed
Title: Message Title Owen Wood started work on JENKINS-53635 Change By: Owen Wood 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-49707) Auto retry for elastic agents after channel closure
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-49707 Auto retry for elastic agents after channel closure Change By: Jesse Glick Summary: Pipeline hangs: "The Auto retry for elastic agents after channel is closing down or has closed down" closure Issue Type: Bug New Feature Component/s: workflow-durable-task-step-plugin Component/s: remoting Assignee: Jeff Thompson 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-53635) xunit step failure is not displayed
Title: Message Title
Owen Wood created an issue
Jenkins / JENKINS-53635
xunit step failure is not displayed
Issue Type:
Bug
Assignee:
Owen Wood
Components:
xunit-plugin
Created:
2018-09-18 00:34
Priority:
Minor
Reporter:
Owen Wood
Same issue as described in https://issues.jenkins-ci.org/browse/JENKINS-47142, except, for xunit step, not archiveArtifacts step. The issue looks to be that the exception is swallowed here - https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java#L164 meaning that it's not able to be handled upstream. Not confirmed. The result is that the stage shows as successful, but the build fails. A simple test case that reproduces the issue:
node {
stage('stage 1') {
git 'https://github.com/dantheman213/java-hello-world-maven.git'
sh 'mvn clean package'
xunit testTimeMargin: '3000', thresholdMode: 1, thresholds: [failed(), passed(), skipped()], tools: [JUnit(deleteOutputFiles: true, failIfNotNew: true, pattern: 'target/failsafe-reports/*.xml', skipNoTestFiles: false, stopProcessingIfError: true)]
}
stage('stage 2') {
echo 'hello from stage 2'
}
}
[JIRA] (JENKINS-51124) Trust Server Certificate not honoured for build failure messages
Title: Message Title Mayank Daswani commented on JENKINS-51124 Re: Trust Server Certificate not honoured for build failure messages I have also recently encountered this bug. Happens with a self-hosted rocketchat instance with a self-signed cert. A workaround is to import the cert into the java keystore on the jenkins host, but it does seem like the "Trust server certificate" setting is not honoured for jobs, only for test connections., 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-53633) Remove pinned certificates
Title: Message Title Baptiste Mathus updated JENKINS-53633 Jenkins / JENKINS-53633 Remove pinned certificates Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53634) AWS Flavor specific allowed certificates are not used
Title: Message Title Baptiste Mathus closed an issue as Won't Fix WONTFIX because we are just going to remove certificate pinning in JENKINS-53633 Jenkins / JENKINS-53634 AWS Flavor specific allowed certificates are not used Change By: Baptiste Mathus Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53634) AWS Flavor specific allowed certificates are not used
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53634 AWS Flavor specific allowed certificates are not used Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-17 22:36 Labels: evergreen Priority: Critical Reporter: Baptiste Mathus Evergreen AWS flavor provisions, but fails to provision any node with the stack trace below. This is because apparently the custom overridden certificates to allow calls into AWS infrastructure are not used anymore. [WARNING][2018-09-17 18:40:26] Exception during provisioning (from hudson.plugins.ec2.EC2Cloud provision) com.amazonaws.SdkClientException: Unable to execute HTTP request: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1116) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1066) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at
[JIRA] (JENKINS-53633) Remove pinned certificates
Title: Message Title Baptiste Mathus started work on JENKINS-53633 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53633) Remove pinned certificates
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53633 Remove pinned certificates Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-17 22:18 Priority: Minor Reporter: Baptiste Mathus Problem statement AWS flavor does not work because overridden pinned certificates are not used anymore. Kohsuke hit a PKIX issue trying to create a Pipeline and adding a GH personal access token Expected behaviour These should work ootb. We discussed this a bit with R. Tyler Croy and we want to move away from the current solution of using that generate-ca-certificates and pinned certificates (as per designed in JEP 307). We'll work out something simpler/different for this purpose. We prefer to move away from this because we're convinced we'll keep hitting such issues as we go and get actual users. Add Comment
[JIRA] (JENKINS-53633) Remove pinned certificates
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-53633 Remove pinned certificates Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53632) Re-organize the client filesystem writes to allow seamless restarts
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-53632 Re-organize the client filesystem writes to allow seamless restarts Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-17 21:23 Priority: Minor Reporter: R. Tyler Croy The volume should be on /evergreen/data /evergreen/data/client /evergreen/data/jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53632) Re-organize the client filesystem writes to allow seamless restarts
Title: Message Title R. Tyler Croy started work on JENKINS-53632 Change By: R. Tyler Croy 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-53631) Number of instances shows the wrong number
Title: Message Title Baptiste Mathus updated JENKINS-53631 Jenkins / JENKINS-53631 Number of instances shows the wrong number Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52750) dir step creates a @tmp directory at level.
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-52750
Re: dir step creates a @tmp directory at level.
The {{dir}} step is generally used for workspace-relative paths where the agent is assumed to have full control over the directory, and Jenkins will use sibling directories for various things such as temp directories or shared libraries. If you want to install things in the absolute directory {{/opt/tmp}} on the agent, I would do it in a script in with the {{sh}} step so that you have full control over what will happen and so that the Pipeline does not run with {{/opt/tmp}} as its workspace directory at any point.You might be able to use the [Workspace Cleanup Plugin|https://plugins.jenkins.io/ws-cleanup] to clear out the temp directory, but to take a step back, I think it would make more sense to just use an agent that already has those tools installed in the first place, i.e. some kind of container or pre-built VM image, so that you aren't changing your agent configuration inside of Jenkins at all.
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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title Alexander Komarov commented on JENKINS-53625 Re: Provisioning an advanced linux image never continues after init.sh Same behavior with plugin version 0.7.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-52750) dir step creates a @tmp directory at level.
Title: Message Title Devin Nusbaum commented on JENKINS-52750 Re: dir step creates a @tmp directory at level. The dir step is generally used for workspace-relative paths where the agent is assumed to have full control over the directory, and Jenkins will use sibling directories for various things such as temp directories or shared libraries. If you want to install things in the absolute directory /opt/tmp on the agent, I would do it in a script in the sh step so that you have full control over what will happen and so that the Pipeline does not run with /opt/tmp as its workspace directory at any point. You might be able to use the Workspace Cleanup Plugin to clear out the temp directory, but to take a step back, I think it would make more sense to just use an agent that already has those tools installed in the first place, i.e. some kind of container or pre-built VM image, so that you aren't changing your agent configuration inside of Jenkins at all. 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-53631) Number of instances shows the wrong number
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53631 Number of instances shows the wrong number Change By: Baptiste Mathus h3. Problem statementOn the http://evergreen.jenkins.io currently we see something inconsistent between the number of instances running each ULs and the overall number of connected instances: !issue.png|thumbnail! h3. Expected behaviorActively connected number is expected to be the addition of all UL. 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-53631) Number of instances shows the wrong number
Title: Message Title Baptiste Mathus assigned an issue to Michael Pailloncy Jenkins / JENKINS-53631 Number of instances shows the wrong number Change By: Baptiste Mathus Assignee: R. Tyler Croy Michael Pailloncy 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-53631) Number of instances shows the wrong number
Title: Message Title Baptiste Mathus started work on JENKINS-53631 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53631) Number of instances shows the wrong number
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53631 Number of instances shows the wrong number Change By: Baptiste Mathus Attachment: issue.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-53631) Number of instances shows the wrong number
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53631 Number of instances shows the wrong number Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-17 21:01 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-53493) Browse pipeline workspaces
Title: Message Title Devin Nusbaum resolved as Duplicate Rafael Pestano thanks for reporting the issue! This looks like a duplicate of the long-standing RFE JENKINS-26138, so I am going to close it as a duplicate. Jenkins is a community project, so you are more than welcome to try to implement the feature if it is important to you and we are happy to help review any PRs you create. Jenkins / JENKINS-53493 Browse pipeline workspaces Change By: Devin Nusbaum Status: Open Resolved Resolution: Duplicate 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-9146) Allow archiving of empty directories to be enabled/disabled
Title: Message Title Maciej Załucki commented on JENKINS-9146 Re: Allow archiving of empty directories to be enabled/disabled I'd like to emphasize that fix for JENKINS-3227 changed default behavior without any notiece, it should be added as an option back then. Now this ticket lays down for 7 years and default behavior is not what you would usually expect, on the other hand you can't just change current default which was used for 7 years since that feral fix. Currently most reasonable option is to add visible checkbox to let is archive empty directories. Don't move it to advanced, make it visible so new user knows right away that it does not archive everything. 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-53630) Error while serving any http://jenkinsURL/configSubmit
Title: Message Title Vladymyr Yuhai commented on JENKINS-53630 Re: Error while serving any http://jenkinsURL/configSubmit seems like all changes are applied but with "Oops" problem Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9146) Allow archiving of empty directories to be enabled/disabled
Title: Message Title Maciej Załucki commented on JENKINS-9146 Re: Allow archiving of empty directories to be enabled/disabled It's surely a bug introduced by inadequate "fix". Directory structure is the same kind of artifact as anything else, you should be able to archive whatever you want. In my case I have specific directory structure which is filled up based on several other jobs artifacts. After all automatic processes prepare delivery content we just fill up a few documents and HW test measurements done by hand and should be able to release that. The problem is that we either have to create a few empty directories (delivery won't pass with missing directories in structure) or remove placeholders created to let Jenkins archive those empty directories. You have powerful automation and yet you can't automate creating a few empty directories. So yes, it's a bug. It does not behave as you would expect it to do and it took me too much time to discover that those directories are properly moved but not archived. Not even a log message telling that this thing won't be archived. I thought I messed up something and removed empty directories during delivery preparations. Great way of wasting time. 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-53629) Coverity plugin reporting defect for one stream but not for another stream
Title: Message Title David Joo updated an issue Jenkins / JENKINS-53629 Coverity plugin reporting defect for one stream but not for another stream Change By: David Joo Environment: Jenkins 1.642Ubuntu 14.04Java 1.7.0_80 Coverity Plugin 1.9.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-9146) Allow archiving of empty directories to be enabled/disabled
Title: Message Title Maciej Załucki updated an issue Jenkins / JENKINS-9146 Allow archiving of empty directories to be enabled/disabled Change By: Maciej Załucki Issue Type: Improvement Bug 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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title
Alexander Komarov edited a comment on JENKINS-53625
Re: Provisioning an advanced linux image never continues after init.sh
I was able to make the slave launching work not block by modifying *AzureVMAgentSSHLauncher.java* (executeRemoteCommand()) as follows (wrapping the IOUtils code in a new Runnable). {code:java}// Read from input streamnew Thread(new Runnable() {@Overridepublic void run() {try {try {IOUtils.copy(inputStream, logger);} finally {IOUtils.closeQuietly(inputStream);}// Read from error streamtry {IOUtils.copy(errorStream, logger);} finally {IOUtils.closeQuietly(errorStream);}} catch (Throwable t) {LOGGER.info("AzureVMAgentSSHLauncher: executeRemoteCommand: failed in read thread: " +t);}}}).start();{code} However, this also makes the code not wait for init.sh to finish, which is also bad.
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-53630) Error while serving any http://jenkinsURL/configSubmit
Title: Message Title Vladymyr Yuhai created an issue Jenkins / JENKINS-53630 Error while serving any http://jenkinsURL/configSubmit Issue Type: Bug Assignee: Unassigned Attachments: image-2018-09-17-15-59-05-262.png, jenkins_logs.txt Components: core Created: 2018-09-17 20:10 Environment: Manage Jenkins/Configuration Priority: Blocker Reporter: Vladymyr Yuhai In any case, when I try to submit any changes in my Jenkins configuration I receive the Stack Trace error please see logs from jenkins in attached text file Add Comment
[JIRA] (JENKINS-45419) 'Use Repository' setting does not find other remote urls if multiple repos are added to job
Title: Message Title Boguslaw Klimas started work on JENKINS-45419 Change By: Boguslaw Klimas Status: Reopened 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-50510) use repository settings dublicates branch listing
Title: Message Title Boguslaw Klimas started work on JENKINS-50510 Change By: Boguslaw Klimas 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-51041) git-parameter-plugin: Tags are duplicated in pipeline
Title: Message Title Boguslaw Klimas started work on JENKINS-51041 Change By: Boguslaw Klimas 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-43106) pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic)
Title: Message Title Veaceslav Gaidarji commented on JENKINS-43106 Re: pipeline job hangs forever at checkout GitSCM - after git rev-list (sporadic) Sam Van Oort ping 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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Mark Laurora updated an issue Jenkins / JENKINS-53233 Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Change By: Mark Laurora Attachment: image-2018-09-18-03-52-32-066.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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Mark Laurora commented on JENKINS-53233 Re: Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Also, on the Post-build Actions section > expand the Add post-build action drop-down, I cannot seem to find the Publish test result. 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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Edwin Avedian commented on JENKINS-49033 Re: Issue with HPE Application Automation Tools plugin Rolando, The plugin version is 5.5 and LoadRunner version is 12.55. I think I may have figured out part of the problem which is some scenarios weren't configured with 'Continue on Error' and that caused some of them to stop and fail and hence not have any data. Now for some of the projects we are getting the following errors in the logs which points to some kind of COM error. If you could help us figure out how to resolve these then we should be able to get back on track: Error: Com error. CoCreateInstance Mercury.LR.WSNetReplay failed. -2147221164. [MsgId: MERR-108908] Error: Com error. CoCreateInstance Mercury.LR.WSNetReplay failed. -2147221008. [MsgId: MERR-108908] Thanks, Edwin 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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Mark Laurora commented on JENKINS-53233 Re: Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Thank you for your response Daniel. I appreciate your assistance on this very much! I have installed the plugin you have shared. I was finally able to login however, I keep on seeing this errors in the Console Output: Please let me know what else I can do about this issue. Your response is highly appreciated. 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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Mark Laurora updated an issue Jenkins / JENKINS-53233 Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Change By: Mark Laurora Attachment: image-2018-09-18-03-39-49-653.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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Mark Laurora updated an issue Jenkins / JENKINS-53233 Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Change By: Mark Laurora Attachment: image-2018-09-18-03-40-58-263.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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Mark Laurora updated an issue Jenkins / JENKINS-53233 Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Change By: Mark Laurora Attachment: image-2018-09-18-03-39-49-653.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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title
Alexander Komarov commented on JENKINS-53625
Re: Provisioning an advanced linux image never continues after init.sh
I was able to make the slave launching work by modifying AzureVMAgentSSHLauncher.java (executeRemoteCommand()) as follows (wrapping the IOUtils code in a new Runnable).
// Read from input stream
new Thread(new Runnable() {
@Override
public void run() {
try {
try {
IOUtils.copy(inputStream, logger);
} finally {
IOUtils.closeQuietly(inputStream);
}
// Read from error stream
try {
IOUtils.copy(errorStream, logger);
} finally {
IOUtils.closeQuietly(errorStream);
}
} catch (Throwable t) {
LOGGER.info("AzureVMAgentSSHLauncher: executeRemoteCommand: failed in read thread: " +t);
}
}
}).start();
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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title
Alexander Komarov edited a comment on JENKINS-53625
Re: Provisioning an advanced linux image never continues after init.sh
After some investigation, I know what line hangs... (inputStream copy after running init.sh). I do not know why it hangs though.{noformat}"Computer.threadPoolForRemoting [#1]" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) java.io.PipedInputStream.read(PipedInputStream.java:326) java.io.PipedInputStream.read(PipedInputStream.java:377) java.io.InputStream.read(InputStream.java:101) org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.executeRemoteCommand(AzureVMAgentSSHLauncher.java:409) com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.launch(AzureVMAgentSSHLauncher.java:172) hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748){noformat} Interestingly, nothing unblocks those threads (I now have one for each time I clicked "Relaunch Agent"). I tried stopping SSHd and even shutting down the VM - the threads keep waiting.
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-53629) Coverity plugin reporting defect for one stream but not for another stream
Title: Message Title David Joo updated an issue Jenkins / JENKINS-53629 Coverity plugin reporting defect for one stream but not for another stream Change By: David Joo We have a defect in a project.One Jenkins job looks at Stream A, and on Jenkins, the Coverity plugin detects that defect and reports it.On another Jenkins job, it looks at Steam B, and on Jenkins, the Coverity plugin does not NOT detect that defect.If I check on Coverity Connect, the defect exists in both of the streams. Because I can see both defects on both streams on Coverity Connect, I'm suspecting that the Jenkins Coverity Plugin is the culprit.The streams share the same codebase. 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-53629) Coverity plugin reporting defect for one stream but not for another stream
Title: Message Title David Joo updated an issue Jenkins / JENKINS-53629 Coverity plugin reporting defect for one stream but not for another stream Change By: David Joo Summary: Coverity plugin reporting same defect for one stream but not for another stream 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-53629) Coverity plugin reporting same defect for one stream but not for another stream
Title: Message Title David Joo created an issue Jenkins / JENKINS-53629 Coverity plugin reporting same defect for one stream but not for another stream Issue Type: Bug Assignee: Synopsys SIG Components: coverity-plugin Created: 2018-09-17 18:43 Environment: Jenkins 1.642 Ubuntu 14.04 Java 1.7.0_80 Labels: plugin coverity Priority: Minor Reporter: David Joo We have a defect in a project. One Jenkins job looks at Stream A, and on Jenkins, the Coverity plugin detects that defect and reports it. On another Jenkins job, it looks at Steam B, and on Jenkins, the Coverity plugin does not detect that defect. If I check on Coverity Connect, the defect exists in both of the streams. Because I can see both defects on both streams on Coverity Connect, I'm suspecting that the Jenkins Coverity Plugin is the culprit. The streams share the same codebase.
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Michael Greco edited a comment on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" Maybe try the LTS? ... uggg I try to be a "start-up" kind of guy ... it sounds like there's maybe some integration tests that need to be part of the project ... If you got access to spinning up another VM maybe launch the LTS version and try it out. I know I keep the jenkins data in a docker volume so moving around between these versions to try stuff out on different docker hosts for exactly these situations is helpful. I'm running 2.140 but maybe the plugin works better with the LTS (ok I'm reaching out side the box). 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-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Michael Greco edited a comment on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" Maybe try the LTS? ... uggg I try to be a "start-up" kind of guy ... it sounds like there's maybe some integration tests that need to be part of the project ... If you got access to spinning up another VM maybe launch the LTS version and try it out. I know I keep the jenkins data in a docker volume so moving around between these versions to try stuff out on different docker hosts for exactly these situations is helpful. I'm running 2.140 but maybe the plugin works better with the LTS ? (ok I'm reaching out side the box ) cause if the plugin has a bug then . ..) 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-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Michael Greco edited a comment on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" Maybe try the LTS? ... uggg I try to be a "start-up" kind of guy ... it sounds like there's maybe some integration tests that need to be part of the project ... If you got access to spinning up another VM maybe launch the LTS version and try it out. I know I keep the jenkins data in a docker volume so moving around between these versions to try stuff out on different docker hosts for exactly these situations is helpful. 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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title
Alexander Komarov edited a comment on JENKINS-53625
Re: Provisioning an advanced linux image never continues after init.sh
After some investigation, I know what line hangs... (inputStream copy after running init.sh). I do not know why it hangs though.{noformat}"Computer.threadPoolForRemoting [#1]" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) java.io.PipedInputStream.read(PipedInputStream.java:326) java.io.PipedInputStream.read(PipedInputStream.java:377) java.io.InputStream.read(InputStream.java:101) org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.executeRemoteCommand(AzureVMAgentSSHLauncher.java:409) com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.launch(AzureVMAgentSSHLauncher.java:172) hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748){noformat}
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-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Michael Greco commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" Maybe try the LTS? ... uggg I try to be a "start-up" kind of guy ... it sounds like there's maybe some integration tests that need to be part of the project ... 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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title
Alexander Komarov edited a comment on JENKINS-53625
Re: Provisioning an advanced linux image never continues after init.sh
After some investigation, I know what line hangs... (inputStream copy after running init.sh). I do not know why it hangs though.{noformat}"Computer.threadPoolForRemoting [#1]" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) java.io.PipedInputStream.read(PipedInputStream.java:326) java.io.PipedInputStream.read(PipedInputStream.java:377) java.io.InputStream.read(InputStream.java:101) org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.executeRemoteCommand(AzureVMAgentSSHLauncher.java:409) com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.launch(AzureVMAgentSSHLauncher.java:172) hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) {noformat}
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-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title Alexander Komarov commented on JENKINS-53625 Re: Provisioning an advanced linux image never continues after init.sh After some investigation, I know what line hangs... (inputStream copy after running init.sh). I do not know why it hangs though. "Computer.threadPoolForRemoting [#1]" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) java.io.PipedInputStream.read(PipedInputStream.java:326) java.io.PipedInputStream.read(PipedInputStream.java:377) java.io.InputStream.read(InputStream.java:101) org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.executeRemoteCommand(AzureVMAgentSSHLauncher.java:409) com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.launch(AzureVMAgentSSHLauncher.java:172) hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) 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
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Jon B commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" If left unfixed for much longer, our organization is going to be forced to use another technology for CICD since this is causing widespread pain and confidence lost in this technology among our hundreds of developers who are using Jenkins at our company. 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-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Michael Greco edited a comment on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" I've been noticing this for MONTHS. And in case people don't realize the master branch of the docker-plugin wasn't building today 9/17/18 :[https://ci.jenkins.io/job/Plugins/job/docker-plugin/] Anyways this weekend I loaded docker-plugin build 1.1.5 and today on every build I was getting "The channel is closing down or has closed down" as my jobs would still appear to be running even though obviously the container was gone. I would up downgrading to an older build I have : |1.1.5-SNAPSHOT (private-554bbf8a-win2012-6d34b0$)| in which the problem seems to happen less. I went so far as to rebuild some of my "build containers" as they are created "FROM jenkinsci/slave" and I noticed that has had an update sometime in August. Again It made no difference using the "released 1.1.5" version of docker-plugin (every thing wound up in the state of "The channel is closing down or has closed down") and that's when I noticed the master branch isn't building either ... so I just went back to my earlier build. 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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Daniel Danan commented on JENKINS-53233 Re: Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 The uploaded files are named micro-focus-performance-center-integration.z01 and micro-focus-performance-center-integration.zip. 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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Daniel Danan updated an issue Jenkins / JENKINS-53233 Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Change By: Daniel Danan Attachment: hp-application-automation-tools-plugin.zip 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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Daniel Danan updated an issue Jenkins / JENKINS-53233 Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Change By: Daniel Danan Attachment: hp-application-automation-tools-plugin.z01 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-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Daniel Danan updated an issue Jenkins / JENKINS-53233 Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Change By: Daniel Danan Attachment: micro-focus-performance-center-integration.zip Attachment: micro-focus-performance-center-integration.z01 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-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Michael Greco commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" I've been noticing this for MONTHS. And in case people don't realize the master branch of the docker-plugin wasn't building today 9/17/18 : https://ci.jenkins.io/job/Plugins/job/docker-plugin/ Anyways this weekend I loaded docker-plugin build 1.1.5 and today on every build I was getting "The channel is closing down or has closed down" as my jobs would still appear to be running even though obviously the container was gone. I would up downgrading to an older build I have : 1.1.5-SNAPSHOT (private-554bbf8a-win2012-6d34b0$) in which the problem seems to happen less. I went so far as to rebuild some of my "build containers" as they are created "FROM jenkinsci/slave" and I noticed that has had an update sometime in August. Again It made no difference using the "released 1.1.5" version of docker-plugin (every thing wound up in the state of "The channel is closing down or has closed down") and that's when I noticed the master branch isn't building either ... so I just went back to my earlier build. 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
[JIRA] (JENKINS-53233) Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001
Title: Message Title Daniel Danan commented on JENKINS-53233 Re: Unable to run Performance Test in Jenkins - executeRequest exception: Operation failed. Error code: 1001 Hi Mark, Please keep bugging me as much you need, i am very happy to help and I will do everything needed so this integration works properly in your environment. Also excuse my lack of response during this period of time as i am in a period of time in which I am mostly out of the office and partially returning to work when i can (I will be ooo for two days, back on Thursday only and then I will be ooo again during next week). I would like you to use a plugin I am developing in which I have integrated the functionality allowing to run tests as this is my current working platform of work. This plugin will contain two step build types. one for syncing performance scripts from Git to PC and you can ignore it (it is being QA and documented) and one allowing to run test which is named "Run performance test using Performance Center". Please use the last one and provide similar input when configuring the job in Jenkins. If you need documentation, use the documentation specified here: https://wiki.jenkins.io/display/JENKINS/MICRO+FOCUS+Application+Automation+Tools and not the one from the helps (some new fields are not yet documented). You will find this plugin compressed to two spitted files and upload to this Jenkins issue as attachment. regards, Daniel 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-53626) Evergreen backend UI should show number of instances per flavor
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53626 Evergreen backend UI should show number of instances per flavor Change By: Baptiste Mathus The backend now shows that nice "3 actively connected" information.I think it would nice to also get the subdivision in flavors there . (my use case 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-53626) Evergreen backend UI should show number of instances per flavor
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53626 Evergreen backend UI should show number of instances per flavor Change By: Baptiste Mathus The backend now shows that nice "3 actively connected" information.I think it would nice to also get the subdivision in flavors there (my use case . 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-53628) Evergreen UI messages should wrap on the screen
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-53628 Evergreen UI messages should wrap on the screen Issue Type: Bug Assignee: R. Tyler Croy Attachments: Selection_548.png Components: evergreen Created: 2018-09-17 18:13 Priority: Minor Reporter: R. Tyler Croy Basically, I'm awesome at HTML Add Comment
[JIRA] (JENKINS-53627) Getting java.lang.NoClassDefFoundError: org/jenkinsci/plugins/workflow/job/WorkflowRun Exception while running Job
Title: Message Title Bidhan Saha created an issue Jenkins / JENKINS-53627 Getting java.lang.NoClassDefFoundError: org/jenkinsci/plugins/workflow/job/WorkflowRun Exception while running Job Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2018-09-17 18:12 Environment: OS: Linux JRE 1.8 Jenkins 2.7.1 Labels: Jenkins Priority: Critical Reporter: Bidhan Saha We are getting the below exception in Jenkins 2.7.1 while running the job. we've tried to install Pipeline SCM API in Blue Ocean to use the Pipeline feature. but after installing the plugin it got this error. we have uninstalled the plugin but it still happening there.We are getting the below exception in Jenkins 2.7.1 while running the job. we've tried to install Pipeline SCM API in Blue Ocean to use the Pipeline feature. but after installing the plugin it got this error. we have uninstalled the plugin but it still happening there. FATAL: org/jenkinsci/plugins/workflow/job/WorkflowRunjava.lang.NoClassDefFoundError: org/jenkinsci/plugins/workflow/job/WorkflowRun at org.jenkinsci.plugins.workflow.job.WorkflowJob$SCMListenerImpl.onCheckout(WorkflowJob.java:750) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at
[JIRA] (JENKINS-53534) Jenkinsfile checkout fails on Merge from Fork using GitLab
Title: Message Title Nicolas De Loof updated an issue Jenkins / JENKINS-53534 Jenkinsfile checkout fails on Merge from Fork using GitLab Change By: Nicolas De Loof Component/s: jenkinsfile-runner 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-53626) Evergreen backend UI should show number of instances per flavor
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53626 Evergreen backend UI should show number of instances per flavor Change By: Baptiste Mathus Sprint: Evergreen - Milestone 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53626) Evergreen backend UI should show number of instances per flavor
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53626 Evergreen backend UI should show number of instances per flavor Change By: Baptiste Mathus Labels: evergreen evergreen-triggered 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-53626) Evergreen backend UI should show number of instances per flavor
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53626 Evergreen backend UI should show number of instances per flavor Issue Type: Improvement Assignee: R. Tyler Croy Components: evergreen Created: 2018-09-17 17:37 Priority: Minor Reporter: Baptiste Mathus The backend now shows that nice "3 actively connected" information. I think it would nice to also get the subdivision in flavors there. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-53625
Provisioning an advanced linux image never continues after init.sh
Change By:
Alexander Komarov
h1. ConfigurationIn Azure, I've defined a Resource Group with a storage account and a virtual network. Launching VMs manually works. In Jenkins, I've configured a Cloud with all the settings above. I'm using an Advanced Image Configuration because I need to specify a virtual network to launch into. Settings are as follows: * Size: Standard A0 * Storage Account Type: Standard_LRS * Storage Account Name: Use existing (pre-created) * Disk: Managed * Image Reference: ** Canonical ** UbuntuServer ** 16.04.0-LTS ** latest * Launch Method: SSH * Initialization Script: {color:#00875a}wget [https://cdn.azul.com/zulu/bin/zulu8.31.0.1-jdk8.0.181-linux_amd64.deb] -O zulu8.deb{color} {color:#00875a}sudo apt install -y ./zulu8.deb{color} {color:#00875a}sudo apt install -y git{color} {color:#00875a}logger "$0 is done!!!"{color} {color:#00875a}echo "This is a success, ignoring failure"{color} * Run as root: false * Don't use VM if initialization script fails: false h1. What Happens # Instance is launched from a pipeline job ( node('matching-label') {} ) # init.sh is run (to the end). My log statement is in /var/log/syslog. # Nothing else happens. Slave is never provisioned.h1. h1. LogsI've created a Log Recorder for com.microsoft.azure.vmagent.remote and all log levels:{noformat}Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher connectToSsh AzureVMAgentSSHLauncher: connectToSsh: start Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher getRemoteSession AzureVMAgentSSHLauncher: getRemoteSession: getting remote session for user XXX to host XX.eastus.cloudapp.azure.com:22 Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher getRemoteSession AzureVMAgentSSHLauncher: getRemoteSession: Got remote session for user XXX to host XX.eastus.cloudapp.azure.com:22 Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher connectToSsh AzureVMAgentSSHLauncher: connectToSsh: Got remote connection Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher executeRemoteCommand AzureVMAgentSSHLauncher: executeRemoteCommand: starting test -e ~/.azure-agent-init Sep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher executeRemoteCommand AzureVMAgentSSHLauncher: executeRemoteCommand: executed successfully Sep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher launch AzureVMAgentSSHLauncher: launch: Init script is not null, preparing to execute script remotely Sep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher copyFileToRemote AzureVMAgentSSHLauncher: copyFileToRemote: Initiating file transfer to init.sh Sep 17, 2018 10:00:00 AM FINE
[JIRA] (JENKINS-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-53625
Provisioning an advanced linux image never continues after init.sh
Change By:
Alexander Komarov
h1. ConfigurationIn Azure, I've defined a Resource Group with a storage account and a virtual network. Launching VMs manually works. In Jenkins, I've configured a Cloud with all the settings above. I'm using an Advanced Image Configuration because I need to specify a virtual network to launch into. Settings are as follows: * Size: Standard A0 * Storage Account Type: Standard_LRS * Storage Account Name: Use existing (pre-created) * Disk: Managed * Image Reference: ** Canonical ** UbuntuServer ** 16.04.0-LTS ** latest * Launch Method: SSH * Initialization Script: {color:#00875a}wget [https://cdn.azul.com/zulu/bin/zulu8.31.0.1-jdk8.0.181-linux_amd64.deb] -O zulu8.deb{color} {color:#00875a}sudo apt install -y ./zulu8.deb{color} {color:#00875a}sudo apt install -y git{color} {color:#00875a}logger "$0 is done!!!"{color} {color:#00875a}echo "This is a success, ignoring failure"{color} * Run as root: false * Don't use VM if initialization script fails: false h1. What Happens # Instance is launched from a pipeline job ( node('matching-label') {} ) # init.sh is run (to the end) . My log statement is in /var/log/syslog. # Nothing else happens. Slave is never provisioned.h1. LogsI've created a Log Recorder for com.microsoft.azure.vmagent.remote and all log levels:{noformat}Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher connectToSsh AzureVMAgentSSHLauncher: connectToSsh: start Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher getRemoteSession AzureVMAgentSSHLauncher: getRemoteSession: getting remote session for user XXX to host XX.eastus.cloudapp.azure.com:22 Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher getRemoteSession AzureVMAgentSSHLauncher: getRemoteSession: Got remote session for user XXX to host XX.eastus.cloudapp.azure.com:22 Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher connectToSsh AzureVMAgentSSHLauncher: connectToSsh: Got remote connection Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher executeRemoteCommand AzureVMAgentSSHLauncher: executeRemoteCommand: starting test -e ~/.azure-agent-init Sep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher executeRemoteCommand AzureVMAgentSSHLauncher: executeRemoteCommand: executed successfully Sep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher launch AzureVMAgentSSHLauncher: launch: Init script is not null, preparing to execute script remotely Sep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher copyFileToRemote AzureVMAgentSSHLauncher: copyFileToRemote: Initiating file transfer to init.sh Sep 17, 2018 10:00:00 AM FINE
[JIRA] (JENKINS-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-53625 Provisioning an advanced linux image never continues after init.sh Change By: Alexander Komarov Summary: Provisioning a custom an advanced linux image never continues after init.sh 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-53625) Provisioning a custom linux image never continues after init.sh
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-53625
Provisioning a custom linux image never continues after init.sh
Change By:
Alexander Komarov
h1. ConfigurationIn Azure, I've defined a Resource Group with a storage account and a virtual network. Launching VMs manually works. In Jenkins, I've configured a Cloud with all the settings above. I'm using an Advanced Image Configuration because I need to specify a virtual network to launch into. Settings are as follows: * Size: Standard A0 * Storage Account Type: Standard_LRS * Storage Account Name: Use existing (pre-created) * Disk: Managed * Image Reference: ** Canonical ** UbuntuServer ** 16.04.0-LTS ** latest * Launch Method: SSH * Initialization Script:{color:#00875a}wget [ https://cdn.azul.com/zulu/bin/zulu8.31.0.1-jdk8.0.181-linux_amd64.deb ] -O zulu8.deb{color}{color:#00875a}sudo apt install -y ./zulu8.deb{color}{color:#00875a}sudo apt install -y git{color}{color:#00875a}logger "$0 is done!!!"{color}{color:#00875a}echo "This is a success, ignoring failure"{color} * Run as root: false * Don't use VM if initialization script fails: false h1. What Happens # Instance is launched from a pipeline job ( node('matching-label') {} ) # init.sh is run (to the end) # Nothing else happens. Slave is never provisioned.h1. LogsI've created a Log Recorder for com.microsoft.azure.vmagent.remote and all log levels: {noformat} Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher connectToSshAzureVMAgentSSHLauncher: connectToSsh: startSep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher getRemoteSessionAzureVMAgentSSHLauncher: getRemoteSession: getting remote session for user XXX to host XX.eastus.cloudapp.azure.com:22Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher getRemoteSessionAzureVMAgentSSHLauncher: getRemoteSession: Got remote session for user XXX to host XX.eastus.cloudapp.azure.com:22Sep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher connectToSshAzureVMAgentSSHLauncher: connectToSsh: Got remote connectionSep 17, 2018 9:59:58 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher executeRemoteCommandAzureVMAgentSSHLauncher: executeRemoteCommand: starting test -e ~/.azure-agent-initSep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher executeRemoteCommandAzureVMAgentSSHLauncher: executeRemoteCommand: executed successfullySep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher launchAzureVMAgentSSHLauncher: launch: Init script is not null, preparing to execute script remotelySep 17, 2018 9:59:59 AM INFO com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher copyFileToRemoteAzureVMAgentSSHLauncher: copyFileToRemote: Initiating file transfer to init.shSep 17, 2018 10:00:00 AM FINE com.microsoft.azure.vmagent.AzureVMCloud getAzureAgentTemplateAzureVMCloud:
[JIRA] (JENKINS-53625) Provisioning a custom linux image never continues after init.sh
Title: Message Title Alexander Komarov created an issue Jenkins / JENKINS-53625 Provisioning a custom linux image never continues after init.sh Issue Type: Improvement Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2018-09-17 17:18 Environment: Centos 6.8 Jenkins 2.141 azure-vm-agents: 1.73 Priority: Minor Reporter: Alexander Komarov Configuration In Azure, I've defined a Resource Group with a storage account and a virtual network. Launching VMs manually works. In Jenkins, I've configured a Cloud with all the settings above. I'm using an Advanced Image Configuration because I need to specify a virtual network to launch into. Settings are as follows: Size: Standard A0 Storage Account Type: Standard_LRS Storage Account Name: Use existing (pre-created) Disk: Managed Image Reference: Canonical UbuntuServer 16.04.0-LTS latest Launch Method: SSH Initialization
[JIRA] (JENKINS-53624) Branch indexing schedules builds for other branches and repos
Title: Message Title
Joe Auty updated an issue
Jenkins / JENKINS-53624
Branch indexing schedules builds for other branches and repos
Change By:
Joe Auty
Hello,I'm having a problem that seems pretty much identical to this one for the Gitlab Branch Source Plugin: [https://github.com/Argelbargel/gitlab-branch-source-plugin/issues/45]I'm assuming the root issue is very similar, if not identical. On Github webhook triggers a number of branch indexing jobs are kicked off for builds in the current repo, as well as for other repos. I'm using BlueOcean.Questions:1) Is this a known issue?2) Is there a workaround?3) As a possible means to come up with a workaround, are there any variables I can latch onto that would give me visibility into the context so in my Jenkinsfile pipeline I can do the following on branch indexing:{noformat}currentBuild.result = 'NOT_BUILT'error('Aborting build triggered by scan process'){noformat}This was a suggestion in the above Gitlab thread, only I'm not seeing an equivalent to `gitlabActionType` in the list of environment variables (output with "env"). It would be great if I could ignore builds from branch indexing as a short term workaround without disabling the webhooks entirely .
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
[JIRA] (JENKINS-53624) Branch indexing schedules builds for other branches and repos
Title: Message Title
Joe Auty updated an issue
Jenkins / JENKINS-53624
Branch indexing schedules builds for other branches and repos
Change By:
Joe Auty
Hello,I'm having a problem that seems pretty much identical to this one for the Gitlab Branch Source Plugin: [https://github.com/Argelbargel/gitlab-branch-source-plugin/issues/45]I'm assuming the root issue is very similar, if not identical. On Github webhook triggers a number of branch indexing jobs are kicked off for builds in the current repo, as well as for other repos. I'm using BlueOcean.Questions:1) Is this a known issue?2) Is there a workaround?3) As a possible means to come up with a workaround, are there any variables I can latch onto that would give me visibility into the context so in my Jenkinsfile pipeline I can do the following on branch indexing:{noformat}currentBuild.result = 'NOT_BUILT'error('Aborting build triggered by scan process'){noformat}This was a suggestion in the above Gitlab thread, only I'm not seeing an equivalent to `gitlabActionType` in the list of environment variables (output with "env"). It would be great if I could ignore builds from branch indexing as a short term workaround.
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
[JIRA] (JENKINS-53624) Branch indexing schedules builds for other branches and repos
Title: Message Title
Joe Auty updated an issue
Jenkins / JENKINS-53624
Branch indexing schedules builds for other branches and repos
Change By:
Joe Auty
Hello,I'm having a problem that seems pretty much identical to this one for the Gitlab Branch Source Plugin: [https://github.com/Argelbargel/gitlab-branch-source-plugin/issues/45]I'm assuming the root issue is very similar, if not identical. On Github webhook triggers a number of branch indexing jobs are kicked off for builds in other repos. I'm using BlueOcean.Questions:1) Is this a known issue?2) Is there a workaround?3) As a possible means to come up with a workaround, are there any variables I can latch onto that would give me visibility into the context so in my Jenkinsfile pipeline I can do the following on branch indexing : {noformat}currentBuild.result = 'NOT_BUILT'error('Aborting build triggered by scan process'){noformat} This was a suggestion in the above Gitlab thread, only I'm not seeing an equivalent to `gitlabActionType` in the list of environment variables (output with "env"). It would be great if I could ignore builds from branch indexing as a short term workaround.
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
[JIRA] (JENKINS-53624) Branch indexing schedules builds for other branches and repos
Title: Message Title
Joe Auty created an issue
Jenkins / JENKINS-53624
Branch indexing schedules builds for other branches and repos
Issue Type:
Bug
Assignee:
Kirill Merkushev
Components:
github-branch-source-plugin, github-plugin
Created:
2018-09-17 17:02
Priority:
Minor
Reporter:
Joe Auty
Hello, I'm having a problem that seems pretty much identical to this one for the Gitlab Branch Source Plugin: https://github.com/Argelbargel/gitlab-branch-source-plugin/issues/45 I'm assuming the root issue is very similar, if not identical. On Github webhook triggers a number of branch indexing jobs are kicked off for builds in other repos. I'm using BlueOcean. Questions: 1) Is this a known issue? 2) Is there a workaround? 3) As a possible means to come up with a workaround, are there any variables I can latch onto that would give me visibility into the context so in my Jenkinsfile pipeline I can:
currentBuild.result = 'NOT_BUILT'
error('Aborting build triggered by scan process')
This was a suggestion in the above Gitlab thread, only I'm not seeing an equivalent to `gitlabActionType` in the list of environment variables (output with "env"). It would be great if I could ignore builds from branch indexing as a short term workaround.
[JIRA] (JENKINS-53149) GitHubCommitStatusSetter is not reading proper commit id from a shared library
Title: Message Title Manuel de la Peña commented on JENKINS-53149 Re: GitHubCommitStatusSetter is not reading proper commit id from a shared library The proposed solution has been merged 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-42192) permissive-security-script plugin should not log full stacktrace
Title: Message Title Alexander Komarov updated JENKINS-42192 Jenkins / JENKINS-42192 permissive-security-script plugin should not log full stacktrace Change By: Alexander Komarov Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52493) Declarative: Steps don't run inside container with "dockerfile true"
Title: Message Title Mikko Ville Valjento commented on JENKINS-52493 Re: Declarative: Steps don't run inside container with "dockerfile true" Any updates on this? I seem to run in to the same problem with Jenkins ver. 2.138.1 trying to run a simple pipeline. The commands are executed outside the Docker container defined as the agent. 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-52493) Declarative: Steps don't run inside container with "dockerfile true"
Title: Message Title Mikko Ville Valjento updated an issue Jenkins / JENKINS-52493 Declarative: Steps don't run inside container with "dockerfile true" Change By: Mikko Ville Valjento Comment: Any updates on this? I seem to run in to the same problem with Jenkins ver. 2.138.1 trying to run a simple pipeline. The commands are executed outside the Docker container defined as the agent. 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-53465) ChannelClosedException in Maven channel
Title: Message Title Jesse Glick commented on JENKINS-53465 Re: ChannelClosedException in Maven channel You should not worry. 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-53623) Add Job DSL support for Parameter Separator Plugin
Title: Message Title Gosha Frost updated an issue Jenkins / JENKINS-53623 Add Job DSL support for Parameter Separator Plugin Change By: Gosha Frost Component/s: parameter-separator-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.
