[JIRA] (JENKINS-42862) Unable to view Performance Center Test Results - HP Application Automation Tools
Title: Message Title Yafim Kazak assigned an issue to Oren Pelzman Jenkins / JENKINS-42862 Unable to view Performance Center Test Results - HP Application Automation Tools Change By: Yafim Kazak Assignee: Ofir Shaked Oren Pelzman Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32348) Jenkins not starting on slave
Title: Message Title Pankaj Malhotra closed an issue as Fixed Jenkins / JENKINS-32348 Jenkins not starting on slave Change By: Pankaj Malhotra Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43083) Investigate how to improve unit and integration tests and avoid relying on E2E (ATH)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-43083 Investigate how to improve unit and integration tests and avoid relying on E2E (ATH) Issue Type: Task Assignee: Cliff Meyers Components: blueocean-plugin Created: 2017/Mar/24 6:26 AM Labels: technical-debt Priority: Major Reporter: Michael Neale Currently we have some unit tests for UI, a lot of unit and integration tests for API, but rely mostly on ATH for feature and integration testing. This is perhaps not optimal, there must be ways where we can unit and even integration tests components without end to end testing with full browsers. Eg, could we aim for a pyramid of tests like: https://2.bp.blogspot.com/-YTzv_O4TnkA/VTgexlumP1I/AJ8/57-rnwyvP6g/s1600/image02.png from: https://testing.googleblog.com/2015/04/just-say-no-to-more-end-to-end-tests.html Investigate what is stopping us from making testable components, plugins etc. Are there better tools, techniques, practices (without resorting to e2e as often as we do). Add Comme
[JIRA] (JENKINS-41737) Dashboard screen when there are no pipelines
Title: Message Title James Dumay commented on JENKINS-41737 Re: Dashboard screen when there are no pipelines Cliff Meyers so Brody Maclean and I were talking about including a snap of this ticket in the video. How far off is it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43082) Investigate TypeScript
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-43082 Investigate TypeScript Issue Type: Task Assignee: Keith Zantow Components: blueocean-plugin Created: 2017/Mar/24 6:13 AM Labels: technical-debt Priority: Minor Reporter: Michael Neale Keith has done some PoC with TypeScript to improve extensibility - enforce what is allowed in extensionpoints, export interfaces that plugins can use (and all the other benefits of types). This should be looked at more seriously. Add Comment
[JIRA] (JENKINS-43081) Quality-gates plugin do not work with SonarQube 6.3
Title: Message Title
Yasuhiro Takahashi updated an issue
Jenkins / JENKINS-43081
Quality-gates plugin do not work with SonarQube 6.3
Change By:
Yasuhiro Takahashi
Quality-gates plugin does not work with SonarQube 6.3.Since SonarQube 6.3, api has been removed/changed.[https://docs.sonarqube.org/display/DEV/API+Changes]*Error message in Jenkins build log:* bq. quality.gates.jenkins.plugin.QGException: Expected status 200, got: 404. Response: \{"errors":[\{"msg":"Unknown url : /api/events"}]} bq. at quality.gates.sonar.api.SonarHttpRequester.executeGetRequest(SonarHttpRequester.java:59) bq. at quality.gates.sonar.api.SonarHttpRequester.getAPIInfo(SonarHttpRequester.java:47) bq. at quality.gates.sonar.api.QualityGatesProvider.getRequesterResult(QualityGatesProvider.java:34) bq. at quality.gates.sonar.api.QualityGatesProvider.getAPIResultsForQualityGates(QualityGatesProvider.java:29) bq. at quality.gates.jenkins.plugin.BuildDecision.getStatus(BuildDecision.java:20) bq. at quality.gates.jenkins.plugin.QGPublisher.perform(QGPublisher.java:73) bq. at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) bq. at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) bq. at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) bq. at hudson.model.Build$BuildExecution.post2(Build.java:186) bq. at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) bq. at hudson.model.Run.execute(Run.java:1758) bq. at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) bq. at hudson.model.ResourceController.execute(ResourceController.java:97) bq. at hudson.model.Executor.run(Executor.java:405) bq. Build step 'Quality Gates' marked build as failure bq. Finished: FAILURE
Add Comment
[JIRA] (JENKINS-43081) Quality-gates plugin do not work with SonarQube 6.3
Title: Message Title
Yasuhiro Takahashi updated an issue
Jenkins / JENKINS-43081
Quality-gates plugin do not work with SonarQube 6.3
Change By:
Yasuhiro Takahashi
Quality-gates plugin does not work with SonarQube 6.3.Since SonarQube 6.3, api has been removed/changed.[https://docs.sonarqube.org/display/DEV/API+Changes] * Error message in Jenkins build log: * bq. quality.gates.jenkins.plugin.QGException: Expected status 200, got: 404. Response: \{"errors":[\{"msg":"Unknown url : /api/events"}]}bq. at quality.gates.sonar.api.SonarHttpRequester.executeGetRequest(SonarHttpRequester.java:59)bq. at quality.gates.sonar.api.SonarHttpRequester.getAPIInfo(SonarHttpRequester.java:47)bq. at quality.gates.sonar.api.QualityGatesProvider.getRequesterResult(QualityGatesProvider.java:34)bq. at quality.gates.sonar.api.QualityGatesProvider.getAPIResultsForQualityGates(QualityGatesProvider.java:29)bq. at quality.gates.jenkins.plugin.BuildDecision.getStatus(BuildDecision.java:20)bq. at quality.gates.jenkins.plugin.QGPublisher.perform(QGPublisher.java:73)bq. at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)bq. at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)bq. at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)bq. at hudson.model.Build$BuildExecution.post2(Build.java:186)bq. at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)bq. at hudson.model.Run.execute(Run.java:1758)bq. at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)bq. at hudson.model.ResourceController.execute(ResourceController.java:97)bq. at hudson.model.Executor.run(Executor.java:405)bq. Build step 'Quality Gates' marked build as failurebq. Finished: FAILURE
Add Comment
[JIRA] (JENKINS-43081) Quality-gates plugin do not work with SonarQube 6.3
Title: Message Title
Yasuhiro Takahashi updated an issue
Jenkins / JENKINS-43081
Quality-gates plugin do not work with SonarQube 6.3
Change By:
Yasuhiro Takahashi
Quality-gates plugin does not work with SonarQube 6.3.Since SonarQube 6.3, api has been removed/changed.[https://docs.sonarqube.org/display/DEV/API+Changes]Error message in Jenkins build log: bq. quality.gates.jenkins.plugin.QGException: Expected status 200, got: 404. Response: \{"errors":[\{"msg":"Unknown url : /api/events"}]} bq. at quality.gates.sonar.api.SonarHttpRequester.executeGetRequest(SonarHttpRequester.java:59) bq. at quality.gates.sonar.api.SonarHttpRequester.getAPIInfo(SonarHttpRequester.java:47) bq. at quality.gates.sonar.api.QualityGatesProvider.getRequesterResult(QualityGatesProvider.java:34) bq. at quality.gates.sonar.api.QualityGatesProvider.getAPIResultsForQualityGates(QualityGatesProvider.java:29) bq. at quality.gates.jenkins.plugin.BuildDecision.getStatus(BuildDecision.java:20) bq. at quality.gates.jenkins.plugin.QGPublisher.perform(QGPublisher.java:73) bq. at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) bq. at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) bq. at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) bq. at hudson.model.Build$BuildExecution.post2(Build.java:186) bq. at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) bq. at hudson.model.Run.execute(Run.java:1758) bq. at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) bq. at hudson.model.ResourceController.execute(ResourceController.java:97) bq. at hudson.model.Executor.run(Executor.java:405) bq. Build step 'Quality Gates' marked build as failure bq. Finished: FAILURE
Add Comment
[JIRA] (JENKINS-43081) Quality-gates plugin do not work with SonarQube 6.3
Title: Message Title Yasuhiro Takahashi updated an issue Jenkins / JENKINS-43081 Quality-gates plugin do not work with SonarQube 6.3 Change By: Yasuhiro Takahashi Summary: Do Quality-gates plugin do not work with SonarQube 6.3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43081) Do not work SonarQube 6.3
Title: Message Title
Yasuhiro Takahashi created an issue
Jenkins / JENKINS-43081
Do not work SonarQube 6.3
Issue Type:
Bug
Assignee:
Ivana Sh
Components:
quality-gates-plugin
Created:
2017/Mar/24 5:59 AM
Labels:
plugins
Priority:
Major
Reporter:
Yasuhiro Takahashi
Quality-gates plugin does not work with SonarQube 6.3. Since SonarQube 6.3, api has been removed/changed. https://docs.sonarqube.org/display/DEV/API+Changes Error message in Jenkins build log: quality.gates.jenkins.plugin.QGException: Expected status 200, got: 404. Response: {"errors":[\{"msg":"Unknown url : /api/events"}]} at quality.gates.sonar.api.SonarHttpRequester.executeGetRequest(SonarHttpRequester.java:59) at quality.gates.sonar.api.SonarHttpRequester.getAPIInfo(SonarHttpRequester.java:47) at quality.gates.sonar.api.QualityGatesProvider.getRequesterResult(QualityGatesProvider.java:34) at quality.gates.sonar.api.QualityGatesProvider.getAPIResultsForQualityGates(QualityGatesProvider.java:29) at quality.gates.jenkins.plugin.BuildDecision.getStatus(BuildDecision.java:20) at quality.gates.jenkins.plugin.QGPublisher.perform(QGPublisher.java:73) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1758) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405) Build step 'Quality Gates' marked build as failure Finished
[JIRA] (JENKINS-43080) java.lang.NullPointerException when Github Branch Source Plugin job executes
Title: Message Title
Marcus Greville updated an issue
Jenkins / JENKINS-43080
java.lang.NullPointerException when Github Branch Source Plugin job executes
Change By:
Marcus Greville
I am having a hard time getting a new setup of the Github Branch Source Plugin executing a build of a candidate branch. This is the output shown below.The repository has been scanned successfully and my credentials are in working order.This looks like a bug to me.The jenkins.log contains only -{code:java}Mar 24, 2017 4:09:45 PM org.jenkinsci.plugins.workflow.job.WorkflowRun finishINFO: AndroidSDKs/accounts_android_sdk/develop #13 completed: FAILUREMar 24, 2017 4:09:46 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregisterWARNING: Owner[AndroidSDKs/accounts_android_sdk/develop/13:AndroidSDKs/accounts_android_sdk/develop #13] was not in the list to begin with: []{code}h1. !https://jenkins-2.ma.extnp.national.com.au/static/dc63d76e/images/48x48/red.png! Console Output {code:java} Started by user [ Marcus Greville |https://jenkins-2.ma.extnp.national.com.au/user/p712384] 15:35:28 Connecting to [ https://github.internal/api/v3/ |https://github.aus.thenational.com/api/v3/] using XXX/** (MAGithubScan)GitHub has been notified of this commit's build result java.lang.NullPointerException at org.kohsuke.github.GitHub.getApiURL(GitHub.java:277) at org.kohsuke.github.Requester.asStream(Requester.java:312) at org.kohsuke.github.GHContent.read(GHContent.java:119) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFile.content(GitHubSCMFile.java:181) at jenkins.scm.api.SCMFile.contentAsString(SCMFile.java:338) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:91) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:232) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405) Finished: FAILURE {code} The Scan works correctlyh1. !https://jenkins-2.ma.extnp.national.com.au/static/6fba09b4/images/48x48/blue_anime.gif! Scan Repository Log {code:java} Started by user [ Marcus Greville |https://jenkins-2.ma.extnp.national.com.au/user/p712384] [Fri Mar 24 13:51:22 AEDT 2017] Starting branch indexing... 13:51:23 Connecting to [ https://github.internal/api/v3/ |https://github.aus.thenational.com/api/v3/] using XXX/** (MAGithubScan) Looking up [ MET/accounts_android_sdk |https://github.aus.thenational.com/MobileEmergingTechnology/accounts_android_sdk] Getting remote pull requests... 0 pull requests were processed Getting remote branches... Checking branch [ develop |https://github.aus.thenational.com/MobileEmergingTechnology/accounts_android_sdk/tree/develop] 'Jenkinsfile' found Met criteria Changes detected: develop (55b30a5f68150f6565bcc6ff2b6b0bf0e8a6f418 → 74199dee312697aee68c818d8757cacf3259a8f4) Scheduled build for branch: develop 1 branches were processed Done examining MET/accounts_android_sdk [Fri Mar 24 13:51:26 AEDT 2017] Finished branch indexing. Indexing took 3.4 sec Evalua
[JIRA] (JENKINS-43080) java.lang.NullPointerException when Github Branch Source Plugin job executes
Title: Message Title Marcus Greville updated an issue Jenkins / JENKINS-43080 java.lang.NullPointerException when Github Branch Source Plugin job executes Change By: Marcus Greville Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43080) java.lang.NullPointerException when Github Branch Source Plugin job executes
Title: Message Title
Marcus Greville updated an issue
Jenkins / JENKINS-43080
java.lang.NullPointerException when Github Branch Source Plugin job executes
Change By:
Marcus Greville
++ I am having a hard time getting a new setup of the Github Branch Source Plugin executing a build of a candidate branch. This is the output shown below.The repository has been scanned successfully and my credentials are in working order.This looks like a bug to me.The jenkins.log contains only -{code:java}Mar 24, 2017 4:09:45 PM org.jenkinsci.plugins.workflow.job.WorkflowRun finishINFO: AndroidSDKs/accounts_android_sdk/develop #13 completed: FAILUREMar 24, 2017 4:09:46 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregisterWARNING: Owner[AndroidSDKs/accounts_android_sdk/develop/13:AndroidSDKs/accounts_android_sdk/develop #13] was not in the list to begin with: []{code}h1. !https://jenkins-2.ma.extnp.national.com.au/static/dc63d76e/images/48x48/red.png! Console Output Started by user [Marcus Greville|https://jenkins-2.ma.extnp.national.com.au/user/p712384]15:35:28 Connecting to [https://github.internal/api/v3/|https://github.aus.thenational.com/api/v3/] using XXX/** (MAGithubScan)GitHub has been notified of this commit's build resultjava.lang.NullPointerException at org.kohsuke.github.GitHub.getApiURL(GitHub.java:277) at org.kohsuke.github.Requester.asStream(Requester.java:312) at org.kohsuke.github.GHContent.read(GHContent.java:119) at org.jenkinsci.plugins.github_branch_source.GitHubSCMFile.content(GitHubSCMFile.java:181) at jenkins.scm.api.SCMFile.contentAsString(SCMFile.java:338) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:91) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:232) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405)Finished: FAILURE The Scan works correctlyh1. !https://jenkins-2.ma.extnp.national.com.au/static/6fba09b4/images/48x48/blue_anime.gif! Scan Repository LogStarted by user[Marcus Greville|https://jenkins-2.ma.extnp.national.com.au/user/p712384][Fri Mar 24 13:51:22 AEDT 2017] Starting branch indexing... 13:51:23 Connecting to [https://github.internal/api/v3/|https://github.aus.thenational.com/api/v3/] using XXX/** (MAGithubScan) Looking up[MET/accounts_android_sdk|https://github.aus.thenational.com/MobileEmergingTechnology/accounts_android_sdk]Getting remote pull requests... 0 pull requests were processed Getting remote branches... Checking branch[develop|https://github.aus.thenational.com/MobileEmergingTechnology/accounts_android_sdk/tree/develop]'Jenkinsfile' foundMet criteriaChanges detected: develop (55b30a5f68150f6565bcc6ff2b6b0bf0e8a6f418 → 74199dee312697aee68c818d8757cacf3259a8f4)Scheduled build for branch: develop1 branches were processed Done examining MET/accounts_android_sdk[Fri Mar 24 13:51:26 AEDT 2017] Finished branch indexing. Indexing took 3.4 secEvaluating orphaned items in Mobile & Emerging Technologies » accounts_andro
[JIRA] (JENKINS-43080) java.lang.NullPointerException when Github Branch Source Plugin job executes
Title: Message Title Marcus Greville created an issue Jenkins / JENKINS-43080 java.lang.NullPointerException when Github Branch Source Plugin job executes Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Mar/24 5:18 AM Environment: Jenkins v2.32.3->2.51 github-branch-source-plugin v 2.0.3->2.0.4 All other plugins also up-to-date CentOS Linux release 7.3.1611 (Core) Linux jenkins-2.ma 3.10.0-514.2.2.el7.x86_64 #1 SMP Tue Dec 6 23:06:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_111-b15 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation Priority: Minor Reporter: Marcus Greville ++I am having a hard time getting a new setup of the Github Branch Source Plugin executing a build of a candidate branch. This is the output shown below. The repository has been scanned successfully and my credentials are in working order. This looks like a bug to me. The jenkins.log contains only - Mar 24, 2017 4:09:45 PM org.jenkinsci.plugins.workflow.job.WorkflowRun finish INFO: AndroidSDKs/accounts_android_sdk/develop #13 completed: FAILURE Mar 24, 2017 4:09:46 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregister WARNING: Owner[AndroidSDKs/accounts_android_sdk/develop/13:AndroidSDKs/accounts_android_sdk/develop #13] was not in the list to begin with: []
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title
Justin Rainwater commented on JENKINS-37491
Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
I wanted to add here a solution I found that feels like a nice workaround at least for my needs:
In GitHub Org options check to build both merged and unmerged PRs so you have a bunch of PR jobs ending in -merge and -head.
In the auto branch triggering field add PR-\d+-head so you auto build all head jobs but not all merge jobs. This will avoid the build storm that causes so many problems.
From inside the Jenkinsfile add something like this:
// have head job trigger merge job...
if (autoTriggered() && env.BRANCH_NAME.endsWith('head')) {
def headJobName = "${env.BRANCH_NAME}"
def mergeJobName = (headJobName.substring(0, headJobName.length() - 4)).concat('merge') // replace head with merge
build job: mergeJobName, wait: false
return
}
autoTriggered() is the function I added that returns false if cause description contains "Started by...". All this does is check if it's a head job and if so it triggers the corresponding merge job and exits. It feels a little too simple and too good to be true, but at first glance it seems like this gives best of both worlds of auto triggering merge jobs only on changes to head and avoiding the buildStorm.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42173) Blue Ocean SDK design document - extensibility improvements
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42173 Blue Ocean SDK design document - extensibility improvements Change By: Michael Neale We want an SDK experience for developing Blue Ocean plugins , should document/research aims and goals *Goals** Public API* Typed extension points* Improved module resolution* Improved module versioning (e.g. we don't have to keep bundling common libraries into Blue Ocean)* Write "_javascript_ only" plugins without maven* Integration with maven-hpi-plugin * Typescript investigation Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40885) Environment variables are not exposed in pipeline script
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-40885
Re: Environment variables are not exposed in pipeline script
There is also actually a strange behavior - noticed also in P4 1.5.1 - when using `env . ` to access variable before the checkout . If I *use the `env` variable to access environment variable in my pipeline anywhere before the checkout step * , the P4 variables are _null_ * . My simplest scenario:{code}node ('master') {stage('checkout') {env.JOB_BASE_NAMEcheckout([$class: 'PerforceScm', credential: 'p4Local', populate: [$class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4'], pin: '', quiet: true, replace: true], workspace: [$class: 'ManualWorkspaceImpl', charset: 'none', name: 'jenkins-test46982', pinHost: false, spec: [allwrite: false, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, streamName: '', view: '//depot/project2/... //jenkins-test46982/...']]])}stage ('tests') {println "P4_CHANGELIST=${env.P4_CHANGELIST}"println "P4_CLIENT=${env.P4_CLIENT}"println "P4_PORT=${env.P4_PORT}"println "P4_USER=${env.P4_USER}"println "P4_TICKET=${env.P4_TICKET}"}}{code}And get:{code}[Pipeline] echoP4_CHANGELIST=null[Pipeline] echoP4_CLIENT=null[Pipeline] echoP4_PORT=null[Pipeline] echoP4_USER=null[Pipeline] echoP4_TICKET=null[Pipeline] }{code}If instead I use env. after the checkout step:{code}node ('master') {stage('checkout') {checkout([$class: 'PerforceScm', credential: 'p4Local', populate: [$class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4'], pin: '', quiet: true, replace: true], workspace: [$class: 'ManualWorkspaceImpl', charset: 'none', name: 'jenkins-test46982', pinHost: false, spec: [allwrite: false, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, streamName: '', view: '//depot/project2/... //jenkins-test46982/...']]])}stage ('tests') {env.JOB_BASE_NAMEprintln "P4_CHANGELIST=${env.P4_CHANGELIST}"println "P4_CLIENT=${env.P4_CLIENT}"println "P4_PORT=${env.P4_PORT}"println "P4_USER=${env.P4_USER}"println "P4_TICKET=${env.P4_TICKET}"}}{code}It works:{code}[Pipeline] echoP4_CHANGELIST=113[Pipeline] echoP4_CLIENT=jenkins-test46982[Pipeline] echoP4_PORT=localhost:1666[Pipeline] echoP4_USER=allan[Pipeline] echoP4_TICKET=C791B911A018354D527B586F593A395D{code}The workaround is to only use groovy variable.
Add Comment
[JIRA] (JENKINS-40885) Environment variables are not exposed in pipeline script
Title: Message Title
Allan BURDAJEWICZ commented on JENKINS-40885
Re: Environment variables are not exposed in pipeline script
There is also a strange behavior when using `env.` to access variable. If I use the `env` variable to access environment variable in my pipeline anywhere before the checkout step, the P4 variables are null. My simplest scenario:
node ('master') {
stage('checkout') {
env.JOB_BASE_NAME
checkout([$class: 'PerforceScm', credential: 'p4Local', populate: [$class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4'], pin: '', quiet: true, replace: true], workspace: [$class: 'ManualWorkspaceImpl', charset: 'none', name: 'jenkins-test46982', pinHost: false, spec: [allwrite: false, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, streamName: '', view: '//depot/project2/... //jenkins-test46982/...']]])
}
stage ('tests') {
println "P4_CHANGELIST=${env.P4_CHANGELIST}"
println "P4_CLIENT=${env.P4_CLIENT}"
println "P4_PORT=${env.P4_PORT}"
println "P4_USER=${env.P4_USER}"
println "P4_TICKET=${env.P4_TICKET}"
}
}
And get:
[Pipeline] echo
P4_CHANGELIST=null
[Pipeline] echo
P4_CLIENT=null
[Pipeline] echo
P4_PORT=null
[Pipeline] echo
P4_USER=null
[Pipeline] echo
P4_TICKET=null
[Pipeline] }
If instead I use env. after the checkout step:
node ('master') {
stage('checkout') {
checkout([$class: 'PerforceScm', credential: 'p4Local', populate: [$class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4'], pin: '', quiet: true, replace: true], workspace: [$class: 'ManualWorkspaceImpl', charset: 'none', name: 'jenkins-test46982', pinHost: false, spec: [allwrite: false, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, streamName: '', view: '//depot/project2/... //jenkins-test46982/...']]])
}
stage ('tests') {
env.JOB_BASE_NAME
println "P4_CHANGELIST=${env.P4_CHANGELIST}"
println "P4_CLIENT=${env.P4_CLIENT}"
println "P4_PORT=${env.P4_PORT}"
println "P4_USER=${env.P4_USER}"
println "P4_TICKET=${env.P4_TICKET}"
}
}
It works:
[Pipeline] echo
P4_CHANGELIST=113
[Pipeline] echo
P4_CLIENT=jenkins-test46982
[Pipeline] echo
P4_PORT=localhost:1666
[Pipeline] echo
P4_USER=allan
[Pipeline] echo
P4_TICKET=C791B911A018354D527B586F593A395D
[JIRA] (JENKINS-41726) form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response
Title: Message Title Janario Oliveira resolved as Cannot Reproduce Jenkins / JENKINS-41726 form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response Change By: Janario Oliveira Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36486) httpRequest executes from Jenkins Master node
Title: Message Title Janario Oliveira resolved as Fixed Jenkins / JENKINS-36486 httpRequest executes from Jenkins Master node Change By: Janario Oliveira Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36486) httpRequest executes from Jenkins Master node
Title: Message Title Janario Oliveira commented on JENKINS-36486 Re: httpRequest executes from Jenkins Master node It wasn't executing on slave node :S I've changed to support it. Thanks for the report. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36486) httpRequest executes from Jenkins Master node
Title: Message Title Janario Oliveira stopped work on JENKINS-36486 Change By: Janario Oliveira Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36486) httpRequest executes from Jenkins Master node
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36486 Re: httpRequest executes from Jenkins Master node Code changed in jenkins User: Janario Oliveira Path: src/main/java/jenkins/plugins/http_request/HttpRequest.java src/main/java/jenkins/plugins/http_request/HttpRequestExecution.java src/main/java/jenkins/plugins/http_request/HttpRequestStep.java src/main/java/jenkins/plugins/http_request/ResponseContentSupplier.java src/main/java/jenkins/plugins/http_request/auth/Authenticator.java src/main/java/jenkins/plugins/http_request/util/HttpClientUtil.java src/main/java/jenkins/plugins/http_request/util/HttpRequestNameValuePair.java src/main/java/jenkins/plugins/http_request/util/RequestAction.java src/test/java/jenkins/plugins/http_request/HttpRequestStepTest.java src/test/java/jenkins/plugins/http_request/HttpRequestTest.java http://jenkins-ci.org/commit/http-request-plugin/7f0b14ca136e15109f279987cb9a6b67c1193537 Log: #JENKINS-36486 - Moved execution to allow serialization and execution on node channel Compare: https://github.com/jenkinsci/http-request-plugin/compare/a5124c6fef73...7f0b14ca136e Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26137) Mysterious serialization errors
Title: Message Title Jesse Glick commented on JENKINS-26137 Re: Mysterious serialization errors Filed workflow-basic-steps PR 39 (and its upstream PRs) attempting to troubleshoot the recurrent exception from RiverWriter. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41650) More documentation on setting up rocketchatnotifier
Title: Message Title Sean Flanigan edited a comment on JENKINS-41650 Re: More documentation on setting up rocketchatnotifier Thanks for improving the documentation, and the link to the test matrix. I have created - JENKINS-42099 - to request API key support. Now that I know that 0.46.0 is supported, I don't think a generic WebHook feature would be needed. EDIT: but it would be a good idea from a security point of view because a WebHook integration doesn't have complete access to a Rocket.Chat account. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42099) Support for API keys instead of username+password
Title: Message Title Sean Flanigan closed an issue as Not A Defect Sorin Sbarnea Well, I am in that boat (SSO, not an admin), and I later got an admin to create a special bot user for Jenkins to bypass SSO (without success so far: JENKINS-42365). Before that, I was hoping to avoid putting my password into Jenkins, and I'd prefer not to put the bot's password in either. I was under the impression Rocket.Chat had API keys, but apparently not (just temporary tokens): https://rocket.chat/docs/developer-guides/rest-api/authentication/ Unless Rocket.Chat gets API keys with restricted capabilities (eg only write to a particular channel, no reading), they wouldn't really be more secure than passwords anyway. Without API keys in Rocket.Chat, I think my request is invalid. Closing. PS webhook integrations in Rocket.Chat do seem to have restricted capabilities, so I would support that idea. I think it should be a separate issue though. Jenkins / JENKINS-42099 Support for API keys instead of username+password Change By: Sean Flanigan Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlas
[JIRA] (JENKINS-43077) withEnv does not set some environment variables
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-43077 withEnv does not set some environment variables Change By: Andrew Bayer Component/s: workflow-basic-steps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42995) Pipeline stages which include a shell script to cat a long log file can lock up the browser
Title: Message Title Thorsten Scherler commented on JENKINS-42995 Re: Pipeline stages which include a shell script to cat a long log file can lock up the browser rofl Michael Neale Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42995) Pipeline stages which include a shell script to cat a long log file can lock up the browser
Title: Message Title Michael Neale commented on JENKINS-42995 Re: Pipeline stages which include a shell script to cat a long log file can lock up the browser Added a cat on a log to help Thorsten: Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42995) Pipeline stages which include a shell script to cat a long log file can lock up the browser
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42995 Pipeline stages which include a shell script to cat a long log file can lock up the browser Change By: Michael Neale Attachment: catonalog.jpg Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42995) Pipeline stages which include a shell script to cat a long log file can lock up the browser
Title: Message Title Karl Shultz commented on JENKINS-42995 Re: Pipeline stages which include a shell script to cat a long log file can lock up the browser I eventually figured it was the loading bar. When I first started the draft of this issue, I was testing with Edge. Its behavior was such that there wasn't any animation showing in the bar, so it looked like a rendering glitch at the time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43078) Admin users could be defined as organization*team too
Title: Message Title Sam Gleske commented on JENKINS-43078 Re: Admin users could be defined as organization*team too This is already possible using one of the matrix-based authorization schemes. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42995) Pipeline stages which include a shell script to cat a long log file can lock up the browser
Title: Message Title Thorsten Scherler commented on JENKINS-42995 Re: Pipeline stages which include a shell script to cat a long log file can lock up the browser hmm, sounds like react not handling that big log very well. We do multiple iterations of render some lines do down render some more AFTER the blue thin line (that is our loading bar BTW ) But it sounds that we do not even get there. One small nit ` sh 'cat /var/log/jenkins/jenkins.log'`would lead on my system to `cat: /var/log/jenkins/jenkins.log: No such file or directory` Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40834) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40834 Re: Report primary branch Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/GitClient.java src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/RemoteGitImpl.java src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java src/test/java/org/jenkinsci/plugins/gitclient/JGitAPIImplTest.java src/test/java/org/jenkinsci/plugins/gitclient/JGitApacheAPIImplTest.java http://jenkins-ci.org/commit/git-client-plugin/85501392a154ed9b48e8e885a4fb1055fbfb3746 Log: Merge pull request #236 from stephenc/jenkins-40834 JENKINS-40834 Add an API to resolve symbolic refs Compare: https://github.com/jenkinsci/git-client-plugin/compare/85f78b9ca80e...85501392a154 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40834) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40834 Re: Report primary branch Code changed in jenkins User: Stephen Connolly Path: src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java src/test/java/org/jenkinsci/plugins/gitclient/JGitAPIImplTest.java src/test/java/org/jenkinsci/plugins/gitclient/JGitApacheAPIImplTest.java http://jenkins-ci.org/commit/git-client-plugin/f5e22966ba11c5e5f309d5e9a0de7adcd99dd6c7 Log: JENKINS-40834 Fix tests to apply for correct versions of the git clients Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40834) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40834 Re: Report primary branch Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/2cb2fc176d47bf1dc0d8017e9bfd567d4fa453e5 Log: JENKINS-40834 Bingo! A nasty hack gets us the symref info for JGit pending their implementation of same Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40834) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40834 Re: Report primary branch Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/GitClient.java src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/c5edec5f795d8bec1c46dccb5b404cde9ecd9b17 Log: JENKINS-40834 Probably safest to let the consumer of the API decide what to do if the is no symbolc ref support Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40834) Report primary branch
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40834 Re: Report primary branch Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/GitClient.java src/main/java/org/jenkinsci/plugins/gitclient/JGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/RemoteGitImpl.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/64f43038d0723c3c313d6bed66edea190b17ba51 Log: JENKINS-40834 Add an API to resolve symbolic refs Sadly JGit needs to try and guess Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42862) Unable to view Performance Center Test Results - HP Application Automation Tools
Title: Message Title Mark Thistlewaite commented on JENKINS-42862 Re: Unable to view Performance Center Test Results - HP Application Automation Tools Yes the problem has been solved, I used the "For LoadRunner Performance reports" portion, but this has led to other problems: Login succeeded Run started (TestID: 359, RunID: 2727, TimeslotID: 19278) Set HP_RUN_ID Env Variable to 2727 RunID: 2727 - State = Initializing RunID: 2727 - State = Running RunID: 2727 - State = Collating Results RunID: 2727 - State = Creating Analysis Data RunID: 2727 - State = Finished Publishing analysis report Adding run: 2727 to trend report: 24 Publishing run: 2727 on trend report: 24 Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Publishing... Run: 2727 publishing status: Trended Downloading trend report: 24 in PDF format Trend report: 24 was successfully downloaded View Analysis Trend Report Logout succeeded Result Status (PC RunID: 2727): SUCCESS 1). Within the Console Log I am able to click on the Link for the results and I get the result values, but the Gifs are not showing. 2). We are also publishing a Trend Report for the test, and it comes out black, the trend is a bar graph. It is a PDF file. 3). Click on the Build Report, rather than the Console Log, we cannot see the results at all, the page is presented and following through the links on the page yields a page that looks like this: Standard Output View analysis report: artifact/performanceTestsReports/pcRun2727/Report.html Download Report: artifact/performanceTestsReports/pcRun2727/zip/pcRun2727 No links or reports. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42995) Pipeline stages which include a shell script to cat a long log file can lock up the browser
Title: Message Title Michael Neale commented on JENKINS-42995 Re: Pipeline stages which include a shell script to cat a long log file can lock up the browser Thorsten Scherler I wonder if this is flooding with events or something else to do with streaming? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Jesse Glick commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Probably less effort to make straight to CLI. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43039) Blue Ocean Test Results fail to load over https
Title: Message Title Michael Neale commented on JENKINS-43039 Re: Blue Ocean Test Results fail to load over https I think har files are best not on a public ticket as it may contain more personal information than should be shared. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43079) Move publishing to ci.jenkins.io or automated location
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-43079 Move publishing to ci.jenkins.io or automated location Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/23 11:10 PM Labels: technical-debt Priority: Major Reporter: Michael Neale Ideally the publishing of the blueocean-plugin multimodule would be moved to a (parametrised?) job on ci.jenkins.io, or some "standard and secure" location so published can be performed on demand by multiple users. This may involve a release branch, or a parametrised job, not sure. We need to find out what the "standard" process is (if there is one). I think we can't use dogfood as it is not a "trusted" environment for credentials, due to it running frequently updated and experimental versions of itself. Publishing should be like the official docker image which is published on jenkins.io secure infrastructure. (need to talk to KK about best way for this). Add Comment
[JIRA] (JENKINS-42099) Support for API keys instead of username+password
Title: Message Title Sorin Sbarnea commented on JENKINS-42099 Re: Support for API keys instead of username+password How about webhook + token? The reality is that most big deployments are using some form of SSO with 2FA which renders username/password authentication useless. The user trying to configure Jenkins is almost not sure an admin on the IM server so he cannot create new accounts. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title Daniel Beck commented on JENKINS-43062 Re: SSH Host Key Verifiers are not configured for all SSH slaves The "Host Key Verification Strategy" I set is "Known hosts file Verification Strategy". What should I do to avoid that warning? Maybe a UI bug, if existing SSH slaves have no strategy set, but there's no entry for 'none' in the list – if so, it should suffice to just submit the form. CC Michael Clarke WDYT? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43032) withCredentials masks every occurence of secret string/username/password even if unrelated to binding
Title: Message Title
Christopher Orr commented on JENKINS-43032
Re: withCredentials masks every occurence of secret string/username/password even if unrelated to binding
How would the plugin know that your Gradle script is doing `echo "coordinates: ${artifactInfo}"` and not `echo "Using password: ${pw}"`, in order to only mask the second version? I would think that the real solution is to use secure passwords.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Arnaud Héritier commented on JENKINS-38062 Re: "Create Delivery Pipeline version" errors JENKINS-34805 didn't solve the problem Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42636) During pipeline step duration reported incorrectly
Title: Message Title Michael Neale commented on JENKINS-42636 Re: During pipeline step duration reported incorrectly Sam Van Oort have seen a few people bring it up - but not in a major way, it happens I would say "often", it smore that people don't often see that screen while it is happening. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27094) WriteFileStep ignores encoding
Title: Message Title Jesse Glick assigned an issue to Daniel Butler Jenkins / JENKINS-27094 WriteFileStep ignores encoding Change By: Jesse Glick Assignee: Jesse Glick Daniel Butler Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27094) WriteFileStep ignores encoding
Title: Message Title Jesse Glick started work on JENKINS-27094 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27094) WriteFileStep ignores encoding
Title: Message Title Jesse Glick updated JENKINS-27094 Jenkins / JENKINS-27094 WriteFileStep ignores encoding Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31173) Invalid characters in Test Results file
Title: Message Title Yafim Kazak assigned an issue to xiwen zhao Jenkins / JENKINS-31173 Invalid characters in Test Results file Change By: Yafim Kazak Assignee: Ofir Shaked xiwen zhao Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26002) Send ALM test execution summary email
Title: Message Title Yafim Kazak assigned an issue to Roy Lu Jenkins / JENKINS-26002 Send ALM test execution summary email Change By: Yafim Kazak Assignee: Ofir Shaked Roy Lu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22109) Link to Test runs incorrect
Title: Message Title Yafim Kazak assigned an issue to xiwen zhao Jenkins / JENKINS-22109 Link to Test runs incorrect Change By: Yafim Kazak Assignee: Amit Bezalel xiwen zhao Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22109) Link to Test runs incorrect
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-22109 Link to Test runs incorrect Change By: Yafim Kazak Labels: link qc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42862) Unable to view Performance Center Test Results - HP Application Automation Tools
Title: Message Title Yafim Kazak commented on JENKINS-42862 Re: Unable to view Performance Center Test Results - HP Application Automation Tools Hi, has this issue was solved using the fix? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42996) Build step 'Execute HP tests using HP Performance Center' changed build result to UNSTABLE
Title: Message Title Yafim Kazak commented on JENKINS-42996 Re: Build step 'Execute HP tests using HP Performance Center' changed build result to UNSTABLE Please update plugin to at least v5 and try again. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title Shannon Kerr commented on JENKINS-43062 Re: SSH Host Key Verifiers are not configured for all SSH slaves Agree, frustrating. Why should I have to change something arbitrary and then change back just to get this to go away? I'm seeing this on two Jenkins instances. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43078) Admin users could be defined as organization*team too
Title: Message Title Aleksi Aalto created an issue Jenkins / JENKINS-43078 Admin users could be defined as organization*team too Issue Type: Improvement Assignee: Sam Gleske Components: github-oauth-plugin Created: 2017/Mar/23 10:05 PM Environment: Now admin users can be defined only with github-usernames. It would be very useful to be able to define Jenkins admins by Github teams. Especially, when administering a larger number of Jenkins, controlling the admin groups through one Github group would be very useful. Priority: Major Reporter: Aleksi Aalto Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42982) Editor is inop with Microsoft Edge
Title: Message Title Keith Zantow updated JENKINS-42982 Jenkins / JENKINS-42982 Editor is inop with Microsoft Edge Change By: Keith Zantow Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35359) Limit concurrent builds for 1 MultiBranch project
Title: Message Title Jesse Glick commented on JENKINS-35359 Re: Limit concurrent builds for 1 MultiBranch project Right use lock for that purpose. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42982) Editor is inop with Microsoft Edge
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42982 Re: Editor is inop with Microsoft Edge Code changed in jenkins User: Keith Zantow Path: src/main/js/components/editor/EditorPipelineGraph.jsx src/main/js/services/fetchClassic.js src/main/less/editor.less http://jenkins-ci.org/commit/blueocean-pipeline-editor-plugin/9ee2d50f565848422f47258e911fbbb0d9c1f95c Log: [FIX JENKINS-42982] - fix issue on EDGE & node styles (#36) JENKINS-42982 - fix issue on EDGE & node styles Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35185) Trigger github multi-branch build via SQS
Title: Message Title Idikoro Eradiri commented on JENKINS-35185 Re: Trigger github multi-branch build via SQS Jesse Glick Stephen Connolly I can confirm that this branch of the plugin https://github.com/jenkinsci/github-sqs-plugin/pull/9 does indeed kick off Multibranch pipleline builds from messages received on SQS! I was able to get jenkins to read from SQS and trigger builds on a multi-branch pipeline that was created with the latest version of the BlueOcean UI. dThe Jenkins instances were both behind our corporate firewall. One was deployed on AWS and the other was on my local machine. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35185) Trigger github multi-branch build via SQS
Title: Message Title Idikoro Eradiri edited a comment on JENKINS-35185 Re: Trigger github multi-branch build via SQS [~jglick] [~stephenconnolly] I can confirm that this branch of the plugin [https://github.com/jenkinsci/github-sqs-plugin/pull/9|http://example.com / ] does indeed kick off Multibranch pipleline builds from messages received on SQS! I was able to get jenkins to read from SQS and trigger builds on a multi-branch pipeline that was created with the latest version of the BlueOcean UI.!image-2017-03-23-17-44-21-564.png! dThe The Jenkins instances were both behind our corporate firewall. One was deployed on AWS and the other was on my local machine. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35185) Trigger github multi-branch build via SQS
Title: Message Title Idikoro Eradiri updated an issue Jenkins / JENKINS-35185 Trigger github multi-branch build via SQS Change By: Idikoro Eradiri Attachment: image-2017-03-23-17-44-21-564.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37221) NullPointerException when running JacocoPublisher
Title: Message Title centic resolved as Fixed Release 2.2.0 is out, please try it and reopen if it still happens then. Jenkins / JENKINS-37221 NullPointerException when running JacocoPublisher Change By: centic Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com
[JIRA] (JENKINS-37161) Release jacoco 2.1
Title: Message Title centic commented on JENKINS-37161 Re: Release jacoco 2.1 BTW, in the future it is likely more effective to discuss release-dates on the mailing-list at http://groups.google.com/group/jenkins-jacoco-plugin-mailing-list, not many people seem to look at issues here. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37161) Release jacoco 2.1
Title: Message Title centic resolved as Fixed 2.1.0 and 2.2.0 are out. Jenkins / JENKINS-37161 Release jacoco 2.1 Change By: centic Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36168) Jacoco pluging does not read values from environment varibles
Title: Message Title centic commented on JENKINS-36168 Re: Jacoco pluging does not read values from environment varibles Because this is open source and there is nobody paid here. So if you need this to be accelerated you need to step in yourself and apply on the jenkins-mailing-list to get rights to contribute the plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-42994 In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42994
In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Change By:
James Dumay
In some situations, the 're-run' button will not trigger a build and not give any feedback. One example:*Classic UI* {code} Job re-run and failed: {code} Started by user [admin|http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/user/admin]17:38:37 Connecting to [https://api.github.com|https://api.github.com/] using admin/** (Github Access Token)Obtained Jenkinsfile from 77d10641d025cf0169f61cd6e769fe72c36abf40Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selectedorg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 1: unable to resolve class com.cloudbees.ops.Builder @ line 1, column 1. import com.cloudbees.ops.Builder; ^1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:946) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:593) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:542) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:430) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:393) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:238) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE{code}*In the Blue Ocean UI*No feedback on re-run buttonJob not retriggeringIncluded are two screenshots with the inert buttons highlighted.
Add Comment
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42994
In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Change By:
James Dumay
In some situations, the 're-run' button will not trigger a build and not give any feedback. One example:*Classic UI* {code} Job re-run and failed:Started by user [admin|http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/user/admin]17:38:37 Connecting to [https://api.github.com|https://api.github.com/] using admin/** (Github Access Token)Obtained Jenkinsfile from 77d10641d025cf0169f61cd6e769fe72c36abf40Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected {code} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 1: unable to resolve class com.cloudbees.ops.Builder @ line 1, column 1. import com.cloudbees.ops.Builder; ^1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:946) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:593) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:542) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:430) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:393) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:238) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE{code}*In the Blue Ocean UI*No feedback on re-run buttonJob not retriggeringIncluded are two screenshots with the inert buttons highlighted.
Add Comment
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42994
In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Change By:
James Dumay
In some situations, the 're-run' button will not trigger a build and not give any feedback. One example:*Classic UI*Job re-run and failed:Started by user [admin|http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/user/admin]17:38:37 Connecting to [https://api.github.com|https://api.github.com/] using admin/** (Github Access Token)Obtained Jenkinsfile from 77d10641d025cf0169f61cd6e769fe72c36abf40Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected {code} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 1: unable to resolve class com.cloudbees.ops.Builder @ line 1, column 1. import com.cloudbees.ops.Builder; ^1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:946) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:593) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:542) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:430) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:393) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:238) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE {code} *In the Blue Ocean UI*No feedback on re-run buttonJob not retriggeringIncluded are two screenshots with the inert buttons highlighted.
Add Comment
[JIRA] (JENKINS-34343) PMD, Jacococ code coverage report and Junit report send in mail
Title: Message Title centic commented on JENKINS-34343 Re: PMD, Jacococ code coverage report and Junit report send in mail I would take a look at the extended mail plugin instead, it can include arbitrary result-files as part of the email and thus you will not require each plugin to support this specifically. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43039) Blue Ocean Test Results fail to load over https
Title: Message Title James Dumay commented on JENKINS-43039 Re: Blue Ocean Test Results fail to load over https Jonathan Brito it seems like that HAR file is corrupt. Can you please try to rerecord and upload it again? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34343) PMD, Jacococ code coverage report and Junit report send in mail
Title: Message Title centic updated an issue Jenkins / JENKINS-34343 PMD, Jacococ code coverage report and Junit report send in mail Change By: centic Component/s: jacoco-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32575) Manually uploading a plugin causes 413 Request Entity Too Large error.
Title: Message Title centic resolved as Cannot Reproduce Closing based on previous comment. Jenkins / JENKINS-32575 Manually uploading a plugin causes 413 Request Entity Too Large error. Change By: centic Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.googl
[JIRA] (JENKINS-28686) ArrayIndexOutOfBoundsException in JACOCO coverage
Title: Message Title centic resolved as Cannot Reproduce No response for a long time and cannot reproduce this locally, thus closing for now, please reopen with updated information if this is still an issue for you. Jenkins / JENKINS-28686 ArrayIndexOutOfBoundsException in JACOCO coverage Change By: centic Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-28636) Jacoco.exec can not be deleted
Title: Message Title centic resolved as Cannot Reproduce No response for a long time, therefore closing for now. Please reopen with some updated information if this is still an issue for you. Jenkins / JENKINS-28636 Jacoco.exec can not be deleted Change By: centic Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@go
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title Michael Neale commented on JENKINS-42994 Re: In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Not sure how to reproduce this, only see the description of what happened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27581) JaCoCo Coverage Trend not displayed
Title: Message Title centic resolved as Cannot Reproduce I could not reproduce this and there were a number of fixes applied since version 1.0.19, please reopen this issue if you are still seeing this issue. Jenkins / JENKINS-27581 JaCoCo Coverage Trend not displayed Change By: centic Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci
[JIRA] (JENKINS-25532) java.util.zip.ZipException: invalid literal/length code in JacocoPublisher
Title: Message Title centic resolved as Cannot Reproduce No answer for a long time. Jenkins / JENKINS-25532 java.util.zip.ZipException: invalid literal/length code in JacocoPublisher Change By: centic Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.co
[JIRA] (JENKINS-42702) Applying the branch filter should set active the activity tab
Title: Message Title Ivan Meredith updated JENKINS-42702 Jenkins / JENKINS-42702 Applying the branch filter should set active the activity tab Change By: Ivan Meredith Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23516) Support matching JARs as class "directories" in class pattern
Title: Message Title centic resolved as Duplicate We do not copy .jar files any more with JENKINS-38604, this should also improve this one. Jenkins / JENKINS-23516 Support matching JARs as class "directories" in class pattern Change By: centic Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more opt
[JIRA] (JENKINS-21859) ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception Caught error while checking for symbolic links
Title: Message Title centic resolved as Cannot Reproduce The error indicates that you are having a symbolic link which points to itself in the build-outputs that are configured for the jacoco-plugin, please check your .class/.java/.exec files and see if there is any such invalid symbolic link. Please reopen with information about which symbolic links there are in your project if this is still a problem for you. Jenkins / JENKINS-21859 ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception Caught error while checking for symbolic links Change By: centic Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-21340) Jacoco report empty when Ant build run with Jenkins
Title: Message Title centic resolved as Cannot Reproduce Processing coverage information works as expected as far as I see. Please read the output of the JaCoCo plugin as part of your build carefully, it prints out which files are found based on your configuration, this typically indicates that the locations of the .exec/.class/.java files are not set correctly. Please reopen this issue together with the relevant parts of the build-output if there is still an issue for you. Jenkins / JENKINS-21340 Jacoco report empty when Ant build run with Jenkins Change By: centic Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-21659) Integrate Emma Coverage Column plugin
Title: Message Title centic resolved as Won't Fix I think we can close this as Won't Fix, the EMMA plugin is not maintained any more, there are only 400 users compared to 9000 for the jacoco-plugin, so I think it finally is not replaced by the jacoco-plugin and thus this task is not necessary any more, all users of EMMA are urged to migrate to jacoco since a long time. Jenkins / JENKINS-21659 Integrate Emma Coverage Column plugin Change By: centic Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message becaus
[JIRA] (JENKINS-20926) Clarify relation to Emma Coverage Column plugin
Title: Message Title centic resolved as Fixed The page for the EMMA plugin now states to simply use the JaCoCo plugin for some time already now, so I think this is resolved. Jenkins / JENKINS-20926 Clarify relation to Emma Coverage Column plugin Change By: centic Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.c
[JIRA] (JENKINS-32847) filter to include only top directories
Title: Message Title centic resolved as Fixed This is included release 2.2.0 Jenkins / JENKINS-32847 filter to include only top directories Change By: centic Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36453) Replay does not reuse commit on non-multibranch pipeline jobs
Title: Message Title James Dumay commented on JENKINS-36453 Re: Replay does not reuse commit on non-multibranch pipeline jobs Jesse Glick great explanation I think we are going to put less emphasis on this job type in the UI in the future so I'd imagine this isn't as high priority as I thought it might be. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26254) Jacoco plugin is too slow and occupies too much microprocessor time
Title: Message Title centic resolved as Fixed I am closing this for the 2.2.0 release, please report new issues if you still have issues when running with that version of the plugin. Jenkins / JENKINS-26254 Jacoco plugin is too slow and occupies too much microprocessor time Change By: centic Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issu
[JIRA] (JENKINS-42508) Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public"
Title: Message Title Jesse Glick commented on JENKINS-42508 Re: Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public" I observed this reproducibly at one point and developed a patch which fixed it—but can no longer reproduce it after many attempts (and the revised patch was developed after no longer being able to reproduce). So you should try a snapshot build to confirm that it helps. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42515) User education empty state updates
Title: Message Title Cliff Meyers commented on JENKINS-42515 Re: User education empty state updates James Dumay referring to the Google Doc, I have two questions about the Activity screen (first row on page #2): In practice, will we really see a multi-branch project which has branches but that has no runs? It seems the first thing Jenkins does when creating a multi-branch pipeline is run any branches w/ Jenkinsfiles. This screen was easy enough to create but I'm not sure we actually need it? What should we display for a freestyle job (no branches) with no runs? As it stands now, it would just be a "Run" button at the top of the screen with nothing below it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42952) Make currentBuild.duration more meaningful and add string equivalent
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42952 Re: Make currentBuild.duration more meaningful and add string equivalent Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-job-plugin/0cfa03044c4a88c80df4ca18b322e4532f7d2b81 Log: Deleting obsolete comment noticed in relation to JENKINS-42952. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17027) Ratio red/green bar wrong
Title: Message Title SCM/JIRA link daemon commented on JENKINS-17027 Re: Ratio red/green bar wrong Code changed in jenkins User: Marcus Bauer Path: src/main/java/hudson/plugins/jacoco/model/Coverage.java src/main/java/hudson/plugins/jacoco/model/CoverageObject.java http://jenkins-ci.org/commit/jacoco-plugin/6adf351a1cef5438d98bf49d4dbc1c45a4b5ec1c Log: JENKINS-17027 Red/green ratio is wrong This issue is adressed by taking the total number of lines, etc. into account – instead of only the covered or missing items (depends on whether you have 50% coverage or more) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27120) Make JacocoPublisher a SimpleBuildStep
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27120 Re: Make JacocoPublisher a SimpleBuildStep Code changed in jenkins User: Alex Soto Path: pom.xml src/main/java/hudson/plugins/jacoco/JacocoBuildAction.java src/main/java/hudson/plugins/jacoco/JacocoPublisher.java src/main/java/hudson/plugins/jacoco/JacocoReportDir.java src/main/java/hudson/plugins/jacoco/model/CoverageObject.java src/main/java/hudson/plugins/jacoco/report/AbstractReport.java src/main/java/hudson/plugins/jacoco/report/CoverageReport.java src/test/java/hudson/plugins/jacoco/report/AbstractReportTest.java src/test/java/hudson/plugins/jacoco/report/CoverageReportTest.java src/test/java/hudson/plugins/jacococoveragecolumn/JaCoCoColumnTest.java http://jenkins-ci.org/commit/jacoco-plugin/ce1f7322f1462ba35c2f7cecc1556d2456066c64 Log: [FIXED JENKINS-27120] Adding Workflow support for JaCoCo publisher Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19789) Coverage table doesn't show methods with the same name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-19789 Re: Coverage table doesn't show methods with the same name Code changed in jenkins User: Marcus Bauer Path: src/main/java/hudson/plugins/jacoco/report/CoverageReport.java src/main/resources/hudson/plugins/jacoco/tags/breakdownMethodsTable.jelly http://jenkins-ci.org/commit/jacoco-plugin/393ff1edf50613875d223de2313222e7522e5e33 Log: JENKINS-19789 Method parameters in the class summary table Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18894) Make coverage column optional in Dashboard Views
Title: Message Title SCM/JIRA link daemon commented on JENKINS-18894 Re: Make coverage column optional in Dashboard Views Code changed in jenkins User: Dominik Stadler Path: src/main/java/hudson/plugins/jacococoveragecolumn/JaCoCoColumn.java http://jenkins-ci.org/commit/jacoco-plugin/00c5a36b2fbe4d326c70b9b37d41af971c4204dc Log: JENKINS-18894: Change descriptor to not show the column by default Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19526) Display Branch Coverage Information
Title: Message Title SCM/JIRA link daemon commented on JENKINS-19526 Re: Display Branch Coverage Information Code changed in jenkins User: Marcus Bauer Path: src/main/java/hudson/plugins/jacoco/report/SourceAnnotator.java http://jenkins-ci.org/commit/jacoco-plugin/7d3db625cfe14bec931626f6e13966f06b8d4dd5 Log: JENKINS-19526 Branch Coverage Information Instead of coverage based on the instruction counter, the displayed partial and full coverage is based solely on branch information per line of code. Lines are colored in green (full coverage), yellow (partly covered) or red (not covered) for where coverage information is available. Lines without coverage information are not formatted any differently from the previous version. Code with branch information is prefixed with a • and has a mouse-over to display either "All X branches covered", "All X branches missed" or "X of Y branches missed" for full, none and partial coverage respectively. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16788) Coverage trend's legend is only partially translated
Title: Message Title SCM/JIRA link daemon commented on JENKINS-16788 Re: Coverage trend's legend is only partially translated Code changed in jenkins User: Dominik Stadler Path: src/main/resources/hudson/plugins/jacoco/Messages_de.properties http://jenkins-ci.org/commit/jacoco-plugin/9fac482e0fcca835ba61b80ddbf3d88e011ab94c Log: JENKINS-16788: adjust german translation Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
