[JIRA] (JENKINS-54561) Job fails even though it succeeded: Java 10
Title: Message Title Daniel Beck commented on JENKINS-54561 Re: Job fails even though it succeeded: Java 10 Oleg Nenashev Are we even attempting to work on Java 10, or does this need to happen on Java 11 for us to care? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54555) ••••••••••••
Title: Message Title
Alis Adrovic updated an issue
Jenkins / JENKINS-54555
Change By:
Alis Adrovic
Summary:
'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45129) Unable to scan branches in multibranch plugin when user has two-step verification enabled
Title: Message Title Chris Hemp commented on JENKINS-45129 Re: Unable to scan branches in multibranch plugin when user has two-step verification enabled Having the same issue. With SAML/SSO configured, App Passwords do not work. Using bitbucket-branch-source-plugin version 2.2.14 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54547) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.NullPointerException
Title: Message Title Oleg Nenashev resolved as Duplicate Jenkins / JENKINS-54547 ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.NullPointerException Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54563) NPE when connecting via SSH to Docker via hostname
Title: Message Title lucamilanesio created an issue Jenkins / JENKINS-54563 NPE when connecting via SSH to Docker via hostname Issue Type: Bug Assignee: Nicolas De Loof Components: docker-plugin Created: 2018-11-09 22:29 Environment: linux Priority: Critical Reporter: lucamilanesio Using the following combination: connection to Docker via unix:///var/run/docker.sock set hostname to the Jenkins master IP set connect to slaves via SSH I am expecting the docker-plugin to be able to create a container, inject the SSH key and connect What I see instead is a NPE: java.lang.NullPointerExceptionjava.lang.NullPointerException at io.jenkins.docker.connector.DockerComputerSSHConnector.createLauncher(DockerComputerSSHConnector.java:230) at io.jenkins.docker.connector.DockerComputerConnector.createLauncher(DockerComputerConnector.java:91) at com.nirima.jenkins.plugins.docker.DockerTemplate.doProvisionNode(DockerTemplate.java:566) at com.nirima.jenkins.plugins.docker.DockerTemplate.provisionNode(DockerTemplate.java:528) at com.nirima.jenkins.plugins.docker.DockerCloud$1.run(DockerCloud.java:365) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-54563) NPE when connecting via SSH to Docker via hostname
Title: Message Title lucamilanesio assigned an issue to lucamilanesio Jenkins / JENKINS-54563 NPE when connecting via SSH to Docker via hostname Change By: lucamilanesio Assignee: Nicolas De Loof lucamilanesio Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46799) Blueocean Docker Pipeline Failed | Cannot start docker container
Title: Message Title Enric Prats reopened an issue Marcelo Tocchetto workaround is good but people should not have to change the docker image once downloaded and running. This should be changed on the Dockerfile which builds the image Jenkins / JENKINS-46799 Blueocean Docker Pipeline Failed | Cannot start docker container Change By: Enric Prats Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46799) Blueocean Docker Pipeline Failed | Cannot start docker container
Title: Message Title Enric Prats updated an issue Jenkins / JENKINS-46799 Blueocean Docker Pipeline Failed | Cannot start docker container Change By: Enric Prats Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46799) Blueocean Docker Pipeline Failed | Cannot start docker container
Title: Message Title Enric Prats edited a comment on JENKINS-46799 Re: Blueocean Docker Pipeline Failed | Cannot start docker container [~mtocchetto] workaround is good but people should not have to change the docker image once downloaded and running. This should be changed on the Dockerfile which builds the image . It's enough to add to the Jenkinsfile: # Allow Jenkins to run docker commands chown :jenkins /var/run/docker.sock I will try to figure how to make the pull request but I have never made one :( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick reopened an issue Best to leave this open at least until distinct issues are filed for such plugins. Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile Change By: Jesse Glick Resolution: Fixed Status: Resolved Reopened Assignee: Stefan Wolf Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54555) 'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met
Title: Message Title Alis Adrovic updated an issue Jenkins / JENKINS-54555 'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met Change By: Alis Adrovic Summary: 'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48198) "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title
Title: Message Title Michael Ferris commented on JENKINS-48198 Re: "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title I have been able to track down a bit more where the problem occurs. In Activity details (https://github.com/jenkinsci/blueocean-plugin/blob/77960a8dc21840ae5f6df784a26f91e09d7da621/blueocean-dashboard/src/main/js/components/ActivityDetailsRow.jsx#L33) There is the following const resultRun = run.result === 'UNKNOWN' ? run.state : run.result; resultRun is later used with .toLowerCase() to show in the page. However, it is possible (not sure how) for run.state to be undefined when run.result is "UNKNOWN" probably should change the check to const resultRun = (run.result === 'UNKNOWN' && typeof run.state === "string") ? run.state : run.result; This way Blue Ocean would be more resilient to builds' data Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54561) Job fails even though it succeeded: Java 10
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54561 Job fails even though it succeeded: Java 10 Change By: Oleg Nenashev Labels: java10 java11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54561) Job fails even though it succeeded: Java 10
Title: Message Title Oleg Nenashev updated JENKINS-54561 Hi. This issue would happen on Java 11 as well. Good news is that it was fixed in Jenkins 2.144, see JENKINS-46523. Although stacktraces are a bit different, this issue should be fixed as well. The fix was not backported to the 2.138.x LTS baseline, but it will appear in the next one which will be released in 1 month or so. W.r.t Java 10 support, yes we do not plan to officially support it. Jenkins JEP-211 was rescoped to Java 11 only. OTOH Java 10 will likely work as well. In order to run with Java 10/11, Jenkins version 2.147 should be used (the most recent functional fix). Ken DeLong Thanks for the report anyway! We will appreciate any testing and feedback for Java 10 or Java 11. https://jenkins.io/blog/2018/06/17/running-jenkins-with-java10-11/ reflects the current guidelines for running it (recent weekly WARs can be used as well tho) Jenkins / JENKINS-54561 Job fails even though it succeeded: Java 10 Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title Simon Weber commented on JENKINS-53858 Re: Deadlock on EC2 resources I was able to recreate the problem pretty easily in staging, and master + https://github.com/jenkinsci/ec2-plugin/pull/321 has fixed it so far for me. I'm planning to roll it out in prod asap. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54562) Jenkins will not start as Window Service error 1053
Title: Message Title marcelino dayrit created an issue Jenkins / JENKINS-54562 Jenkins will not start as Window Service error 1053 Issue Type: Bug Assignee: Unassigned Components: jdk-tool-plugin Created: 2018-11-09 21:12 Priority: Major Reporter: marcelino dayrit Jenkins will no longer start as a Window Service after a symantec update to v14. It was working prior to this but I am not sure if this is related to the error. When I attempt to start Jenkins as a service I receive the error: " Windows could not start the Jenkins service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion" When I try to start it using cmd using the command "jenkins.exe start"I get this error: "System.ArgumentNullException: Value cannot be null. Parameter name: path1 at System.IO.Path.Combine(String path1, Stringpath2) at winsw.ServiceDescriptor..ctor() at winsw.WrapperService.Run(String[] _args) at winsw.WrapperService.Main(string[] args)" Does anyone have any idea on how to fix this? I tried using https://support.symantec.com/en_US/article.TECH193916.html and I also tried creating a jenkins.exe.config file to prevent the firewall from blocking it Add Comment
[JIRA] (JENKINS-54547) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.NullPointerException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54547 ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.NullPointerException Change By: Oleg Nenashev Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54562) Jenkins will not start as Window Service error 1053
Title: Message Title Oleg Nenashev commented on JENKINS-54562 Re: Jenkins will not start as Window Service error 1053 marcelino dayrit please provide your jenkins.xml configuration Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54562) Jenkins will not start as Window Service error 1053
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54562 Jenkins will not start as Window Service error 1053 Change By: Oleg Nenashev Component/s: windows-slave-installer-module Component/s: jdk-tool-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54565) added matrix-bases security plugin, then user, saved and got stack trace
Title: Message Title Michael Vensky created an issue Jenkins / JENKINS-54565 added matrix-bases security plugin, then user, saved and got stack trace Issue Type: Bug Assignee: Daniel Beck Components: matrix-auth-plugin Created: 2018-11-10 00:40 Environment: FROM jenkins/jenkins:lts-alpine; docker running on Mac High Sierra 1 ace-editor: 1.1 2 apache-httpcomponents-client-4-api: 4.5.5-3.0 3 authentication-tokens: 1.3 4 bouncycastle-api: 2.17 5 branch-api: 2.0.21 6 cloudbees-folder: 6.6 7 command-launcher: 1.2 8 credentials-binding: 1.17 9 credentials: 2.1.18 10 display-url-api: 2.2.0 11 docker-commons: 1.13 12 docker-workflow: 1.17 13 durable-task: 1.27 14 git-client: 2.7.3 15 git-server: 1.7 16 git: 3.9.1 17 github-api: 1.92 18 github: 1.29.3 19 gitlab-plugin: 1.5.10 20 handlebars: 1.1.1 21 jackson2-api: 2.9.7.1 22 jdk-tool: 1.1 23 jquery-detached: 1.2.1 24 jsch: 0.1.54.2 25 junit: 1.26.1 26 lockable-resources: 2.3 27 mailer: 1.22 28 matrix-project: 1.13 29 momentjs: 1.1.1 30 pipeline-build-step: 2.7 31 pipeline-graph-analysis: 1.7 32 pipeline-input-step: 2.8 33 pipeline-milestone-step: 1.3.1 34 pipeline-model-api: 1.3.2 35 pipeline-model-declarative-agent: 1.1.1 36 pipeline-model-definition: 1.3.2 37 pipeline-model-extensions: 1.3.2 38 pipeline-rest-api: 2.10 39 pipeline-stage-step: 2.3 40 pipeline-stage-tags-metadata: 1.3.2 41 pipeline-stage-view: 2.10 42 plain-credentials: 1.4 43 scm-api: 2.3.0 44 script-security: 1.48 45 ssh-credentials: 1.14 46 structs: 1.17 47 token-macro: 2.5 48 workflow-aggregator: 2.6 49 workflow-api: 2.32 50 workflow-basic-steps: 2.12 51 workflow-cps-global-lib: 2.12 52 workflow-cps: 2.60 53 workflow-durable-task-step: 2.26 54 workflow-job: 2.29 55 workflow-multibranch: 2.20 56 workflow-scm-step: 2.7 57 workflow-step-api: 2.16 58 workflow-support: 2.22 Priority: Blocker Reporter: Michael Vensky
[JIRA] (JENKINS-54564) Jenkins master CPU pegs pegs at >= 18% - Killing telemetry collection thread seems to fix it
Title: Message Title Jon B commented on JENKINS-54564 Re: Jenkins master CPU pegs pegs at >= 18% - Killing telemetry collection thread seems to fix it In the thread dump I took prior to killing the thread, here's what I see with respect to telemetry: "telemetry collection thread" #1313308 daemon prio=5 os_prio=0 tid=0x561f7e3f0800 nid=0x2e99 runnable [0x7ff048996000]"telemetry collection thread" #1313308 daemon prio=5 os_prio=0 tid=0x561f7e3f0800 nid=0x2e99 runnable [0x7ff048996000] java.lang.Thread.State: RUNNABLE at java.util.TreeMap.successor(TreeMap.java:2154) at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1212) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1265) at java.util.AbstractSet.hashCode(AbstractSet.java:124) at java.util.TreeMap$Entry.hashCode(TreeMap.java:2112) at java.util.AbstractMap.hashCode(AbstractMap.java:530) at java.util.HashMap.hash(HashMap.java:339) at java.util.HashMap.put(HashMap.java:612) at java.util.HashSet.add(HashSet.java:220) at net.sf.json.AbstractJSON.addInstance(AbstractJSON.java:67) at net.sf.json.JSONObject._fromMap(JSONObject.java:1059) at net.sf.json.JSONObject.fromObject(JSONObject.java:160) at net.sf.json.JSONObject.fromObject(JSONObject.java:132) at jenkins.telemetry.impl.StaplerDispatches.createContent(StaplerDispatches.java:83) at jenkins.telemetry.Telemetry$TelemetryReporter.lambda$execute$0(Telemetry.java:167) at jenkins.telemetry.Telemetry$TelemetryReporter$$Lambda$260/1575862926.accept(Unknown Source) at java.lang.Iterable.forEach(Iterable.java:75) at jenkins.telemetry.Telemetry$TelemetryReporter.execute(Telemetry.java:155) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Thread.java:748) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54564) Jenkins master CPU pegs pegs at >= 18% - Killing telemetry collection thread seems to fix it
Title: Message Title Jon B created an issue Jenkins / JENKINS-54564 Jenkins master CPU pegs pegs at >= 18% - Killing telemetry collection thread seems to fix it Issue Type: Bug Assignee: Unassigned Attachments: image-2018-11-09-16-19-28-490.png, image-2018-11-09-16-22-18-743.png, image-2018-11-09-16-22-43-321.png, jenkinscpustealer.png Components: core Created: 2018-11-10 00:24 Priority: Minor Reporter: Jon B I noticed my CPU randomly seems to peg to ~18%. This has happened several times without warning. I used a Jenkins monitoring feature in order to look at all of the threads and I noticed this one thread which seemed to be taking a huge amount of resources and I decided to click on the terminate button on the right After terminating that thread, the CPU levels returned to their normal levels: The only clue that I can think of is that I run a script on the master host which uses the jenkins CLI to idempotently ensure certain workers are attached on a 10m interval.. that's why you see a spike every 10m. The CPU problem I am reporting seems to usually kick off at the beginning of those 10m intervals.
[JIRA] (JENKINS-48516) When adding a new Global Pipeline Libraries the previous repository information is lost
Title: Message Title Devin Nusbaum updated JENKINS-48516 Given that the fix in Core was backported to the 2.138 LTS line, I am closing the issue. Jenkins / JENKINS-48516 When adding a new Global Pipeline Libraries the previous repository information is lost Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.145 and Jenkins 2.138.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace Uma Shankar no idea. Please install this update and create a logger (Manage Jenkins » System Log) on jenkins.branch.WorkspaceLocatorImpl recording at least FINER and check for messages there when you build a branch project for the first time on a given agent. Also check whether c:\Jenkins\workspace\workspaces.txt exists and, if so, what it contains. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34262) Support for OAuth credentials
Title: Message Title Chris Hemp commented on JENKINS-34262 Re: Support for OAuth credentials Having the same issue. With SAML/SSO configured, App Passwords do not work. Using bitbucket-branch-source-plugin version 2.2.14 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54562) Jenkins will not start as Window Service error 1053
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-54562 Jenkins will not start as Window Service error 1053 Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54523) Ability to stop an UNSTABLE declarative pipeline
Title: Message Title
Jon B commented on JENKINS-54523
Re: Ability to stop an UNSTABLE declarative pipeline
Here's the only method I could find to make this work.. which is not a very good way to accomplish this:
pipeline {
options {
skipDefaultCheckout true
}
agent {
label 'universal'
}
stages {
stage('Stage 1') {
steps {
script {
currentBuild.result = 'ABORTED'
}
}
}
stage('Stage 2') {
when {
_expression_ { currentBuild.result == 'SUCCESS' }
}
steps {
script {
println "REALLY DONT WANT THIS TO BE EXECUTED!"
}
}
}
}
post {
aborted {
println "aborted!"
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54213) MAC OS linked clone
Title: Message Title babak khoueinia commented on JENKINS-54213 Re: MAC OS linked clone Thanks pjdarton. I will give it a try and will get back to you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48198) "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title
Title: Message Title Michael Ferris reopened an issue I have been able to track down a bit more where the problem occurs. In Activity details (https://github.com/jenkinsci/blueocean-plugin/blob/77960a8dc21840ae5f6df784a26f91e09d7da621/blueocean-dashboard/src/main/js/components/ActivityDetailsRow.jsx#L33) There is the following const resultRun = run.result === 'UNKNOWN' ? run.state : run.result; resultRun is later used with .toLowerCase() to show in the page. However, it is possible (not sure how) for run.state to be undefined when run.result is "UNKNOWN" probably should change the check to const resultRun = (run.result === 'UNKNOWN' && typeof run.state === "string") ? run.state : run.result; This way Blue Ocean would be more resilient to builds' data Jenkins / JENKINS-48198 "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title Change By: Michael Ferris Resolution: Fixed Status: Closed Reopened Add Comment
[JIRA] (JENKINS-48198) "TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title
Title: Message Title
Michael Ferris updated an issue
Jenkins / JENKINS-48198
"TypeError: Cannot read property 'toLowerCase' of undefined" for i18n title
Change By:
Michael Ferris
Comment:
I have been able to track down a bit more where the problem occurs.In Activity details ([https://github.com/jenkinsci/blueocean-plugin/blob/77960a8dc21840ae5f6df784a26f91e09d7da621/blueocean-dashboard/src/main/js/components/ActivityDetailsRow.jsx#L33)]There is the following {code:java}const resultRun = run.result === 'UNKNOWN' ? run.state : run.result;{code}resultRun is later used with .toLowerCase() to show in the page. However, it is possible (not sure how) for run.state to be undefined when run.result is "UNKNOWN" probably should change the check to{code:java}const resultRun = (run.result === 'UNKNOWN' && typeof run.state === "string") ? run.state : run.result;{code}This way Blue Ocean would be more resilient to builds' data
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)
Title: Message Title Uhsarp Rin commented on JENKINS-49588 Re: java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035) Fixed after stopping the server, deleting the fingerprints folder and restarting the server. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54551) Revert JENKINS-53462 if necessary
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-54551 Revert JENKINS-53462 if necessary Issue Type: Bug Assignee: Oliver Gondža Components: core Created: 2018-11-09 09:15 Labels: lts-candidate Priority: Minor Reporter: Daniel Beck Tracking the potential need to revert the fix for JENKINS-53462 towards 2.150.1 because of the regressions it caused (linked there). Add Comment
[JIRA] (JENKINS-54551) Revert JENKINS-53462 if necessary
Title: Message Title Daniel Beck resolved as Fixed Resolving to make this show up in the LTS filter. Jenkins / JENKINS-54551 Revert JENKINS-53462 if necessary Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54553) Jenkins to disable editing security from UI (even for admins)
Title: Message Title Rakesh Nagarajan created an issue Jenkins / JENKINS-54553 Jenkins to disable editing security from UI (even for admins) Issue Type: Task Assignee: Unassigned Attachments: image-2018-11-09-15-07-03-793.png Components: core Created: 2018-11-09 09:37 Priority: Minor Reporter: Rakesh Nagarajan Hi Team, I am facing an issue, we have given admin rights to several users in jenkins. But due to some reasons, some one is removing our user id from accessing the jenkins (even i am also an admin in jenkins) Is there any option for resolving this issue. Add Comment
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E commented on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too. Short-term workaround, either of the following under "Orphaned Item Strategy": Switch off "Discard old items" entirely, and take care of that by hand Set positive number in "Max # of old items to keep"/"Days to keep old items". Your mileage may vary depending on how often your Mercurial server goes down. Having dug into this a bit, I believe the orphaned item stuff is behaving as expected. The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in MercurialSCMSource.java it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling to abort entirely if the cache is not available/working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java| [https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java #L211],] it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling /indexing to abort entirely if the cache is not available/working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54554) Jenkins CLI is not working in reverse proxy (traefik)
Title: Message Title Rakesh Nagarajan created an issue Jenkins / JENKINS-54554 Jenkins CLI is not working in reverse proxy (traefik) Issue Type: Task Assignee: Unassigned Components: core Created: 2018-11-09 09:47 Priority: Minor Reporter: Rakesh Nagarajan Hi Team, We have a docker swarm cluster setup, all the jenkins containers created in the docker is managed by traefik. Problem is "Jenkins CLI is not working in this". But without traefik, its working fine. Is this related to fullduplex ? is there any alternative way ? even if we enabled "enable remote CLI" it is not helping us. Add Comment
[JIRA] (JENKINS-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52280 Create official Java 11 Docker Packaging for BlueOcean Change By: Oleg Nenashev During the hackathon we have created [https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10] . Now it needs to be expanded to Java 11 and added to the common release flowsAcceptance: * Create official Docker packaging for Java 11 which runs OOTB * Update jenkins.io documentation to reflect the new repo: [https://jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker] Approach 1: * Promote [https://github.com/oleg-nenashev/jenkins-blueocean-experimental] to jenkinsci * Setup new DockerHub repo with Automatic build, e.g. jenkins/blueocean which is unused * Define naming strategy * Create Java 8 and Java 11 branches there, similar to the source repo * Update jenkins.io documentation to reflect the new repo Approach 2 : * We could replace [https:// jenkins github . io com / doc jenkinsci / book blueocean-plugin / installing blob / #downloading-and-running-jenkins-in-docker master/Dockerfile.jdk10 ] by the new file and make it a part of the Default build by the Docker team It needs agreement with the BlueOcean team. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-54552) code analyzer tool exe to analyze the code and generate the excel file
Title: Message Title praveen kumar created an issue Jenkins / JENKINS-54552 code analyzer tool exe to analyze the code and generate the excel file Issue Type: Task Assignee: Michael Fowler Attachments: Jenkins.png Components: windows-exe-runner-plugin Created: 2018-11-09 09:20 Environment: DEv Labels: jenkins windows Priority: Critical Reporter: praveen kumar Hi team, We are working on COde analyzer tool to run the exe and analyze the openspan(RPA) code and get the results in excel file. We are running batch file and running using commands and we are getting success and not generating the excel file in specified folder. Please help us on with solution. Thanks Praveen K.
[JIRA] (JENKINS-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan reopened an issue This is also an issue. I am working on this Jenkins / JENKINS-54451 Jenkins Set a banner message Change By: Rakesh Nagarajan Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan commented on JENKINS-54451 Re: Jenkins Set a banner message I found an alternative way for doing this. jenkins --> manage jenkins --> prepare for shut down a new pop-up will come up "JENKINS IS GOING TO SHUTDOWN" (But if we do so, then no other jobs will run) Which java function is doing this job? if we can find the function alone, we can modify the wordings and analyze the script. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan assigned an issue to Rakesh Nagarajan Jenkins / JENKINS-54451 Jenkins Set a banner message Change By: Rakesh Nagarajan Assignee: Rakesh Nagarajan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E commented on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down It doesn't help that the next consequence of this is a build storm when the mercurial server comes back up. All branches are marked as reopened and everything rebuilds. We currently have some issues with our hg server, and it reboots several times a week, so the build storms are proving to be the most frustrating consequence. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54554) Jenkins CLI is not working in reverse proxy (traefik)
Title: Message Title Rakesh Nagarajan commented on JENKINS-54554 Re: Jenkins CLI is not working in reverse proxy (traefik) CLI is working fine in SSH. But unfortunately it is not working through http. -auth command is not recognizing in this case. Do we need to use crumb ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan commented on JENKINS-54451 Re: Jenkins Set a banner message Something just like this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54451) Jenkins Set a banner message
Title: Message Title Rakesh Nagarajan updated an issue Jenkins / JENKINS-54451 Jenkins Set a banner message Change By: Rakesh Nagarajan Attachment: image-2018-11-09-15-28-20-204.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Joerg Schwaerzler commented on JENKINS-51143 Re: List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Timothy Bingaman, Sven Schoenung: We're still preparing the PR which initially was created by Moritz Knolle - we're almost done. Wonder whether so else is working on that topic as well. Please let us know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54451) Jenkins Set a banner message
Title: Message Title Daniel Beck closed an issue as Not A Defect The feature exists. It's called "System Message" in the global configuration. Hence this is a request for help, and not a bug or feature request. Please read https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue – you're on the wrong site. Jenkins / JENKINS-54451 Jenkins Set a banner message Change By: Daniel Beck Status: Reopened Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java|https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java#L211], it the retrieve methods simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling/indexing to abort entirely if the cache is not available/working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev commented on JENKINS-52280 Re: Create official Java 11 Docker Packaging for BlueOcean Adrien Lecharpentier: Having separate repo may be a problem Oleg: We could replace https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10 by the new file and make it a part of the Default build by the Docker team Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev edited a comment on JENKINS-52280 Re: Create official Java 11 Docker Packaging for BlueOcean [~alecharp]: * Having separate repo may be a problem . It may a problem for maintainers Oleg: * We could replace [https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10] by the new file and make it a part of the Default build by the Docker team Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Jan Kacik commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step It is not working for parallel stages in declarative pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java| https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java #L211], ] it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling/indexing to abort entirely if the cache is not available/working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Oleg Nenashev commented on JENKINS-51985 Re: Create official jenkins/jenkins Docker images for Java 10 and 11 versions The proposal is to go with the option 1 right now, because it saves a lot of time Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54555) 'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met
Title: Message Title
Alis Adrovic created an issue
Jenkins / JENKINS-54555
'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met
Issue Type:
Bug
Assignee:
Andrew Bayer
Attachments:
2018-11-09 11_14_34-Pipelines.png
Components:
pipeline-model-definition-plugin
Created:
2018-11-09 10:22
Labels:
pipeline plugin
Priority:
Minor
Reporter:
Alis Adrovic
My(stripped out) Jenkinsfile looks like this: pipeline { options { gitlabBuilds(builds: ['prepare-build-environment', 'build']) {{ }}} stages { //stages for preparing the build environment and building stage('Deploy'){ when { anyOf { branch 'dev' branch 'release' branch 'master' {{ }}} {{ }}} options { gitlabBuilds(builds: ['deploy']) {{ }}} steps { //my steps {{ }}} post { failure { updateGitlabCommitStatus name: 'deploy', state: 'failed' {{ }}} success { updateGitlabCommitStatus name: 'deploy', state: 'success' {{ }}} {{ }}} {{ }}} {{ }}} //more stuff } Since I'm using Multibranch Pipeline, I don't want 'Deploy' stage to happen on feature branches. But GitLab gets notified about 'deploy' stage in all cases, and even if the Jenkins job finishes successfully, pipeline status on GitLab is still "running": This makes "Merge when pipeline succeeds" useless, since it will never succeed.
[JIRA] (JENKINS-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52280 Create official Java 11 Docker Packaging for BlueOcean Change By: Oleg Nenashev During the hackathon we have created [https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10] . Now it needs to be expanded to Java 11 and added to the common release flowsAcceptance: * Create official Docker packaging for Java 11 which runs OOTB * Update jenkins.io documentation to reflect the new repo: [https://jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker] Approach 1: * Promote [https://github.com/oleg-nenashev/jenkins-blueocean-experimental] to jenkinsci * Setup new DockerHub repo with Automatic build, e.g. jenkins/blueocean which is unused * Define naming strategy * Create Java 8 and Java 11 branches there, similar to the source repoApproach 2: * We could replace [https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10] by the new file and make it a part of the Default build by the Docker team * Update scripts to do build/deployment of the second Dockerfile It needs agreement with the BlueOcean team. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev commented on JENKINS-52280 Re: Create official Java 11 Docker Packaging for BlueOcean For whomever works on it, Olivier Lamy is probably the best contact in the team Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title Jan Kacik edited a comment on JENKINS-49131 Re: Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition We are too experiencing this . on the latest LTS and plugins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54555) 'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met
Title: Message Title
Alis Adrovic updated an issue
Jenkins / JENKINS-54555
'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met
Change By:
Alis Adrovic
My(stripped out) Jenkinsfile looks like this:{{pipeline {}} {{ options {}} {{ gitlabBuilds(builds: ['prepare-build-environment', 'build'])}} } {{ stages {}} {{ //stages for preparing the build environment and building }}{{ stage('Deploy'){}} {{ when {}} {{ anyOf {}} {{ branch 'dev'}} {{ branch 'release'}} {{ branch 'master'}} \{{ } }} \{{ } }} {{ options {}} {{ gitlabBuilds(builds: ['deploy'])}} \{{ } }} {{ steps {}} {{ //my steps}} \{{ } }} {{ post {}} {{ failure {}} {{ updateGitlabCommitStatus name: 'deploy', state: 'failed'}} \{{ } }} {{ success {}} {{ updateGitlabCommitStatus name: 'deploy', state: 'success'}} \{{ }}} \{{ } }} \{{ } }} \{{ } }}{{ //more stuff}} } {{}}} Since I'm using Multibranch Pipeline, I don't want 'Deploy' stage to happen on feature branches. But GitLab gets notified about 'deploy' stage in all cases, and even if the Jenkins job finishes successfully, pipeline status on GitLab is still "running":!2018-11-09 11_14_34-Pipelines.png! This makes "Merge when pipeline succeeds" useless, since it will never succeed.
Add Comment
[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title Jan Kacik commented on JENKINS-49131 Re: Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition We are too experiencing this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48694) Notifies successful build when still in progress
Title: Message Title Søren Friis commented on JENKINS-48694 Re: Notifies successful build when still in progress **2.2.14 seems to fix the problem we were facing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54553) Jenkins to disable editing security from UI (even for admins)
Title: Message Title Rakesh Nagarajan started work on JENKINS-54553 Change By: Rakesh Nagarajan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54554) Jenkins CLI is not working in reverse proxy (traefik)
Title: Message Title Rakesh Nagarajan started work on JENKINS-54554 Change By: Rakesh Nagarajan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51985 Create official jenkins/jenkins Docker images for Java 10 and 11 versions Change By: Oleg Nenashev In [https://github.com/jenkinsci/docker/pull/690/commits/ffe36e0f9d6d94b1c10e2fc71751e5fbba0a26f4] and [https://github.com/jenkinsci/docker/pull/690] only base images have been adjusted to Java 10 and 11 (in java10 and java11 branches). We need to upstream these changes and integrate into the common weekly release flow.It would be also great to update Alpine and Slim images as well so that they can be shipped within the common release flow (if possible & feasible). Attack plan 1: * Take [https://github.com/jenkinsci/docker/blob/java11/Dockerfile] and put it to master * Update scripts to also build and publish Java 11 * Risk: The build runs on Trusted CI, may need help from [~olblak] . May have issues with debugging * Possible resolution: parameterize scripts and deploy to jenkins4eval (for local debugging). [~oleg_nenashev] can help with permissions Attack plan 2 : * Get [https://github.com/jenkinsci/docker/pull/719] integrated * Upstream Java 11 support patches from [https://github.com/jenkinsci/remoting/pull/292] to the master scripts * Enable the new build mode on trusted-ci which can deploy images Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You
[JIRA] (JENKINS-51985) Create official jenkins/jenkins Docker images for Java 10 and 11 versions
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51985 Create official jenkins/jenkins Docker images for Java 10 and 11 versions Change By: Oleg Nenashev In [https://github.com/jenkinsci/docker/pull/690/commits/ffe36e0f9d6d94b1c10e2fc71751e5fbba0a26f4] and [https://github.com/jenkinsci/docker/pull/690] only base images have been adjusted to Java 10 and 11 (in java10 and java11 branches). We need to upstream these changes and integrate into the common weekly release flow.It would be also great to update Alpine and Slim images as well so that they can be shipped within the common release flow (if possible & feasible).Attack plan 1: additional Dockerfile in the repo * Take [https://github.com/jenkinsci/docker/blob/java11/Dockerfile] and put it to master (Dockerfile-jdk11) * Update scripts to also build and publish Java 11 * Risk: The build runs on Trusted CI, may need help from [~olblak] . May have issues with debugging * Possible resolution: parameterize scripts and deploy to jenkins4eval (for local debugging). [~oleg_nenashev] can help with permissionsAttack plan 2: via multi-platform * Get [https://github.com/jenkinsci/docker/pull/719] integrated * Upstream Java 11 support patches from [https://github.com/jenkinsci/remoting/pull/292] to the master scripts * Enable the new build mode on trusted-ci which can deploy images Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52280) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52280 Create official Java 11 Docker Packaging for BlueOcean Change By: Oleg Nenashev During the hackathon we have created [ https://github.com/jenkinsci/blueocean-plugin/blob/master/Dockerfile.jdk10 ] . Now it needs to be expanded to Java 11 and added to the common release flows Acceptance: * Promote [https://github.com/oleg-nenashev/jenkins-blueocean-experimental] to jenkinsci * Setup new DockerHub repo with Automatic build, e.g. jenkins/blueocean which is unused * Define naming strategy * Create Java 8 and Java 11 branches there, similar to the source repo * Update jenkins.io documentation to reflect the new repo: [https://jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker] It needs agreement with the BlueOcean team. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54555) 'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met
Title: Message Title
Alis Adrovic updated an issue
Jenkins / JENKINS-54555
'stage' directive with nested 'when' and 'options' directives executes the 'options' block even if the condition is not met
Change By:
Alis Adrovic
My(stripped out) Jenkinsfile looks like this:{{pipeline {}}{{ options {}}{{ gitlabBuilds(builds: ['prepare-build-environment', 'build'])}} {{ } }} {{ stages {}}{{ //stages for preparing the build environment and building }}{{ stage('Deploy'){}}{{ when {}}{{ anyOf {}}{{ branch 'dev'}}{{ branch 'release'}}{{ branch 'master'}} \ {{ }}} \ {{ }}}{{ options {}}{{ gitlabBuilds(builds: ['deploy'])}} \ {{ }}}{{ steps {}}{{ //my steps}} \ {{ }}}{{ post {}}{{ failure {}}{{ updateGitlabCommitStatus name: 'deploy', state: 'failed'}} \ {{ }}}{{ success {}}{{ updateGitlabCommitStatus name: 'deploy', state: 'success'}} \ {{ }}} \ {{ }}} \ {{ }}} \ {{ }}}{{ //more stuff}}{{}}}Since I'm using Multibranch Pipeline, I don't want 'Deploy' stage to happen on feature branches. But GitLab gets notified about 'deploy' stage in all cases, and even if the Jenkins job finishes successfully, pipeline status on GitLab is still "running":!2018-11-09 11_14_34-Pipelines.png! This makes "Merge when pipeline succeeds" useless, since it will never succeed.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54539) REST API to generate API tokens
Title: Message Title Antonio Muñiz updated JENKINS-54539 Jenkins / JENKINS-54539 REST API to generate API tokens Change By: Antonio Muñiz Status: In Review Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54556) The authorizationMatrix plugin doesent work with pipeline
Title: Message Title Sergey Bralgin created an issue Jenkins / JENKINS-54556 The authorizationMatrix plugin doesent work with pipeline Issue Type: Bug Assignee: Daniel Beck Attachments: Jenkinsfile Components: matrix-auth-plugin Created: 2018-11-09 14:04 Labels: plugin pipeline matrix-auth Priority: Minor Reporter: Sergey Bralgin I'm trying to configure Project-based Matrix Authorization Strategy throw multibranch pipeline. What i want to do - have different Project-based Matrix Authorization Strategy for each branch But if I add some user to Matrix Authorization Strategy as "read" on multibranch projects's level then the user will have "read" permissions for all of branches which include in multibranch project Job. I tried to set Matrix Authorization Strategy in Jenkinsfile for each branch but with different perrmissions for user. According changes https://wiki.jenkins.io/display/JENKINS/Matrix+Authorization+Strategy+Plugin: Add support for use in the properties() pipeline step. For usage example, see the snippet generator. (JENKINS-34616) But when i added properties() to my Jenkinsfile I got the error: WorkflowScript: 4: The 'properties' section has been renamed as of version 0.8. Use 'options' instead Then I changed properties() to "options" and got the errror again: java.lang.NoSuchMethodError: No such DSL method 'permissions' I attached Jenkinsfile - just uncomment needed
[JIRA] (JENKINS-39960) EC2 Plugin: Invalid groupID parameter when provisioning
Title: Message Title Dominik Bartholdi commented on JENKINS-39960 Re: EC2 Plugin: Invalid groupID parameter when provisioning sorry, forget it - I just found the missing piece - I found the field for the "Subnet ID" in the advanced settings Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Uma Shankar commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace Jesse Glick I cleared up everything from my workspace (master/slave), I still see the same issue with folder name on slave workspace (Still adding %2F. I created a new branch to test, so there were no history about this branch) Also, Jenkins master workspace has a file called `workspace.txt`, but slave doesn't have it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Uma Shankar edited a comment on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace [~jglick] I cleared up everything from my workspace (master/slave), I still see the same issue with folder name on slave workspace (Still adding %2F. I created a new branch to test, so there were no history about this branch) !image-2018-11-09-14-25-37-159.png|width=780,height=75!Also, Jenkins master workspace has a file called `workspace.txt`, but slave doesn't have it. Build on master looks good!image-2018-11-09-14-40-45-316.png|width=519,height=55! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Sven Schoenung commented on JENKINS-51143 Re: List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs As chance would have it I actually looked at this issue and the pull request just yesterday. The actual code fix is pretty straightforward. It's the minimum required Jenkins version that makes me hesitate. When I fixed the broken build I made sure not to increase the minimum required Jenkins version by too much. It's 1.625.3 right now and it seems fixing this will increase that number to 2.62. There's quite a few versions in between those two where people are using this plugin. Right now it seems like they are not updating the plugin anyway, but it might to too early to tell. There's always the option of fixing this through reflection without increasing the required Jenkins version (as was done here), but that's complicated, ugly, hard to test, etc... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54552) code analyzer tool exe to analyze the code and generate the excel file
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-54552 code analyzer tool exe to analyze the code and generate the excel file Change By: Michael Fowler Component/s: core Component/s: windows-exe-runner-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54552) code analyzer tool exe to analyze the code and generate the excel file
Title: Message Title Michael Fowler commented on JENKINS-54552 Re: code analyzer tool exe to analyze the code and generate the excel file hi praveen kumar You can ask questions about using Jenkins in the user forum. Jira is for reporting bugs. https://groups.google.com/forum/#!forum/jenkinsci-users Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54552) code analyzer tool exe to analyze the code and generate the excel file
Title: Message Title Michael Fowler resolved as Not A Defect Jenkins / JENKINS-54552 code analyzer tool exe to analyze the code and generate the excel file Change By: Michael Fowler Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43632) Not Possible to Set Blank Environment Variables?
Title: Message Title Todd Lindstrom commented on JENKINS-43632 Re: Not Possible to Set Blank Environment Variables? Vote for this issue is disabled for me. Please count this as my +1 - Blue ocean USER INTERFACE should not drive the requirements for how a program displays its data - it should respond to the needs of the users and accommodate the use cases that customers need. Clearly if the job description allows HTML for normal Jenkins use - then BO should accommodate this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32740) Slaves which never connect due to ECS resource constraints never get removed
Title: Message Title Philipp Garbe closed an issue as Done No feedback since months Jenkins / JENKINS-32740 Slaves which never connect due to ECS resource constraints never get removed Change By: Philipp Garbe Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31197) New jobs are not creating a new container
Title: Message Title Philipp Garbe closed an issue as Done No feedback since months Jenkins / JENKINS-31197 New jobs are not creating a new container Change By: Philipp Garbe Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51775) New ECS task definition created for each instance of an Agent requested
Title: Message Title Philipp Garbe updated JENKINS-51775 Jenkins / JENKINS-51775 New ECS task definition created for each instance of an Agent requested Change By: Philipp Garbe Status: Open Fixed but Unreleased Resolution: Fixed Released As: v1.17 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52032) Replace slave occurrence by agent in the Amazon ECS plugin
Title: Message Title Philipp Garbe assigned an issue to Philipp Garbe Jenkins / JENKINS-52032 Replace slave occurrence by agent in the Amazon ECS plugin Change By: Philipp Garbe Assignee: Jan Roehrich Philipp Garbe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51775) New ECS task definition created for each instance of an Agent requested
Title: Message Title Philipp Garbe updated JENKINS-51775 Jenkins / JENKINS-51775 New ECS task definition created for each instance of an Agent requested Change By: Philipp Garbe Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48694) Notifies successful build when still in progress
Title: Message Title Rasmus Pedersen commented on JENKINS-48694 Re: Notifies successful build when still in progress I tried version 2.2.14 and it doesn't cover all cases, but probably most. If there's no checkout scm step, like in stage 1 above, it is still reporting a successful build after completing stage 1 and then failing the build after stage 2. If checkout scm is added as the first step in stage 1 the status is now reported correctly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51775) New ECS task definition created for each instance of an Agent requested
Title: Message Title Philipp Garbe closed an issue as Fixed Jenkins / JENKINS-51775 New ECS task definition created for each instance of an Agent requested Change By: Philipp Garbe Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53644) Is it possible to configure the color of the job (success or not) depending on the error number of one parser
Title: Message Title iostrym commented on JENKINS-53644 Re: Is it possible to configure the color of the job (success or not) depending on the error number of one parser done, thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54550) Add usage of new Error severity in Quality Gate Thresholds
Title: Message Title iostrym created an issue Jenkins / JENKINS-54550 Add usage of new Error severity in Quality Gate Thresholds Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-11-09 09:03 Environment: Jenkins 2.121.2 + warning plug-in version 5.X (beta) Priority: Critical Reporter: iostrym I have a problem because I can only set threshold for : Severity High / normal / low And it seems that it correspond only to WARNING_HIGH, WARNING_NORMAL, WARNING_LOW severity. And I don't succeed to make my job failing when I have at least one ERROR. Is it normal ? My parser only generates warning with severity : "Low" or "Error". Is it possible to use Quality Gate Thresholds on "Error" severity ? Because if I'm correct, Severity High is WARNING_HIGH and not Error. Am I correct ? Add Comment
[JIRA] (JENKINS-14463) email ext plugin : full console log mail
Title: Message Title Vijayakumar Shanmugam commented on JENKINS-14463 Re: email ext plugin : full console log mail santhosh s Thanks a lot. That worked. I was struggling to get the correct syntax to use in my DSL pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45833) Can not spin up JNLP agent on Amazon ECS
Title: Message Title Philipp Garbe assigned an issue to Philipp Garbe Jenkins / JENKINS-45833 Can not spin up JNLP agent on Amazon ECS Change By: Philipp Garbe Assignee: Jan Roehrich Philipp Garbe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37293) ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks
Title: Message Title Philipp Garbe closed an issue as Done No feedback since months Jenkins / JENKINS-37293 ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks Change By: Philipp Garbe Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Philipp Garbe updated JENKINS-54428 Jenkins / JENKINS-54428 ECS plugin fails if task definition ARN is used Change By: Philipp Garbe Status: Open Fixed but Unreleased Resolution: Fixed Released As: v1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52032) Replace slave occurrence by agent in the Amazon ECS plugin
Title: Message Title Philipp Garbe updated JENKINS-52032 Jenkins / JENKINS-52032 Replace slave occurrence by agent in the Amazon ECS plugin Change By: Philipp Garbe Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53405) Support of "customWorkspace" is missing for kubernets-plugin
Title: Message Title Bahram Parsapour commented on JENKINS-53405 Re: Support of "customWorkspace" is missing for kubernets-plugin Winfried Wasser did you had a chance to test the latest version of the plugin? If so, does it solve your problems described here? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54108) "JIRA: Progress issues by workflow action" fails when job is located within a folder
Title: Message Title Anna Tyshkevich commented on JENKINS-54108 Re: "JIRA: Progress issues by workflow action" fails when job is located within a folder I have same problem. My Jenkins (ver. 2.138.3) env vars: HOME=/var/lib/jenkins, but JENKINS_HOME=/home/jenkins and installed jira-plugin (ver. 3.0.5). When i run build with step "JIRA: Progress issues by workflow action", then i get error: [JIRA] Failed to connect to JIRA and log: ноя 09, 2018 2:17:10 PM WARNING hudson.plugins.jira.JiraSite progressMatchingIssues JIRA session could not be established When i validate settings Jira sites, then i get success result and log: ноя 09, 2018 2:16:51 PM FINE hudson.plugins.jira.JiraSite creating JIRA Session: https://jira.mydomen.my/ I think plugin can not get credentials in runtime build for this configuration server. I also have other Jenkins server (ver. 2.149) with env var HOME equals JENKINS_HOME=/var/lib/jenkins and Jira-plugin (ver 3.0.3) and for this configuration plugin is working successful. Add Comment
[JIRA] (JENKINS-54108) "JIRA: Progress issues by workflow action" fails when job is located within a folder
Title: Message Title
Anna Tyshkevich edited a comment on JENKINS-54108
Re: "JIRA: Progress issues by workflow action" fails when job is located within a folder
I have same problem. My Jenkins (ver. 2.138.3 , LTS ) env vars: HOME=/var/lib/jenkins, but JENKINS_HOME=/home/jenkins and installed jira-plugin (ver. 3.0.5) and folders plugin (ver . 6.6). When i run build with step "JIRA: Progress issues by workflow action", then i get error:{code:java}[JIRA] Failed to connect to JIRA{code}and log:{code:java}ноя 09, 2018 2:17:10 PM WARNING hudson.plugins.jira.JiraSite progressMatchingIssues{code}{code:java}JIRA session could not be established{code}When i validate settings Jira sites, then i get success result and log: {code:java}ноя 09, 2018 2:16:51 PM FINE hudson.plugins.jira.JiraSite{code}{code:java}creating JIRA Session: https://jira.mydomen.my/{code}I think plugin can not get credentials in runtime build for this configuration server.I also have other Jenkins server (ver. 2.149 , weekly release ) with env var HOME equals JENKINS_HOME=/var/lib/jenkins and Jira-plugin (ver 3.0.3) and folder plugin (ver. 6.5.1) and for this configuration plugin is working successful.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39960) EC2 Plugin: Invalid groupID parameter when provisioning
Title: Message Title Dominik Bartholdi commented on JENKINS-39960 Re: EC2 Plugin: Invalid groupID parameter when provisioning Rob Birdwell Carlos Rodríguez López can you please explain exactly what you did (maybe with a screenshot)? I have the exact same problem, but I was not able to solve it so far Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50633) JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Title: Message Title Robin Smith commented on JENKINS-50633 Re: JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting Thanks Jesse Glick. It would be great to have that in the docs too - I suppose that will happen after the PR is merged. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51979) subversion checkout fails with SAXException
Title: Message Title Shannon Kerr commented on JENKINS-51979 Re: subversion checkout fails with SAXException We just encountered this. Jenkins via docker: 2.138.1 Subversion plugin: 2.11.1 svn: direct No externals No different credentials So far, just one build. I recently added the sleep per JENKINS-34313 to avoid the changelog11.xml parsing failure as we were hitting that more and more often. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54559) Build result regression since pipeline-maven 3.5.15 for failing tests (UNSTABLE)
Title: Message Title
Falko Modler updated an issue
Jenkins / JENKINS-54559
Build result regression since pipeline-maven 3.5.15 for failing tests (UNSTABLE)
Change By:
Falko Modler
The removal of [this block |https://github.com/jenkinsci/pipeline-maven-plugin/commit/cfe37eeb66c07fc81c286f78499acfdef7aa05ec#diff-2b37dae22162f359b4bc1b4f1c45d897L295] block is causing a (temporary) inconsistent overall build result because {{archiver.perform()}} used to set {{currentBuild.result}} in 3.5.14 (see also [here|https://github.com/jenkinsci/junit-plugin/blob/master/src/main/java/hudson/tasks/junit/JUnitResultArchiver.java#L157]) but now (due to the removal) the result is not set anymore.This now leads to other plugins picking up the wrong result (SUCCESS) when being used in {{post}} pipeline blocks. We, for instance, explicitely call {{step([$class: 'StashNotifier'])}} in {{cleanup}} which before 3.5.15 sent the correct status to BitBucket PRs but now with 3.5.15 the PRs always receive SUCCESS/OK even though there are test failures. And of course if you evaluate {{currentBuild.result}} directly (like we also do to send messages via Rocket.Chat), you also see the wrong result.The final pipeline build result _is correct_ in these cases (UNSTABLE) but you just cannot retrieve it anymore from within the pipeline while it is still running.I consider this a severe breaking change.What puzzles me is that the very same commit that removed the invokation of {{archiver.perform()}} also remove removed this note (further down):{quote}// TODO: Once JENKINS-43995 lands, update this to set the step status instead of the entire build.{quote}Judging from it's status, JENKINS-43995 has *not* "landed" yet!
Add Comment
[JIRA] (JENKINS-54558) Debian package update failed because setup step tries to restart Jenkins service
Title: Message Title dma_k created an issue Jenkins / JENKINS-54558 Debian package update failed because setup step tries to restart Jenkins service Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-11-09 16:03 Environment: Debain 9.5 (stretch) Priority: Minor Reporter: dma_k On Debian stretch I had Jenkins configured to be run under Tomcat 8 server, hence in /etc/default/jenkins I have specified that: RUN_STANDALONE=false During package update (e.g. via apt-get update) the following error happened: Setting up jenkins (2.138.2) ... Job for jenkins.service failed because the control process exited with error code. See "systemctl status jenkins.service" and "journalctl -xe" for details. invoke-rc.d: initscript jenkins, action "start" failed. ● jenkins.service - LSB: Start Jenkins at boot time Loaded: loaded (/etc/init.d/jenkins; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-11-05 00:31:47 CET; 20ms ago Docs: man:systemd-sysv-generator(8) Process: 29959 ExecStart=/etc/init.d/jenkins start (code=exited, status=1/FAILURE) Nov 05 00:31:47 debian systemd[1]: Starting LSB: Start Jenkins at boot time... Nov 05 00:31:47 debian jenkins[29959]: Not configured to run standalone Nov 05 00:31:47 debian systemd[1]: jenkins.service:
[JIRA] (JENKINS-54556) The authorizationMatrix plugin doesent work with pipeline
Title: Message Title Daniel Beck commented on JENKINS-54556 Re: The authorizationMatrix plugin doesent work with pipeline Andrew Bayer I think this is declarative pipeline weirdness, PTAL. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
