Chat for people who just starting contributing to Jenkins or want to do so. https://jenkins.io/participate/
@sidshah203_gitlab Hi. Have you already seen https://wiki.jenkins.io/display/JENKINS/Basic+guide+to+Jelly+usage+in+Jenkins ?
@oleg-nenashev Yep, I was trying to add new field into the config page,so I created groovy view file inside the /resources/jenkins/model/Test and it's respective java file under /java/jenkins/model/Test.java but it isn't being displayed in the config menu. I tried finding how to link the view inside the config page but couldn't find it.
All I found was either groovy views or jelly views and their respective java files.
... Describable
@sidshah203_gitlab if you could publish your current could somewhere, I could take a look. Also note that /configure includes only descriptor configs (aka global configs) automatically. The rest requires a GlobalConfiguration extension point
https://pastebin.com/QW2DBYa8 Can someone guide me on how do I get the following field under
/configure ?
Hello! I am wondering what open source license is being used for the token-macro-plugin (https://github.com/jenkinsci/token-macro-plugin). I don't see any specific license file in the repo, so does that imply that it uses the same license as Jenkins itself?
5 replies
@alfabravoteam yeah, we are working on improving our contribiting guidelines and on adding more features like automatic review requests and various automation bots. If you have any feedback or suggestiins about how we can improve contributor experience, please let us know
I think this is one of the most welcoming open-source projects for new contributors. Most things are covered and it's easy to start checking, reading, testing and submitting changes.
1 reply
If on interest to anyone, there will be a Jenkins Pipeline Workshop in Brussels on January 30, details here https://www.meetup.com/jenkinsmeetup/events/267974781/
roughly*
I've wanted to go to Canada for a long time
There are plans for CI/CD meetup in Ottawa - martinda is on the case
Hi all. Want to consult and receive recommendations about one plugin that I am interested in.
Prehistory: When I tried to get rid of freestyle jobs in preference to scripted pipeline, I faced problem with rewriting Matrix job because of build parameter - matrix-configuration-parameter-plugin (it is a table with axis and checkboxes). I want to find analogue for it, because I cannot use this parameter not in "Matrix job" (scripted pipeline is not a matrix kind). Moreover, last updates of this plugin were 2 years ago and I suppose it is abandoned.
Proposal: I just need build-parameter that will render table with multiple axis and checkboxes that will transform to multidimensional groovy array.
Questions: Does this kind of plugin already exist? If not, how difficult will it be to implement? Will it be in demand for other people or it is just a waste of time? Should I "enhance" matrix-configuration-parameter plugin or construct my own, without tying to "Matrix jobs" but create parameter to use it in pipeline jobs?
Prehistory: When I tried to get rid of freestyle jobs in preference to scripted pipeline, I faced problem with rewriting Matrix job because of build parameter - matrix-configuration-parameter-plugin (it is a table with axis and checkboxes). I want to find analogue for it, because I cannot use this parameter not in "Matrix job" (scripted pipeline is not a matrix kind). Moreover, last updates of this plugin were 2 years ago and I suppose it is abandoned.
Proposal: I just need build-parameter that will render table with multiple axis and checkboxes that will transform to multidimensional groovy array.
Questions: Does this kind of plugin already exist? If not, how difficult will it be to implement? Will it be in demand for other people or it is just a waste of time? Should I "enhance" matrix-configuration-parameter plugin or construct my own, without tying to "Matrix jobs" but create parameter to use it in pipeline jobs?
@Yunir You want that for pipeline? Is it something like this that you are looking for? https://jenkins.io/blog/2019/12/02/matrix-building-with-scripted-pipeline/
FYI, this might be better suited for the normal jenkins room here on gitter
"Matrix-logic" have already been implemented with
parallel command in scripted pipeline.
it was shut down in 2015 (https://issues.jenkins-ci.org/browse/INFRA-317) @Yunir as slide said, where did you find that link?
sorry for delay, it is in wiki page about Basic guide to Jelly usage in Jenkins attached as a "Useful links", but as it in read-only mode I cant do anything
anyway, is there any milestone (progress-bar/deadline) when all the wiki-pages will be transported to https://jenkins.io/doc and wiki will be shutdown (so there will be no reason jumping around first and second resource to find essential information)? Where can I watch the progress?
@Yunir there is not a milestone or progress bar or deadline for wiki page conversion to https://jenkins.io/doc, though I think that is a good idea. There is an ongoing discussion in the jenkinsci/docs gitter channel about the transition process. Gavin Mogan has suggested page redirects when a wiki page has been moved to jenkins.io.
@Yunir We have the plugin Docs migration tracking in https://jenkins-wiki-exporter.jenkins.io/progress . There is no tracking for no-plugin documentation as far as I know. I could create an EPIC for it, but we would need somebody to build a list of all pages to be migrated
There are 3 spaces in Confluence, in "jenkins" space there are 130 pages (1st level page under the "Home" page) - so we can count as progress these 130 pages with "Home" parent, and all nested pages down the tree can be counted as parent's page progress. That is the only way to find and note all the pages if I correctly understand the logic of Confluence.
It will be easier to draw the progress if u install trial version of any plugin that shows site-map for the separate space (after googling, I found two that might help, I suppose: better-content-archiving-for-confluence and sitemap-for-confluence) and create EPIC or the same page as https://jenkins-wiki-exporter.jenkins.io/progress but by this site-map for wiki-pages.
It will be easier to draw the progress if u install trial version of any plugin that shows site-map for the separate space (after googling, I found two that might help, I suppose: better-content-archiving-for-confluence and sitemap-for-confluence) and create EPIC or the same page as https://jenkins-wiki-exporter.jenkins.io/progress but by this site-map for wiki-pages.
I don't think we're willing to install a any trial plugins on that wiki instance. However, I like the idea of showing progress somewhere. We could create a ticket in Jira that tracks the progress on pages or we could extract the count of pages and compare the count of wiki pages to the count of redirects (see Gavin's proposal in the jenkinsci/docs channel)
The wiki is intentionally read only because of the spam problems that we are not willing to spend admin time to fight.
Then we can scrub them and close ones which are already migrated
Or close ones which should be just killed
@oleg-nenashev that sounds reasonable to me. There is a REST API call that will list all the wiki pages in a space. https://community.atlassian.com/t5/Answers-Developer-Questions/Way-to-find-all-pages/qaq-p/551847