[JIRA] (JENKINS-54389) Containers with ENTRYPOINT is not started correctly
Title: Message Title Brian Redbeard commented on JENKINS-54389 Re: Containers with ENTRYPOINT is not started correctly Similarly, I'm hitting this with builds of Hugo. The container has a single binary in it: hugo. I'm watching both the race condition called out above occurring as well as the incorrect behavior of attempting to override the valid ENTRYPOINT defined in the file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195143.1541061335000.4698.1558155840171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57529) Unable to identify builds run as SYSTEM user
Title: Message Title ikedam assigned an issue to Unassigned This is an issue of Jenkins core as this warning is shown by Jenkins core. Jenkins / JENKINS-57529 Unable to identify builds run as SYSTEM user Change By: ikedam Component/s: core Component/s: authorize-project-plugin Assignee: ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199436.1558108275000.4696.1558140120274%40Atlassian.JIRA. For more
[JIRA] (JENKINS-57536) Pending build status now shown as disabled (MultiJob)
Title: Message Title Stefan Drissen created an issue Jenkins / JENKINS-57536 Pending build status now shown as disabled (MultiJob) Issue Type: Bug Assignee: Unassigned Components: core, multijob-plugin Created: 2019-05-17 22:47 Environment: Windows Server 2012R2 Jenkins 2.177 Priority: Minor Reporter: Stefan Drissen The change to distinguish between new / aborted / disabled jobs by ball color https://github.com/jenkinsci/jenkins/pull/3997 - is not working for the MultiJob plug-in. I think, it has made the MultiJob view worse since it is (now) showing all pending jobs as disabled. Add Comment
[JIRA] (JENKINS-55255) FlowInterruptedException always marks stages as Aborted despite Result
Title: Message Title Stuart Rowe updated JENKINS-55255 Jenkins / JENKINS-55255 FlowInterruptedException always marks stages as Aborted despite Result Change By: Stuart Rowe Status: Fixed but Unreleased Closed Released As: https://github.com/jenkinsci/pipeline-graph-analysis-plugin/releases/tag/pipeline-graph-analysis-1.10 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196338.154521133.4690.1558130760119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Martin Weber commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline Concerning the workaroung, see JENKINS-29142: look for MSVC 15.x toolchain. Feel free to re-open and submit a pull request. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.4689.1558129560489%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title Chris N. commented on JENKINS-44860 Re: Disable masking of usernames +1 to fix this. very painful with configuration where the credential user is also the jenkins user (username is in home dir!!!). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182924.1497380811000.4675.1558128780853%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Damian Szczepanik resolved as Fixed Jenkins / JENKINS-57497 Cucumber Report displays incorrect total duration if total duration is more than 24 hours Change By: Damian Szczepanik 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.4673.1558127700214%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Damian Szczepanik commented on JENKINS-57497 Re: Cucumber Report displays incorrect total duration if total duration is more than 24 hours I haven't thought that tests could take more than hour or two. Will be fixed with next release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.4671.1558127700186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43587) Pipeline fails to resume after master restart/plugin upgrade
Title: Message Title Alex Taylor commented on JENKINS-43587 Re: Pipeline fails to resume after master restart/plugin upgrade Mircea-Andrei Albu I think this may be a different issue since this is a much later version you are updating Jenkins to. I would open a new JIRA with the Jenkins logs included since there may be an error there about why the build did not resume Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180909.1492112497000.4647.1558127400537%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Paul P commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id I can confirm 1.43 & 2.177 work fine with Spot instances Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.4630.1558125420595%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57535) Sonar Issue
Title: Message Title vasanth dhandayuthapani updated an issue Jenkins / JENKINS-57535 Sonar Issue Change By: vasanth dhandayuthapani Attachment: pom.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199443.1558123768000.4627.1558124100117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57535) Sonar Issue
Title: Message Title vasanth dhandayuthapani assigned an issue to vasanth dhandayuthapani Jenkins / JENKINS-57535 Sonar Issue Change By: vasanth dhandayuthapani Assignee: Sonar Team vasanth dhandayuthapani Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199443.1558123768000.4623.1558124040145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57535) Sonar Issue
Title: Message Title vasanth dhandayuthapani assigned an issue to Sonar Team Jenkins / JENKINS-57535 Sonar Issue Change By: vasanth dhandayuthapani Assignee: vasanth dhandayuthapani Sonar 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199443.1558123768000.4625.1558124040172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57535) Sonar Issue
Title: Message Title
vasanth dhandayuthapani updated an issue
Jenkins / JENKINS-57535
Sonar Issue
Change By:
vasanth dhandayuthapani
Attachment:
pom.xml
Hi I am getting below issue from Jenkins. Can you please advise ?Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on project kbsql-extract-estate: For artifact \{null:null:null:jar}: The groupId cannot be empty. -> [Help 1] {{Jenkins version :2.138. 4Java 4}}{{Java version: 1.8}} {{Pom file entry:}} {{ }}{{ org.sonarsource.scanner.maven }}{{ sonar-maven-plugin }}{{ 3.2 }}{{ }} {{}} I have attached pom file as well. Thanks in Advance.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199443.1558123768000.4621.1558123980162%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57535) Sonar Issue
Title: Message Title vasanth dhandayuthapani updated an issue Jenkins / JENKINS-57535 Sonar Issue Change By: vasanth dhandayuthapani Attachment: pom.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199443.1558123768000.4619.1558123920284%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57535) Sonar Issue
Title: Message Title
vasanth dhandayuthapani created an issue
Jenkins / JENKINS-57535
Sonar Issue
Issue Type:
Task
Assignee:
Sonar Team
Components:
sonar
Created:
2019-05-17 20:09
Environment:
DIT enviorment
Priority:
Minor
Reporter:
vasanth dhandayuthapani
Hi I am getting below issue from Jenkins. Can you please advise ? Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on project kbsql-extract-estate: For artifact {null:null:null:jar}: The groupId cannot be empty. -> [Help 1] Jenkins version :2.138.4Java version: 1.8 Pom file entry: org.sonarsource.scanner.mavensonar-maven-plugin3.2{{}}
Add Comment
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Audun Halland commented on JENKINS-57371 Re: error message when building PR Regular github.com, our jenkins is set up to scan the github organization. The repo in question is a private repository. According to the Organization configuration page, these settings are active: Behaviours: Discover branches, Strategy: Exclude branches that are also filed as PRs Discover pull requests from origin, Strategy: Merging the pull request with the current target branch revision Checkout over SSH, Credentials: Project recognizers: Pipeline Jenkinsfile, Script Path: Jenkinsfile Build strategies: Ignore committer strategy Don't trigger builds for pushes by certain Git commit author (comma-delimited list of author emails): [ci email address] Allow builds when a changeset contains non-ignored author(s): ENABLED I might also add that when PR-47 was initially created, its branch was not up to date with master, and master got merged into it later, after its jenkins job was created. The latest commit of that PR currently is merge commit 5729, referencing child commits d75b (change set) + 76ff (master). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57534) P4_CHANGELIST entry in map returned by checkout step is sometimes wrong
Title: Message Title Stuart Rowe created an issue Jenkins / JENKINS-57534 P4_CHANGELIST entry in map returned by checkout step is sometimes wrong Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-05-17 18:44 Environment: p4-plugin 1.9.7 Priority: Minor Reporter: Stuart Rowe The value of P4_CHANGELIST always reflects the requested sync changelist. The actual synced changelist value is less than or equal to the requested sync changelist, depending on the client view. The value of P4_CHANGELIST should always reflect the actual synced changelist value. Add Comment
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman edited a comment on JENKINS-57371 Re: error message when building PR [~audunhalland]The fact that build now is broken is extremely odd. Is it broken in the same way (same commits and message)? The place where "Build Now" calculates the HEAD of the base branch should be ignoring any filter.Update: I've tested this with the Ignore Committer strategy and it works as expected: When I push a commit to master from a committer that should be ignored, the master branch doesn't build, but PR correctly detects the change and gets the most current commit from master which is the valid parent of the merge commit. What other plugins do you have configured? Also, out of curiosity are you using GitHub or GitHub Enterprise? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.4607.1558116960167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman edited a comment on JENKINS-57371 Re: error message when building PR [~audunhalland]The fact that build now is broken is extremely odd. Is it broken in the same way (same commits and message)? The place where "Build Now" calculates the HEAD of the base branch should be ignoring any filter. Update: I've tested this with the Ignore Committer strategy and it works as expected: When I push a commit to master from a committer that should be ignored, the master branch doesn't build, but PR correctly detects the change and gets the most current commit from master which is the valid parent of the merge commit. What other plugins do you have configured? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.4603.1558116840138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57533) Update project description on jenkins.io
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-57533 Update project description on jenkins.io Issue Type: Task Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-05-17 18:10 Priority: Minor Reporter: Long Nguyen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199440.1558116648000.4601.1558116660626%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57422) Verify and cleanup Docker performance test configuration
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57422 Verify and cleanup Docker performance test configuration Change By: Oleg Nenashev Sprint: GSoC 2019. Community Bonding Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199234.1557738945000.4600.1558116660612%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57532) Setup K8s demo from existing Docker Compose
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57532 Setup K8s demo from existing Docker Compose Change By: Oleg Nenashev Sprint: GSoC 2019. Community Bonding Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199439.1558116161000.4597.1558116660569%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57531) Initial design diagrams
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57531 Initial design diagrams Change By: Oleg Nenashev Sprint: GSoC 2019. Coding Phase 1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199438.1558115587000.4591.1558116600225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57531) Initial design diagrams
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57531 Initial design diagrams Change By: Oleg Nenashev Sprint: GSoC 2019. Coding Phase 1 Community Bonding Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199438.1558115587000.4594.1558116600260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57422) Verify and cleanup Docker performance test configuration
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57422 Verify and cleanup Docker performance test configuration Change By: Oleg Nenashev Labels: gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199234.1557738945000.4587.1558116540113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57421) Profile Role Strategy Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57421 Profile Role Strategy Plugin Change By: Oleg Nenashev Labels: gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199233.1557738834000.4585.1558116480211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57415) [GSoC] Role Strategy Plugin Performance Improvements: Community bonding period
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57415 [GSoC] Role Strategy Plugin Performance Improvements: Community bonding period Change By: Oleg Nenashev Epic Name: GSoC 2019: Role Strategy Plugin Performance Improvements GSoC2019 - Community RoleStrategy- Bonding Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199221.1557584264000.4583.1558116480189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57530) GSoC 2019 - Remoting over Kafka with Kubernetes features Community Bonding Period
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57530 GSoC 2019 - Remoting over Kafka with Kubernetes features Community Bonding Period Change By: Oleg Nenashev Summary: GSoC 2019 - Remoting over Kafka with Kubernetes features Community Bonding Period Epic Name: GSoC2019- Remoting over - Kafka with Kubernetes features Community -K8s- Bonding Period Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199437.1558113146000.4577.1558116420291%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57532) Setup K8s demo from existing Docker Compose
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57532 Setup K8s demo from existing Docker Compose Change By: Oleg Nenashev Labels: gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199439.1558116161000.4580.1558116420351%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57531) Initial design diagrams
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57531 Initial design diagrams Change By: Oleg Nenashev Labels: gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199438.1558115587000.4574.1558116360155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57532) Setup K8s demo from existing Docker Compose
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-57532 Setup K8s demo from existing Docker Compose Issue Type: Task Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-05-17 18:02 Priority: Minor Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199439.1558116161000.4571.1558116180179%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57531) Initial design diagrams
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-57531 Initial design diagrams Issue Type: Task Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-05-17 17:53 Priority: Minor Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199438.1558115587000.4566.1558115640168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54059) GSoC 2019 prepwork (October-December)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54059 GSoC 2019 prepwork (October-December) Change By: Oleg Nenashev Labels: gsoc gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194676.1539398554000.4558.1558115400197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57437) Update jenkins.io page for the Role Strategy GSoC 2019 project
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57437 Update jenkins.io page for the Role Strategy GSoC 2019 project Change By: Oleg Nenashev Sprint: GSoC 2019. Community Bonding Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199250.1557766913000.4554.1558115280105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57437) Update jenkins.io page for the Role Strategy GSoC 2019 project
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57437 Update jenkins.io page for the Role Strategy GSoC 2019 project Change By: Oleg Nenashev Labels: gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199250.1557766913000.4545.1558115160135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Mark Waite commented on JENKINS-21248 Re: Add shallow update init for submodule My acceptance test is strong evidence that there is not an issue with version parsing . Check the jenkins system configuration of the git tool and the agent configuration of the git tool Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152811.138908257.4491.1558113720464%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57530) Remoting over Kafka with Kubernetes features Community Bonding Period
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-57530 Remoting over Kafka with Kubernetes features Community Bonding Period Issue Type: Epic Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-05-17 17:12 Labels: gsoc-2019 plugin Priority: Minor Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-13916) Multiline text parameter displays as single line
Title: Message Title Peter MacNeil commented on JENKINS-13916 Re: Multiline text parameter displays as single line That's interesting Annie and different from what I saw. My experience with 2.150.2 was all with manual promotions. Only the first promotion has the new lines intact. In all subsequent promotions (Re-execute promotion) the multi-line field is displayed as a single line field and new lines have been lost. All the best, Pete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.144384.1337950164000.4472.1558112940515%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51474) CloudAPI implementation for Remoting Kafka
Title: Message Title Pham Vu Tuan started work on JENKINS-51474 Change By: Pham Vu Tuan 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190834.1526977991000.4469.1558112880132%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55344) Allow to run Groovy scripts in JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55344 Allow to run Groovy scripts in JCasC Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196439.1545908966000.4464.1558112820336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54780) Support JCASC in Publish Over FTP plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54780 Support JCASC in Publish Over FTP plugin Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195588.1542914177000.4466.1558112820364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57515) AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so
Title: Message Title Jeff Thompson commented on JENKINS-57515 Re: AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so Similar to JENKINS-54196 and various others. May require an update to the JNA library to get the correct library to load on AIX. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199418.1558076672000.4462.1558112100128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57515) AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so
Title: Message Title Jeff Thompson assigned an issue to Unassigned Jenkins / JENKINS-57515 AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so Change By: Jeff Thompson Component/s: core Component/s: remoting Labels: remoting slave Assignee: Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199418.1558076672000.4460.1558112040098%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Stefan Verhoeff commented on JENKINS-21248 Re: Add shallow update init for submodule Thanks for the details Mark Waite. I'm happy to help with testing this useful feature. How can I check what version of Git is used by the checkout() command? I assume it would be the same I get when I run git --version just above it. Is there a different Git binary used? Is the checkout actually happening on the Master and the sh() command on the agent? Is JGit involved? I'm confused here. As per your acceptance test, does this point at an issue with the version parsing or not? I've checked the code around where the warning Git client older than 1.8.4 doesn't support shallow submodule updates. This flag is ignored. is raised, the shallow clone arguments are never actually added to the Git command because of the failed version check, so I'm not getting errors from Git on 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152811.138908257.4434.1558111020528%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman commented on JENKINS-57371 Re: error message when building PR Audun Halland The fact that build now is broken is extremely odd. Is it broken in the same way (same commits and message)? The place where "Build Now" calculates the HEAD of the base branch should be ignoring any filter. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.4430.1558110780253%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen edited a comment on JENKINS-57513 Re: Split the large databound constructors into databound setters [~jvz] I agree with you but for JCasC we only really care about the lovely data binding ;)I would like to point out this lovely PR which could solve all our data binding problem and jelly problems at the same time: https://github.com/stapler/stapler/pull/147 https://github.com/jenkinsci/jenkins/pull/3669 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199415.1558053245000.4428.1558109460150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Matt Sicker commented on JENKINS-57513 Re: Split the large databound constructors into databound setters I'd love to get that merged, though my Stapler street cred hasn't been enough yet to gain committership yet. I hope to change that over the next couple months, though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199415.1558053245000.4425.1558109220148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen commented on JENKINS-57513 Re: Split the large databound constructors into databound setters Matt Sicker I agree with you but for JCasC we only really care about the lovely data binding I would like to point out this lovely PR which could solve all our data binding problem and jelly problems at the same time: https://github.com/stapler/stapler/pull/147 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199415.1558053245000.4422.1558109040282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title Rishi Thakkar commented on JENKINS-39464 Re: Pipeline with parallel and no stages does not get visualised correctly Why does the resolution to this issue say "Fixed" but the issue itself is still "In Porgress"? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176008.1478136419000.4419.1558108800761%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57522) Export for JCasC is empty
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57522 Export for JCasC is empty Change By: Oleg Nenashev Labels: jcac Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199427.1558094828000.4383.1558108380581%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57523) Export for JCasC is empty
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57523 Export for JCasC is empty Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199428.155809487.4389.1558108380641%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57522) Export for JCasC is empty
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57522 Export for JCasC is empty Change By: Oleg Nenashev Labels: jcac jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199427.1558094828000.4386.1558108380612%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57521) Export for JCasC is empty
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57521 Export for JCasC is empty Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199426.1558094741000.4380.1558108380539%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57529) Unable to identify builds run as SYSTEM user
Title: Message Title Jeff Fairchild created an issue Jenkins / JENKINS-57529 Unable to identify builds run as SYSTEM user Issue Type: Bug Assignee: ikedam Attachments: image-2019-05-17-11-48-24-356.png, image-2019-05-17-11-49-15-611.png, image-2019-05-17-11-50-21-011.png Components: authorize-project-plugin Created: 2019-05-17 15:51 Environment: amazon linux, Jenkins ver. 2.172 Priority: Minor Reporter: Jeff Fairchild https://jenkins.io/doc/book/system-administration/security/build-authorization/ All builds are set to run as the User who triggered the build. but the warning never goes away The general build authorization properties are: Expected behavior: Show the builds running as SYSTEM. Allow admin user to purge those builds and respect the Per-project configuration. Add Comment
[JIRA] (JENKINS-57520) Declaring Tools installation via JCasC doesn't work
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57520 Declaring Tools installation via JCasC doesn't work Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199425.1558094032000.4377.1558108320420%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57524) JCasC export contains only one record
Title: Message Title Oleg Nenashev commented on JENKINS-57524 Re: JCasC export contains only one record Pavel Janoušek please use "jcasc-compatibility" so that the tickets properly appear on the JCasC Compatibility Dashboard Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199429.1558095004000.4374.1558108320378%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57525) JCasC export contains only one record
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57525 JCasC export contains only one record Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199430.1558095041000.4365.1558108260279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57524) JCasC export contains only one record
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57524 JCasC export contains only one record Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199429.1558095004000.4368.1558108260342%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Matt Sicker commented on JENKINS-57513 Re: Split the large databound constructors into databound setters I'd also like to consider some form of data bound builder class feature so we can avoid using poor Java patterns. Let me give you an example from the Log4j plugin system. The more typical use of DataBoundConstructor is equivalent to PluginFactory in Log4j: https://github.com/apache/logging-log4j2/blob/a6b1cbfc9d4257baaa6760e58426f0f4dfa99b0f/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/FailoverAppender.java#L183 In order to add new options over time, we used to deprecate a factory method, remove the annotation, and move it to the new factory method that contained default values for new parameters (as well as validation; you could return null instead of the plugin object to signify an error without throwing exceptions which was important in this part of our design, but I digress). This pattern was extremely brittle and is fairly similar to DataBoundConstructor. However, in order to follow Effective Java and other similar best practices, we'd still like to prefer that our objects are fully constructed and ready to use as soon as they're "created" whether that be via a constructor, a factory method, a builder class, or whatever. Having to call setters after creating the object leaves the object in intermediary states that typically don't have meaning, and this can cause runtime bugs in practice. This is getting a bit long, so let me wrap it up. My preferred approach would be what we did in Log4j with newer plugins via a builder class pattern: https://github.com/apache/logging-log4j2/blob/a6b1cbfc9d4257baaa6760e58426f0f4dfa99b0f/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/HttpAppender.java#L48 As you can see, due to syntactical features of Java, it is much easier to add and rename things in a builder class over time independently from the implementation details of the plugin class itself. I'd also note that there was a time in Log4j history before there was automatic type conversion in the annotated factory methods, so some old code still have all string parameters with manual type conversion. Also, why do I bring this up in EC2 and not structs or whatever the appropriate plugin is? Good question, but a new issue should likely be filed about it linked back here. Add Comment
[JIRA] (JENKINS-38658) File parameters are ignored
Title: Message Title Pieter Vogelaar commented on JENKINS-38658 Re: File parameters are ignored The build root token plugin is great. But it's really unfortunate that is doesn't support file parameters. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175050.1475492318000.4356.1558105320143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57460) Create a new design document from the original proposal.
Title: Message Title Prastik Gyawali resolved as Fixed Jenkins / JENKINS-57460 Create a new design document from the original proposal. Change By: Prastik Gyawali Status: Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199320.1557845087000.4347.1558104120135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated JENKINS-57528 To be landed in 2.178 Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4346.1558103340346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Labels: detached-plugin docker lts-candidate plugin-manager Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4341.1558102800262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev assigned an issue to Jesse Glick Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Assignee: Carlos Sanchez Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4344.1558102800302%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev It is a placeholder for [https://github.com/jenkinsci/docker/issues/698] and for [https://github.com/jenkinsci/jenkins/pull/4000] which addresses it in the core Using newer cores that have part of it moved to plugins and is now implied dependencies in other plugins is causing to have bad Jenkins installation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4339.1558102680318%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Summary: Jenkins in Docker does not install detached plugins which are implicit deps of other plugin when there is no UC 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4337.1558102680297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins which are implicit deps of other plugin when there is no UC data
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins which are implicit deps of other plugin when there is no UC data Issue Type: Bug Assignee: Carlos Sanchez Components: core, docker Created: 2019-05-17 14:17 Labels: plugin-manager docker detached-plugin Priority: Critical Reporter: Oleg Nenashev It is a placeholder for https://github.com/jenkinsci/docker/issues/698 and for https://github.com/jenkinsci/jenkins/pull/4000 which addresses it in the core Using newer cores that have part of it moved to plugins and is now implied dependencies in other plugins is causing to have bad Jenkins installation. Add Comment
[JIRA] (JENKINS-44316) Minimun dependency breaks docker lts build
Title: Message Title Oleg Nenashev resolved as Fixed I believe this was fixed by https://github.com/jenkinsci/docker/pull/495 Jenkins / JENKINS-44316 Minimun dependency breaks docker lts build Change By: Oleg Nenashev 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182121.1495029922000.4330.1558102380382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Mark Waite commented on JENKINS-21248 Re: Add shallow update init for submodule I've further investigated the JENKINS-21248 acceptance test failures in my environment. The initial submodule checkout succeeds on the following versions of command line git: 2.21 2.20 2.17 2.16 The initial submodule checkout fails on the following versions of command line git: 2.11 2.10 2.7 2.1 The stack trace in the checkout failure is: hudson.plugins.git.GitException: Command "git submodule update --reference /var/lib/git/mwaite/bugs/jenkins-bugs.git --depth=1 modules/JENKINS-46504.url" returned status code 1: stdout: stderr: Cloning into 'modules/JENKINS-46504.url'... warning: no common commits fatal: reference is not a tree: 0736ba35a0d8c05236e3b71584bc4e149aa5f10a Unable to checkout '0736ba35a0d8c05236e3b71584bc4e149aa5f10a' in submodule path 'modules/JENKINS-46504.url' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2298) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1910) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:81) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.lambda$execute$0(CliGitAPIImpl.java:1334) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253) at java.base/java.util.concurrent.ExecutorCompletionService.submit(ExecutorCompletionService.java:184) at org.jenkinsci.plugins.gitclient.cgit.GitCommandsExecutor.submitRemainingCommand(GitCommandsExecutor.java:75) at org.jenkinsci.plugins.gitclient.cgit.GitCommandsExecutor.invokeAll(GitCommandsExecutor.java:64) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to debian8-mwaite at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at jdk.internal.reflect.GeneratedMethodAccessor323.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy119.execute(Unknown Source) at
[JIRA] (JENKINS-57527) Unable to update Review due to bad Swarm URL
Title: Message Title
Paul Allen created an issue
Jenkins / JENKINS-57527
Unable to update Review due to bad Swarm URL
Issue Type:
Bug
Assignee:
Paul Allen
Components:
p4-plugin
Created:
2019-05-17 14:07
Priority:
Minor
Reporter:
Paul Allen
Hi Paul
[Pipeline] echo
Review: 12229, review type: SHELVED
[Pipeline] p4approve
... p4 property -nP4.Swarm.URL -l +
... p4 info +
... p4 login -s +
[Pipeline] echoException occurred
[Pipeline] echo
java.io.IOException: Unable to update Review.
[Pipeline] }
In the above, the Swarm URL was incorrect. It would be nice to see something more than “Exception occurred”.
script {
try {
echo "Review type: ${P4_REVIEW_TYPE}"
if ("${P4_REVIEW_TYPE}" == "SHELVED") {
echo "Review: ${P4_REVIEW}, review type: ${P4_REVIEW_TYPE}"
p4approve credential: "${env.p4_credential}",
review: '${P4_REVIEW}', status: 'COMMIT'
// Now set the review state back to 'needs review'
p4approve credential: "${env.p4_credential}",
review: '${P4_REVIEW}', status: 'REVIEW'
} else {
echo "Skipping Swarm approval as changelist already submitted"
}
} catch(Exception e) {
// Do something with the exception
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
Some changes have recently been released to address this issue for Blue Ocean . All of the changes require Jenkins 2.138.4 or newer. The main fixes are in Pipeline: API Plugin version 2.34 and Pipeline: Graph Analysis Plugin version 1.10, but in most cases you will need to change your Pipelines to be able to take advantage of the fixes:* If you are currently setting the build result to unstable using {{currentBuild.result = 'UNSTABLE'}}, you need to update to Pipeline: Basic Steps Plugin version 2.16 and start using the {{unstable}} step instead. See the changelog [here|https://wiki.jenkins.io/display/JENKINS/Pipeline+Basic+Steps+Plugin] for details. You may also be interested in the new {{warnError}} step.** In case you are curious why we can't make {{currentBuild.result = 'UNSTABLE'}} work as-is, the problem is that {{currentBuild}} is implemented as a [GlobalVariable|https://github.com/jenkinsci/workflow-cps-plugin/blob/e5e5f8054ff485685e0a5b36db65d549604ed956/src/main/java/org/jenkinsci/plugins/workflow/cps/GlobalVariable.java#L60] rather than a regular Pipeline Step, so there is no way to associate the setting of the build result with the current Pipeline stage, especially if a {{parallel}} step is being executed.* If the build result is being set to unstable by the {{junit}} step from the JUnit Plugin, then update the JUnit Plugin to version 1.28 and the visualization should be fixed.* If the build result is being set to unstable by the {{publishIssues}} or {{recordIssues}} steps in the Warnings NG Plugin, then keep an eye on [this in-progress PR|https://github.com/jenkinsci/warnings-ng-plugin/pull/58] which will update those steps to use a new API that will fix the visualization.* If the build result is being set to unstable by a Pipeline step in some other plugin, then file a new issue with the component set to that plugin, and ask the maintainer to start using the new [WarningAction API|https://github.com/jenkinsci/workflow-api-plugin/blob/c84dbab8cd35c90f70d84390dc711901fa73b7ad/src/main/java/org/jenkinsci/plugins/workflow/actions/WarningAction.java] from Pipeline: Basic Steps Plugin version 2.16 wherever they change the build result.In case of problems, the new behavior can be disabled by setting the system property {{org.jenkinsci.plugins.workflow.pipelinegraphanalysis.StatusAndTiming.DISABLE_WARNING_ACTION_LOOKUP}} to "true", or by setting the static variable of the same name to {{true}} via the Jenkins script console.Note that the Blue Ocean steps view will not yet display the status of individual steps using the new API correctly, keep an eye on [this in-progress PR|https://github.com/jenkinsci/blueocean-plugin/pull/1954] which will fix that issue. Once that PR is merged and released, I plan to mark this issue as closed. The visualization provided by Pipeline: Stage View Plugin has not been integrated with the new API added in Pipeline: API 2.34, and so that visualization is not currently affected by these changes.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Devin Nusbaum edited a comment on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should [~twalter] I just tested your code and it works ok for me in some basic test tests . Please open a new issue for your problem, assign it to me, add any additional information or context that might be useful and include a list of all plugins you have installed and their versions. Thanks![~reinholdfuereder] Can you please open a new issue, including a minimal Pipeline that reproduces the issue and assign the issue to me? Thanks!Also I was not explicit in my original post that these fixes do not currently affect Stage View at all, they only affect Blue Ocean, so I will update my post to make that clear. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.3838.1558100890536%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Devin Nusbaum commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Torsten Walter I just tested your code and it works ok for me in some basic test. Please open a new issue for your problem, assign it to me, add any additional information or context that might be useful and include a list of all plugins you have installed and their versions. Thanks! Reinhold Füreder Can you please open a new issue, including a minimal Pipeline that reproduces the issue and assign the issue to me? Thanks! Also I was not explicit in my original post that these fixes do not currently affect Stage View at all, they only affect Blue Ocean, so I will update my post to make that clear. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.3836.1558100890511%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57526) Blue Ocean Bitbucket : Failed to get "repositories" is very slow and loops for ever
Title: Message Title Shyamkumar Chintakindi created an issue Jenkins / JENKINS-57526 Blue Ocean Bitbucket : Failed to get "repositories" is very slow and loops for ever Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-05-17 13:28 Priority: Major Reporter: Shyamkumar Chintakindi 2019-05-17 12:22:02.999+ [id=1097] WARNING i.j.b.c.s.e.ExportInterceptor$1#getValue: Failed to get "repositories" from a io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer io.jenkins.blueocean.commons.ServiceException: Unknown Status Code at io.jenkins.blueocean.blueocean_bitbucket_pipeline.HttpResponse.getContent(HttpResponse.java:71) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.cloud.BitbucketCloudApi.getDefaultBranch(BitbucketCloudApi.java:249) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.model.BbRepo.toScmRepository(BbRepo.java:63) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer$BitbucketRepositories.(BitbucketRepositoryContainer.java:82) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer.getRepositories(BitbucketRepositoryContainer.java:41) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:72) Caused: java.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:74) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:196) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title
Mark Waite edited a comment on JENKINS-21248
Re: Add shallow update init for submodule
There could be a bug in the [version detection logic|https://github.com/jenkinsci/git-client-plugin/blob/63dd47319914cbe72948e18d83f62c62365ba6c7/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1269], but you should probably first check that the version of git being used by your job is the same as the version reported in the pipeline script {{sh}} step.I've not seen any other bug reports of broken version detection. There are [specific automated tests|https://github.com/jenkinsci/git-client-plugin/blob/88def8591098610255185f7d895f4474589bc9e2/src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java#L99] in the plugin to confirm that git version numbers in various formats are detected correctly. Those tests don't use 2.11.0 specifically, but they use 2.10.0 and other interesting values near it.If there is a bug in the detection logic, I'll need to update my [acceptance test|https://github.com/MarkEWaite/jenkins-bugs/blob/52c665176dac63a20b81238c38f25c849e877151/Jenkinsfile#L22] to exercise that bug. There seem to be some interesting cases in that [acceptance test|https://github.com/MarkEWaite/jenkins-bugs/blob/52c665176dac63a20b81238c38f25c849e877151/Jenkinsfile#L22] when running on command line git version 2.11.0, but the cases that I'm seeing are not related to version checking logic. In my case, the {{git submodule update}} fails with a warning that there are {{no common commits}}. The same message does not appear on at least some other command line git versions. I'll need to extend the acceptance test to execute with each of the versions of command line git in my test environment. That will then tell me if there are problems related to command line git version. Note that the issue I'm investigating shows that in my environment I'm able to perform the expected command line git operations. Thus, at least in my environment, the version check is working, since my investigation could not have started without passing that version check.
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-43587) Pipeline fails to resume after master restart/plugin upgrade
Title: Message Title Mircea-Andrei Albu commented on JENKINS-43587 Re: Pipeline fails to resume after master restart/plugin upgrade +1 Same behaviour also on Jenkins 2.164.2 Our master doesn't have any executors and after master restart all the agents are staying like this for a while without resuming: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180909.1492112497000.3540.1558098601418%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43587) Pipeline fails to resume after master restart/plugin upgrade
Title: Message Title Mircea-Andrei Albu updated an issue Jenkins / JENKINS-43587 Pipeline fails to resume after master restart/plugin upgrade Change By: Mircea-Andrei Albu Attachment: image-2019-05-17-16-09-05-599.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180909.1492112497000.3516.1558098601118%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.
Title: Message Title Alex Earl commented on JENKINS-54363 Re: ERROR: Could not send email as a part of the post-build publishers. I'm still trying to replicate it so that I can make sure the fix is good. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195113.1540977422000.3512.1558098240148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Jayashree Rokde updated an issue Jenkins / JENKINS-57497 Cucumber Report displays incorrect total duration if total duration is more than 24 hours Change By: Jayashree Rokde Attachment: json.zip Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.3510.1558098000275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Jayashree Rokde commented on JENKINS-57497 Re: Cucumber Report displays incorrect total duration if total duration is more than 24 hours Thanks Damian Szczepanik fro responding I have executed on 10 parallel sessions, attached zip files contains 85 JSON files that was used to create the Report. (Also attached the overview-feature.html) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.3508.1558097940106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Jayashree Rokde updated an issue Jenkins / JENKINS-57497 Cucumber Report displays incorrect total duration if total duration is more than 24 hours Change By: Jayashree Rokde Attachment: overview-features.html Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.3506.1558097880121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title
Mark Waite edited a comment on JENKINS-21248
Re: Add shallow update init for submodule
There could be a bug in the [version detection logic|https://github.com/jenkinsci/git-client-plugin/blob/63dd47319914cbe72948e18d83f62c62365ba6c7/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1269], but you should probably first check that the version of git being used by your job is the same as the version reported in the pipeline script {{sh}} step.I've not seen any other bug reports of broken version detection. There are [specific automated tests|https://github.com/jenkinsci/git-client-plugin/blob/88def8591098610255185f7d895f4474589bc9e2/src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java#L99] in the plugin to confirm that git version numbers in variouos various formats are detected correctly. Those tests don't use 2.11.0 specifically, but they use 2.10.0 and other interesting values near it.If there is a bug in the detection logic, I'll need to update my [acceptance test|https://github.com/MarkEWaite/jenkins-bugs/blob/52c665176dac63a20b81238c38f25c849e877151/Jenkinsfile#L22] to exercise that bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152811.138908257.3480.1558097400479%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Mark Waite commented on JENKINS-21248 Re: Add shallow update init for submodule There could be a bug in the version detection logic, but you should probably first check that the version of git being used by your job is the same as the version reported in the pipeline script sh step. I've not seen any other bug reports of broken version detection. There are specific automated tests in the plugin to confirm that git version numbers in variouos formats are detected correctly. Those tests don't use 2.11.0 specifically, but they use 2.10.0 and other interesting values near it. If there is a bug in the detection logic, I'll need to update my acceptance test to exercise that bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152811.138908257.3478.1558097340853%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48035) Github multibranch: GitHub Webhook is not created right after saving the job
Title: Message Title
Carlos Rodríguez López edited a comment on JENKINS-48035
Re: Github multibranch: GitHub Webhook is not created right after saving the job
[~rsandell] [~stephenconnolly] I am reopening this ticket again because the same reported issue seems to be back running (Regression?)h4. Environment{code:java}Jenkins LTS 2.164.2 * github:1.29.4 'GitHub plugin' * github-api:1.95 'GitHub API Plugin' * github-branch-source:2.5.0 *(update available)* 'GitHub Branch Source Plugin'{code}h4. Observation Observations h6. What we see on Jenkins logs{code:java}May 16, 2019 3:12:38 PM org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeWARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]java.lang.NullPointerException: There are no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]{code}But it is not right... I am using this repo https://github.com/mock-carlosrodlop-org/my-hw-maven-app with user:carlosrodlop and pass:APIToken and as you can tell from the following images carlosrodlop is an admin!repo-team.png|thumbnail! !repo-team-2.png|thumbnail! h6. Custom dedicated loggers as explained in this guide: [GitHub-Webhook-Troubleshooting |https://support.cloudbees.com/hc/en-us/articles/224621648-GitHub-Webhook-Troubleshooting] are not providing any useful hint just{code:java}May 16, 2019 4:05:50 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 applyCalling registerHooks() for multibranch-example-jobMay 16, 2019 4:05:51 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 applyCalling registerHooks() for multibranch-example-job{code} h6. Manage Jenkins > GitHub plugin > Advanced > Re-register hooks for all jobs > webhook in GitHub is NOT generated either. Independently if I enabled or disable Manage hooks options the output is the same: Works only when Jenkins manages hooks (one or more creds specified)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Stefan Verhoeff commented on JENKINS-21248 Re: Add shallow update init for submodule Tried this feature in beta git-4.0.0-beta9. But the plugin is refusing the allow the option: > git submodule init # timeout=10 [WARNING] Git client older than 1.8.4 doesn't support shallow submodule updates. This flag is ignored. However my Git version should support this, see output of sh 'git --version' in my pipeline script: + git --version git version 2.11.0 Bug in the version detection? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152811.138908257.3441.1558095601175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57482) Heap size issue while building using ANT
Title: Message Title Stephan Watermeyer updated JENKINS-57482 Jenkins / JENKINS-57482 Heap size issue while building using ANT Change By: Stephan Watermeyer Status: Closed Fixed but Unreleased Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199342.1557922754000.3415.1558095240357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57482) Heap size issue while building using ANT
Title: Message Title Stephan Watermeyer commented on JENKINS-57482 Re: Heap size issue while building using ANT Happy to hear that Pelican and sorry for not being more responsive. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199342.1557922754000.3413.1558095180104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57525) JCasC export contains only one record
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57525 JCasC export contains only one record Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-05-17 12:10 Priority: Minor Reporter: Pavel Janoušek JCasC export contains only one record (not the first - based on WebGUI Tools confiration page) even we have declared more of them. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57524) JCasC export contains only one record
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57524 JCasC export contains only one record Issue Type: Bug Assignee: Devin Nusbaum Components: jdk-tool-plugin Created: 2019-05-17 12:10 Priority: Minor Reporter: Pavel Janoušek JCasC export contains only one record (not the first - based on WebGUI Tools confiration page) even we have declared more of them. I'm not sure if the issue can be fixed in plugin or is in the core itself, so feel free to re-route the issue if necessary. Add Comment
[JIRA] (JENKINS-57522) Export for JCasC is empty
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57522 Export for JCasC is empty Issue Type: Bug Assignee: Stefan Wolf Components: gradle-plugin Created: 2019-05-17 12:07 Priority: Major Reporter: Pavel Janoušek When configured and seen via Tools configuration WebGUI page I expect an exported record like: tool: gradle: installations: - name: "gradle" home: "/bin/groovy" but nothing is produced. Add Comment
[JIRA] (JENKINS-57523) Export for JCasC is empty
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57523 Export for JCasC is empty Issue Type: Bug Assignee: Armando Fernandez Components: ant-plugin Created: 2019-05-17 12:07 Priority: Major Reporter: Pavel Janoušek When configured and seen via Tools configuration WebGUI page I expect an exported record like: tool: ant: installations: - name: "ant" home: "/bin/ant" but nothing is produced. Add Comment
[JIRA] (JENKINS-57521) Export for JCasC is empty
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57521 Export for JCasC is empty Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 2019-05-17 12:05 Priority: Major Reporter: Pavel Janoušek When configured and seen via Tools configuration WebGUI page I expect an exported record like: tool: groovy: installations: - name: "groovy" home: "/bin/groovy" but nothing is produced. Add Comment
[JIRA] (JENKINS-57520) Declaring Tools installation via JCasC doesn't work
Title: Message Title Pavel Janoušek updated an issue Jenkins / JENKINS-57520 Declaring Tools installation via JCasC doesn't work Change By: Pavel Janoušek Summary: Declaration Declaring Tools installation via JCasC doesn't work Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199425.1558094032000.3402.1558094580287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-57201
[Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Change By:
Baptiste Mathus
h3. Problem statement To enable So an instance can itself detect it's not able to update, it would need to know it's not on latest. And endpoint to easily do that from the Evergreen Jenkins plugin, and then surface an Admin Monitor alert, would be good. h3. ExpectedThe backend should expose a publicly accessible endpoint returning the current updateLevel. (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel).(This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.)h3. Technical asides{noformat}$ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channelgeneral$ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level188{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Title: Message Title Baptiste Mathus commented on JENKINS-57201 Re: [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel R. Tyler Croy in case you missed this. When/if you can do it, would be great. Danke! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198956.155631493.3396.1558094040216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57520) Declaration Tools installation via JCasC doesn't work
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57520 Declaration Tools installation via JCasC doesn't work Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 2019-05-17 11:53 Priority: Major Reporter: Pavel Janoušek Basic declaration via JCasC yaml like: tool: groovy: installations: - name: "Groovy1" home: "/bin/groovy" doesn't work - it produces an exception: May 17, 2019 11:51:05 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed ConfigurationAsCode.init java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1096) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Daan van den Akker commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Torsten Walter: using the fully qualified names like hudson.model.Result.FAILURE works for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.3394.1558092372584%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title RG commented on JENKINS-45579 Re: Step to set stage or parallel status Hi. Would you mind adding an example in https://github.com/jenkinsci/pipeline-examples ? I'm not exactly an expert and coming up with the right syntax assembling bit of code & release note is quite hard. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183763.1500306894000.3161.1558092369597%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48518) Docker Pipeline: invalid volume specification with Windows slave and Linux master
Title: Message Title Raphael Höser commented on JENKINS-48518 Re: Docker Pipeline: invalid volume specification with Windows slave and Linux master Larry Silverman Sadly not really - the github issue had some ideas with writing libraries, which call the docker commands directly, but that doesn't provide the same feature set. Maybe it is possible to use a kubernetes cluster to use docker on windows. (We switched to jenkins in kubernetes, but we also now use wine in the most part with linux hosts) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187135.1513098516000.2973.1558091940725%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
