Re: GSOC Idea? Maintainers Heartbeat

> On 5. Feb 2021, at 06:05, 'Gavin Mogan' via Jenkins Developers > wrote: > > 1) Update jenkins core to highlight plugins that have the adopt plugin label > (either via github or directly in update center) This already exists on the plugin site and in Jenkins directly, or are you thinking

Re: Jenkins LTS Baseline Selection

> On 28. Jan 2021, at 10:49, fque...@cloudbees.com > wrote: > > +1 for 2.277 Agree. There's no other reasonable choice at the moment. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Jenkins 3.x

The existing 1.x/2.x versioning scheme which only ever increases minor versions seems like it reinforces the idea that nothing is happening. Would going with a date-based versioning scheme help? For example YY.nn (year and release, roughly corresponding to week in year), or YY.m.nn (year,

Re: Jenkins Security Advisories - UX Improvement Suggestions

> On 14. Jan 2021, at 17:58, 'FredG' via Jenkins Developers > wrote: > > I'd suggest to add the severity to each issue's description to avoid the > scrolling. If there is no added value in the separate severity section, than > maybe getting rid of it entirely makes sense as well. Thanks

Re: Jenkins 2.263.2 LTS RC testing started

> On 8. Jan 2021, at 09:47, Vibhav Bobade wrote: > > Would an update to winstone also be made in this new LTS release ? > The fix for the CVE > https://github.com/eclipse/jetty.project/security/advisories/GHSA-86wm-rrjm-8wh8 > is available in 5.13 of winstone. Based on my research, the

Re: Data binding: Bind repeatable list of textboxes into List

u are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkin

Re: Using AJAX and Jelly to render a simple Widget

> On 2. Jan 2021, at 20:20, Robert Smith wrote: > > 1) What magic is happening to tell Jenkins to bind all of the > hudson/model/View/ajax*.jelly files to a URL of the same name? I couldn't > figure it out. Stapler, the web framework used in Jenkins. For this specifically, see the section

Re: Discussion - Plugins reporting issue trackers

> On 17. Dec 2020, at 23:01, 'Gavin Mogan' via Jenkins Developers > wrote: > > If a repo has github issues enabled, assume it uses that. > else If the plugin name has a jira component, assume it uses that. > else no issues link The beauty of the one time mass definition of issue trackers is

Re: Discussion - Plugins reporting issue trackers

> On 17. Dec 2020, at 07:53, 'Gavin Mogan' via Jenkins Developers > wrote: > > 1) Overrides file > 2) Issue Managemnet section in pom.xml ( > https://maven.apache.org/pom/maven/issue-management.html). I was thinking > we should use jira:$component-name, or github:repo-name > 3) Github if

Re: Jenkins Operator managed service name (sublicensing)

> On 16. Dec 2020, at 00:06, Oleg Nenashev wrote: > > Our public doc is still behind the actual state, my bad. Will make sure to > file a PR tomorrow on the morning. At the Oct 14 governance meeting we agreed > that: > > * We adopt Linux Foundation pre-approved trademark patterns and usage

Re: Jenkins Operator managed service name (sublicensing)

> On 15. Dec 2020, at 22:18, Oleg Nenashev wrote: > > It was me pushing for LF trademark guidelines adoption at the end of the day. Oleg, could you summarize the current situation of this? My vote basically hinges on whether we've done this and we'd be granting an exception; or whether

Re: Add tentative LTS release dates for next baseline in Jenkins.io events calendar?

> On 10. Dec 2020, at 15:44, Baptiste Mathus wrote: > > Can we please consider updating the Jenkins events calendar with the next .1 > (and possibly .2, and .3)? FWIW I think we haven't done that in general in the past because - the LTS schedule is known anyway, except for the occasional

Re: Core Baseline Java8 -> Java11?

> On 4. Dec 2020, at 09:43, Ullrich Hafner wrote: > > Ok, I understand that. I wasn’t aware that so may people are still using Java > 8. Jenkins stats (scroll down for recent months): https://stats.jenkins.io/plugin-installation-trend/jvms.json Obviously, Jenkins influences the stats here

Re: Config round trip failures in plugin unit tests?

> On 28. Nov 2020, at 20:58, Mark Waite wrote: > > I assume commons-beanutils 1.9.4 (released in August 2019) is not being used > by anyone else in Jenkins core or plugins. commons-beanutils 1.9.4 is known to core maintainers to not be useable in Jenkins. We've now had two PRs for that

Re: Jenkins 3.x

> On 27. Nov 2020, at 18:26, James Nord wrote: > > Could we maybe keep the discussion here to just a 3.x bump as we are more > likely to reach a consensus? As a technical/compatibility indicator, 3.0 makes little sense because it's late. None of the related documentation would even say

Re: Error: This repository is over its data quota

On Thu, Nov 26, 2020 at 3:51 PM 'Ciprian Burca' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > > How can I fix this? > Don't use Git LFS. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group

Re: Jenkins 3.x

On Thu, Nov 26, 2020 at 1:53 PM Manuel Ramón León Jiménez < manuelramonleonjime...@gmail.com> wrote: > > Anyway, I would like, when the time comes, to introduce semantic > versioning , adding a > third number to the version and using them according

Re: Config round trip failures in plugin unit tests?

On Thu, Nov 26, 2020 at 6:58 AM 'Gavin Mogan' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I don't know which hasClassName is undefined as your linking to a local > file, and >

Re: Request using the certificate file of the official Jenkins Update Center

> On 17. Nov 2020, at 15:01, Rick wrote: > > > You mean generate two or more versions of update-cener.json files? For > example, update-center.json and update-center-zh.json ? Am I right? Basically this, yes. Re mirrors, did you test using the regular update site recently, and still

Re: Request using the certificate file of the official Jenkins Update Center

> On 17. Nov 2020, at 14:48, Rick wrote: > > I try to modify the URL plugins into a mirror one. But it's unavailable due > to security reasons. Jenkins will do the validation with update-center.json > file. In order to fix this, I just make my own certificate file. Before > using it, you need

Re: How often is the downloadables crawler run?

Usually it runs every four hours, but an infra change two weeks ago accidentally caused it to stop. For posterity: Someone changed the configured Jenkins URL to fix an issue with Jetty. That caused

Re: Writing from Slave To Master

> On 12. Nov 2020, at 22:40, Tal Yanai wrote: > > String buildDir = build.getRootDir().getAbsolutePath(); > FilePath masterDirectory = new FilePath(new File(buildDir + File.separator + > fileName)); As all paths here are on the master, is this the same as the following? FilePath

Re: New Jenkins Operator for kubernetes: repository request creation: simple-jenkins-operator

On Thu, Nov 12, 2020 at 12:07 PM Oleg Nenashev wrote: > Since this is a request for a new repo creation (not a fork/move) && there > is a consensus here, I do not see a particular need. A HOSTING ticket would > be useful to understand the desired permissions, but we can figure it out > as we go.

Re: Need help with accessing Praqma Support user

> On 11. Nov 2020, at 22:05, Mark Waite wrote: > > I was surprised when I sent an email to supp...@praqma.net yesterday and > received a response that opened a ticket in their bug tracker. So emails to that account are still accessible? Why the need for outside help? Why not request a

Re: LTS schedule winter break

On Wed, Nov 11, 2020 at 3:01 PM Tim Jacomb wrote: > Is someone going to want to do an RC on 'Dec 30 - 2.263.2 RC' though? > I address that in my proposal, that can always be created earlier if necessary due to scheduling/vacation issues. If you implement it as you propose, there will still be

Re: Writing from Slave To Master

> On 11. Nov 2020, at 12:58, Tal Yanai wrote: > > Trying to write a code that let me dump new file with content over to the > master workspace (while running on a remote Node). > > 2 things I'm struggling with: > > 1. How to find out the Master 'FilePath' while running within the Node. >

LTS schedule winter break

Hi everyone, We have an LTS release scheduled for December 30, which probably isn't useful: The RC testing period is from Dec 16 to Dec 30. Plus who wants to release things the day before NYE? I propose we add a two-week break between 2.263.1 release and 2.263.2 RC, postponing all future RCs

Re: Jenkins Jira migration has started

ot;Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAB-RWjL6ucuS9zytwDhjfT2C5_hDNergzPSqHXQ5%2B1qq1wNpV

Re: What is the appropriate settings.xml to use these days?

On Sat, Nov 7, 2020 at 4:35 PM Mez Pahlan wrote: > Without the mirrors section I was getting the following error: Could not > find artifact org.jenkins-ci.tools:maven-hpi-plugin:pom in central ( > https://repo.maven.apache.org/maven2). That plugin is clearly not in the > Central repo which lead

Re: Redirecting to git Hub instead of plugin site

On Sat, Nov 7, 2020 at 6:34 AM selva vignesh wrote: > Old one is latest version of published version. > Enhanced plugin is not yet available In plugin site. > If it's a plugin not published on Jenkins update sites, the URL it declares in pom.xml is used. (For already published plugins, the

Re: sqlplus-script-runner help - MS Windows issue

ers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/f25d0a51-ba77-434e-bdf1-367e7ed97c0en%40googlegro

Re: Jenkins 2.249.3 LTS RC testing started

On Thu, Nov 5, 2020 at 7:02 PM Jesse Glick wrote: > > There is a revert in progress so 2.249.3 should be held awaiting that. > 2.249.3 was released yesterday around 3 PM UTC. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Proposal: Excluding JRebel support from the Jenkins core (JENKINS-64037)

On Mon, Nov 2, 2020 at 5:44 PM Oleg Nenashev wrote: > Same question about > https://github.com/stapler/stapler-adjunct-zeroclipboard . It is a part > of the Jenkins core API and it "provides an easy way to copy text to the > clipboard using an invisible Adobe Flash >

Re: Jenkins-specific warnings for GitHub code scanning

On Sun, Oct 18, 2020 at 3:05 PM Ullrich Hafner wrote: > Where should we report issues for false positives? I assume that those > rules are written by a Jenkins community member, or are these general rules > from Semmle? > These are Jenkins project specific rules only, we use CodeQL as the

Re: What is the appropriate settings.xml to use these days?

On Mon, Oct 12, 2020 at 7:19 PM Jesse Glick wrote: > On Mon, Oct 12, 2020 at 7:36 AM Mez Pahlan wrote: > > I am still curious as to what I should be putting in my settings.xml > > You do not really need one at all, as all Jenkins components declare > the Jenkins Artifactory repository. > Well,

Jenkins-specific warnings for GitHub code scanning

Hi everyone, GitHub announced last week that their code scanning functionality is now generally available[1]. The Jenkins security team has worked on queries specifically for Jenkins and Jenkins plugins. I'd now like to share them with a limited audience to get some initial feedback before

Re: Unable to install Liquibase Runner Plugin via Jenkins

learn at: learn.liquibase.com > <http://learn.liquibase.com/> | > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, s

Re: Unable to upload plugin to Jenkins center 401, Unauthorized

Please see https://www.jenkins.io/doc/developer/publishing/releasing/#the-upload-to-the-maven-repository-fails-with-401-unauthorized for possible causes. See https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-whitesource.yml for who should have upload

Re: Incrementals and ATH tests (inside a plugin CI)

On Thu, Aug 27, 2020 at 11:22 PM Ullrich Hafner wrote: > > Yes, I had that problem a couple of weeks ago. One of my dependencies > upgraded its Jenkins version to a higher version than the version I was > using in my UI tests: that broke my build. > Do you still have the failing build log, or

Re: Forked repositories in GitHub

clude from the list the repos when they aren't > existing anymore in the jenkinsci side (not sure how many repos could be > like this) > > On Tue, Aug 18, 2020 at 1:39 PM Daniel Beck wrote: > >> Hi everyone, >> >> I'd like to propose a cleanup of 'fork' relati

Forked repositories in GitHub

Hi everyone, I'd like to propose a cleanup of 'fork' relationships of the repositories in the jenkinsci GitHub organization. Background: For many years, the plugin hosting process has forked existing repositories. The expectation was always that the new repo in jenkinsci was the canonical

Re: Cannot assign configuration entry 'pluginArtifacts' with value '${plugin.artifacts}'

Your chosen parent pom is several years out of date and its configuration no longer works with recent releases of Maven. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it,

Re: Proposal: Jenkins baseline selection

> On 12. Aug 2020, at 19:13, Ullrich Hafner wrote: > > Recently a lot of my builds failed (my baseline was 2.204.4) because some > frequently used base plugins updated their minimum Jenkins version to a > higher LTS minor version (like 2.222.1) or a higher patch version (2.204.6). I'm

Re: LTS baseline selection for the successor of 2.235

On Fri, Jul 31, 2020 at 7:11 PM Mark Waite wrote: > We could also choose 2.251 and have the most of the same improvement in > clarity for user communication, but it would bring the other changes from > 2.251 into the LTS baseline. > Unless we merge something potentially causing regressions (and

Re: LTS baseline selection for the successor of 2.235

> On 29. Jul 2020, at 13:59, Oleg Nenashev wrote: > > 2.250 is a fancy number, so why not? As I previously explained, too similar to 2.150 which was also an LTS baseline. Since there's no other notable difference to 2.249, I would prefer less confusing bug reports over having a nice

Re: LTS baseline selection for the successor of 2.235

> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion

Re: Terminology: agent vs node

> On 22. Jul 2020, at 13:40, Daniel Beck wrote: > > These terms are useful and consistent, as master can also be a node. By > default, it's even the only node. I forgot to mention: Master is not an agent (but both are nodes). This distinction was somewhat clearer, IMO, before w

Re: Terminology: agent vs node

> On 21. Jul 2020, at 23:05, 'Martin Schmude' via Jenkins Developers > wrote: > > This reminds me of that I am worried from time to time by the terms "agent" > and "node". > They seem to be synonyms - am I right? > If so, shouldn't "agent" be the preferred term, due to the decision of 2016

Re: How to override the plugin version seen by plugin manager area

> On 14. Jul 2020, at 18:39, Jesse Glick wrote: > > Would not recommend it unless there is a > compelling need. Recent releases of Jenkins also show release dates in the plugin manager, the release dates are shown on the plugins site and in tooltips on the archives page, so I would be

Re: modifying a @DataboundConstructor

You want something like this: - public class MySecurityRealm extends SecurityRealm { private MyConfiguration configuration; private transient String clientId; private transient Secret clientSecret; private Object readResolve() { if (clientId != null || clientSecret !=

Re: Proposed changes to update center tiers

> On 17. May 2020, at 14:26, Daniel Beck wrote: > > To address this, I propose to dynamically determine which tiered update sites > to generate based on core dependencies declared in plugins. While this will > increase the number of tiers (every release ever used as

Re: GitHub issues option in HOSTING

> On 19. Jun 2020, at 11:47, Radosław Antoniuk wrote: > >> I would be surprised if we wouldn't regularly get 0-days because people with >> just a GH account don't bother to do it properly, and just report issues on >> GH. If that is enabled in repos without someone regularly reviewing

Re: GitHub issues option in HOSTING

> On 18. Jun 2020, at 22:50, Tim Jacomb wrote: > > The security team already uses a different project in Jira to everyone else, > I don't think we need to change that currently, maintainers will just use > whatever the security team decides I would think? > > Mentioned this earlier: > >

Re: Jenkins Governance Meeting on Jun 17, 2020

> On 16. Jun 2020, at 23:06, Oleg Nenashev wrote: > > • Terminology updates > • > https://groups.google.com/forum/#!topic/jenkinsci-dev/CLR55wMZwZ8 > • Vote: Replacing the whitelist/blacklist terminology > • Allowlist/Denylist >

Re: Terminology Updates

> On 15. Jun 2020, at 22:39, Markus Winter wrote: > > Second the server is also just plain agent (more or less). For this we > could use the term "main" as the default label. That's what I proposed earlier in the thread as well. 'main' seems reasonable, but still has the connotation that

Re: Terminology Updates

> On 15. Jun 2020, at 16:00, Antonio Muñiz wrote: > > In spanish the term "Master" ("Maestro"), when used in isolation (no > "slave" in the context), has no negative connotations. If Jenkins (and before it, Hudson) had always used Master/Agent terminology, that would apply. But it didn't. I

Re: Terminology Updates

> On 14. Jun 2020, at 02:46, Mark Waite wrote: > > Using the word 'valet' instead of 'master' to refer to the node that executes > inside the original Jenkins Java process. Replace it with the term you prefer > • Redirect requests from /computer/(master)/ to /computer/(valet)/ Good

Re: Terminology Updates

> On 12. Jun 2020, at 20:05, Slide wrote: > > Jenkins Server makes sense to me as well. I'll add as a topic for the next > Governance meeting. It seems as if this thread so far lacks considerations regarding the implementation of such a decision. This is concerning because a superficially

Re: Adding Downloadables to Jenkins

> On 1. Jun 2020, at 14:56, Tim Van Holder wrote: > > The second is still a question mark. I found one page somewhere about needing > to write a scraper to generate the file, but that did not go into details on > what that would look like, or how to get an update center to use it. >

Re: Adding Javascript to config.groovy

> On 29. May 2020, at 11:47, Esther Alvarez wrote: > > To pass around data from jelly to javascript, you can write "data-" > attributes in HTML tags with jelly and then load them with javascript. Here > some examples about how to do it: >

Re: Adding Javascript to config.groovy

On Thu, May 21, 2020 at 10:35 PM Parichay Barpanda < parichay.barpa...@gmail.com> wrote: > because lack of IDE support make tags unreadable. > There are IDE plugins adding support for this. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Unable to perform plugin release to repo.jenkins-ci.org

If your plugin overrides the distributionManagement, as in https://github.com/jenkinsci/codedx-plugin/blob/d56180188ae138677f09214f57c1b8d840375477/pom.xml#L70-L75 our instructions no longer apply. In this case, it is named 'repo.jenkins-ci.org', not the default 'maven.jenkins-ci.org', so the

Re: regarding issues publishing new plugin, but publishing works when publishing a snapshot

io/jenkins/plugin io/jenkins/plugins > On 23. May 2020, at 02:26, john rowley wrote: > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Proposed changes to update center tiers

> On 17. May 2020, at 14:26, Daniel Beck wrote: > > To address this, I propose to dynamically determine which tiered update sites > to generate based on core dependencies declared in plugins. While this will > increase the number of tiers (every release ever used as

Re: Proposal: Release Jenkins weekly on Tuesday

Easy fix: Whoever wants to merge something on a weekend is responsible for updating the changelog. If this isn't done, and you've merged fixes a few times, you lose commit access. > On 18. May 2020, at 20:55, Mark Waite wrote: > > I worry that creating the changelog on Friday with release on

Re: Remove plugin from update site?

> On 18. May 2020, at 21:13, Steve Springett wrote: > > Is this possible? And if so, how can i go about doing this? > Please see the instructions here: https://jenkins.io/doc/developer/publishing/removing-from-distribution/ -- You received this message because you are subscribed to the

Re: Proposal: Release Jenkins weekly on Tuesday

> On 18. May 2020, at 19:30, Mark Waite wrote: > > I propose that we move the weekly build to Tuesday so that I don't need to > prepare the weekly changelog on Sunday night. FWIW I proposed my favored approach in https://groups.google.com/d/msg/jenkinsci-dev/kVjOddydLEI/5-xDPIW7AQAJ but

Proposed changes to update center tiers

Hi everyone, A few weeks ago I announced an improvement to the the update site generator[1]. Since then I've been busy modernizing the tool further. One change I'm implementing is flexible tiering. Right now, we determine the last five LTS baselines, and generate weekly and LTS update sites

Re: Plugin: Liquibase Runner

> On 1. May 2020, at 15:15, Robert Reeves wrote: > > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on > project liquibase-runner: Failed to deploy artifacts: Could not transfer > artifact

Re: Equalizing external dependency between plugins

Depends on whether you just want your plugin to compile, or whether you want to actually prevent problems at runtime. If the latter, I don't see how the POM or BOM would help with that. > On 30. Apr 2020, at 10:43, Radosław Antoniuk wrote: > > Yes, I saw those two approaches but I don't like

Re: LTS baseline selection for the successor of 2.222

> On 29. Apr 2020, at 12:44, Oliver Gondža wrote: > > In accordance we recently approved process changes, we are doing next > baseline section two weeks earlier in the cycle. Assuming nobody merges something crazy into core this week, I'm for 2.235. We've moved the baseline decision

Re: Equalizing external dependency between plugins

> On 28. Apr 2020, at 11:31, Radek Antoniuk wrote: > > So in this very specific example, if we have jira-plugin that depends on > maven-artifact and another maven-plugin that also depends on maven-artifact - > what is the best approach to maintain those two plugins compatible with each >

Update center now independent from Nexus Maven index

Hi everyone, The main problem delaying the availability of plugins through the update center (even when everything was running smoothly) was always that the update center generator used a Nexus Maven index to enumerate available plugins. This central feature survived all previous attempts at

Re: Plugin Licenses

> On 27. Apr 2020, at 10:46, Oleg Nenashev wrote: > > What we definitely need is do document our license requirements in > https://www.jenkins.io/doc/developer https://www.jenkins.io/doc/developer/publishing/preparation/#license is very clear about this, and is linked as the first

Re: Prevent building branches/PRs existing before the first branch indexing (Branch API plugin)

> On 24. Apr 2020, at 09:48, Jon Brohauge wrote: > > I would love to be able to trigger a "index, but don't build". Isn't this possible with a suitable build strategies configuration? For example "Named Branches" and the branch name you specify doesn't exist and never will. Should also be

Re: Plugin Licenses

> On 23. Apr 2020, at 15:27, Robert Reeves wrote: > > They should update it or have the plugin removed. FYI https://github.com/jenkins-infra/update-center2/pull/371 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: Plugin Licenses

> On 23. Apr 2020, at 01:54, 'Gavin Mogan' via Jenkins Developers > wrote: > > [NOTMIT] ci-with-toad-devops-toolkit - Continuous Integration with Toad > DevOps Toolkit License Agreement > [NOTMIT] ci-with-toad-edge - Continuous Integration with Toad Edge License > Agreement Interesting.

Re: Approval to use the Jenkins logo

> On 21. Apr 2020, at 13:39, Christopher Orr wrote: > > I've also copied the Jenkins Developers' mailing list; someone there can > maybe give you a more comprehensive answer, or you can ask ask about other > terms, if need be. Questions not answered by the second paragraph of the linked

Re: Where and how to store/retrieve secrets needed for Jenkins plugin Continuous Integration?

If this is referring to the CI of a Jenkins plugin built on ci.jenkins.io, I don't think there's a good solution. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: Prevent building branches/PRs existing before the first branch indexing (Branch API plugin)

Untested, but looks promising: https://plugins.jenkins.io/github-scm-filter-aged-refs/ > On 18. Apr 2020, at 17:48, tony.no...@gmail.com wrote: > > I think the point is to prevent an automatic build of a shedload of old > pre-existing branches when creating a multi branch pipeline job for an

Re: Plugin: Liquibase Runner

> On 16. Apr 2020, at 20:16, Robert Reeves wrote: > > Just to follow up…we’re trying to get this security issue resolved but have > not been able to get access to SECURITY-519. How can we view that so we can > fix the issue? As I wrote in a previous response, Keith's account has access to

Re: ANN: Agent Docker images renaming on April 12-13

On Mon, Apr 13, 2020 at 10:52 PM Oleg Nenashev wrote: > My pull request is already built for "ssh-agent", so I will go ahead and > setup DockerHub builds for this image. > If there are strong opinions, we have 1-2 extra days to revisit naming > before the blogpost is shipped. > AFAIUI,

Re: ANN: Agent Docker images renaming on April 12-13

> On 12. Apr 2020, at 15:59, Oleg Nenashev wrote: > > Regarding the SSH agent image, will wait till tomorrow to get more feedback. The plugin is now called "SSH Build Agents", so it makes sense to me to call the corresponding image ssh-build-agent. In fact, all the labels on

Re: How can i remove the plugin's warning?

> On 12. Apr 2020, at 04:51, liuweiGL wrote: > > Why does the warning still exist? These warnings don't get updated automatically. See the documentation here for how you can request changes to warnings: https://jenkins.io/security/plugins/#followup -- You received this message because

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 11. Apr 2020, at 19:53, Radosław Antoniuk wrote: > > For me the availability of on-line archive of online chats, whether it be IRC > or Slack is not an argument for the tool, especially for the external > communication - for internal communication of the core contributors, it might >

Re: plugin not appearing in pluginManager

On Fri, Apr 10, 2020 at 5:54 PM Marina Goltseva wrote: > The wallarm-fast plugin is not appearing in the /pluginmanager area of a > jenkins instance > https://github.com/jenkinsci/wallarm-fast-plugin/commit/7a104befdab2697114de99864c421ad61ce21329 looks like it wasn't created following the

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 11. Apr 2020, at 01:06, Oleg Nenashev wrote: > > TBH if we use Slack for runtime communications only, even losing history is > not a big deal Strongly disagree. Even such conversations have a tendency to contain useful information, I'm not interested in having to keep a text editor

Re: Proposal: Windows support policy for Jenkins

> On 10. Apr 2020, at 14:26, Oleg Nenashev wrote: > > I know for sure that there are Jenkins users running on Windows XP That's no reason to enable this insanity. I would advocate for just going with what's generally supported by Microsoft: Extended support would be in, "throwing bags of

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 9. Apr 2020, at 10:55, Radosław Antoniuk wrote: > > Gitter/Slack, JIRA Infra and dev mailing list should be enough and then if > #core on Gitter then #infra also on Gitter. Didn't Gitter have problems maintaining the platform? Have those been resolved? And Slack costs money unless

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 9. Apr 2020, at 10:31, Radek Antoniuk wrote: > > I'd also love to have a channel for #infra. Multiple references to #jenkins-infra on https://jenkins.io/projects/infrastructure/ Not intended that way, but still a great example what a major downside is when jumping on every chat

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 8. Apr 2020, at 14:17, Oleg Nenashev wrote: > > creation of chats and other communication channels for Jenkins core > maintainers which could help in the case of runtime communications: > merge/changelog discussions, sync-ups between maintainers, etc. Right now we > mostly use pull

Re: How to not break dependant plugins and keep moving forward?

On Thu, Apr 2, 2020 at 5:25 PM Eric Citaire wrote: > > is it Ok to re-upload the same release of a plugin for this kind of change > or does it require a new release > > You cannot overwrite existing releases, so it will require a new release. -- You received this message because you are

Re: How to not break dependant plugins and keep moving forward?

On Thu, Apr 2, 2020 at 3:35 PM Eric Citaire wrote: > > I really don't like breaking things and I was wondering if there were a > way to avoid this and still be able to move forward. Dependant plugins are > able to declare a minimum version of a dependency, but not a maximum > version. Is there

Re: Adopt a plugin: Klocwork

> On 30. Mar 2020, at 13:26, Michael Baron wrote: > > currently owned by the Github user account “michael-baron", which is in fact > myself File a PR changing https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-klocwork.yml accordingly. As

Re: Plugin release

> On 30. Mar 2020, at 06:38, selva vignesh wrote: > > I have done release steps and uploaded the plugin to the Jenkins repo. Still > i am unable to find the plugin under > http://localhot:8080/pluginManager/available. > The plugin is available. Try refreshing. -- You received this

Re: Git plugin 5.0 require Jenkins 2.190.3

> On 26. Mar 2020, at 14:43, Mark Waite wrote: > > Are there pitfalls or problems that I have not considered in making the > Jenkins version required by git plugin 5.0 be Jenkins 2.190.3? 2.190.x requires the BOM (-Duse-jenkins-bom) otherwise it won't compile out of the box. At least

Re: GitHub Team Discussions in jenkinsci GH Org

> On 25. Mar 2020, at 17:34, Radek Antoniuk wrote: > > Tim Jacomb mentioned that the reason for this is that the teams were often > re-created in the past, but I think that: > - if we assume that each plugin "automatically" has a long-lived team that is > called "-admins" or "-maintainers"

Re: Proposal: Public community-driven roadmap for the Jenkins project

> On 12. Mar 2020, at 17:09, Oleg Nenashev wrote: > > On Jan 31 we had a Jenkins contributor summit in Brussels. At this > unconference we discussed a number of ongoing projects and key initiatives > which could help us to evolve the project (meeting notes). One of the > proposals there

Re: Backporting for LTS 2.222.1 started

FYI it looks like 2.222.1 will have an "LTS regression" over 2.204.x: https://issues.jenkins-ci.org/browse/JENKINS-61429 Probably at least something for the upgrade guide if we cannot / do not want to expedite a fix post-RC. -- You received this message because you are subscribed to the Google

Re: Failing REST API tests in 2.222 and newer

> On 9. Mar 2020, at 16:17, Jesse Glick wrote: > > I guess this should not affect typical functional tests due to > > https://github.com/jenkinsci/jenkins-test-harness/blob/d0fc8acc9be04ba3f4b81317734f23a96626a6d4/src/main/java/org/jvnet/hudson/test/JenkinsRule.java#L417 > > Maybe JTH

<    1   2   3   4   5   6   7   8   9   10   >