[JIRA] (JENKINS-51063) Multibranch pipeline does not handle correctly webhook of kind tag created
Title: Message Title Nikolas Falco updated JENKINS-51063 Jenkins / JENKINS-51063 Multibranch pipeline does not handle correctly webhook of kind tag created Change By: Nikolas Falco Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51063) Multibranch pipeline does not handle correctly webhook of kind tag created
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-51063 Multibranch pipeline does not handle correctly webhook of kind tag created Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54255) xUnit sets build status incorrectly
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-54255
xUnit sets build status incorrectly
Change By:
Nikolas Falco
We are counting on the xUnit "Publish xUnit test report" post-build step to properly set the build status. The Failed Tests section has 4 inputs that let you set thresholds to set the build to either UNSTABLE or FAILED based on whether the Total number of Failed tests, or total number of New failures, exceeds the specified thresholds.There is something broken in the test of the number of failures against the specified threshold. A recent build has the number of actual failures < the specified threshold for Total, and the number of New failures (1) < the specified threshold for New (5). It set the build to failed anyway.It appears that whenever the number of New failed tests is positive, that is reported as a build failure even when that number is less than the specified threshold. * {noformat} 00:17:17 * [xUnit] [INFO] - Starting to record. * 00:17:17 * [xUnit] [INFO] - Processing CppUnit-1.12.1 (default) * 00:17:18 * [xUnit] [INFO] - [CppUnit-1.12.1 (default)] - 1 test report file(s) were found with the pattern '**/testResult.xml' relative to '/home/bnet/jenkins/workspace/Linux-integration-test' for the testing framework 'CppUnit-1.12.1 (default)'. * 00:17:18 * [xUnit] [INFO] - Check 'Failed Tests' threshold. * 00:17:18 * [xUnit] [INFO] - Check 'Skipped Tests' threshold. * 00:17:18 * [xUnit] [INFO] - Setting the build status to FAILURE * 00:17:18 * [xUnit] [INFO] - Stopping recording. {noformat}
Add Comment
[JIRA] (JENKINS-54255) xUnit sets build status incorrectly
Title: Message Title Nikolas Falco edited a comment on JENKINS-54255 Re: xUnit sets build status incorrectly Update xunit plugin to latest version . If happens again please post the cppunit report and the xunit configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file Same here after update from jenkins 2.107.3 to 2.138.2 and cppcheck plugin update from 1.21 to 1.24! * jenkins 2.138.2 * cppcheck plugin 1.24 * cppcheck 1.85Report not located in subdirectory.Downgrade the cppcheck plugin to 1.21 is not a solution, because the plugin can't render the diff html file. We urgently need feedback as our qa pipeline is affected. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54210) Jenkins integration with load runner
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-54210 Re: Jenkins integration with load runner Hello Mohan, The test is unstable because the Service Level Agreement fails (you set a goal value of 0, whilst the actualy value is 0.091). Regards, Rolando Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51308) [JEP-305] Incrementalify the Metrics plugin
Title: Message Title Baptiste Mathus updated JENKINS-51308 Finally done, and filed https://github.com/jenkins-infra/evergreen/pull/333 to close the loop. Jenkins / JENKINS-51308 [JEP-305] Incrementalify the Metrics plugin Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54056) Implement Evergreen automated Update Level rollback
Title: Message Title Baptiste Mathus updated JENKINS-54056 It's working AFAICT, also automatically tested. Also demoed last week many times during a public presentation at Day Of Jenkins in Copenhagen. Jenkins / JENKINS-54056 Implement Evergreen automated Update Level rollback Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54263) Fix/make sure the AWS flavor still works
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54263 Fix/make sure the AWS flavor still works Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-26 07:58 Priority: Major Reporter: Baptiste Mathus Last time I tried, for some reason, it seemed to not be working anymore. We should fix it. (Ideally, this should also be tested automatically during PR build rather sooner than later. I'm going to make sure we have a Jira filed for this and it's tagged correctly to look into it for M2). Add Comment
[JIRA] (JENKINS-54242) Redundant runs using Poll SCM (No changes)
Title: Message Title
Aleksandrs Surname edited a comment on JENKINS-54242
Re: Redundant runs using Poll SCM (No changes)
{color:#172b4d}This is interesting case, because first build was with changes and after it probably noticed 114945 by but he ran 114944 one more time...{color}h1. Build #28 (Oct 25, 2018 12:50:09 PM)|!http://sostools.corp.tele2.com:8080/static/de0f188a/images/48x48/notepad.png!|Revision: 114944Changes # test is broken for jenkins test;|h1. Build #29 (Oct 25, 2018 1:05:09 PM)|!http://sostools.corp.tele2.com:8080/static/de0f188a/images/48x48/notepad.png!|Revision: 114944No changes.|h1. Build #30 (Oct 25, 2018 1:10:09 PM)|!http://sostools.corp.tele2.com:8080/static/de0f188a/images/48x48/notepad.png!|Revision: 114945Changes # back to stable 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-54015) ldap authentication problem
Title: Message Title runze xia commented on JENKINS-54015 Re: ldap authentication problem http://forum.spring.io/forum/spring-projects/data/ldap/96508-ldap-authentication-intermittent-socket-closed-error I think this is a problem with the dependencies of the ldap plugin. https://issues.jenkins-ci.org/browse/JENKINS-5303 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54015) ldap authentication problem
Title: Message Title runze xia edited a comment on JENKINS-54015 Re: ldap authentication problem [http://forum.spring.io/forum/spring-projects/data/ldap/96508-ldap-authentication-intermittent-socket-closed-error]I think this is a problem with the dependencies of the ldap plugin. https://issues.jenkins-ci.org/browse/JENKINS-5303 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title runze xia commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release http://forum.spring.io/forum/spring-projects/data/ldap/96508-ldap-authentication-intermittent-socket-closed-error Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title
Nikolas Falco edited a comment on JENKINS-53237
Re: Maven Surefire Report XSD requires a fix
{quote}Not sure why you validate XML but anyway.{quote}I validate report in input to reduce possible unexpected parse/transformer (XSLT for not junit report) errors. This make easier resolve bugs.Since JUnit it's just a library and does not produce a report since 2.0 of xunit-plugin, supported JUnit report are those produced by the ant task and maven surefire. [ The My XSD is compatible for both|https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd].{quote}Parsing the XML and displaying the statistics is what has to be done by the plugins.{quote}Yes but testsuite attributes meaningful depends from version.What I wanted to say with "At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XML" is that when rerun feature was introduced if had been added additional attribute for flaky failures (maybe also an attribute for runs) the XML would be full backward compatible at all because the attributes had the same meaningful of before. Now we have the root testsuite element that declare 10 tests and 2 failures when in real you have only 7 test method (but 10 runs...) and no failures.{code:xml}{code}About the XSD version for what I can see for other software I consider a best practice publish XSD for each version and the XML declare the path to the specific XSD version{code:xml} (to be compatible with actual){code}{quote}If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used.{quote}From the point of view of end user if I get an error updating from 2.x to 2.22.1 I have good reason to open a bug. In 3.x thanks to semantic versioning you can answer "we have changed the format". These kind of changes from 2.22.0 to 2.22.1 is much less reasonable, it looks more like a bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Not sure why you validate XML but anyway. I validate report in input to reduce possible unexpected parse/transformer (XSLT for not junit report) errors. This make easier resolve bugs. Since JUnit it's just a library and does not produce a report since 2.0 of xunit-plugin, supported JUnit report are those produced by the ant task and maven surefire. The XSD is compatible for both. Parsing the XML and displaying the statistics is what has to be done by the plugins. Yes but testsuite attributes meaningful depends from version. What I wanted to say with "At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XML" is that when rerun feature was introduced if had been added additional attribute for flaky failures (maybe also an attribute for runs) the XML would be full backward compatible at all because the attributes had the same meaningful of before. Now we have the root testsuite element that declare 10 tests and 2 failures when in real you have only 7 test method (but 10 runs...) and no failures. "...FooTest" time="0" tests="7" errors="0" skipped="0" failures="0" runs="10" flakyfailures="2"> About the XSD version for what I can see for other software I consider a best practice publish XSD for each version and the XML declare the path to the specific XSD version "https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report" ... /> (to be compatible with actual) "https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-2.2.xsd" ... /> "https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd" ... /> If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used. From the point of view of end user if I get an error updating from 2.x to 2.22.1 I have good reason to open a bug. In 3.x thanks to semantic versioning you can answer "we have changed the format". These kind of changes from 2.22.0 to 2.22.1 is much less reasonable, it looks more like a bug.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title
Nikolas Falco edited a comment on JENKINS-53237
Re: Maven Surefire Report XSD requires a fix
{quote}Not sure why you validate XML but anyway.{quote}I validate report in input to reduce possible unexpected parse/transformer (XSLT for not junit report) errors. This make easier resolve bugs.Since JUnit it's just a library and does not produce a report since 2.0 of xunit-plugin, supported JUnit report are those produced by the ant task and maven surefire. [My XSD is compatible for both|https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd].{quote}Parsing the XML and displaying the statistics is what has to be done by the plugins.{quote}Yes but testsuite attributes meaningful depends from version.What I wanted to say with " ?? At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XML " ?? is that when rerun feature was introduced if had been added additional attribute for flaky failures (maybe also an attribute for runs) the XML would be full backward compatible at all because the attributes had the same meaningful of before. Now we have the root testsuite element that declare 10 tests and 2 failures when in real you have only 7 test method (but 10 runs...) and no failures.{code:xml}{code}About the XSD version for what I can see for other software I consider a best practice publish XSD for each version and the XML declare the path to the specific XSD version{code:xml} (to be compatible with actual){code}{quote}If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used.{quote}From the point of view of end user if I get an error updating from 2.x to 2.22.1 I have good reason to open a bug. In 3.x thanks to semantic versioning you can answer "we have changed the format". These kind of changes from 2.22.0 to 2.22.1 is much less reasonable, it looks more like a bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title
Nikolas Falco edited a comment on JENKINS-53237
Re: Maven Surefire Report XSD requires a fix
{quote}Not sure why you validate XML but anyway.{quote} I validate report in input to reduce possible unexpected parse/transformer (XSLT for not junit report) errors. This make easier resolve bugs. Since JUnit it's just a library and does not produce a report since 2.0 of xunit-plugin, supported JUnit report are those produced by the ant task and maven surefire. [My XSD is compatible for both|https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd]. I validate report in input to reduce possible unexpected parse/transformer (XSLT for not junit report) errors. This make easier resolve bugs because XSD filter out JUnit reports produced by other tools that declare to produce a correct report but they produces custom attributes and some times a different XML structure that could failure in the parser. {quote}Parsing the XML and displaying the statistics is what has to be done by the plugins.{quote}Yes but testsuite attributes meaningful depends from version.What I wanted to say with ??At this point why do not add an attribute to mark the differences between flaky failures and failure also in the XML?? is that when rerun feature was introduced if had been added additional attribute for flaky failures (maybe also an attribute for runs) the XML would be full backward compatible at all because the attributes had the same meaningful of before. Now we have the root testsuite element that declare 10 tests and 2 failures when in real you have only 7 test method (but 10 runs...) and no failures.{code:xml}{code}About the XSD version for what I can see for other software I consider a best practice publish XSD for each version and the XML declare the path to the specific XSD version{code:xml} (to be compatible with actual){code}{quote}If the change present in 3.0 version, we would have to wait quite long time and there would be a risk that the rerun feature as well as flaky failures are heavily used.{quote}From the point of view of end user if I get an error updating from 2.x to 2.22.1 I have good reason to open a bug. In 3.x thanks to semantic versioning you can answer "we have changed the format". These kind of changes from 2.22.0 to 2.22.1 is much less reasonable, it looks more like a bug.
Add Comment
[JIRA] (JENKINS-54263) Fix/make sure the AWS flavor still works
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54263 Fix/make sure the AWS flavor still works 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-54234) p4 sync sometimes produces no file, or empty file, when readFile is used immediately after
Title: Message Title Paul Allen assigned an issue to Karl Wirth Jenkins / JENKINS-54234 p4 sync sometimes produces no file, or empty file, when readFile is used immediately after Change By: Paul Allen Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54234) p4 sync sometimes produces no file, or empty file, when readFile is used immediately after
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-54234 p4 sync sometimes produces no file, or empty file, when readFile is used immediately after Change By: Paul Allen Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54234) p4 sync sometimes produces no file, or empty file, when readFile is used immediately after
Title: Message Title
Paul Allen commented on JENKINS-54234
Re: p4 sync sometimes produces no file, or empty file, when readFile is used immediately after
Hi Sean, I'm no expert on Jenkinsfile Groovy scripts, but the User Groups might be able to help. I don't normally run p4sync inside a script block, but it seems to make no difference. Here is a simple test Jenkinsfile:
pipeline {
agent any
stages {
stage('Stage') {
steps {
script {
p4sync(credential: 'phooey',
populate: forceClean(parallel: [enable: true, minbytes: '1024', minfiles: '1', threads: '4']),
source: depotSource('//depot/...'))
readFile 'projA/Project.txt'
}
}
}
}
}
I have enabled parallel sync just incase, but have not been able to reproduce your issue (//depot/... represents about 1600 files). The p4sync seems to block until all the files are synced. Have you tried checkout instead of p4sync? The p4sync step is extended from SCMStep which seems to use AbstractSynchronousNonBlockingStepExecution, but it is not clear if this is asynchronous in the Jenkinsfile script.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54264) Automatically file PRs for repetitive tasks
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54264 Automatically file PRs for repetitive tasks Issue Type: Epic Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-26 08:54 Priority: Critical Reporter: Baptiste Mathus Problem statement There are a few repetitve tasks for the project that we have been handling manually until now that should be automated. They share the common feature that they end up being a PR on the Evergreen source repo itself or another. Running plugins or core upgrades, or npm packages security bumps, or bumping Expected behavior These tasks should be automated. We should write a common tool that makes it easy to file a PR against a given repo with a set of change that a script or so has created. Add Comment
[JIRA] (JENKINS-54264) Automatically file PRs for repetitive tasks
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54264 Automatically file PRs for repetitive tasks 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-54264) Automatically file PRs for repetitive tasks
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-54264
Automatically file PRs for repetitive tasks
Change By:
Baptiste Mathus
h3. Problem statementThere are a few repetitve tasks for the project that we have been handling manually until now that should be automated.They share the common feature that they end up being a PR on the Evergreen source repo itself or another. Running plugins or Examples:* running core upgrades, or plugins upgrades* updating the backend to latest* updating npm packages security bumps, or bumping * running {{npm audit fix}} to fix vulnerabilities * ... h3. Expected behaviorThese tasks should be automated. We should write a common tool that makes it easy to file a PR against a given repo with a set of change that a script or so has created.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54265) Sending Parameters or initialize environment variables
Title: Message Title Lena Herrmann created an issue Jenkins / JENKINS-54265 Sending Parameters or initialize environment variables Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-10-26 08:57 Priority: Minor Reporter: Lena Herrmann Jenkins Version: 2.138.2 GitHub Branch Source Plugin Version 2.4.1 Within our Jenkins-Setup we integrated a github.dsl which is able to detect new projects or branches within a project and creates dynamically new Pipeline-Jobs. Every project contains a Jenkinsfile, which defines the build-process. Within our organization, we would like to set-up an integrate and push mechanism, in order to keep a master-branch clean from any not working source-code. To lock the jobs within a project, we would like to use the option "lock resource: any-name". If you add a specific name, the locking works just fine. But we would like to set the name of the resource to lock dynamically via either parameters or environments variables. At the time, the options-block gets evaluated the environment does not seem to be available, hence any env-var is null and cannot be used. Is it possible to expand the configuration within the github-dsl to send parameters to the generated job, so that these parameters contain values like the project-name or similar, that can be used inside the option-block? Or is there a way to initialize the environment variables, so that these can be used within the option-block?
[JIRA] (JENKINS-54264) Automatically file PRs for repetitive tasks
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-54264
Automatically file PRs for repetitive tasks
Change By:
Baptiste Mathus
h3. Problem statementThere are a few repetitve repetitive tasks for the project that we have been handling manually until now that should be automated.They share the common feature that they end up being a PR on the Evergreen source repo itself or another.Examples:* running core or plugins upgrades ([PR-330|https://github.com/jenkins-infra/evergreen/pull/330], [PR-327|https://github.com/jenkins-infra/evergreen/pull/327], [PR-326|https://github.com/jenkins-infra/evergreen/pull/326], [PR-318|https://github.com/jenkins-infra/evergreen/pull/318], ...) * updating the backend to latest (example: https://github.com/jenkins-infra/jenkins-infra/pull/1174) * updating all npm packages ([PR-323|https://github.com/jenkins-infra/evergreen/pull/323]) * running {{npm audit fix}} to fix vulnerabilities ([PR-329|https://github.com/jenkins-infra/evergreen/pull/329]) * ...h3. Expected behaviorThese tasks should be automated. We should write a common tool that makes it easy to file a PR against a given repo with a set of change that a script or so has created.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-54100) Need plugin that has incompatible format from one version to the next to test evergreen snapshot restore
Title: Message Title Baptiste Mathus stopped work on JENKINS-54100 Change By: Baptiste Mathus Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-54266
fails to start agent because of missing label
Issue Type:
Task
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2018-10-26 09:07
Environment:
AWS ec2-plugin: 1.41 Jenkins: 2.138.2
Priority:
Blocker
Reporter:
Dominik Bartholdi
I upgraded to version 1.41 and now launching of a new agent fails with this:
SlaveTemplate{ami='ami-06870ca4fe1151af2', labels='agent'}. Attempting to provision slave needed by excess workload of 1 units
Oct 26, 2018 8:58:29 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-06870ca4fe1151af2', labels='agent'}. Considering launching
Oct 26, 2018 8:58:29 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-06870ca4fe1151af2', labels='agent'}. Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate
Oct 26, 2018 8:58:29 AM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfoSlaveTemplate{ami='ami-06870ca4fe1151af2', labels='agent'}. Looking for existing instances with describe-instance: {Filters: [{Name: image-id,Values: [ami-06870ca4fe1151af2]}, {Name: instance-type,Values: [t2.medium]}, {Name: key-name,Values: [YooJks]}, {Name: instance.group-name,Values: [yoo-test18493-YootureJksAgentSecurityGroup-VL4P3JGXGAG3]}, {Name: tag:jenkins_server_url,Values: [null]}, {Name: tag:jenkins_slave_type,Values: [demand_EC2 Agent]}],InstanceIds: [],}
Oct 26, 2018 8:58:29 AM WARNING hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-06870ca4fe1151af2', labels='agent'}. Exception during provisioning
com
[JIRA] (JENKINS-47229) Support other pod attribute such as dnsPolicy
Title: Message Title Rohtash Kumar commented on JENKINS-47229 Re: Support other pod attribute such as dnsPolicy Hi Chen , How you manage it , can you share workaround for me Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54266 Re: fails to start agent because of missing label Did you have define the server url in the global config ? it is used today to create unique tag in AWS. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47229) Support other pod attribute such as dnsPolicy
Title: Message Title Carlos Sanchez commented on JENKINS-47229 Re: Support other pod attribute such as dnsPolicy use the yaml syntax, see plugin docs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54257) Infinite loop when an exception occurs on slave
Title: Message Title Nikolas Falco updated JENKINS-54257 Jenkins / JENKINS-54257 Infinite loop when an exception occurs on slave Change By: Nikolas Falco Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54257) Infinite loop when an exception occurs on slave
Title: Message Title Nikolas Falco updated JENKINS-54257 Jenkins / JENKINS-54257 Infinite loop when an exception occurs on slave Change By: Nikolas Falco Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title Dominik Bartholdi commented on JENKINS-54266 Re: fails to start agent because of missing label FABRIZIO MANFREDI thanks - that really fixed the issue, do you really need the url for anything else then identifying the master? If not, I think you would be a lot better by using the instance identifier as described here: https://wiki.jenkins.io/display/JENKINS/Instance+Identity Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54090) EC2 Plugin instance cap is enforeced by AMI ID, not by per-slave template
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-54090 Re: EC2 Plugin instance cap is enforeced by AMI ID, not by per-slave template if I have understood you need a cluster function, where to group by jenkins instances , is correct ? We support users who rely on this indeed. The total cap was design to count the max number of nodes that was allow for the jenkins and not for the entire account, for this reason it was a bug. Digging further, there are other cloud implementations like for example the Kubernetes plugin that have the same bug although kubernetes provides some other way to achieve the isolation. Some like the docker plugin use the cap per master. Since this has always worked that way for EC2, maybe some user rely on this now and the fix provided does not provide a way to control this which is my concern. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54257) Infinite loop when an exception occurs on slave
Title: Message Title Nikolas Falco updated JENKINS-54257 Jenkins / JENKINS-54257 Infinite loop when an exception occurs on slave Change By: Nikolas Falco Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54228) xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1
Title: Message Title Nikolas Falco updated JENKINS-54228 Jenkins / JENKINS-54228 xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1 Change By: Nikolas Falco Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54267) TlsConfigurationAdministrativeMonitor is missing its name
Title: Message Title Francisco Fernández started work on JENKINS-54267 Change By: Francisco Fernández 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-54267) TlsConfigurationAdministrativeMonitor is missing its name
Title: Message Title Francisco Fernández created an issue Jenkins / JENKINS-54267 TlsConfigurationAdministrativeMonitor is missing its name Issue Type: Task Assignee: Francisco Fernández Attachments: active-directory-monitor.png Components: active-directory-plugin Created: 2018-10-26 10:26 Priority: Minor Reporter: Francisco Fernández After installing the plugin I can see one administrative monitor is running: hudson.plugins.active_directory.ActiveDirectorySecurityRealm$TlsConfigurationAdministrativeMonitor. It's missing its display name (see attachment), so in order to ease the understanding of the monitor, it could be good idea to add the displayMethod to the monitor. Add Comment
[JIRA] (JENKINS-54267) TlsConfigurationAdministrativeMonitor is missing its name
Title: Message Title Francisco Fernández updated JENKINS-54267 Jenkins / JENKINS-54267 TlsConfigurationAdministrativeMonitor is missing its name Change By: Francisco Fernández 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-32681) Option to disable script security approval
Title: Message Title Adrian Vlad commented on JENKINS-32681 Re: Option to disable script security approval I just opened a new bug (https://issues.jenkins-ci.org/browse/JENKINS-54262). Thank you for the suggestion. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54268) Incrementalify Blue Ocean
Title: Message Title Baptiste Mathus started work on JENKINS-54268 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-54268) Incrementalify Blue Ocean
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54268 Incrementalify Blue Ocean Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2018-10-26 10:36 Labels: evergreen-triggered Priority: Minor Reporter: Baptiste Mathus It would be useful to incrementalify Blue Ocean, so we can update it more often if needed. Add Comment
[JIRA] (JENKINS-54268) Incrementalify Blue Ocean
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54268 Incrementalify Blue Ocean Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54268) Incrementalify Blue Ocean
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54268 Incrementalify Blue Ocean 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-47229) Support other pod attribute such as dnsPolicy
Title: Message Title
Rohtash Kumar commented on JENKINS-47229
Re: Support other pod attribute such as dnsPolicy
I tried in pod template but giving error, I am using below syntax how i can create YML for the same if possible and thanks for your reply pipeline { agent { kubernetes { cloud 'kubernetes2' label "k8saov-${UUID.randomUUID().toString()}" inheritFrom 'base2' nodeSelector 'executor=aov-jenkins' containerTemplate { name 'baseci' image 'test-images0' ttyEnabled true command 'run-with-dind.sh cat' privileged true } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54144) Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads
Title: Message Title Olivier Lamy resolved as Fixed Jenkins / JENKINS-54144 Job fails as JiraSCMListsener/JiraSite potentially creating Executor with 0 threads Change By: Olivier Lamy 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-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Olivier Lamy resolved as Fixed Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Change By: Olivier Lamy 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-54093) Jenkins Jira Plugin sets connection timeout to default = 10 after Jenkins restart
Title: Message Title Olivier Lamy resolved as Fixed Jenkins / JENKINS-54093 Jenkins Jira Plugin sets connection timeout to default = 10 after Jenkins restart Change By: Olivier Lamy 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-41660) JIRA Issue linking in build Changelog doesn't work
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-41660 JIRA Issue linking in build Changelog doesn't work Change By: Olivier Lamy Labels: jira-plugin-2.0.2 jira-plugin-2.3 jira-plugin-3.0.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-54269) MissingVerificationStrategyAdministrativeMonitor is missing its name
Title: Message Title Francisco Fernández started work on JENKINS-54269 Change By: Francisco Fernández 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-54269) MissingVerificationStrategyAdministrativeMonitor is missing its name
Title: Message Title Francisco Fernández created an issue Jenkins / JENKINS-54269 MissingVerificationStrategyAdministrativeMonitor is missing its name Issue Type: Task Assignee: Francisco Fernández Attachments: ssh-slave-monitor.png Components: ssh-slaves-plugin Created: 2018-10-26 10:53 Priority: Minor Reporter: Francisco Fernández After installing the plugin I can see one administrative monitor is running: hudson.plugins.sshslaves.verifiers.MissingVerificationStrategyAdministrativeMonitor. It's missing its display name (see attachment), so in order to ease the understanding of the monitor, it could be good idea to add the displayMethod to the monitor. Add Comment
[JIRA] (JENKINS-48865) JNLP Agents/Slaves Disconnecting Unpredictably
Title: Message Title Piotr Plenik commented on JENKINS-48865 Re: JNLP Agents/Slaves Disconnecting Unpredictably Oleg Nenashev indeed JENKINS-48865 and JENKINS-48865 is precisely the same issue. I guess that you mean JENKINS-44132. Isn't? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54269) MissingVerificationStrategyAdministrativeMonitor is missing its name
Title: Message Title Francisco Fernández updated JENKINS-54269 Jenkins / JENKINS-54269 MissingVerificationStrategyAdministrativeMonitor is missing its name Change By: Francisco Fernández 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-54268) Incrementalify Blue Ocean
Title: Message Title Baptiste Mathus commented on JENKINS-54268 Re: Incrementalify Blue Ocean https://github.com/jenkinsci/blueocean-plugin/pull/1818 https://github.com/jenkinsci/blueocean-plugin/pull/1838 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54268) Incrementalify Blue Ocean
Title: Message Title Baptiste Mathus updated JENKINS-54268 Jenkins / JENKINS-54268 Incrementalify Blue Ocean 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-54270) Clicking graph on JUnit History defaults to port 8080
Title: Message Title Topi Kettunen created an issue Jenkins / JENKINS-54270 Clicking graph on JUnit History defaults to port 8080 Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2018-10-26 11:10 Environment: Jenkins 2.138.2 (weekly docker image) Installed plugins: Suggested plugins Browser: Firefox Labels: plugin plugins jenkins Priority: Minor Reporter: Topi Kettunen I'm running Jenkins locally in Docker container at port 8090. While I'm at http://localhost:8090/job/TestHardwareX/12/testReport/history/ and I click the graph made by JUnit plugin it should go to http://localhost:8090/job/TestHardwareX/12/testReport/junit/ but the port defaults to 8080 and directs the page to http://localhost:8080/job/TestHardwareX/12/testReport/junit resulting in an empty page on my case. Add Comment
[JIRA] (JENKINS-54263) Fix/make sure the AWS flavor still works
Title: Message Title Baptiste Mathus started work on JENKINS-54263 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-54057) [JEP-302] Implement evergreen Data auto-rollback using the snapshotting system
Title: Message Title Baptiste Mathus stopped work on JENKINS-54057 Change By: Baptiste Mathus Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54247) Add to TROUBLESHOOTING how to backup/restore current keys
Title: Message Title Andrei Stepanov commented on JENKINS-54247 Re: Add to TROUBLESHOOTING how to backup/restore current keys Hi, thank you for answer. I our Jenkins: checkbox "Encryption Configuration" is not set. Does this mean that Jenkins master doesn't have personal private key to talk to idP? Could you please just in steps say what I need to back up, and how to restore? We do not use "Encryption Configuration" checkbox is SAML plugin configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title James Howe commented on JENKINS-50223 Re: Pipeline Jenkins master ran out of Java Metaspace Just to note: I performed a System.gc() to force a full garbage collection If you have -XX:+ExplicitGCInvokesConcurrent then it doesn't do a "full" collection. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54271) ZPoolExpandNotice is missing its name
Title: Message Title Francisco Fernández started work on JENKINS-54271 Change By: Francisco Fernández 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-54271) ZPoolExpandNotice is missing its name
Title: Message Title Francisco Fernández created an issue Jenkins / JENKINS-54271 ZPoolExpandNotice is missing its name Issue Type: Task Assignee: Francisco Fernández Attachments: ec2-monitor.png Components: ec2-plugin Created: 2018-10-26 11:42 Priority: Minor Reporter: Francisco Fernández After installing the plugin I can see a new administrative monitor is running: zpool.ebs. It's missing its display name (see attachment), so in order to ease the understanding of the monitor, it could be good idea to add the displayMethod to the monitor. Add Comment
[JIRA] (JENKINS-54271) ZPoolExpandNotice is missing its name
Title: Message Title Francisco Fernández updated JENKINS-54271 Jenkins / JENKINS-54271 ZPoolExpandNotice is missing its name Change By: Francisco Fernández 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-54263) Fix/make sure the AWS flavor still works
Title: Message Title Baptiste Mathus commented on JENKINS-54263 Re: Fix/make sure the AWS flavor still works Confirmed, provisioning the master through the existing CF file works, but EC2 agent provisioning fails. Digging. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53332) Allow picking a lockable resource from a node label
Title: Message Title Aaron Marasco assigned an issue to Unassigned Jenkins / JENKINS-53332 Allow picking a lockable resource from a node label Change By: Aaron Marasco Assignee: Aaron Marasco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53332) Allow picking a lockable resource from a node label
Title: Message Title Aaron Marasco assigned an issue to Aaron Marasco Jenkins / JENKINS-53332 Allow picking a lockable resource from a node label Change By: Aaron Marasco Assignee: Aaron Marasco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53332) Allow picking a lockable resource from a node label
Title: Message Title Aaron Marasco commented on JENKINS-53332 Re: Allow picking a lockable resource from a node label I think this is a dupe/specialized case of JENKINS-44141. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54271) ZPoolExpandNotice is missing its name
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-54271
ZPoolExpandNotice is missing its name
Change By:
Baptiste Mathus
After installing the plugin I can see a new administrative monitor is running: {{zpool.ebs}}. It's missing its display name (see attachment) , so in order to ease the understanding of the monitor, it could be good idea to add the {{displayMethod}} to the monitor. Screenshot of the problem:!ec2-monitor.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-48430) Provided config file is sometimes not complete
Title: Message Title Aviad M commented on JENKINS-48430 Re: Provided config file is sometimes not complete Dominik Bartholdi It's a master and 5-6 slaves. Linux (Ubuntu 16.04 servers) and windows (2012 servers) slaves, however the problem occurs on the linux slaves (haven't tried personally the windows ones). I save a plain config file in a .env format. It takes some build attempts in order to the file successfully being present in the slave machine. I have, like the author of this thread, an IF clause alerting me if the file not present when the build starts. More details here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48430) Provided config file is sometimes not complete
Title: Message Title Aviad M edited a comment on JENKINS-48430 Re: Provided config file is sometimes not complete [~imod]It's a master and 5-6 slaves.Linux (Ubuntu 16.04 servers) and windows (2012 servers) slaves, however the problem occurs on the linux slaves (haven't tried personally the windows ones).I save a plain config file in a [.env |https://www. google npmjs . co.il com / search?q=npm+ package/ dotenv &oq=npm+dotenv&aqs=chrome..69i57j0l5.1933j0j7&sourceid=chrome&ie=UTF-8 ] format. It takes some build attempts in order to the file successfully being present in the slave machine.I have, like the author of this thread, an IF clause alerting me if the file not present when the build starts.More details [ here |https://issues . jenkins-ci.org/browse/JENKINS-51750]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48430) Provided config file is sometimes not complete
Title: Message Title Aviad M edited a comment on JENKINS-48430 Re: Provided config file is sometimes not complete [~imod]It's a master and 5-6 slaves.Linux (Ubuntu 16.04 servers) and windows (2012 servers) slaves, however the problem occurs on the linux slaves (haven't tried personally the windows ones).I save a plain config file in a [.env|https://www.npmjs.com/package/dotenv] format. It takes some build attempts in order to the file successfully being present in the slave machine.I have, like the author of this thread, an IF clause alerting me if the file not present when the build starts.More details [ here |https://issues . jenkins-ci.org/browse/JENKINS-51750]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Viacheslav Subotskyi updated an issue Jenkins / JENKINS-54133 No ANSI coloring on slave agents in pipeline Change By: Viacheslav Subotskyi Attachment: image.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-29603) notifyCommit branch parameter can't contain slashes
Title: Message Title Jakub Bochenski commented on JENKINS-29603 Re: notifyCommit branch parameter can't contain slashes I confirm using the origin/ workaround helps. No other forms seem to work though (e.g refs/heads/... or refs/remotes/...) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54266 fails to start agent because of missing label Change By: Baptiste Mathus Labels: evergreen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title Paul Allen commented on JENKINS-54222 Re: p4-plugin keeps opening connection during the build. Causing long delays Yes I did try you example; I do see additional commands after the sync. Some of these will be related to change reporting and saving the build state, there did seem to be a few more than I was expecting and that may need investigating. However, the overhead was at most a second not the 53 seconds you reported. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick commented on JENKINS-54133 Re: No ANSI coloring on slave agents in pipeline Since I see that I have not commented here recently: I do plan to offer a fix for this, I am just trying to deal with higher-priority issues first (JENKINS-54073, then JENKINS-54078, then JENKINS-54081, then this). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title Baptiste Mathus commented on JENKINS-54266 Re: fails to start agent because of missing label I'm seeing this too on Evergreen, about to propose a fix. If anyone is also working on this, please let me know Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54266 fails to start agent because of missing label Change By: Baptiste Mathus Assignee: FABRIZIO MANFREDI 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-54266) fails to start agent because of missing label
Title: Message Title Baptiste Mathus commented on JENKINS-54266 Re: fails to start agent because of missing label FABRIZIO MANFREDI I've assigned this issue to myself to clarify. But feel free to take it back and tell me if you are working on this. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Alex Earl assigned an issue to David van Laatum Jenkins / JENKINS-54261 Submit ( go ) on Email Template Testing produces blank screen Change By: Alex Earl Assignee: David van Laatum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Alex Earl commented on JENKINS-54261 Re: Submit ( go ) on Email Template Testing produces blank screen This may be related to the onSubmit being used on the form in the template testing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-54261 Submit ( go ) on Email Template Testing produces blank screen Change By: Alex Earl Component/s: email-ext-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54261) Submit ( go ) on Email Template Testing produces blank screen
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-54261 Submit ( go ) on Email Template Testing produces blank screen Change By: Alex Earl Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title Baptiste Mathus updated JENKINS-54266 Jenkins / JENKINS-54266 fails to start agent because of missing label 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-54266) fails to start agent because of missing label
Title: Message Title Baptiste Mathus commented on JENKINS-54266 Re: fails to start agent because of missing label Proposed fix as https://github.com/jenkinsci/ec2-plugin/pull/314 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39742) Active Choice Plugin should honor ParameterDefinition serializability (was: Active Choice Plugin in Pipelines throw NotSerializableException)
Title: Message Title chris starling commented on JENKINS-39742 Re: Active Choice Plugin should honor ParameterDefinition serializability (was: Active Choice Plugin in Pipelines throw NotSerializableException) I'm wondering if pipeline support has been added since this ticket, or is there a plan to add support for it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54247) Add to TROUBLESHOOTING how to backup/restore current keys
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54247 Re: Add to TROUBLESHOOTING how to backup/restore current keys >Does this mean that Jenkins master doesn't have personal private key to talk to idP? The plugin creates a key pair automatically and stores them in "JENKINS_HOME/saml-jenkins-keystore.jks", then store the data related into "JENKINS_HOME/saml-jenkins-keystore.xml", you can grab the public key from "JENKINS_HOME/saml-sp-metadata.xml". >Could you please just in steps say what I need to back up, and how to restore? You need the following files to restore the SAML configuration JENKINS_HOME/config.xml JENKINS_HOME/saml-jenkins-keystore.jks JENKINS_HOME/saml-jenkins-keystore.xml JENKINS_HOME/saml-ipd-metadata.xml JENKINS_HOME/saml-sp-metadata.xml Also you need the same secret.key, if not the configuration is impossible to unencrypt but in any case, you use to make a backup of your full JENKINS_HOME to make your Jenkins instance work properly (not only SAML Plugin), I recommend you to take a look at this CloudBees KB https://support.cloudbees.com/hc/en-us/articles/216241937-Migration-Guide-CloudBees-Jenkins-Platform-and-CloudBees-Jenkins-Team- Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54272) Bibucket Plugin is not triggering the job because of minimal url mismatch (".*/scm/.*")
Title: Message Title
Roxana Muresan created an issue
Jenkins / JENKINS-54272
Bibucket Plugin is not triggering the job because of minimal url mismatch (".*/scm/.*")
Issue Type:
Bug
Assignee:
Roxana Muresan
Components:
bitbucket-plugin
Created:
2018-10-26 14:08
Environment:
Jenkins 2.138.2 Bitbucket Plugin 1.1.8. Bitbucket Server 5.13.1.
Labels:
bitbucket-server bitbucket-plugin
Priority:
Critical
Reporter:
Roxana Muresan
Bitbucket Plugin is not triggering matching Jobs. I have added a FINE log to investigate where it hangs and I followed the source code in Github in paralel to understand the source of the problem. Looks like the match method in BitbucketJobProbe returns false when it checks the url from my jenkins job with the url from the payload. Logs: Considering candidate job trigger-build-branch Oct 26, 2018 3:15:14 PM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbe Considering to poke trigger-build-branch Oct 26, 2018 3:15:14 PM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbe Trying to match https://[host]/scm/[project]/[repository].git<-->https://[host]/[project]/[repository] Oct 26, 2018 3:15:14 PM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbe trigger-build-branch SCM doesnt match remote repo {1} There is a check for "/scm" before actually comparing the url but it removes the "/scm" only if it appears at the start. In my case "/scm" is somewhere inside the url. [https://[host]/scm/[project]/[repository].git] https://[host]/[project]/[repository]
[JIRA] (JENKINS-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title Erez Arbell commented on JENKINS-54222 Re: p4-plugin keeps opening connection during the build. Causing long delays So you do not see that the p4 connections keep opening and closing without stop? I tried to do "p4 login" manually and I see that it always take little more than a second. So maybe my Perforce server is slower than the one you have, and this is why the effect on me is bigger? Can you suggest how can I investigate the issue, or how to tell the p4 plugin to stop to connect to the p4 server once it finished its task? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54266) fails to start agent because of missing label
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54266 Re: fails to start agent because of missing label Thanks, it is merged, it will be part of the 1.42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54273) RAW HTML is shown in maven deployment links since 2.138.2
Title: Message Title Hans Stekelenburg created an issue Jenkins / JENKINS-54273 RAW HTML is shown in maven deployment links since 2.138.2 Issue Type: Bug Assignee: Larry Shatzer, Jr. Components: maven-deployment-linker-plugin Created: 2018-10-26 14:52 Environment: Jenkins 2.138.2 Labels: plugin Priority: Minor Reporter: Hans Stekelenburg After the jenkins 2.138.2 upgrade our maven deployment links are shown as raw HTML. Probably something has to be done in the jelly scripts of this plugin. It isn't maintained since a few years. Add Comment
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Michel Zanini commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults I am having this issue as well, or similar. After upgrading cps plugin I get this: Error storing the arguments for step: checkout org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class jenkins.plugins.git.AbstractGitSCMSource$SpecificRevisionBuildChooser at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:265) at org.jenkinsci.plugins.structs.describable.DescribableModel.(DescribableModel.java:144) at org.jenkinsci.plugins.structs.describable.DescribableModel.of(DescribableModel.java:114) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:294) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:311) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeListAndRecordMutation(ArgumentsActionImpl.java:242) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:313) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:311) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.(ArgumentsActionImpl.java:74) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:245) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:76) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor284.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lan
[JIRA] (JENKINS-54247) Add to TROUBLESHOOTING how to backup/restore current keys
Title: Message Title Andrei Stepanov commented on JENKINS-54247 Re: Add to TROUBLESHOOTING how to backup/restore current keys Okay, thank you. I think this ticket can be closed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53927) Jenkins Build opens up multiple Chrome instances
Title: Message Title ajjan basma commented on JENKINS-53927 Re: Jenkins Build opens up multiple Chrome instances can you attach, project config or the command line to start the msbuild!! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Ruslan Zenin commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Thank you! That worked for me! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54084) Create audit catalog repository
Title: Message Title Matt Sicker assigned an issue to Matt Sicker Jenkins / JENKINS-54084 Create audit catalog repository Change By: Matt Sicker Assignee: Hashini Galappaththi Matt Sicker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54084) Create audit catalog repository
Title: Message Title Matt Sicker updated JENKINS-54084 Jenkins / JENKINS-54084 Create audit catalog repository Change By: Matt Sicker Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jvz/audit-log-plugin/pull/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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Ruslan Zenin edited a comment on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) [~kodstark] Thank you! That worked for me! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54210) Jenkins integration with load runner
Title: Message Title mohan jayaram closed an issue as Fixed Jenkins / JENKINS-54210 Jenkins integration with load runner Change By: mohan jayaram Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
