I just commit to origin when i'm doing small fixes as it's far easier
I'm mentoring a friend of mine to get started on contributing, and he opened his 1st PR: jenkins-infra/jenkins.io#4319. It looks like that we (maintainers) have to approve the worflow for each newcomer (see screenshot below). I understand it's the new GitHub "feature" to fight against bitcoin miners etc. Have we discussed how to sustain the fact that we have to curate PR to approve and run regularly?
Hello :wave: I was scratching my head this morning to understand how the help button magically appears on form, I was missing the field parameter in my jelly.... what do you think about adding some words about it in this page https://www.jenkins.io/doc/developer/forms/jelly-form-controls/ ? or is the magical help already documented somewhere else maybe ?
14 replies
Docs office hours start in 30 minutes at https://zoom.us/j/97040667867?pwd=UmU4MHl0V05pUkNzQlN5WStXZVdDdz09 . Meeting agenda at https://docs.google.com/document/d/1ygRZnVtoIvuEKpwNeF_oVRVCV5NKcZD1_HMtWlUZguo/edit#heading=h.js0tcvsxym7i
@rinino I think you're likely to find more help with that type of pipeline specific question by asking in the https://gitter.im/jenkinsci/jenkins channel. This channel focuses on creating the documentation and maintaining. It does not focus on specific Pipeline use cases
it seems the plugin API fails to get the github readme content in some cases: https://plugins.jenkins.io/api/plugin/conventional-commits/ any idea what went wrong?
1 reply
@zbynek: honestly, not really. lemme see if i currently have access to the logs and can look. Right now api is a bit of a black box
2021-05-04 21:31:56
04:31:56.522 [qtp580024961-1949] WARN i.j.plugins.services.impl.HttpClient - Unable to get content from https://api.github.com/repos/jenkinsci/conventional-commits-plugin/readme?ref=master - returned status code 404
04:31:56.522 [qtp580024961-1949] WARN i.j.plugins.services.impl.HttpClient - Unable to get content from https://api.github.com/repos/jenkinsci/conventional-commits-plugin/readme?ref=master - returned status code 404
@zbynek: so atm i was working on replacing the entire logic so it could handle different branches... buut i was doing it by moving that behavior into plugin-site instead of plugin-site-api, but it got overwhelming and didn't finish. Default branch is in update center now, so it should be doable to make the code process then use that field.
Currently, information on the above project is at https://groups.google.com/d/msgid/jenkinsci-docs/75abf68f-7f8e-41eb-a7ad-65935b6a1c79n%40googlegroups.com?utm_medium=email&utm_source=footer
@yr-sudhakar I think you'll want a local development environment for the Jenkins documentation site (www.jenkins.io). Refer to https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc for an introduction to the steps needed to do the setup. If you encounter problems while trying to configure a local development environment, we're happy to help here or we can have you share your screen during Docs office hours next week (Tuesday morning your time)
Currently checking jenkins-infra/jenkins.io#4333 to help the user, and I wonder why do we have this
Dockerfile with a docker build/docker run steps in the first steps in https://www.jenkins.io/doc/book/installing/docker/ ?
(same question: why recommended
dind or installing the docker-ce-client package on the controller node? Even why adding custom plugins ? )
(I'm hopefully willing to propose a page update if it would be the way to go: asking here to be sure that I don't step on any toe)
@dduportal:matrix.org we wanted the "Installing Docker" instructions to work for both a base installation and for the 3 tutorials related to build tools (Maven, NodeJS, and Python). In order to run a Maven container without requiring the complexity of creating separate agents, we used the Docker in Docker image to handle that case
Office hours now at https://zoom.us/j/97040667867?pwd=UmU4MHl0V05pUkNzQlN5WStXZVdDdz09
Hello! So as discussed on most recent Docs Office hours, I was supposed to write some blog(s) around the topic “My Experiences with Configuration as Code” so I chose to write a blog specifically about "Configuring Plugins with the help of the JCasC"
I'm sharing the Google Doc where you can find the blog contents along with a "Video Demo" link at the end of the blog. Since this is the first draft, I'm expecting tons of suggestions from your end to improve the quality of both the blog as well as the video demo. Feel free to point out if there's a sound problem, something which is unclear (due to accent maybe), if I'm doing something wrong, or really anything! Thank you!
Here's the link: https://docs.google.com/document/d/1S4kwEdRKD2y9_ojm89mS94akWcEnciyLb221fSQKb_s/edit?usp=sharing
2 replies
arg, plugin-site-api is so frustrating. The tests are failing during release step due to an elastic search data change. But it also seems like it can't read that file from target/ because it gets reset on prep. I feel ugly but skipping tests on release to get it out
Docs office hours for Asia and Australia will start in 7 minutes at https://zoom.us/j/97040667867?pwd=UmU4MHl0V05pUkNzQlN5WStXZVdDdz09 . Agenda is at https://docs.google.com/document/d/1ygRZnVtoIvuEKpwNeF_oVRVCV5NKcZD1_HMtWlUZguo/edit#heading=h.js0tcvsxym7i
Does https://plugins.jenkins.io/tfs/ show a suspended notice for anyone else? Warnings https://plugins.jenkins.io/warnings/ shows a suspended notice, as does https://plugins.jenkins.io/dry/
Thanks very much @zbynek ! That resolves many of the "no search result" queries that are being reported by Algolia statistics
@MarkEWaite: no i looked, tfs isn't there for some reason, its not in the update center json either
curl -qs 'https://updates.jenkins.io/current/update-center.actual.json' | jq '.deprecations | keys'
tfs probably should get added to the first one
it's available to be restored if a maintainer steps up and fixes tables to divs + the security issue
i guess yea, its suspended not depreciated, depreciated means won't come back
ish
wasn't un-suspended though because of a number of un-fixed security vulnerabilities
ah okay, i was just basing my statements on what people told me, which i guess is dangerous
https://github.com/jenkins-infra/plugin-site/pull/669#discussion_r628958863 -- @halkeye:g4v.dev these are the plugins we may consider adding to the deprecations file (sorted by usage)
@MarkEWaite is there any preference for capital letters in section names?
@zbynek Thanks for asking. The style guide says "Titles should only have the first letter intentionally capitalized ("sentence case")." https://github.com/jenkins-infra/jenkins.io/blame/master/STYLEGUIDE.adoc#L263 . However, I suspect that we've failed to follow that pattern in many places