[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert commented on JENKINS-41308 Re: support Use Groovy Sandbox scripts in activeChoiceParams It is actually not fully supported by Dynamic DSL and causes problems like not showing up or not being able to be used due to conflicts. The Pull Request works, there is obviously a real need for this fix (see all the people having issues with Dynamic DSL and the ugliness of the Configure block (causing other problems for example with other plugins). Existing functionality and tests are unchanged with the PR. What is the real reason this is being closed? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.2743.1583740860362%40Atlassian.JIRA.
[JIRA] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title Daniel Steiert commented on JENKINS-26535 Re: DescribableHelper does not handle wildcards well We have an issue which depends on this in a few ways. Without it being fixed, we are stuck with a Jenkins that keeps rerunning a whole bunch of jobs every day for no reason besides it being a bug. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160203.1421868708000.4795.1583324160491%40Atlassian.JIRA.
[JIRA] (JENKINS-61119) Cannot configure Bitbucket ForkPullRequestDiscoveryTrait by using Job DSL dynamic API
Title: Message Title Daniel Steiert commented on JENKINS-61119 Re: Cannot configure Bitbucket ForkPullRequestDiscoveryTrait by using Job DSL dynamic API We have the same problem. Where is the bump button? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204634.1582018032000.4788.1583324040266%40Atlassian.JIRA.
[JIRA] (JENKINS-61119) Cannot configure Bitbucket ForkPullRequestDiscoveryTrait by using Job DSL dynamic API
Title: Message Title Daniel Steiert commented on JENKINS-61119 Re: Cannot configure Bitbucket ForkPullRequestDiscoveryTrait by using Job DSL dynamic API Joseph Petersen, I updated the link to reflect that fact. The linking was saying this ticket block JENKINS-26535, which is not the way it should be I guess, correct? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204634.1582018032000.4770.1583323680378%40Atlassian.JIRA.
[JIRA] (JENKINS-61119) Cannot configure Bitbucket ForkPullRequestDiscoveryTrait by using Job DSL dynamic API
Title: Message Title Daniel Steiert edited a comment on JENKINS-61119 Re: Cannot configure Bitbucket ForkPullRequestDiscoveryTrait by using Job DSL dynamic API [~casz], I updated the link to reflect that fact. The linking was saying this ticket block blocks JENKINS-26535, which is not the way it should be I guess, correct? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204634.1582018032000.4776.1583323680470%40Atlassian.JIRA.
[JIRA] (JENKINS-60730) Add possibility to exclude branches and tags older than X days
Title: Message Title Daniel Steiert created an issue Jenkins / JENKINS-60730 Add possibility to exclude branches and tags older than X days Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2020-01-10 12:20 Priority: Major Reporter: Daniel Steiert Problem Statement We have had problems with anything that reacts to multiple branches or tags for quite some time now. Any form of multibranch plugin or plugins that check for tags, Pull Requests or anything like it. They all cause issues as soon as there is either an upgrade in which there are no logs from previous builds, after a disaster with data-loss or when re-running certain seed-jobs that modify (e.g. multibranch-) configurations. The issue presents itself in the form of complications due to rebuilds of every single branch, PR and tag for every single repository, at the same time. This might not be a problem for small and very short builds, but it becomes a huge issue for anything that runs longer than 5 minutes. Firstly, this blocks the ability to build current and urgent jobs (since all slaves are busy building old branches/tags/PRs). Secondly, it requires immense amounts of resources (often times all of them, even if that means 120+ x 16 GB with 4 cores slaves) that wouldn't have to be used necessarily. Thirdly, the Jenkins Master almost always suffers from further crashes or erratic behaviour, since a lot of jobs are queueing up, all slaves are engaged and there is in general a lot of load on the system (unnecessarily so). This kind of behaviour can not only be experienced on older environments with static slaves and everything running on VMs, but more specifically on more modern setups in which the Jenkins is created and runs stateless in a Kubernetes cluster. If there was a way to restrict or ignore old/stale branches/tags/PRs, basically all of the above mentioned problems could be solved. Feature Proposal The github-branch-source-plugin is one of the plugins that
[JIRA] (JENKINS-60722) Add possibility to restrict building branches and tags by age
Title: Message Title
Daniel Steiert updated an issue
Jenkins / JENKINS-60722
Add possibility to restrict building branches and tags by age
Change By:
Daniel Steiert
h3. Problem StatementWe have had problems with anything that reacts to multiple branches or tags for quite some time now. Any form of multibranch plugin or plugins that check for tags, Pull Requests or anything like it. They all cause issues as soon as there is either an upgrade in which there are not no logs from previous builds, after a disaster with data-loss or when re-running certain seed-jobs that modify (e.g. multibranch-) configurations. The issue presents itself in the form of complications due to rebuilds of every single branch, PR and tag for every single repository, at the same time. This might not be a problem for small and very short build builds , but it becomes a huge issue for anything that runs longer than 5 minutes.Firstly, this blocks the ability to build current and urgent jobs (since all slaves are busy building old branches/tags/PRs). Secondly, it requires immense amounts of resources (often times all of them, even if that means 120+ x 16 GB with 4 cores or more slaves) that don wouldn 't have to be used necessarily. Thirdly, the Jenkins Master almost always suffers from further crashes or erratic behaviour, since a lot of jobs are queueing up, all slaves are engaged and there is in general a lot of load on the system (unnecessarily so).This kind of behaviour can not only be experienced on older environments with static slaves and everything running on VMs , but especially more specifically on more modern setups in which the Jenkins is created and runs stateless in a Kubernetes cluster. If there was a way to restrict or ignore old/stale branches/tags/PRs, basically all of the above mentioned problems could be solved.h3. Feature ProposalThe {{inline-pipeline-plugin}} can be used with all of these plugins and comes after configuring all of the branch, tag or PR itself above mentioned plugins . It is the perfect location to add a restriction that would ignore branches/tags/PRs with a {{HEAD}} commit older than {{X}} days. Any branch/tag/PR with a {{HEAD}} commit older than that would not be listed and not built. In the case of a disaster, re-run of a seed-job, re-configuration of multibranch-jobs and even in the case of data-loss, only those branches/tags/PRs would be built that are relevant for current work. Anything old and stale could be ignored. To make it configurable, there should be a field right beside the {{Markerfile}} field to define how old a {{HEAD}} commit in one of these branches/tags/PRs has to be , to be ignored.h3. Current StateAttached to this ticket is a Pull Request with a ready and working feature implementation for the proposed solution. It has been tested with our setup and works flawlessly with the full potential to solve our problems organisation-wide in case it gets merged and supported.
[JIRA] (JENKINS-60722) Add possibility to restrict building branches and tags by age
Title: Message Title Daniel Steiert created an issue Jenkins / JENKINS-60722 Add possibility to restrict building branches and tags by age Issue Type: New Feature Assignee: Daniel Beck Components: inline-pipeline-plugin Created: 2020-01-10 08:12 Priority: Major Reporter: Daniel Steiert Problem Statement We have had problems with anything that reacts to multiple branches or tags for quite some time now. Any form of multibranch plugin or plugins that check for tags, Pull Requests or anything like it. They all cause issues as soon as there is either an upgrade in which there are not logs from previous builds, after a disaster with data-loss or when re-running certain seed-jobs that modify (e.g. multibranch-) configurations. The issue presents itself in the form of rebuilds of every single branch, PR and tag for every single repository, at the same time. This might not be a problem for small and very short build, but it becomes a huge issue for anything that runs longer than 5 minutes. Firstly, this blocks the ability to build current and urgent jobs (since all slaves are busy building old branches/tags/PRs). Secondly, it requires immense amounts of resources (often times all of them, even if that means 120+ x 16 GB with 4 cores or more slaves) that don't have to be used necessarily. Thirdly, the Jenkins Master almost always suffers from further crashes or erratic behaviour, since a lot of jobs are queueing up, all slaves are engaged and there is in general a lot of load on the system (unnecessarily so). This kind of behaviour can not only be experienced on older environments with static slaves and everything running on VMs but especially on more modern setups in which the Jenkins is created and runs stateless in a Kubernetes cluster. If there was a way to restrict or ignore old/stale branches/tags/PRs, basically all of the above mentioned problems could be solved. Feature Proposal The inline-pipeline-plugin can be used with all of these plugins and comes after
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert edited a comment on JENKINS-41308 Re: support Use Groovy Sandbox scripts in activeChoiceParams The To fix this issue, I created a PR ([https://github.com/jenkinsci/job-dsl-plugin/pull/1211)] with a green build ([https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fjob-dsl-plugin/detail/PR-1211/1/pipeline/).] All the old functionality stays unchanged and only the `sandbox` option was added in. There are tests, documentation of course also is updated and the contribution guidelines have been followed . Please have a look and let me know if any changes need to be made before this can be integrated. Please have a look at the PR Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.3507.1575972660470%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title
Daniel Steiert edited a comment on JENKINS-41308
Re: support Use Groovy Sandbox scripts in activeChoiceParams
To fix this issue, I created a PR according to the guidelines with the addition The documentation of the {{sandbox}} option for scripts. I made sure all the old functionality course also is untouched (works the same) and added tests for the new options updated . The build should also go through ([https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fjob-dsl-plugin/detail/PR-1211/1/pipeline)] and I tested it on my own Jenkins instance. Please review and let me know if you need any changes before it can be merged.The PR can be found here: https://github.com/jenkinsci/job-dsl-plugin/pull/1211
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.3500.1575972480350%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert assigned an issue to Daniel Spilker Jenkins / JENKINS-41308 support Use Groovy Sandbox scripts in activeChoiceParams Change By: Daniel Steiert Assignee: Daniel Steiert Spilker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.3493.1575971942602%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert updated JENKINS-41308 Jenkins / JENKINS-41308 support Use Groovy Sandbox scripts in activeChoiceParams Change By: Daniel Steiert Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.3490.1575971942442%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert commented on JENKINS-41308 Re: support Use Groovy Sandbox scripts in activeChoiceParams To fix this issue, I created a PR according to the guidelines with the addition of the sandbox option for scripts. I made sure all the old functionality is untouched (works the same) and added tests for the new options. The build should also go through (https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fjob-dsl-plugin/detail/PR-1211/1/pipeline) and I tested it on my own Jenkins instance. Please review and let me know if you need any changes before it can be merged. The PR can be found here: https://github.com/jenkinsci/job-dsl-plugin/pull/1211 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.3451.1575970202146%40Atlassian.JIRA.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Daniel Steiert reopened an issue Jenkins / JENKINS-41308 support Use Groovy Sandbox scripts in activeChoiceParams Change By: Daniel Steiert Resolution: Fixed Status: Closed Reopened Assignee: Daniel Spilker Steiert Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178082.148516094.3391.1575968280895%40Atlassian.JIRA.
