[JIRA] (JENKINS-61810) Post build script not showing
Title: Message Title Balaji BG created an issue Jenkins / JENKINS-61810 Post build script not showing Issue Type: Bug Assignee: Daniel Heid Attachments: PostBuildScriptInstalled.PNG, PostBuildScriptNotShowing.PNG, TestEmailConfigurationError.PNG Components: postbuildscript-plugin Created: 2020-04-04 04:17 Priority: Blocker Reporter: Balaji BG Hi Team, I want to use email notifications for jenkins build. I referred some docs online and installed postbuild script plugins from manage jenkins. Postbuild script plugin is installed but its not showing to configure email notifications. This is a blocker for me. Please do the needful at the earliest. Also test email configuration fails. It does not show any information. It just shows "Error". PFA screen shots Thanks, Balaji B G Add Comment
[JIRA] (JENKINS-61809) Google play android publisher - credentials not working through JCasC
Title: Message Title
Nada Bourounia created an issue
Jenkins / JENKINS-61809
Google play android publisher - credentials not working through JCasC
Issue Type:
Improvement
Assignee:
Christopher Orr
Components:
credentials-plugin, google-play-android-publisher-plugin
Created:
2020-04-04 02:24
Labels:
jcasc plugin
Priority:
Minor
Reporter:
Nada Bourounia
Hi, I'm unable to get the credentials configured properly for Google play Android publisher plugin. Can you please confirm the following syntax:
googleRobotPrivateKey: projectId: "google-play-account" serviceAccountConfig: json: filename: "xxx" secretJsonKey: ${GOOGLE_PLAY_KEY}
The key should be base64 encoded? Thanks in advance, Nada
Add Comment
[JIRA] (JENKINS-61808) Always encrypt f:password values, not just those backed by Secret
Title: Message Title Daniel Beck started work on JENKINS-61808 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205653.1585961043000.6420.1585963260240%40Atlassian.JIRA.
[JIRA] (JENKINS-61808) Always encrypt f:password values, not just those backed by Secret
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-61808 Always encrypt f:password values, not just those backed by Secret Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 2020-04-04 00:44 Priority: Minor Reporter: Daniel Beck Too many people get the Secret getters wrong. What if we just always returned a Secret, and had a StringConverter to handle submitted secrets and transparently decrypt again? This would eliminate this class of problem. Only storage would really need to be done as Secret, but the internal API types wouldn't matter so much. Test cases need to include String typed encrypted secrets, and unmatched getter/setter types. Add Comment
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Daniel Beck commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade May be caused by https://github.com/jenkinsci/jenkins/pull/3983 in Jenkins 2.205. If a similar behavior works in 2.204 (not LTS), and doesn't work in 2.205, that would be a strong indication. A bit weird we're only hearing about this now though. I cannot find similar recent bugs in throttle-concurrents either. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205618.158582599.6416.1585960920197%40Atlassian.JIRA.
[JIRA] (JENKINS-61760) Setting CloneOption trait on SCMSource with shallow depth causes MR builds to fail
Title: Message Title Parichay Barpanda started work on JENKINS-61760 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205597.158568376.6374.1585951200281%40Atlassian.JIRA.
[JIRA] (JENKINS-61144) Projects are checked out over HTTPs after updating to 1.4.4
Title: Message Title Parichay Barpanda updated JENKINS-61144 Jenkins / JENKINS-61144 Projects are checked out over HTTPs after updating to 1.4.4 Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204672.158210835.6368.1585950780887%40Atlassian.JIRA.
[JIRA] (JENKINS-61144) Projects are checked out over HTTPs after updating to 1.4.4
Title: Message Title Parichay Barpanda updated JENKINS-61144 Jenkins / JENKINS-61144 Projects are checked out over HTTPs after updating to 1.4.4 Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204672.158210835.6370.1585950780986%40Atlassian.JIRA.
[JIRA] (JENKINS-61144) Projects are checked out over HTTPs after updating to 1.4.4
Title: Message Title Parichay Barpanda commented on JENKINS-61144 Re: Projects are checked out over HTTPs after updating to 1.4.4 Fixed in 1.4.5 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204672.158210835.6364.1585950780685%40Atlassian.JIRA.
[JIRA] (JENKINS-61144) Projects are checked out over HTTPs after updating to 1.4.4
Title: Message Title Parichay Barpanda started work on JENKINS-61144 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204672.158210835.6358.1585950720282%40Atlassian.JIRA.
[JIRA] (JENKINS-61132) accountID not available on jira assign
Title: Message Title Naresh Rayapati commented on JENKINS-61132 Re: accountID not available on jira assign Can you provide more information, may be with the code snippet that you have? I am guessing this is related to: https://github.com/jenkinsci/jira-steps-plugin/pull/103 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204654.1582045488000.6336.1585949280168%40Atlassian.JIRA.
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title Naresh Rayapati updated JENKINS-61762 Jenkins / JENKINS-61762 Intermittent Socket closed or Read timed out error Change By: Naresh Rayapati Status: Fixed but Unreleased Closed Resolution: Fixed Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205599.1585716788000.6333.1585949100714%40Atlassian.JIRA.
[JIRA] (JENKINS-61388) jiraGetFields: "Illegal base64 character" since 1.5.2
Title: Message Title Naresh Rayapati commented on JENKINS-61388 Re: jiraGetFields: "Illegal base64 character" since 1.5.2 Kevin Huber Thank you pointing out the code, Can you try to update the site credentials after upgrade to see this is going to fix? I guess probably it was a non-passive change, I didn't check that to see if it is going to decode the previous values Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205041.1583744817000.6330.1585949100670%40Atlassian.JIRA.
[JIRA] (JENKINS-60593) Unable to run a background process using sshCommand
Title: Message Title Naresh Rayapati closed an issue as Cannot Reproduce Jenkins / JENKINS-60593 Unable to run a background process using sshCommand Change By: Naresh Rayapati Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203815.1577436007000.6327.1585948800642%40Atlassian.JIRA.
[JIRA] (JENKINS-60593) Unable to run a background process using sshCommand
Title: Message Title Naresh Rayapati commented on JENKINS-60593 Re: Unable to run a background process using sshCommand Closing as there isn't much activity on this PR. Please reopen if you are still facing this issue and have more information. Thank you for logging an issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203815.1577436007000.6322.1585948800297%40Atlassian.JIRA.
[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Stephen Smith updated an issue Jenkins / JENKINS-61807 "restrict where this project can be run" setting missing from job configuration Change By: Stephen Smith Environment: Jenkins version: 2.222.1OS: Windows Server 2016Browser: Google Chrome Version 80.0.3987.149 Plugs Plugins : a large list, not sure which are relevant Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205652.1585948729000.6319.1585948800239%40Atlassian.JIRA.
[JIRA] (JENKINS-61357) every time I click the Save button in Configure System Jenkins Crashes
Title: Message Title Mark Waite commented on JENKINS-61357 Re: every time I click the Save button in Configure System Jenkins Crashes No problem, and perfectly understandable Steven Fransen. I'll set myself a reminder to revisit this in a month or so. If you haven't been able to duplicate it by then and no one else has reported a similar condition, I'll close it as "cannot reproduce". It will remain in the issue tracker and will continue to be indexed by search engines so that others can find it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204942.1583438464000.6324.1585948800331%40Atlassian.JIRA.
[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Stephen Smith created an issue Jenkins / JENKINS-61807 "restrict where this project can be run" setting missing from job configuration Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-03 21:18 Environment: Jenkins version: 2.222.1 OS: Windows Server 2016 Browser: Google Chrome Version 80.0.3987.149 Plugs: a large list, not sure which are relevant Labels: jenkins slave configuration windows Priority: Blocker Reporter: Stephen Smith I have a master node, and I just added a slave node running as a service. A single machine runs jenkins, the master node, and the slave node. Both master and slave nodes have labels, and they are both connected and running. However, in attempting to set up a project to build on this slave node as per https://scmquest.com/jenkins-master-slave-setup-and-configuration-with-screenshots/ the "Restrict where this project can be run" option is missing from the "general" section. On a single branch project, I see the options "Discard old builds," "Do not allow concurrent builds ," and "Do not allow the pipeline to resume if the master restarts." But not the actual option i need: "Restrict where this project can be run." In a multibranch project, I don't see any additional options at all. I'm at a loss of how to proceed from here. I can try using another plugin to restrict which nodes build which project as a workaround to this broken feature, but it would be nice if the feature just worked. Is there further troubleshooting I can perform at my end?
[JIRA] (JENKINS-61357) every time I click the Save button in Configure System Jenkins Crashes
Title: Message Title Steven Fransen commented on JENKINS-61357 Re: every time I click the Save button in Configure System Jenkins Crashes I am totally afraid to upload at this point. it took me so long to get it back working again. Also with the lock down I am not willing to do anything to risk it again. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204942.1583438464000.6317.1585945380200%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Andrew Martin commented on JENKINS-59788 Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1 I enabled Timestamper both via the global enable button as well as via the Jenkinsfile timestamps() option, however I have zero timestamps in the pipeline build output. Freestyle projects that I've explicitly enabled it for do, indeed, have timestamps. I'm using jenkins 2.229 with the latest timestamper. Our Jenkinsfile is basically just a list of stages for an AWS deployment and a couple in-line shell scripts. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202518.1571132852000.6307.1585942860258%40Atlassian.JIRA.
[JIRA] (JENKINS-61716) Improve tests for Score (in ScoreTest)
Title: Message Title Oliver Scholz resolved as Done Tests hinzugefügt und PR gemerged. Jenkins / JENKINS-61716 Improve tests for Score (in ScoreTest) Change By: Oliver Scholz Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-61716) Improve tests for Score (in ScoreTest)
Title: Message Title Oliver Scholz edited a comment on JENKINS-61716 Re: Improve tests for Score (in ScoreTest) Tests hinzugefügt und added and PR gemerged merged . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205542.1585329997000.6305.1585940820451%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith edited a comment on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) [~jvz]Hey Matt - So I can't downgrade the ssh-credential-plugin any lower than version 1. 8 18 . When I attempt to downgrade to version 1.17.4 or lower, the Build Agent gives an error and removes the Launch Agent button from launching via SSH(see new attachments). It looks like SSH is completely removed from the Master, do I need to reset something under MANAGE JENKINS -> CONFIGURE SECURITY? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204941.158343741.6301.1585939200216%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith edited a comment on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) [~jvz]Hey Matt - So I can't downgrade the ssh-credential-plugin any lower than version 18 1 . 0 8 . When I attempt to downgrade to version 1.17.4 or lower, the Build Agent gives an error and removes the Launch Agent button from launching via SSH(see new attachments). It looks like SSH is completely removed from the Master, do I need to reset something under MANAGE JENKINS -> CONFIGURE SECURITY? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204941.158343741.6299.1585939200182%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jeff Thompson commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb Should I create that intermediate version of Remoting, without those minor cleanup changes? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205063.1583801943000.6293.1585938840338%40Atlassian.JIRA.
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title Joseph Petersen updated JENKINS-60143 Released as 1.4.5 Jenkins / JENKINS-60143 Behaviour SSH Checkout not working after Jenkins restart Change By: Joseph Petersen Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.4.5 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title Joseph Petersen updated JENKINS-59753 Released as 1.4.5 Jenkins / JENKINS-59753 Error cloning remote repo Change By: Joseph Petersen Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.4.5 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You
[JIRA] (JENKINS-61792) DoubleLaunchChecker false positive
Title: Message Title Wade Cline commented on JENKINS-61792 Re: DoubleLaunchChecker false positive We've hit this issue twice recently on the same machine, here is the snippet from earlier: 2020-03-14 02:02:45.357+ [id=56]SEVERE hudson.util.DoubleLaunchChecker#execute: Collision detected. timestamp=1584146805000, expected=1584146805350 The underlying filesystem is 'ext4' with standard options 'rw,relatime,errors=remount-ro', and the unit test shows that the filesystem does support sub-second timestamps... and yet the messages appear to suggest the opposite. There might be an uncommon case which causes the sub-second timestamp to be downgraded to a second timestamp when writing to disk (yet that didn't happen in the unit test I wrote), or there might be something more nefarious going on here. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205632.1585870918000.6277.1585937520130%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker Hey Matt - So I can't downgrade the ssh-credential-plugin any lower than version 18.0. When I attempt to downgrade to version 1.17.4 or lower, the Build Agent gives an error and removes the Launch Agent button from launching via SSH(see new attachments). It looks like SSH is completely removed from the Master, do I need to reset something under MANAGE JENKINS -> CONFIGURE SECURITY? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204941.158343741.6273.1585936260202%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith updated an issue Jenkins / JENKINS-61356 Unable to connect to slave via Launch Agent mode(SSH) Change By: Charles Smith Attachment: Unable to launch agent using plugin-ver.1.17.4.PNG Attachment: ver1.17.4.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204941.158343741.6275.1585936260229%40Atlassian.JIRA.
[JIRA] (JENKINS-60837) Migrate GCE plugin documentation from Wiki to GitHub
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60837 Migrate GCE plugin documentation from Wiki to GitHub Change By: Mark Waite Summary: Migrate GCE plugin documentation from Wiki to GitHub Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204192.1579694274000.6271.1585935120251%40Atlassian.JIRA.
[JIRA] (JENKINS-60497) Filesystem list parameter reset to default when rebuilding previous job
Title: Message Title René Korthaus commented on JENKINS-60497 Re: Filesystem list parameter reset to default when rebuilding previous job Fix tested and confirmed in 0.0.6. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203587.1576492111000.6268.1585934940111%40Atlassian.JIRA.
[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams closed an issue as Incomplete While a specific fix from AccuRev was never provided to address this issue, several fixes to the plug-in were provided - those fixes in addition to recreating the jobs with some AccuRev filtering changes has provided more consistent results in the job changes report. Closing this issue as clean-up, as it will never be specifically worked on. Jenkins / JENKINS-41102 Job "Changes" do not match "Filter for Poll SCM" Change By: Timothy Williams Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61758) Test Result Summary in logs is incorrect.
Title: Message Title Barrie Sager updated JENKINS-61758 Jenkins / JENKINS-61758 Test Result Summary in logs is incorrect. Change By: Barrie Sager Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205595.1585676315000.6262.1585929600213%40Atlassian.JIRA.
[JIRA] (JENKINS-61758) Test Result Summary in logs is incorrect.
Title: Message Title Barrie Sager started work on JENKINS-61758 Change By: Barrie Sager Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205595.1585676315000.6252.1585929480467%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Félix Queiruga Balado commented on JENKINS-61480 Re: Dark Theme Gábor Tasnádi The neo2 theme for simple-theme-plugin has a dark mode option: https://github.com/TobiX/jenkins-neo2-theme/tree/master/less Maybe you'll find it interesting. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205164.1584202104000.6232.1585927260285%40Atlassian.JIRA.
[JIRA] (JENKINS-61806) Remove the timestamp from the page footer
Title: Message Title Félix Queiruga Balado created an issue Jenkins / JENKINS-61806 Remove the timestamp from the page footer Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-04-03 15:02 Priority: Minor Reporter: Félix Queiruga Balado Remove the "Page generated" timestamp from the footer. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-61798 New Windows Installer always redirects to 8080 after completing the installation Change By: Alex Earl Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205642.1585912413000.6229.1585925760251%40Atlassian.JIRA.
[JIRA] (JENKINS-61805) Display URL Plugin should not provice Blue Ocean url
Title: Message Title Marcus Held created an issue Jenkins / JENKINS-61805 Display URL Plugin should not provice Blue Ocean url Issue Type: Bug Assignee: James Dumay Components: display-url-api-plugin Created: 2020-04-03 14:41 Priority: Major Reporter: Marcus Held Since the development of blue ocean has been stopped I would like to have the classic url returned in the display url api plugin so as a consequence I also have the link to the classic view in Bitbucket when updating the build result. Note: There seems to be a workaround as suggested in this issue (hence not tested by me yet) It is possible to set the used provider via property or environment variable. The provider you should use is org.jenkinsci.plugins.displayurlapi.ClassicDisplayURLProvider. See https://github.com/jenkinsci/display-url-api-plugin/blob/master/src/main/java/org/jenkinsci/plugins/displayurlapi/DisplayURLProvider.java#L158-L159 Hence, under debian you can set the property in /etc/default/jenkins with JAVA_ARGS="-Djenkins.displayurl.provider=org.jenkinsci.plugins.displayurlapi.ClassicDisplayURLProvider"
[JIRA] (JENKINS-61496) Update page footer
Title: Message Title Félix Queiruga Balado resolved as Done Jenkins / JENKINS-61496 Update page footer Change By: Félix Queiruga Balado Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205183.1584379178000.6218.1585921920178%40Atlassian.JIRA.
[JIRA] (JENKINS-61800) New Windows Installer has no icon in the permission elevation screen
Title: Message Title Tim Jacomb commented on JENKINS-61800 Re: New Windows Installer has no icon in the permission elevation screen This may not be fixable, see https://stackoverflow.com/questions/11054069/how-to-change-icon-in-uac-prompt-of-signed-installer-wix, apparently the calling process is msiexec which doesn't have a logo set, there might be a work around but likely not worth the effort Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205644.1585913166000.6217.1585921320112%40Atlassian.JIRA.
[JIRA] (JENKINS-61804) = sign in path lead to bug in msbuild
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-61804 = sign in path lead to bug in msbuild Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 2020-04-03 13:40 Environment: Windows Priority: Minor Reporter: Ronny Borchert Caused by the matrix plugin the jobname: JOB_NAME xxx/CONFIGURATION=Release is generated. We are tried to copy the source into this path and start build, This lead to error CS0006 in msbuild 4.0 for VS2010 or CS1679 for MSbuild shipped with VS2019. Report: https://github.com/dotnet/roslyn/issues/5623 It would be nice if this = sign could be configured.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y)Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less...{code:java}// library importssharedPipeline(){code}vars/sharedPipeline.groovy{code:java}def call() { throttle(['throttle-category']) {sharedPipelineInner() }}{code}vars/sharedPipelineInner.groovy{code:java}def call() { pipeline { agent { label 'mylabel' } stages {stage('first') { steps { sleep 60 }} }}{code} I did try to simply shift the pipeline config into a {{def}} within the original file, but that did not work.This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this. Edit - Then again, the title says _entire build_ so maybe this solution does apply and the example in the body does not. [~anthonymastrean], can you comment?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61803) Configure Global Security should accept both entries: default and per project
Title: Message Title Maxime Hochet created an issue Jenkins / JENKINS-61803 Configure Global Security should accept both entries: default and per project Issue Type: Bug Assignee: Unassigned Components: authorize-project-plugin Created: 2020-04-03 13:20 Environment: All Priority: Minor Reporter: Maxime Hochet Description The menu (http://myjenkins/configureSecurity) related to Authorize Project Plugin can accept both entries: Project default Build Authorization Per-project configurable Build Authorization But only Project default Build Authorization is applied to all jobs. Actual Behavior All jobs, even those with Authorization configured are run with the settings defined for Project default Build Authorization. Expected Behavior If a job has an Authorization configured explicitly in its configuration, then this one should be applied. Otherwise, the one defined in for Project default Build Authorization is applied. Implementation details This behavior can be discovered in the beginning of the build logs with: originally caused by: Started by user yyy Running as xxx
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Neha Singh closed an issue as Fixed Jenkins / JENKINS-61601 Unable to trigger job on deletion of branch when configured with job DSL. Change By: Neha Singh Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205299.1584706587000.6174.1585919280726%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Neha Singh updated JENKINS-61601 Jenkins / JENKINS-61601 Unable to trigger job on deletion of branch when configured with job DSL. Change By: Neha Singh Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205299.1584706587000.6172.1585919280592%40Atlassian.JIRA.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y)Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less...{code:java}// library importssharedPipeline(){code}vars/sharedPipeline.groovy{code:java}def call() { throttle(['throttle-category']) {sharedPipelineInner() }}{code}vars/sharedPipelineInner.groovy{code:java}def call() { pipeline { agent { label 'mylabel' } stages {stage('first') { steps { sleep 60 }} }}{code} I did try to simply shift the pipeline config into a {{def}} within the original file, but that did not work. This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y)Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less... {code:java}// library imports sharedPipeline() {code} vars/sharedPipeline.groovy{code:java}def call() { throttle(['throttle-category']) {sharedPipelineInner() }}{code}vars/sharedPipelineInner.groovy{code:java}def call() { pipeline { agent { label 'mylabel' } stages {stage('first') { steps { sleep 60 }} }}{code} This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y) Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less... sharedPipeline() vars/sharedPipeline.groovy{code:java}def call() { throttle(['throttle-category']) {sharedPipelineInner() }}{code}vars/sharedPipelineInner.groovy{code:java}def call() { pipeline { agent { label 'mylabel' } stages {stage('first') { steps { sleep 60 }} }}{code} This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y) Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less... sharedPipeline() vars/sharedPipeline.groovy{code:java}def call() { throttle(['throttle-category']) {sharedPipelineInner() }}{code}vars/sharedPipelineInner.groovy{code:java}def call() { pipeline { agent { label 'mylabel' } stages {stage('first') { steps { sleep 60 }} }}{code} This way, no {{Jenkinsfile}} will need to be updated and they will all be throttled for free. This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title Parichay Barpanda commented on JENKINS-59753 Re: Error cloning remote repo Sent fix https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/80 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202476.1570810205000.6014.1585917843807%40Atlassian.JIRA.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y) Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less... sharedPipeline() vars/sharedPipeline.groovy{code:java}def call() { throttle(['throttle-category']) { sharedPipelineInner() }}{code}vars/sharedPipelineInner.groovy{code:java}def call() { pipeline { agent { label 'mylabel' } stages {stage('first') { steps { sleep 60 }} }}{code} This way, no {{Jenkinsfile}} will need to be updated and they will all be throttled for free. This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title Parichay Barpanda commented on JENKINS-60143 Re: Behaviour SSH Checkout not working after Jenkins restart Sent fix https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/80 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203004.1573562285000.6008.1585917843503%40Atlassian.JIRA.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y) Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less... sharedPipeline() vars/sharedPipeline.groovy{code:java}def call() { throttle(['throttle-category']) { sharedPipelineInner() }}{code}vars/sharedPipelineInner.groovy{code:java}def call() { pipeline { agent { label 'mylabel' } stages {stage('first') { steps {sleep 60 } }} }}{code} This way, no {{Jenkinsfile}} will need to be updated and they will all be throttled for free. This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y) Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less... sharedPipeline() vars/sharedPipeline.groovy ``` {code:java} def call() { throttle(['throttle-category']) { sharedPipelineInner() } } {code } ``` vars/sharedPipelineInner.groovy {code:java} def call() { pipeline { agent { label 'mylabel' } stages { stage('first') { steps { sleep 60 } } } } } {code } This way, no {{Jenkinsfile}} will need to be updated and they will all be throttled for free. This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title Parichay Barpanda updated JENKINS-59753 Jenkins / JENKINS-59753 Error cloning remote repo Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202476.1570810205000.5909.1585917662519%40Atlassian.JIRA.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning.[~marcus_phi], I'll second your comment/excitement on finally having a solution to this mystery. (flag)[~metamilk], thank you so much! (y) Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by [~metamilk] and here is a little more on how I think I'll `throttle` in our builds by renaming {{sharedPipeline}} to {{sharedPipelineInner}} and having {{sharedPipeline}} wrap the throttle category around the {{sharedPipeline()}} call. This way, I don't need to update 100+ repositories * number of branches. The current {{Jenkinsfile}} looks like this more or less...sharedPipeline()vars/sharedPipeline.groovy ``` def call() {throttle(['throttle-category']) { { sharedPipelineInner() } } ``` vars/sharedPipelineInner.groovydef call() {pipeline {agent { label 'mylabel' } stages {stage('first') \ {steps { { sleep 60 } }}}} This way, no {{Jenkinsfile}} will need to be updated and they will all be throttled for free. This defect asks for {{throttle}} within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title Parichay Barpanda started work on JENKINS-60143 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203004.1573562285000.5891.1585917662247%40Atlassian.JIRA.
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title Parichay Barpanda updated JENKINS-60143 Jenkins / JENKINS-60143 Behaviour SSH Checkout not working after Jenkins restart Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203004.1573562285000.5903.1585917662422%40Atlassian.JIRA.
[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title Parichay Barpanda started work on JENKINS-59753 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.202476.1570810205000.5897.1585917662349%40Atlassian.JIRA.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Jeff G commented on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I honestly did not have much hope when I saw this issue having been updated in my e-mail this morning. Marcus Philip, I'll second your comment/excitement on finally having a solution to this mystery. Dmitry Mamchur, thank you so much! Our team already has our declarative and scripted pipelines largely live in libraries. I gave a couple attempts to implement the throttle as described by Dmitry Mamchur and here is a little more on how I think I'll `throttle` in our builds by renaming sharedPipeline to sharedPipelineInner and having sharedPipeline wrap the throttle category around the sharedPipeline() call. This way, I don't need to update 100+ repositories * number of branches. The current Jenkinsfile looks like this more or less... sharedPipeline() vars/sharedPipeline.groovy def call() { throttle(['throttle-category']) { sharedPipelineInner() } } vars/sharedPipelineInner.groovy def call() { pipeline { agent { label 'mylabel' } stages { stage('first') { steps { sleep 60 } } } } } This way, no Jenkinsfile will need to be updated and they will all be throttled for free. This defect asks for throttle within a step, which this solution does not provide, so I guess it will need to stay open. The docs for the plugin should be updated, for sure, with an example like this.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-54905) Support of Java 11 in Jenkinsfile Runner and Custom WAR Packager
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-54905 Support of Java 11 in Jenkinsfile Runner and Custom WAR Packager Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: 1.0-beta-6 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.195912.1543392684000.5854.1585915620096%40Atlassian.JIRA.
[JIRA] (JENKINS-54342) Jenkinsfile Runner productization
Title: Message Title Oleg Nenashev resolved as Fixed All scope of this EPIC was completed by beta-11. Vanilla packaging is now published to the experimental repo, will make it official before 1.0. Francisco Fernández Evaristo Gutierrez FYI I will close it and follow-up on next issues without EPIC. Thanks for your contributions! Jenkins / JENKINS-54342 Jenkinsfile Runner productization Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Released As: 1.0-beta-11 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61801) IvyTrigger is not triggering when modified (already existing) artifact is uploaded to remote artifactory
Title: Message Title
Peter Horecny updated an issue
Jenkins / JENKINS-61801
IvyTrigger is not triggering when modified (already existing) artifact is uploaded to remote artifactory
Change By:
Peter Horecny
IvyTrigger trigger output after uploading updated artifact to remote artifactory: {code:java}Resolving Ivy dependencies. - | |modules|| artifacts | | conf | number| search|dwnlded|evicted|| number|dwnlded| - |lib | 1 | 1 | 0 | 0 || 1 | 1 | -Resolved dependency tools#testNew;1.0.0-SNAPSHOT ...Checking comparison to previous recorded dependencies.Checking previous recording dependency tools#testNew;1.0.0-SNAPSHOT...Checking comparison to previous recorded artifacts.Polling complete. Took 0.94 sec.No changes.{code}As new or updated artifact is present, ivy downloaded it (as seen in output - artifacts dwnlded 1), it can be also found on local file system, BUT job is not triggered (modification date comparison should follow, but it doesnt) Possibly, the reason could be using dependencyNode.isDownloaded() added in 0.34 version (in IvyTriggerEvaluator getMapDependencies method) , which is not used to indicate whether the artifacts were downloaded, but the whole module (which is not)...so isDownloaded() is false even if artifact was downloaded, related ivy ticket (old, but described the same in the comment): [https://issues.apache.org/jira/browse/IVY-320?jql=project%20%3D%20IVY%20AND%20text%20~%20%22downloaded%22]Therefore, no comparison of modification date is performed. ResultReport update after downloading artifacts, Ivy code snippet: {code:java}report.getConfigurationReport(dconf).addDependency(dependency,dReport);{code}Information about download success of artifacts are stored in ArtifactDownloadReport, which is in dReport.Following code produces true, and could be used in plugin instead of dependencyNode.isDownloaded(){code:java}resolveReport.getConfigurationReport(dependencyNode.getRootModuleConfigurations()[0]).getDownloadReports(moduleRevisionId)[0].isDownloaded());{code}Also, if downloading from remote Artifactory, downloaded artifacts are considered NOT local, and modification date of ArtifactOrigin used is always 0. Related ticket: JENKINS-24950Instead, local file from ArtifactDownloadReport could be used:{code:java}File localFile = resolveReport.getConfigurationReport(dependencyNode.getRootModuleConfigurations()[0]).getDownloadReports(moduleRevisionId)[0].getLocalFile; localFile.getAbsolutePath(); // C:\...\Jenkins\...\testNew-1.0.0-SNAPSHOT.jarlocalFile.lastModified(); // 1585639081000{code}
[JIRA] (JENKINS-61802) New Windows installer: Add option to show the temporary password in the installer UI
Title: Message Title
Oleg Nenashev created an issue
Jenkins / JENKINS-61802
New Windows installer: Add option to show the temporary password in the installer UI
Issue Type:
New Feature
Assignee:
Kohsuke Kawaguchi
Components:
packaging
Created:
2020-04-03 11:46
Priority:
Minor
Reporter:
Oleg Nenashev
Right now a user gets a request to provide the password when installation wizard starts up. If you install the service with a custom user account, it is not exactly trivial to access the file ("Run as Administrator"). It would be great to allow getting a temporary password from the installer. Such feature likely requires Jenkins core patches to allow overriding the temporary password somehow. It might be also useful for other use-cases, so IMHO it is something to consider
Add Comment
[JIRA] (JENKINS-61801) IvyTrigger is not triggering when modified (already existing) artifact is uploaded to remote artifactory
Title: Message Title Peter Horecny created an issue Jenkins / JENKINS-61801 IvyTrigger is not triggering when modified (already existing) artifact is uploaded to remote artifactory Issue Type: Bug Assignee: Tony Noble Components: ivytrigger-plugin Created: 2020-04-03 11:39 Environment: Jenkins 2.204.5, tested also on version 2.121.1 IvyTrigger 0.34 Artifactory 5.2.1 Labels: ivytrigger Priority: Major Reporter: Peter Horecny IvyTrigger trigger output after uploading updated artifact to remote artifactory: Resolving Ivy dependencies. - | |modules|| artifacts | | conf | number| search|dwnlded|evicted|| number|dwnlded| - |lib | 1 | 1 | 0 | 0 || 1 | 1 | - Resolved dependency tools#testNew;1.0.0-SNAPSHOT ...Checking comparison to previous recorded dependencies. Checking previous recording dependency tools#testNew;1.0.0-SNAPSHOT ...Checking comparison to previous recorded artifacts. Polling complete. Took 0.94 sec. No changes. As new or updated artifact is present,
[JIRA] (JENKINS-55642) Create experimental "vanilla" Docker packages for the Vanilla version of JFR
Title: Message Title Oleg Nenashev updated JENKINS-55642 Jenkins / JENKINS-55642 Create experimental "vanilla" Docker packages for the Vanilla version of JFR Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.196819.1547715487000.5841.1585913940300%40Atlassian.JIRA.
[JIRA] (JENKINS-61800) New Windows Installer has no icon in the permission elevation screen
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-61800 New Windows Installer has no icon in the permission elevation screen Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: 20200403_131845.jpg Components: packaging Created: 2020-04-03 11:26 Priority: Minor Reporter: Oleg Nenashev See the attached screenshot. It would be great to have an icon Add Comment
[JIRA] (JENKINS-61800) New Windows Installer has no icon in the permission elevation screen
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-61800 New Windows Installer has no icon in the permission elevation screen Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205644.1585913166000.5839.1585913220311%40Atlassian.JIRA.
[JIRA] (JENKINS-61799) New Windows Installer redirects to browser after uninstalling Jenkins
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-61799 New Windows Installer redirects to browser after uninstalling Jenkins Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 2020-04-03 11:24 Priority: Minor Reporter: Oleg Nenashev As a user, I do not expect the Installer to open the browser after uninstalling Jenkins. Just getting a page not exists error, but a bit unexpected Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-61799) New Windows Installer redirects to browser after uninstalling Jenkins
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-61799 New Windows Installer redirects to browser after uninstalling Jenkins Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205643.1585913087000.5835.1585913100286%40Atlassian.JIRA.
[JIRA] (JENKINS-60143) Behaviour SSH Checkout not working after Jenkins restart
Title: Message Title Joseph Petersen commented on JENKINS-60143 Re: Behaviour SSH Checkout not working after Jenkins restart There is no reason for these fields being transient, feel free to submit a PR that removes transient for those fields. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203004.1573562285000.5828.1585912920277%40Atlassian.JIRA.
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Oleg Nenashev commented on JENKINS-61798 Re: New Windows Installer always redirects to 8080 after completing the installation Also, redirect still happens after removing the package. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205642.1585912413000.5823.1585912560175%40Atlassian.JIRA.
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-61798 New Windows Installer always redirects to 8080 after completing the installation Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205642.1585912413000.5825.1585912560203%40Atlassian.JIRA.
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-61798 New Windows Installer always redirects to 8080 after completing the installation Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 2020-04-03 11:13 Priority: Minor Reporter: Oleg Nenashev Just a minor issue. I installed Jenkins via the new installer and changed the port to 8081 in settings. Once the installation was completed, the installer redirected me to 8080 instead of the configured port. It is a minor issue, it could be fixed later FYI Alex Earl Add Comment
[JIRA] (JENKINS-61797) How to disable CSRF in Jenkins 2.222.1 to run remote parameterized builds
Title: Message Title Ibrahim Patel created an issue Jenkins / JENKINS-61797 How to disable CSRF in Jenkins 2.222.1 to run remote parameterized builds Issue Type: Task Assignee: Ibrahim Patel Components: parameterized-trigger-plugin Created: 2020-04-03 10:50 Environment: Jenkins 2.222.1 Priority: Minor Reporter: Ibrahim Patel Getting below error while running remote builds after Jenkins version upgrade to 2.222.1, please help to resolve below issue. Triggering remote job now. CSRF protection is enabled on the remote server. ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. org.jenkinsci.plugins.ParameterizedRemoteTrigger.exceptions.ExceedRetryLimitException: Max number of connection retries have been exeeded. at org.jenkinsci.plugins.ParameterizedRemoteTrigger.utils.HttpHelper.sendHTTPCall(HttpHelper.java:569) Add Comment
[JIRA] (JENKINS-61796) Add JCasC compatibility to support-core
Title: Message Title Ramon Leon updated JENKINS-61796 Jenkins / JENKINS-61796 Add JCasC compatibility to support-core Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205640.1585907879000.5818.1585910460269%40Atlassian.JIRA.
[JIRA] (JENKINS-61796) Add JCasC compatibility to support-core
Title: Message Title Ramon Leon started work on JENKINS-61796 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205640.1585907879000.5817.1585910460162%40Atlassian.JIRA.
[JIRA] (JENKINS-61785) REST API requires Job/Build permission
Title: Message Title Juan Pablo Santos Rodríguez updated an issue Jenkins / JENKINS-61785 REST API requires Job/Build permission Change By: Juan Pablo Santos Rodríguez Summary: REST API requires Task Job /Build permission Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205624.1585839242000.5816.1585909740180%40Atlassian.JIRA.
[JIRA] (JENKINS-61279) Update version number dependency to 1.7
Title: Message Title Tim Jacomb commented on JENKINS-61279 Re: Update version number dependency to 1.7 It's more that it's annoying and wastes time for the plugin developer whose IDE is complaining about all these deprecation warnings after bumping the minimum required core version, and has to go investigate them, it's a waste of time IMO. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204854.1582987621000.5814.1585909260299%40Atlassian.JIRA.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title Marcus Philip commented on JENKINS-45140 Re: Add support of throttling of the entire build in Declarative Pipeline Je-s F-ng C-st! It's insane that that would make a difference but it does. So the 'pipeline block must be at the top-level' check is just on a file (textual) basis, not on the actual code structure. Thanks Dmitry Mamchur! You made my day! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.183244.1498502397000.5784.1585908180730%40Atlassian.JIRA.
[JIRA] (JENKINS-61279) Update version number dependency to 1.7
Title: Message Title Oliver Gondža commented on JENKINS-61279 Re: Update version number dependency to 1.7 Tim Jacomb, thanks. Though since this only affects plugin build and not its executions and (as I understood) it does not even prevent the static analysis to detect problems, I still lean towards not to add this. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204854.1582987621000.5780.1585908060347%40Atlassian.JIRA.
[JIRA] (JENKINS-61796) Add JCasC compatibility to support-core
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-61796 Add JCasC compatibility to support-core Issue Type: Improvement Assignee: Ramon Leon Components: support-core-plugin Created: 2020-04-03 09:57 Priority: Minor Reporter: Ramon Leon Ensure support-core is compatible with JCasC. Put the configuration under the security group because there is already a PR #211 aiming to do the same on the UI. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Marcus Philip edited a comment on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I tried [~metamilk]s creative suggestion but on more recent versions this is explicitly prohibited: {noformat}WorkflowScript: 2: pipeline block must be at the top-level, not within another block. @ line 2, column 5. pipeline { ^{noformat} h3. Demo pipeline:{code: groovy java } throttle(['myThrottle']) {pipeline {agent { label 'mylabel' }stages {stage('first') {steps {sleep 60}}}}}{code} I've tested many other variants and I claim it is currently (with latest versions) impossible to get node throttling on a declarative pipeline. If someone has a counterexample I would appreciate that.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.183244.1498502397000.5750.1585907640734%40Atlassian.JIRA.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Dmitry Mamchur commented on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
Marcus Philip The secret sauce is having your pipeline defined in a shared library. vars/myPipeline.groovy
def call() {
pipeline {
agent { label 'mylabel' }
stages {
stage('first') {
steps {
sleep 60
}
}
}
}
}
jobs/my-pipeline/Jenkinsfile
throttle(['myThrottle']) {
myPipeline()
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.183244.1498502397000.5720.1585907460719%40Atlassian.JIRA.
[JIRA] (JENKINS-61279) Update version number dependency to 1.7
Title: Message Title Tim Jacomb commented on JENKINS-61279 Re: Update version number dependency to 1.7 This is for CheckNonNull, Nullable etc, without this change when you increase your minimum core version you pick up a version of spotbugs that has deprecated the annotations that don't violate the javax license. When we increased the configuration-as-code baseline to ~2.220 we got 50+ deprecation warnings due to this, this one line lib bump fixes it for plugins without any workaround on the plugin side having to mess around excluding core dependencies Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204854.1582987621000.5717.1585907160255%40Atlassian.JIRA.
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Marcus Philip commented on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I tried Dmitry Mamchurs creative suggestion but on more recent versions this is explicitly prohibited:
WorkflowScript: 2: pipeline block must be at the top-level, not within another block. @ line 2, column 5.
pipeline {
^
Demo pipeline:
throttle(['myThrottle']) {
pipeline {
agent { label 'mylabel' }
stages {
stage('first') {
steps {
sleep 60
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-61792) DoubleLaunchChecker false positive
Title: Message Title Oleg Nenashev commented on JENKINS-61792 Re: DoubleLaunchChecker false positive > Has anyone seen this issue before, or have any ideas how to debug it? I have not seen such issue before. It may be easily a filesystem problem or a glitch in the code. Did you hit this issue only once? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205632.1585870918000.5684.1585906440223%40Atlassian.JIRA.
[JIRA] (JENKINS-61465) Make Functions#checkAnyPermission work on objects that aren't AccessControlled
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61465 Make Functions#checkAnyPermission work on objects that aren't AccessControlled Change By: Oliver Gondža Labels: lts 2.222.2 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205146.1584097006000.5681.1585904520229%40Atlassian.JIRA.
[JIRA] (JENKINS-61688) Global build discarders configuration isn't loaded from disk
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61688 Global build discarders configuration isn't loaded from disk Change By: Oliver Gondža Labels: lts 2.222.2 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205511.1585182181000.5676.1585904460324%40Atlassian.JIRA.
[JIRA] (JENKINS-61429) Unable to move/reorder steps within a job
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61429 Unable to move/reorder steps within a job Change By: Oliver Gondža Labels: lts 2.222.1 - candidate fixed regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205106.1583931628000.5670.1585903440340%40Atlassian.JIRA.
[JIRA] (JENKINS-60454) Jenkins.instance is missing after restart
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60454 Jenkins.instance is missing after restart Change By: Oliver Gondža Labels: lts 2.222.2 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203532.1576121478000.5664.1585903260345%40Atlassian.JIRA.
[JIRA] (JENKINS-61692) "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61692 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException Change By: Oliver Gondža Labels: lts 2.222.2 - candidate fixed regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205516.1585227401000.5660.1585902840216%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Oliver Gondža commented on JENKINS-61224 Re: "Monitors" terminology should not be used in GUI I am removing the `lts-candidate` as the is too minor to qualify for LTS backport. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204778.158264254.5652.1585902600235%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61224 "Monitors" terminology should not be used in GUI Change By: Oliver Gondža Labels: lts-candidate newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204778.158264254.5644.1585902540354%40Atlassian.JIRA.
[JIRA] (JENKINS-61279) Update version number dependency to 1.7
Title: Message Title Oliver Gondža commented on JENKINS-61279 Re: Update version number dependency to 1.7 Tim Jacomb, how does the deprecation manifests? It is a build warning for plugins depending on affected core version? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204854.1582987621000.5640.1585902240147%40Atlassian.JIRA.
[JIRA] (JENKINS-61279) Update version number dependency to 1.7
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61279 Update version number dependency to 1.7 Change By: Oliver Gondža The library changes https://github.com/jenkinsci/lib-version-number/compare/version-number-1.6...version-number-1.7 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204854.1582987621000.5637.1585902120226%40Atlassian.JIRA.
[JIRA] (JENKINS-60788) NullPointerException when hitting Check Now against a custom update center
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60788 NullPointerException when hitting Check Now against a custom update center Change By: Oliver Gondža Labels: lts 2.222.2 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204116.1579162845000.5635.1585901820289%40Atlassian.JIRA.
[JIRA] (JENKINS-61678) bitbucket build status notifier stopped working
Title: Message Title Alon Hoftman commented on JENKINS-61678 Re: bitbucket build status notifier stopped working This was resolved and the solution is a bit odd: A checkout (of even a single file) should occur before bitbucketStatusNotify(), only then the status accepts correctly. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205415.1585130395000.5626.1585899540671%40Atlassian.JIRA.
[JIRA] (JENKINS-61678) bitbucket build status notifier stopped working
Title: Message Title Alon Hoftman updated JENKINS-61678 Jenkins / JENKINS-61678 bitbucket build status notifier stopped working Change By: Alon Hoftman Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205415.1585130395000.5630.1585899540719%40Atlassian.JIRA.
