[JIRA] (JENKINS-50449) Post build steps appear in previous stage's steps
Title: Message Title
Paul Dragoonis commented on JENKINS-50449
Re: Post build steps appear in previous stage's steps
HI Vivek Pandey thanks for the comprehensive proposal: If I have a post{} after my main stages{} block .. I expect to see a stage for this on the UI. `if there is at least one post declarative stage` this means I need `>1` post{} ? but you can only have one post{} at the end of the pipeline, so I'm a little confused. Based on the following syntax ``` stages { } post { always { sh 'stuff'' } } ```
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50449) Post build steps appear in previous stage's steps
Title: Message Title
Paul Dragoonis edited a comment on JENKINS-50449
Re: Post build steps appear in previous stage's steps
HI [~vivek] thanks for the comprehensive proposal:If I have a post{} after my main stages{} block .. I expect to see a stage for this on the UI.`if there is at least one post declarative stage` this means I need `>1` post{} ? but you can only have one post{} at the end of the pipeline, so I'm a little confused.Based on the following syntax ``` {code} stages {}post {always { sh 'stuff''}} ``` {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41239) Error during always block skips execution of remaining steps
Title: Message Title Moritz Baumann commented on JENKINS-41239 Re: Error during always block skips execution of remaining steps Andrew Bayer thank you very much! While it doesn't fix the original issue, it very much fixes my use case. Especially the fact that `always` ran before `success` was giving me headaches. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Tobias Peitzsch commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification Antonio Muñiz: I would like to understand why it is not desirable to have 2 projects built by the same job? In my opinion it is a limitation as additional maintenance needed (DRY principle is not fulfilled) higher dependency to Jenkins / more Jenkins centric view e.g. multi branch has limitations (e.g. try to handle Subversion and GIT in one job) For me, Jenkins is a infrastructure tool. I use it to define where data shall be processed but not how. Representation of the result is not done with Jenkins (could this be the main reason to have one job per project?) E.g. my generalized workflow build is triggered by external tool build pulls data depending on provided parameters build processes data build pushes result to other tools (e.g. dashboard, artifactory ...) So in case of double builds / same data shall be processed twice I would like to abort one build. Unfortunately, it is not possible with the current implementation of the milestone. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50563) support declarative pipeline parameter definition
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-50563 support declarative pipeline parameter definition Issue Type: New Feature Assignee: Gesh Markov Components: maven-metadata-plugin Created: 2018-04-04 08:09 Priority: Minor Reporter: Dominik Bartholdi It would be very helpful to be able to define a maven-metadata parameter in declarative pipeline as described here: https://jenkins.io/doc/book/pipeline/syntax/#parameters I know I can do something similar with 'input', but it is not quite the same, as one has to wait for the pipeline to be running. Also I did not find any docu except this commit: https://github.com/jenkinsci/maven-metadata-plugin/commit/a74b2d65824d13f76e175c406983f104390854a0 Add Comment
[JIRA] (JENKINS-50563) support declarative pipeline parameter definition
Title: Message Title Dominik Bartholdi assigned an issue to Marc Rohlfs Jenkins / JENKINS-50563 support declarative pipeline parameter definition Change By: Dominik Bartholdi Assignee: Gesh Markov Marc Rohlfs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50528) Incorrect count of test results in the email body when Job runs in parallel instances
Title: Message Title David van Laatum commented on JENKINS-50528 Re: Incorrect count of test results in the email body when Job runs in parallel instances Need more info, but I suspect this is actually the unit test plugins as all those macros do is ask the unit test plugin for the info. If you are using pipeline parallel then unit test info will be the total for all branches at the time the email is sent. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50563) support declarative pipeline parameter definition
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-50563 support declarative pipeline parameter definition Change By: Dominik Bartholdi It would be very helpful to be able to define a maven-metadata parameter in declarative pipeline as described here:[https://jenkins.io/doc/book/pipeline/syntax/#parameters] I know I can do something similar with 'input', but it is not quite the same, as one has to wait for the pipeline to be running and the parameter is not visible in the job configuration . Also I did not find any docu except this commit: [https://github.com/jenkinsci/maven-metadata-plugin/commit/a74b2d65824d13f76e175c406983f104390854a0] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.go
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling. We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 25% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user/user/teams/user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25% of our API quota by the numbers I've been shown. As it is the plugin doesn't seem to scale to large orgs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg created an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-04-04 08:17 Environment: Jenkins 2.107.1 github-branch-source-plugin 2.3.3 Priority: Critical Reporter: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling. We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 25% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin: /user /user/teams /user/orgs This past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25% of our API quota by the numbers I've been shown. As it is the plugin doesn't seem to scale to large orgs.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 25% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25% of our API quota by the numbers I've been shown. As it is the plugin doesn't seem to scale to well for large orgs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 25% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The credentials drain seems worse around PRs. This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25% of our API quota by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 25% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The credentials drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25% of our API quota by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Robin Smith commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries rsandell will your changes fix loading shared libraries from a Bitbucket PR? Or should I raise a separate issue for that? It was possible to do this until version 3.6.4 of the plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 25% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The credentials drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25% of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Robin Smith edited a comment on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries [~rsandell] will your changes fix loading shared libraries from a Bitbucket PR? Or should I raise a separate issue for that? It was [ possible to [ do this|https://issues.jenkins-ci.org/browse/JENKINS-48061?focusedCommentId=327443&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-327443] until version 3.6.4 of the plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 25 75 % of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The credentials drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25% of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg Attachment: Github support reply with api usage stats.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg Attachment: Github support reply with api usage stats.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg Attachment: Github support reply with api usage stats.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg Attachment: Github support reply with api usage stats.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg Attachment: Github support reply with api usage stats.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 75% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The credentials drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25% of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Please see the attached conversation with Github Support for stats. The top three are just crazy compared to our other traffic. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 75% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The credentials drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 25 75 % of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Please see the attached conversation with Github Support for stats. The top three are just crazy compared to our other traffic. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50565) Jenkins proxy settings are ignored
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-50565 Jenkins proxy settings are ignored Issue Type: Bug Assignee: Stephen Connolly Attachments: Screen Shot 2018-04-04 at 09.44.53.png Components: gitea-plugin Created: 2018-04-04 08:45 Priority: Minor Reporter: Stephen Connolly The Jenkins proxy settings are ignored when connecting to Gitea. This is fine if your gitea server would be in the "No Proxy Host" section, but it is not fine if the proxy is required to connect to Gitea. Add Comment
[JIRA] (JENKINS-50565) Jenkins proxy settings are ignored
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-50565 Jenkins proxy settings are ignored Change By: Stephen Connolly The Jenkins proxy settings are ignored when connecting to Gitea.!Screen Shot 2018-04-04 at 09.44.53.png |width=600px !This is fine if your gitea server would be in the "No Proxy Host" section, but it is not fine if the proxy is required to connect to Gitea. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48135) kubernetes-plugin should support podTemplate in declarative templates
Title: Message Title Frederic Rousseau assigned an issue to Andrew Bayer Jenkins / JENKINS-48135 kubernetes-plugin should support podTemplate in declarative templates Change By: Frederic Rousseau Assignee: James Strachan Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50565) Jenkins proxy settings are ignored
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-50565 Jenkins proxy settings are ignored Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50565) Jenkins proxy settings are ignored
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50565 Re: Jenkins proxy settings are ignored Code changed in jenkins User: Stephen Connolly Path: CHANGES.md src/main/java/org/jenkinsci/plugin/gitea/client/impl/DefaultGiteaConnection.java http://jenkins-ci.org/commit/gitea-plugin/2a291d5d4784988d1e6ee87c95df388c8b902b40 Log: [FIXED JENKINS-50565] Use Jenkins proxy configuration Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48135) kubernetes-plugin should support podTemplate in declarative templates
Title: Message Title Frederic Rousseau commented on JENKINS-48135 Re: kubernetes-plugin should support podTemplate in declarative templates Changed assignee. indeed a lot of people, including me, are actively waiting the draft replacement for PR260 Andrew told us he'll come up with 2 months ago Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 75% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The credentials API drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 75% of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Please see the attached conversation with Github Support for stats. The top three are just crazy compared to our other traffic. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50560) add some docs to the readme on what kinds of Secrets are supported
Title: Message Title James Nord commented on JENKINS-50560 Re: add some docs to the readme on what kinds of Secrets are supported For now see https://github.com/jenkinsci/kubernetes-credentials-provider-plugin/tree/master/docs/examples Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 75% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The API drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 75% of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Please see the attached conversation with Github Support for stats. The top three are just crazy compared to our other traffic. * Edit: * I just had a thought. We are also using the Github Authentication plugin. Is there a way to determine definitively which of these two plugins is making these calls? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50560) add some docs to the readme on what kinds of Secrets are supported
Title: Message Title James Strachan commented on JENKINS-50560 Re: add some docs to the readme on what kinds of Secrets are supported how about for now copy/pasting that into the README? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 75% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The API drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 75% of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Please see the attached conversation with Github Support for stats. The top three are just crazy compared to our other traffic. Edit: I just had a thought. We are also using the Github Authentication plugin. Is there a way to determine definitively which of these two plugins is making these calls? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 75% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The API drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 75% of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Please see the attached conversation with Github Support for stats. The top three are just crazy compared to our other traffic.*Edit:* I just had a thought. We are also using the Github Authentication plugin. Is there a way to determine definitively which of these two plugins is making these calls? Happy to do some debugging and digging if necessary. Add Comment This message was sent by At
[JIRA] (JENKINS-50560) add some docs to the readme on what kinds of Secrets are supported
Title: Message Title James Nord commented on JENKINS-50560 Re: add some docs to the readme on what kinds of Secrets are supported you could have done a PR in the time it took to write that comment Readme tweaked. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50560) add some docs to the readme on what kinds of Secrets are supported
Title: Message Title James Strachan commented on JENKINS-50560 Re: add some docs to the readme on what kinds of Secrets are supported ditto to your first comment Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50560) add some docs to the readme on what kinds of Secrets are supported
Title: Message Title James Strachan closed an issue as Fixed Jenkins / JENKINS-50560 add some docs to the readme on what kinds of Secrets are supported Change By: James Strachan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50566) Google Compute Engine Plugin JEP-200 Class rejected
Title: Message Title Emil Wypych created an issue Jenkins / JENKINS-50566 Google Compute Engine Plugin JEP-200 Class rejected Issue Type: Bug Assignee: Evan Brown Attachments: Screen Shot 2018-04-04 at 11.21.09.png, Screen Shot 2018-04-04 at 11.21.20.png Components: google-compute-engine-plugin Created: 2018-04-04 09:24 Environment: Jenkins 2.107 - docker image Google Compute Engine Plugin - v. 1.0.1 Labels: JEP-200 Priority: Critical Reporter: Emil Wypych Google Compute Engine Plugin is affected by JEP-200, there you have full stacktrace: Apr 04, 2018 9:06:13 AM WARNING jenkins.security.ClassFilterImpl lambda$isBlacklisted$1 com.google.api.services.compute.model.Operation in file:/var/jenkins_home/plugins/google-compute-engine/WEB-INF/lib/google-api-services-compute-v1-rev165-1.22.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ Apr 04, 2018 9:06:13 AM WARNING org.eclipse.jetty.server.handler.ContextHandler$Context log Error while serving http://my-site.local/cloud/gce-Test-GCP/provision java.lang.UnsupportedOperationException: Refusing to marshal com.google.api.services.compute.model.Operation for security reasons; see https://jenkins.io/
[JIRA] (JENKINS-47055) Jenkins kubernetes plugin - support freestyle jobs
Title: Message Title Harry Stempher commented on JENKINS-47055 Re: Jenkins kubernetes plugin - support freestyle jobs Help me please. I use multi-container pods in freestyle jobs - the first container is jnlp, the second is mariadb. How to me to be connected from jnlp to mariadb? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50162) NUnit test results don't encode characters correctly in unit test report
Title: Message Title Shin-ichi Morita commented on JENKINS-50162 Re: NUnit test results don't encode characters correctly in unit test report I understand the difficulty. As the second best solution, how about converting negative values to unsigned ints in isValid()? input = input & 0xff; It would work for me as long as the character encoding is utf-8. Regards, Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50567) Docker cloud can get blocked by idleMinutes set to 0
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-50567 Docker cloud can get blocked by idleMinutes set to 0 Issue Type: Bug Assignee: Nicolas De Loof Components: docker-slaves-plugin Created: 2018-04-04 10:13 Priority: Major Reporter: Oliver Gondža When plugin gets configured with idleMinutes == 0, not only the agents get deleted sooner then they are launched turning the setup practically useless as reported in JENKINS-47953. It even seem to cause the provisioning for serviced labels to stuck almost completely. Here is what I observed is happening: Agents was created and launching yet disappearing instantly. The plugin was logging "No such container"[1] 3 times in a row, roughly for every botched node. Both stopped to happen after changing idleMinutes from 0 to 10. I presume the JENKINS-47953 kicked in deleting the container while provisioning was in progress. Eventually, and presumably because of this, all provisioning stopped with multiple pending launches that never completes[2][3] that are not done nor cancelled and yet they do not have a running thread in stacktrace. This is causing the plannedCapacity > demand so nothing else is provisioned. I admit a do not quite understand how did the futures get in such state but this too stopped occurring right after fixing idleMinutes and canc
[JIRA] (JENKINS-50567) Docker cloud can get blocked by idleMinutes set to 0
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-50567 Docker cloud can get blocked by idleMinutes set to 0 Change By: Oliver Gondža Component/s: docker-plugin Component/s: docker-slaves-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32710) Configure AD Authorization with Groovy
Title: Message Title Vishwadeep Bansal reopened an issue import jenkins.model.import hudson.security.*import hudson.plugins.active_directory. def instance = Jenkins.getInstance()String domain = 'my.domain.com'String site = 'site'String server = '192.168.1.1'String bindName = 'acco...@my.domain.com'String bindPassword = 'password' adrealm = new ActiveDirectorySecurityRealm(domain, site, bindName, bindPassword, server) instance.setSecurityRealm(adrealm) I am doing automated AD integration with the code mentioned above, however getting issues. bindName is not getting updated on the page and authentication do not work. Jenkins / JENKINS-32710 Configure AD Authorization with Groovy Change By: Vishwadeep Bansal Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-32710) Configure AD Authorization with Groovy
Title: Message Title Vishwadeep Bansal edited a comment on JENKINS-32710 Re: Configure AD Authorization with Groovy import jenkins.model.*import hudson.security.*import hudson.plugins.active_directory.* def instance = Jenkins.getInstance()String domain = 'my.domain.com'String site = 'site'String server = '192.168.1.1'String bindName = 'acco...@my.domain.com'String bindPassword = 'password'adrealm = new ActiveDirectorySecurityRealm(domain, site, bindName, bindPassword, server)instance.setSecurityRealm(adrealm)I am doing automated AD integration with the code mentioned above, however getting issues. bindName is not getting updated on the page and authentication do not work. Also I would like to keep the script in init.groovy.d folder so that it could do the charm when service starts. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50541) Pipeline failing - due to java.io.NotSerializableException
Title: Message Title Alexey Vishnaikov commented on JENKINS-50541 Re: Pipeline failing - due to java.io.NotSerializableException Thank you for quick answer. Sometimes it is very hard to understand where problem is located. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49977) Deserialization of hudson.model.ParametersDefinitionProperty$1
Title: Message Title Reinhold Füreder commented on JENKINS-49977 Re: Deserialization of hudson.model.ParametersDefinitionProperty$1 Since I still get this warning: 2018-04-04 12:26:59 WARNING [org.jenkinsci.remoting.util.AnonymousClassWarnings warn] Attempt to (de-)serialize anonymous class hudson.model.ParametersDefinitionProperty$1 in file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.114.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Is that OK? Or when is it still expected to pop up (e.g. solely due to looking at pipeline job in classic UI via stage view for instance)? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50562) logstash-plugin does not work with elasticsearch 6
Title: Message Title Jakub Bochenski commented on JENKINS-50562 Re: logstash-plugin does not work with elasticsearch 6 Per https://github.com/logstash-plugins/logstash-input-http/blob/master/lib/logstash/inputs/http.rb Logstash should also accept PUT Still because the documentation is talking about POSTing it should be safer to have the HTTP method configurable Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29963) MatrixProject builds previous revision in pull request
Title: Message Title Marshall Galbraith closed an issue as Fixed Jenkins / JENKINS-29963 MatrixProject builds previous revision in pull request Change By: Marshall Galbraith Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Antonio Muñiz commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification additional maintenance needed (DRY principle is not fulfilled) Not necessarily. Use a shared library loaded from a separated SCM, then create a really simple Jenkinsfile on each project (this is the approach of the Jenkins Plugins project, this is the Jenkinsfile for the milestone plugin for example). Maintenance would be mostly centralized in the shared library. higher dependency to Jenkins / more Jenkins centric view Can you elaborate? I see the same grade of dependency in both approaches. multi branch has limitations (e.g. try to handle Subversion and GIT in one job) You can use more than one call to `checkout` step to get Git and Subversion workspaces in the same pipeline. What's the limitation? I use it to define where data shall be processed but not how Pipelines are designed to define "how" the project is built (among other things), not sure what other use you could do of it. So in case of double builds Why would you have double builds? A commit in a specific repository should trigger a single build in the corresponding job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50508) 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed
Title: Message Title Alexander Willhaug commented on JENKINS-50508 Re: 3.5.0 regression: NPE on withMaven step when after specifying "openTasksPublisher" and "tasks scanner plugin" not installed The same problem if Findbugs Plugin is not installed and findbugsPublisher(disabled: true) Please correct NPE. Best regards, Alex Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50554) Cant expand to multi lines "warnings to ignore" field
Title: Message Title Ulli Hafner resolved as Won't Fix The next major release will have a totally new UI. Then you can specify multiple ignores using a + button (like the other repeatable items in Jenkins' UI). Jenkins / JENKINS-50554 Cant expand to multi lines "warnings to ignore" field Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-50554) Cant expand to multi lines "warnings to ignore" field
Title: Message Title Ulli Hafner edited a comment on JENKINS-50554 Re: Cant expand to multi lines "warnings to ignore" field The next major release will have a totally new UI. Then you can specify multiple ignores using a + button (like the other repeatable items in Jenkins' UI). This field does not exist anymore. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33969) claim-plugin cannot be used with pipelines (workflows)
Title: Message Title
Steve Boardwell commented on JENKINS-33969
Re: claim-plugin cannot be used with pipelines (workflows)
As a side note, the ClaimPublisher step needs a node to work meaning it will fail if you are
using the declarative pipeline
using stage-based agents (setting agent none under the global pipeline declaration)
you will need to put the step in a node closure
pipeline {
agent none
stages {
stage('Build') {
agent any
steps {
bat 'exit 1;'
}
}
}
post {
always {
// need the node closure here because agent none was set above
node {
step([$class: 'ClaimPublisher'])
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50568) Receiving Workers thread are not reconfigurable without Jenkins restart
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-50568 Receiving Workers thread are not reconfigurable without Jenkins restart Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 2018-04-04 12:14 Environment: gerrit-trigger-plugin 2.27.5 Priority: Major Reporter: Markus Winter We today had the problem that the receiving workers queue was somehow stuck and we have piled up 800k events. After reconnecting the event listener events were processed again, but with only 8 threads and 18k jobs it would take over 10h to process all events (even though 99% of the events are replication events which are not of interest for us). Changing the # of receiving worker threads has no effect. Looking at the code this requires a restart of Jenkins. JENKINS-20120 only solved the thing for the sending queue Add Comment
[JIRA] (JENKINS-6918) optionalBlock tag is not initialized correctly when declared within a radioBlock
Title: Message Title Stefan Eder commented on JENKINS-6918 Re: optionalBlock tag is not initialized correctly when declared within a radioBlock This happens also when nesting a radioBlock inside an optionalBlock. Every nested item of the radioBlocks inside the optionalBlocks are shown, whether or not they are selected. However, selecting a specific radioBlock item again leads to the desired state of only the selected radioBlock item showing its nested items. Tested on Jenkins 2.73.2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50569) AccessDeniedException when copying VCS dir
Title: Message Title
Rafael Pestano created an issue
Jenkins / JENKINS-50569
AccessDeniedException when copying VCS dir
Issue Type:
Bug
Assignee:
Unassigned
Components:
last-changes-plugin
Created:
2018-04-04 12:21
Priority:
Minor
Reporter:
Rafael Pestano
Some times LastChanges throws java.nio.file.AccessDeniedException at this line: {{ vcsTargetDir = new FilePath(new File(workspaceTargetDir.getRemote() + "/.svn")); vcsDirFound.copyRecursiveTo("*/", vcsTargetDir); }} It looks like it is related to slave, need to confirm that. Following is full stacktrace: {{java.nio.file.AccessDeniedException: /var/procergs/build-tools/jenkins/jobs/apm-pipeline/builds/34/.svn/all-wcprops at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434) at java.nio.file.Files.newOutputStream(Files.java:216) at hudson.util.IOUtils.copy(IOUtils.java:39) at hudson.FilePath.readFromTar(FilePath.java:2307) Caused: java.io.IOException: Failed to extract /var/procergs/build-tools-2/workspace/apm-pipeline/.svn/*/ at hudson.FilePath.readFromTar(FilePath.java:2317) at hudson.FilePath.copyRecursiveTo(FilePath.java:2221) at hudson.FilePath.copyRecursiveTo(FilePath.java:2124) at hudson.FilePath.copyRecursiveTo(FilePath.java:2107) at com.github.jenkins.lastchanges.LastChangesPublisher.perform(LastChangesPublisher.java:169) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.w
[JIRA] (JENKINS-50569) AccessDeniedException when copying VCS dir
Title: Message Title
Rafael Pestano updated an issue
Jenkins / JENKINS-50569
AccessDeniedException when copying VCS dir
Change By:
Rafael Pestano
Some times LastChanges throws java.nio.file.AccessDeniedException at [this line|https://github.com/jenkinsci/last-changes-plugin/blob/2e0f1c1c58d7a1ccda8118f98d874951a4dab7f6/src/main/java/com/github/jenkins/lastchanges/LastChangesPublisher.java#L169]: bq. vcsTargetDir = new FilePath(new File(workspaceTargetDir.getRemote() + "/.svn"));bq. vcsDirFound.copyRecursiveTo("**/*", vcsTargetDir); It looks like it is related to slave, need to confirm that. Following is full stacktrace: {{ bq. java.nio.file.AccessDeniedException: /var/procergs/build-tools/jenkins/jobs/apm-pipeline/builds/34/.svn/all-wcprops bq. at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) bq. at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) bq. at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) bq. at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) bq. at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434) bq. at java.nio.file.Files.newOutputStream(Files.java:216) bq. at hudson.util.IOUtils.copy(IOUtils.java:39) bq. at hudson.FilePath.readFromTar(FilePath.java:2307) bq. Caused: java.io.IOException: Failed to extract /var/procergs/build-tools-2/workspace/apm-pipeline/.svn/**/* bq. at hudson.FilePath.readFromTar(FilePath.java:2317) bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2221) bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2124) bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2107) bq. at com.github.jenkins.lastchanges.LastChangesPublisher.perform(LastChangesPublisher.java:169) bq. at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) bq. at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) bq. at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) bq. at hudson.security.ACL.impersonate(ACL.java:260) bq. at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) bq. at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) bq. at java.util.concurrent.FutureTask.run(FutureTask.java:266) bq. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) bq. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) bq. at java.lang.Thread.run(Thread.java:748) }}
[JIRA] (JENKINS-50569) AccessDeniedException when copying VCS dir
Title: Message Title
Rafael Pestano updated an issue
Jenkins / JENKINS-50569
AccessDeniedException when copying VCS dir
Change By:
Rafael Pestano
Some times LastChanges throws java.nio.file.AccessDeniedException at [this line|https://github.com/jenkinsci/last-changes-plugin/blob/2e0f1c1c58d7a1ccda8118f98d874951a4dab7f6/src/main/java/com/github/jenkins/lastchanges/LastChangesPublisher.java#L169]: {{ bq. vcsTargetDir = new FilePath(new File(workspaceTargetDir.getRemote() + "/.svn")); bq. vcsDirFound.copyRecursiveTo("**/*", vcsTargetDir); }} It looks like it is related to slave, need to confirm that. Following is full stacktrace:{{ java.nio.file.AccessDeniedException: /var/procergs/build-tools/jenkins/jobs/apm-pipeline/builds/34/.svn/all-wcprops at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434) at java.nio.file.Files.newOutputStream(Files.java:216) at hudson.util.IOUtils.copy(IOUtils.java:39) at hudson.FilePath.readFromTar(FilePath.java:2307)Caused: java.io.IOException: Failed to extract /var/procergs/build-tools-2/workspace/apm-pipeline/.svn/**/* at hudson.FilePath.readFromTar(FilePath.java:2317) at hudson.FilePath.copyRecursiveTo(FilePath.java:2221) at hudson.FilePath.copyRecursiveTo(FilePath.java:2124) at hudson.FilePath.copyRecursiveTo(FilePath.java:2107) at com.github.jenkins.lastchanges.LastChangesPublisher.perform(LastChangesPublisher.java:169) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) }}
[JIRA] (JENKINS-50569) AccessDeniedException when copying VCS dir
Title: Message Title
Rafael Pestano updated an issue
Jenkins / JENKINS-50569
AccessDeniedException when copying VCS dir
Change By:
Rafael Pestano
Some times LastChanges throws java.nio.file.AccessDeniedException at [this line|https://github.com/jenkinsci/last-changes-plugin/blob/2e0f1c1c58d7a1ccda8118f98d874951a4dab7f6/src/main/java/com/github/jenkins/lastchanges/LastChangesPublisher.java#L169]: bq. vcsTargetDir = new FilePath(new File(workspaceTargetDir.getRemote() + "/.svn"));bq. vcsDirFound.copyRecursiveTo("**/*", vcsTargetDir); //here is where the exception is raised It looks like it is related to slave, need to confirm that. Following is full stacktrace:bq. java.nio.file.AccessDeniedException: /var/procergs/build-tools/jenkins/jobs/apm-pipeline/builds/34/.svn/all-wcpropsbq. at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)bq. at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)bq. at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)bq. at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)bq. at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)bq. at java.nio.file.Files.newOutputStream(Files.java:216)bq. at hudson.util.IOUtils.copy(IOUtils.java:39)bq. at hudson.FilePath.readFromTar(FilePath.java:2307)bq. Caused: java.io.IOException: Failed to extract /var/procergs/build-tools-2/workspace/apm-pipeline/.svn/**/*bq. at hudson.FilePath.readFromTar(FilePath.java:2317)bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2221)bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2124)bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2107)bq. at com.github.jenkins.lastchanges.LastChangesPublisher.perform(LastChangesPublisher.java:169)bq. at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)bq. at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)bq. at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49)bq. at hudson.security.ACL.impersonate(ACL.java:260)bq. at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46)bq. at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)bq. at java.util.concurrent.FutureTask.run(FutureTask.java:266)bq. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)bq. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)bq. at java.lang.Thread.run(Thread.java:748) LastChanges 2.6.1
[JIRA] (JENKINS-50569) AccessDeniedException when copying VCS dir
Title: Message Title
Rafael Pestano updated an issue
Jenkins / JENKINS-50569
AccessDeniedException when copying VCS dir
Change By:
Rafael Pestano
Some times LastChanges throws java.nio.file.AccessDeniedException at [this line|https://github.com/jenkinsci/last-changes-plugin/blob/2e0f1c1c58d7a1ccda8118f98d874951a4dab7f6/src/main/java/com/github/jenkins/lastchanges/LastChangesPublisher.java#L169]: bq. vcsTargetDir = new FilePath(new File(workspaceTargetDir.getRemote() + "/.svn"));bq. vcsDirFound.copyRecursiveTo("**/*", vcsTargetDir); //here is where the exception is raised It looks like it is related to slave, need to confirm that. Following is full stacktrace:bq. java.nio.file.AccessDeniedException: /var/procergs/build-tools/jenkins/jobs/apm-pipeline/builds/34/.svn/all-wcpropsbq. at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)bq. at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)bq. at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)bq. at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)bq. at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)bq. at java.nio.file.Files.newOutputStream(Files.java:216)bq. at hudson.util.IOUtils.copy(IOUtils.java:39)bq. at hudson.FilePath.readFromTar(FilePath.java:2307)bq. Caused: java.io.IOException: Failed to extract /var/procergs/build-tools-2/workspace/apm-pipeline/.svn/**/*bq. at hudson.FilePath.readFromTar(FilePath.java:2317)bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2221)bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2124)bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2107)bq. at com.github.jenkins.lastchanges.LastChangesPublisher.perform(LastChangesPublisher.java:169)bq. at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)bq. at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)bq. at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49)bq. at hudson.security.ACL.impersonate(ACL.java:260)bq. at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46)bq. at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)bq. at java.util.concurrent.FutureTask.run(FutureTask.java:266)bq. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)bq. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)bq. at java.lang.Thread.run(Thread.java:748) Environment:Jenkins 2.89.3 LastChanges 2.6.1
[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Carlos Sanchez started work on JENKINS-50525 Change By: Carlos Sanchez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50569) AccessDeniedException when copying VCS dir
Title: Message Title
Rafael Pestano updated an issue
Jenkins / JENKINS-50569
AccessDeniedException when copying VCS dir
Change By:
Rafael Pestano
Some times LastChanges throws java.nio.file.AccessDeniedException at [this line|https://github.com/jenkinsci/last-changes-plugin/blob/2e0f1c1c58d7a1ccda8118f98d874951a4dab7f6/src/main/java/com/github/jenkins/lastchanges/LastChangesPublisher.java#L169]: bq. {code:java} vcsTargetDir = new FilePath(new File(workspaceTargetDir.getRemote() + "/.svn")); bq. vcsDirFound.copyRecursiveTo("**/*", vcsTargetDir); //here is where the exception is raised {code} It looks like it is related to slave, need to confirm that. Following is full stacktrace: bq. {noformat} java.nio.file.AccessDeniedException: /var/procergs/build-tools/jenkins/jobs/apm-pipeline/builds/34/.svn/all-wcprops bq. at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) bq. at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) bq. at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) bq. at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) bq. at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434) bq. at java.nio.file.Files.newOutputStream(Files.java:216) bq. at hudson.util.IOUtils.copy(IOUtils.java:39) bq. at hudson.FilePath.readFromTar(FilePath.java:2307) bq. Caused: java.io.IOException: Failed to extract /var/procergs/build-tools-2/workspace/apm-pipeline/.svn/**/* bq. at hudson.FilePath.readFromTar(FilePath.java:2317) bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2221) bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2124) bq. at hudson.FilePath.copyRecursiveTo(FilePath.java:2107) bq. at com.github.jenkins.lastchanges.LastChangesPublisher.perform(LastChangesPublisher.java:169) bq. at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) bq. at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) bq. at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) bq. at hudson.security.ACL.impersonate(ACL.java:260) bq. at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) bq. at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) bq. at java.util.concurrent.FutureTask.run(FutureTask.java:266) bq. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) bq. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) bq. at java.lang.Thread.run(Thread.java:748) {noformat} Environment:Jenkins 2.89.3 LastChanges 2.6.1
[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Carlos Sanchez updated JENKINS-50525 Jenkins / JENKINS-50525 Error When Provisioning Slave: mountPath: Required value Change By: Carlos Sanchez Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50566) Google Compute Engine Plugin JEP-200 Class rejected
Title: Message Title Emil Wypych commented on JENKINS-50566 Re: Google Compute Engine Plugin JEP-200 Class rejected This is the list of affected classes - it's not complete. Just cannot dig deeper... com.google.api classes are easy to fix, but I don't know what about java.lang.* com.google.api.client.googleapis.javanet.GoogleNetHttpTransport com.google.api.client.googleapis.services.AbstractGoogleClientRequest com.google.api.client.googleapis.services.GoogleClientRequestInitializer com.google.api.services.compute.model.AcceleratorType com.google.api.services.compute.Compute com.google.api.services.compute.model.Instance com.google.api.client.json.jackson.JacksonFactory com.google.api.client.util.PemReader com.google.api.services.compute.model.Network com.google.api.services.compute.model.Subnetwork com.google.api.services.compute.model.Image com.google.api.services.compute.model.Operation com.google.api.client.util.ArrayMap com.google.api.client.util.ClassInfo java.util.IdentityHashMap com.google.api.client.util.FieldInfo java.lang.reflect.Field Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr.
[JIRA] (JENKINS-33023) Enums are not supported in sandbox
Title: Message Title Magnus Reftel assigned an issue to Andrew Bayer Jenkins / JENKINS-33023 Enums are not supported in sandbox Change By: Magnus Reftel Assignee: Magnus Reftel Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50566) Google Compute Engine Plugin JEP-200 Class rejected
Title: Message Title Oleg Nenashev commented on JENKINS-50566 Re: Google Compute Engine Plugin JEP-200 Class rejected I cannot imagine wy the plugin would need to persist "java.lang.reflect.Field", likely needs to be fixed. IdentityHashMap could be whitelisted. Regarding google classes, things like PemReader indicate that likely there are issues with transient fields in the plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50566) Google Compute Engine Plugin JEP-200 Class rejected
Title: Message Title Oleg Nenashev edited a comment on JENKINS-50566 Re: Google Compute Engine Plugin JEP-200 Class rejected I cannot imagine wy the plugin would need to persist "java.lang.reflect.Field", likely needs to be fixed. IdentityHashMap could be whitelisted.Regarding google classes, things like PemReader indicate that likely there are issues with transient fields in the plugin (likely anon classes are passed) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50566) Google Compute Engine Plugin JEP-200 Class rejected
Title: Message Title Emil Wypych commented on JENKINS-50566 Re: Google Compute Engine Plugin JEP-200 Class rejected There is a full stacktrace with "java.lang.reflect.Field": java.lang.UnsupportedOperationException: Refusing to marshal java.lang.reflect.Field for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) Caused: java.lang.RuntimeException: Failed to serialize com.google.api.client.util.FieldInfo#field for class com.google.api.client.util.FieldInfo at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.reflection.SerializableConverter$1.writeToStream(SerializableConverter.java:140) at com.thoughtworks.xstream.core.util.CustomObjectOutputStream.writeObjectOverride(CustomObjectOutputStream.java:84) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344) at java.util.IdentityHashMap.writeObject(IdentityHashMap.java:1289) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call java.util.IdentityHashMap.writeObject() : Failed to serialize com.google.api.client.util.FieldInfo#field for class com.google.api.client.util.FieldInfo Debugging information message : Could not call java.util.IdentityHashMap.writeObject() cause-exception : java.lang.RuntimeException cause-message : Failed to serialize com.google.api.client.util.FieldInfo#field for class com.google.api.client.util.FieldInfo --- at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(Seri
[JIRA] (JENKINS-50379) Jenkins kills long running sh script with no output
Title: Message Title Evan Ward commented on JENKINS-50379 Re: Jenkins kills long running sh script with no output Daniel Beck the script initially generates some output to show that it started and then generates no output for a long time. I think this has the same effect as your suggestion of using echo. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50564) Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs
Title: Message Title David Sanftenberg updated an issue Jenkins / JENKINS-50564 Branch Source Plugin is blowing away our Github API quota in minutes by spamming requests to /user, /user/teams, and /user/orgs Change By: David Sanftenberg We have a Github organization with about 100 users and 163 repos. There's a fair amount of traffic here, with many PRs being built daily. We have webhooks enabled to our Jenkins instance and have disabled all repo scanning / SCM polling.We've been experiencing rapid drains of our Github API quota and queried Github to determine the source of the calls. 75% of our hourly quota is being burned by calls to the following endpoints by the Branch Source Plugin:/user /user/teams /user/orgsThis past week I've seen the quota drained to zero from 3000 in mere minutes when several PRs are being built at once. The API drain seems worse around PRs.This seems like a caching problem, in that I imagine there isn't any. A configurable credentials cache would reduce fully 75% of our API quota usage by the numbers I've been shown.As it is the plugin doesn't seem to scale well for large orgs. It is becoming unusable. Please see the attached conversation with Github Support for stats. The top three are just crazy compared to our other traffic. *Edit:* I just had a thought. We are also using the Github Authentication plugin. Is there a way to determine definitively which of these two plugins is making these calls? Happy to do some debugging and digging if necessary. Add Comment This message was sent
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title Reinhold Füreder commented on JENKINS-47286 Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view Ben Keil Great + thanks! Some questions and comments WRT https://github.com/comquent/imperative-when: James Dumay org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME) is annotated with @Restricted(NoExternalUse.class) => I assume one therefore should not and cannot rely on this method being available forever. However, since this approach seems to work very well or would be at least an acceptable workaround for scripted pipelines, how are the chances that this will be get part of the official API (via removing this annotation?) or might even get used/wrapped by a new official API? James Dumay The mouse over hovering text in blue ocean shows "common.state.skipped": Since I also get this in a little declarative pipeline prototype I guess this is a minor bug (missing translation, or – maybe even better/preferable – missing to state the reason for the skipping) and not a side effect of (ab-)using this method in the wrong context? @ All: I am wondering why the body closure evaluation is coded with delegation based on config map in this example!? @ All: The STAGE_NAME is an unknown property in class section of shared library (that is not in "vars" section) but works in "Jenkinsfile" – I guess that is due to some transformation magic applied on "vars" section? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50379) Jenkins kills long running sh script with no output
Title: Message Title Daniel Beck commented on JENKINS-50379 Re: Jenkins kills long running sh script with no output Evan Ward I expect so. Thanks for the clarification. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50566) Google Compute Engine Plugin JEP-200 Class rejected
Title: Message Title Oleg Nenashev commented on JENKINS-50566 Re: Google Compute Engine Plugin JEP-200 Class rejected AFAICT all problems come from the Launcher classes, which includes com.google.api.services.compute.model.Operation and the referenced chain of classes. But maybe there are other entries as well. It should be relatively easy to write a unit test and to capture at least some missing classes, but things like JacksonFactory worry me a lot. at hudson.XmlFile.write(XmlFile.java:200) at jenkins.model.Nodes.persistNode(Nodes.java:160) at jenkins.model.Nodes.addNode(Nodes.java:142) at jenkins.model.Jenkins.addNode(Jenkins.java:2054) at com.google.jenkins.plugins.computeengine.ComputeEngineCloud.doProvision(ComputeEngineCloud.java:283) The entire idea to Serialize Cloud agents to disk is a bit questionable, but there is some logic dependent on it. Note that Google OAuth plugin is also affected by JEP-200 (JENKINS-50216). Without it this plugin cannot work AFAICT, at least in some cases. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.goo
[JIRA] (JENKINS-46587) Allow to stash/unstash without using the workspace in Jenkins
Title: Message Title Jesse Glick resolved as Won't Do There is an external workspace plugin which is designed for Pipeline and is usable if you are able to set up shared mounts. The Artifact Manager over S3 plugin (under development) also allows stashes to be kept in AWS S3 rather than on the Jenkins home filesystem. In either case you of course need to use the workspace as a source of files when stashing, and as a destination when unstashing, so the RFE as reported makes little sense. Jenkins / JENKINS-46587 Allow to stash/unstash without using the workspace in Jenkins Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50559) Authorization Folder property for Multibranch jobs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50559 Authorization Folder property for Multibranch jobs Change By: Jesse Glick Component/s: workflow-multibranch-plugin Labels: authorization folders permissions pipeline h3. Request I would like to set up Authorization ([Authorize Project plugin|https://plugins.jenkins.io/authorize-project]) for a Multibranch item. Setting up authorization at multibranch level is required to prevent branch projects to be able to build ANY project in the system. h3. WorkaroundA workaround is to set the Authorize project property from the Jenkinsfile but there is no special support for multibranch projects. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-37718) Block Pipeline job while upstream or downstream projects are building
Title: Message Title Steve Berube commented on JENKINS-37718 Re: Block Pipeline job while upstream or downstream projects are building This would be very useful for us as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49805) Prototype error telemetry logging with a Java Util Logger configuration
Title: Message Title Baptiste Mathus updated JENKINS-49805 Jenkins / JENKINS-49805 Prototype error telemetry logging with a Java Util Logger configuration Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50294) Design (JEP) how to determine the "health level" of Jenkins
Title: Message Title Baptiste Mathus started work on JENKINS-50294 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50410) Periods of high load cause "Invalid virtual machine image" exceptions
Title: Message Title R. Tyler Croy commented on JENKINS-50410 Re: Periods of high load cause "Invalid virtual machine image" exceptions Our max configured agents was 50 at this time. We were not making thousands of VMs an hour. The problem here, in my opinion, could be two-fold: The plugin is making lots of ARM API requests The plugin is not handling rate-limiting gracefully. Perhaps there's something that's polling and iterating over each agent? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50480) UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.*
Title: Message Title Viktor Sadovnikov commented on JENKINS-50480 Re: UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.* It was a mistake on my side : old libraries of the plugin were still available. Clean installation of 1.1.3 (and upgrading its dependencies) resolved the problem. Though now I'm not sure about the purpose of https://github.com/jenkinsci/docker-plugin/pull/619, which was merged after 1.1.3 is released Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49805) Prototype error telemetry logging with a Java Util Logger configuration
Title: Message Title Baptiste Mathus commented on JENKINS-49805 Re: Prototype error telemetry logging with a Java Util Logger configuration Status update: after some experimentation, I submitted a JEP for review on the dev ML https://groups.google.com/forum/#!msg/jenkinsci-dev/IrNOfrlgEEw/MiR5wDiXAQAJ The implementation for demonstration of feasibility is filed at https://github.com/jenkins-infra/evergreen/pull/43 on evergreen, using https://github.com/batmat/essentials-plugin on my GH account for now before I have the community agreement it's the right path, and I move it to the jenkinsci org. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50480) UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.*
Title: Message Title Oleg Nenashev commented on JENKINS-50480 Re: UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.* Viktor Sadovnikov this PR has been reverted, so 1.1.4 won't include this code anyway Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50570) WARNING: Failed to monitor master for Free Swap Space. No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32
Title: Message Title Drew Ritter created an issue Jenkins / JENKINS-50570 WARNING: Failed to monitor master for Free Swap Space. No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32 Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-04-04 13:58 Environment: Customer updated to the latest Long-Term Support version, 2.107.1, and is experiencing this warning with our NonStop platform. Labels: jenkins memory Priority: Minor Reporter: Drew Ritter This exception is thrown by Jenkins to indicate that memory monitor inside Jenkins is unable to find "/proc/meminfo" or "top" command on nonstop platform. INFO: Jenkins is fully up and running Mar 28, 2018 12:44:28 PM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor WARNING: Failed to monitor master for Free Swap Space java.util.concurrent.ExecutionException: java.io.IOException: No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32 at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:206) at hudson.remoting.LocalChannel$2.get(LocalChannel.java:81) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:96) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305) Caused by: java.io.IOException: No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32 at org.jvnet.hudson.MemoryMonitor.obtain(MemoryMonitor.java:91
[JIRA] (JENKINS-50533) YAML definition of jnlp container isn't updated with env variables and arguments
Title: Message Title Carlos Sanchez started work on JENKINS-50533 Change By: Carlos Sanchez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50494) Ensure registration is persisted to the database
Title: Message Title R. Tyler Croy updated JENKINS-50494 Jenkins / JENKINS-50494 Ensure registration is persisted to the database Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50543) Document the runPCT step design
Title: Message Title Raul Arabaolaza started work on JENKINS-50543 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50325) Some part of the code uses object.assign which needs to be polyfill to support IE11
Title: Message Title Vivek Pandey updated JENKINS-50325 Jenkins / JENKINS-50325 Some part of the code uses object.assign which needs to be polyfill to support IE11 Change By: Vivek Pandey Status: Resolved In Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50570) WARNING: Failed to monitor master for Free Swap Space. No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32
Title: Message Title Drew Ritter updated an issue Jenkins / JENKINS-50570 WARNING: Failed to monitor master for Free Swap Space. No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32 Had "Epic Link" set to HPE Plugin Pipeline, but with a closer look saw that that has to do with MicroFocus plugins. Linking to Pipeline Compatibility now, since that is the closest description I could find. If this needs to be changed, please let me know. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50325) Some part of the code uses object.assign which needs to be polyfill to support IE11
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-50325 Some part of the code uses object.assign which needs to be polyfill to support IE11 Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 3 , Blue Ocean 1.6 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50325) Some part of the code uses object.assign which needs to be polyfill to support IE11
Title: Message Title Vivek Pandey commented on JENKINS-50325 Re: Some part of the code uses object.assign which needs to be polyfill to support IE11 https://github.com/jenkinsci/blueocean-plugin/pull/1698 is not merged yet, its pending ATH tests. Once merged we can cherry pick to release/1.5 branch. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50570) WARNING: Failed to monitor master for Free Swap Space. No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32
Title: Message Title Drew Ritter updated an issue Jenkins / JENKINS-50570 WARNING: Failed to monitor master for Free Swap Space. No suitable implementation found: os.name=NONSTOP_KERNEL os.arch=x86_64N sun.arch.data.model=32 Change By: Drew Ritter Comment: Had "Epic Link" set to HPE Plugin Pipeline, but with a closer look saw that that has to do with MicroFocus plugins. Linking to Pipeline Compatibility now, since that is the closest description I could find. If this needs to be changed, please let me know. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49863) Include a Pipeline Shared Library to provide additional useful (community managed) Pipeline steps
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49863 Include a Pipeline Shared Library to provide additional useful (community managed) Pipeline steps Change By: R. Tyler Croy Sprint: Blue Ocean Essentials - Candidates Milestone 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49265) Investigate incorporating the Metrics plugin into Essentials for metrics/instrumentation
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49265 Investigate incorporating the Metrics plugin into Essentials for metrics/instrumentation Change By: R. Tyler Croy Sprint: Blue Ocean Essentials - Candidates Milestone 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50544) Update pipeline-library doc to include all changes and code consolidation derived from the new runPCT step
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-50544 Update pipeline-library doc to include all changes and code consolidation derived from the new runPCT step Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50543) Document the runPCT step design
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-50543 Document the runPCT step design Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50571) Add support of Configuration-as-Code in Artifact Manager S3
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-50571 Add support of Configuration-as-Code in Artifact Manager S3 Change By: Oleg Nenashev Assignee: Jesse Glick Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49853) Provide a cloud-friendly installation for AWS
Title: Message Title R. Tyler Croy assigned an issue to Baptiste Mathus Jenkins / JENKINS-49853 Provide a cloud-friendly installation for AWS Change By: R. Tyler Croy Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50571) Add support of Configuration-as-Code in Artifact Manager S3
Title: Message Title Oleg Nenashev started work on JENKINS-50571 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
