Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

GitHub documentation support is available thanks to Zbynek, I am just facilitating things and helping PRs to land. Anyway, I agree we should consider moving content to GitHub and jenkins.io where possible. Some useful links: * Plugin Documentation (including GitHub):

Re: Plugin Pull Request Approval

> Am 16.10.2019 um 19:58 schrieb Julio Guereca : > > Hi All!! > > I am attempting to merge a pull request for a plugin > (https://github.com/jenkinsci/bigpanda-plugin/pull/1 > ) > > Reading through some instructions, I did attempt to

Plugin Pull Request Approval

Hi All!! I am attempting to merge a pull request for a plugin ( https://github.com/jenkinsci/bigpanda-plugin/pull/1) Reading through some instructions, I did attempt to create a Jira ticket but could not find the *bigpanda-plugin *for the component field and didn't feel like I could move

wiki.jenkins.io is now effectively in read-only mode

Our primary wiki has been struggling lately without sufficient or motivation from anybody in the infrastructure team to fix it or keep it alive. We have also seen increased spam attacks, which must be pain-stakingly cleaned up. As a stop-gap measure I have restricted adding pages, comments, and

Re: Jenkins(Classic-Static-Core vs X) Pipeline Orchestration Definition

Hello Nofar, Thanks very much for your detailed response and product guidance. Regards Firmsoil On Monday, October 14, 2019 at 9:43:55 AM UTC-7, Nofar Bluestein wrote: > > Hello Firmsoil, > > Thank you for your question. > > Jenkins and Jenkins X today have very different use cases and

Re: Any workspace change between LTS 2.138 and 2.150?

The BOM (bill of materials) provides a set of dependency versions that are known to work together and that do not have enforcer conflicts. Refer to https://github.com/jenkinsci/git-plugin/pull/762/files and https://github.com/jenkinsci/git-plugin/pull/768/files for an example of the transition

Re: Any workspace change between LTS 2.138 and 2.150?

> `FilePathDynamicContext`? Quite possibly. Update your `test`-scoped > dependencies (or use the BOM) and check. > > > If this is right, how should it be modified so that it works again? > > Possibly just by wrapping in `FilePathDynamicContext. >> >> createContextualObject`. > > Thanks. I

Re: Question about reading json for plugin

Yea that's certainly related and a good long term solution On Wed., Oct. 16, 2019, 11:03 a.m. Jesse Glick, wrote: > On Wed, Oct 16, 2019 at 1:24 PM Gavin Mogan wrote: > > Because the htmlpublisher/archive doesn't let you view html pages that > have javascript due to the CSP security rules > >

Re: Question about reading json for plugin

On Wed, Oct 16, 2019 at 1:24 PM Gavin Mogan wrote: > Because the htmlpublisher/archive doesn't let you view html pages that have > javascript due to the CSP security rules See JENKINS-41891. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Ci-builds and release of hosted plugin

https://github.com/jenkinsci/jep/blob/master/jep/221/README.adoc For those who was trying to google jep and getting lots of results. On Wed., Oct. 16, 2019, 10:16 a.m. Jesse Glick, wrote: > On Tue, Oct 15, 2019 at 10:12 AM Fredrik > wrote: > > Am I miss understanding this or? > > > > The code

Re: Question about reading json for plugin

Because the htmlpublisher/archive doesn't let you view html pages that have javascript due to the CSP security rules https://github.com/halkeye/lighthouse-report-plugin Its just rendering the data, not doing any real work On Wed, Oct 16, 2019 at 10:22 AM Jesse Glick wrote: > On Wed, Oct 16,

Re: Question about reading json for plugin

On Wed, Oct 16, 2019 at 2:34 AM 'Gavin Mogan' via Jenkins Developers wrote: > I'm making a simple little plugin that takes in some json and spits it out > again inside of a react component. Why does this need to be a plugin at all? As opposed to just some CLI tool (or even Gist) you run inside

Re: Any workspace change between LTS 2.138 and 2.150?

On Wed, Oct 16, 2019 at 8:54 AM martinda wrote: > I suspect this change: > https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/101/files#diff-08a6dd4e3141d4c4e0c00e1e80734e19 > > might have broken the external workspace manager plugin. `FilePathDynamicContext`? Quite possibly.

Re: INFRA ci.jenkins.io

On Tue, Oct 15, 2019 at 6:48 AM pallen wrote: >win2012-1f85e0 was marked offline: Connection was broken: > java.util.concurrent.TimeoutException: Ping started at 1571135261424 hasn't > completed by 1571135501425 INFRA-2075 for the record. You can try adding forceAci: true to your

Re: Ci-builds and release of hosted plugin

On Tue, Oct 15, 2019 at 10:12 AM Fredrik wrote: > Am I miss understanding this or? > > The code is hosted at Jenkins and we will run ci-builds there. > But when releasing we will do it from our maven here. I am afraid there is no misunderstanding. See JEP-221. -- You received this message

Re: 2019 Elections: voting is delayed

I can shed some light on the challenges here. This year's election will run with the Condorcet Internet Voting System , a system pretty much used widely with other OSS projects/foundations. As with any software, Condorcet has its limitations which it shares in the

Re: Enabling ImgBot in jenkinsci and in jenkins-infra/jenkins.io?

None from me On Wed., Oct. 16, 2019, 6:33 a.m. Mark Waite, wrote: > No objections from me. > > On Wed, Oct 16, 2019 at 7:22 AM Oleg Nenashev > wrote: > >> Is everyone fine with enabling it for the Jenkins Core repository? >> Just to check whether we are ready for it >> >> On Tuesday, October

Re: Enabling ImgBot in jenkinsci and in jenkins-infra/jenkins.io?

No objections from me. On Wed, Oct 16, 2019 at 7:22 AM Oleg Nenashev wrote: > Is everyone fine with enabling it for the Jenkins Core repository? > Just to check whether we are ready for it > > On Tuesday, October 8, 2019 at 1:04:06 PM UTC+2, Arnaud Héritier wrote: >> >> The same I cannot add /

Re: Enabling ImgBot in jenkinsci and in jenkins-infra/jenkins.io?

Is everyone fine with enabling it for the Jenkins Core repository? Just to check whether we are ready for it On Tuesday, October 8, 2019 at 1:04:06 PM UTC+2, Arnaud Héritier wrote: > > The same I cannot add / change anything in >

Re: Question about reading json for plugin

In the past I've ignored Freestyle jobs in my plugins, but it's hard to say whether that works for you. I will say that I've had to retroactively add it when I found some luddites at my company that wanted to use it. How is the React component being served? Is it possible to add the JSON as a

Re: Any workspace change between LTS 2.138 and 2.150?

I suspect this change: https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/101/files#diff-08a6dd4e3141d4c4e0c00e1e80734e19 might have broken the external workspace manager plugin. If this is right, how should it be modified so that it works again? Thanks, Martin On Wednesday,

Re: Any workspace change between LTS 2.138 and 2.150?

On Wednesday, October 16, 2019 at 7:20:41 AM UTC-4, Daniel Beck wrote: >> On 15. Oct 2019, at 14:30, martinda wrote: >> >> Can someone explain why the inner-most sh step has a different workspace since LTS 2.150? > >Identical versions of plugins between the two? Excellent question. No

Re: Any workspace change between LTS 2.138 and 2.150?

> On 15. Oct 2019, at 14:30, martinda wrote: > > Can someone explain why the inner-most sh step has a different workspace > since LTS 2.150? Identical versions of plugins between the two? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: auto backward compatibility of plugin

> On 16. Oct 2019, at 11:03, Nikhil Bhoski wrote: > > protected Object ReadResolve() { > It's called readResolve, not ReadResolve. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: INFRA ci.jenkins.io

Hi Gavin, Thanks for the tip - certainly better then committing random edits to re-trigger the builds. Kind regards, Paul > On 15 Oct 2019, at 17:35, Gavin wrote: > > For now the easiest solution is to close the pr. Wait 30 secs and reopen it > > On Tue., Oct. 15, 2019, 3:48 a.m. pallen,

Re: auto backward compatibility of plugin

I tried below Read resolve did not seem to be working with this scenario. i may not be doing things rite . i tried below protected Object ReadResolve() { if(matlabRoot != null) { MatlabInstallation matlab = new MatlabInstallation("default", matlabRoot, null, false, false);

Question about reading json for plugin

Hey everyone, I'm making a simple little plugin that takes in some json and spits it out again inside of a react component. My original plan was just to do step(readFile('./report.json')) and take in the json as a large blob. I wanted to do this so I didn't have to worry about any logic to