Re: GitHub issues option in HOSTING

>> Regarding Security issues - maybe GH new Security Advisories hub could be used for that? >> https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories >> https://github.blog/2020-05-26-giving-credit-for-security-advisories/ > Our usual workflow is

Re: GitHub issues option in HOSTING

Resurrecting via PR: https://github.com/jenkinsci/.github/pull/42/files - let's discuss this there. Regarding Security issues - maybe GH new Security Advisories hub could be used for that? https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories

Re: LTS baseline selection for the successor of 2.249

> > > Since the selection took place and I can see 2.263.1 in > https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in > https://github.com/jenkinsci/bom ? > I think that you will eventually see 2.263.x in the bom rather than 2.264.x. I'm sure that a pull

Re: LTS baseline selection for the successor of 2.249

> > >> Since the selection took place and I can see 2.263.1 in >> https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in >> https://github.com/jenkinsci/bom ? >> >> > I think that you will eventually see 2.263.x in the bom rather than > 2.264.x. I'm sure that a pull request would be

Re: LTS baseline selection for the successor of 2.249

Since the selection took place and I can see 2.263.1 in https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in https://github.com/jenkinsci/bom ? On Monday, 9 November 2020 at 14:06:02 UTC+1 Mark Waite wrote: > Yes, 2.263 is the selected baseline for the next Jenkins LTS. > > On

@JenkinsRule plugin list customisation

In the context of how can I customise the list of plugins that the test runs with to detect a missing dependency in tests? There is https://wiki.jenkins.io/display/JENKINS/Unit+Test#UnitTest-@WithPlugin(NameOfPlugin) but there is no @WithoutPlugin and it seems that JenkinsRule somehow installs

Equalizing external dependency between plugins

While implementing dependabot in jira-plugin, we had a discussion about version incompatibility between different Jenkins plugins that might use the same external library. I'm wondering what's the current best practice

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Definitely +1 for core channel, definitely -1 for gitter and +1 for Slack or some other alternative like Rocket.Chat: I'd also love to have a channel for #infra. Something on that:

Automating plugin release process via GitHub Actions

I'm thinking about automating the plugin release process using GH Actions: - https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets - https://github.com/marketplace/actions/maven-release -

GitHub Team Discussions in jenkinsci GH Org

I'm sure than other people co-maintaining the plugins over the world also have the problem that we have multiple ideas and discussions regarding project maintenance. Those obviously could be maintained in GitHub Issues, but since we have dedicated GitHub Teams per plugin maintainers, I'd like

Re: GitHub issues option in HOSTING

I would like to vote +1 for GitHub Issues. I tried migration via the API for jira plugin and the only thing that we would lose is the original reporter (it would be noted in the comment but not the issue creator) - I think that this can be lived with. See

SonarCloud JenkinsCI organisation?

Hey, I'm trying to hook jira-plugin into SonarCloud, but when I'm trying to create jenkins or jenkinsci organisation, it shows me that the organisation already exists. Additionally, apparently I need organisation admin permissions on github.com/jenkinsci organisation to be able to link it

Re: Secrets in cloudbees builds of plugins

Resurrecting an old thread, Jesse, did anything change? On the current infra, is there any way to provide securely the token for coveralls? Travis has done it in the neat way: https://docs.travis-ci.com/user/environment-variables/#Defining-encrypted-variables-in-.travis.yml So this can be

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

Actually I think something's wrong. I have the same issue with jira-plugin that was released over 24h ago. v.2.2 is visible in both places: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/jira/ http://updates.jenkins-ci.org/download/plugins/jira/ but still not visible in Update Center

Re: Jenkins-ci.org v.2 (for love or money!)

On Wednesday, 7 October 2015 13:51:15 UTC+2, James Nord wrote: > > One thing I just realize is that we have our documentation (javadocs) on a > separate website. > Most sites these days just have a "documentation " section which will also > have an api section within the same site (and themed in

jira-plugin repository access

Hi, There is a pile of PRs waiting in https://github.com/jenkinsci/jira-plugin/pulls and nobody seems to maintain it anymore. Please grant committer access (gh user: warden) Thanks! Regards, Radek -- You received this message because you are subscribed to the Google Groups Jenkins