Can not download the archive
https://updates.jenkins.io/download/plugins/javadoc/
https://get.jenkins.io/plugins/javadoc/1.6/javadoc.hpi

Hi Team,
As mentioned in the Doc the following line states that this plugin will be able to connect to bitbucket.org (cloud).
"This plugin builds pull requests from Bitbucket.org and will report the test results. Basic documentation can be found on GitHub."
Can you confirm on this that if this supports the same functionality with bitbucket datacenter as same as it functions with bitbucket cloud?

Thanks in advance.

Regards,
Manjunath R

Problem with the Pipeline: Stage View page, source file

The github link redirects to https://github.com/jenkinsci/pipeline-stage-view-plugin/pipeline-stage-view which is a 404

Screenshots

TODO: Add screenshots if possible

Possible Solution

N/A

There are many plugins which use CHANGELOG.md, e.g.

• https://github.com/jenkinsci/workflow-job-plugin/blob/master/CHANGELOG.md
• ... many other Pipeline plugins
• https://github.com/jenkinsci/compuware-topaz-utilities-plugin

It would be great to add support for this source if the information cannot be retrieved from GitHub Releases

Going to page 2 of search results, then searching for more specific (adding labels/categorys/or query string) will show no results cause on page 2 not page 1

Problem with the Search page, source file

Single-column layout looks bad on mobile

Screenshots

Android/Chrome:

Possible Solution

• fix minimum width, reallign controls

Problem with the docker-build-step page, source file

The documentation is misleading
at the
"Set Docker URL" section, it is mentioned
"For other nodes, you may need to set something like http://127.0.0.1:2375"
Setting such URL leads to
"Something went wrong, cannot connect to http://172.16.1.12:2376, cause: null"
Log shows
"Unsupported protocol scheme found: 'http://172.16.1.12:2376'. Only 'tcp://' or 'unix://' supported."
Switching to
tcp://172.16.1.12:2376
Seems solves the issue

Screenshots

TODO: Add screenshots if possible

Possible Solution

N/A

Problem with the Job Import page, source file

TODO: Describe the expected and actual behavior here
The job description in remote jenkins server is in Japanese of UTF-8. After pressing query button, the list shows up the
job lists from remote jenkins server, but the job description is garbled.

Screenshots

TODO: Add screenshots if possible

Possible Solution

In the following part of source, couldn't find handling of UTF encoding.

file: src\main\java\org\jenkins\ci\plugins\jobimport\client\RestApiClient.java

DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setFeature("http://xml.org/sax/features/external-general-entities", false);
factory.setFeature("http://xml.org/sax/features/external-parameter-entities", false);
factory.setFeature("http://apache.org/xml/features/disallow-doctype-decl", true);
factory.setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false);

Somthing like below, directly handle UTF-8. Or use another configuration parameter.

InputStream inputStream= new FileInputStream(completeFileName);
Reader reader = new InputStreamReader(inputStream,"UTF-8");
InputSource is = new InputSource(reader);
is.setEncoding("UTF-8");

    DocumentBuilderFactory dbFactory = DocumentBuilderFactory.newInstance();
    DocumentBuilder dBuilder = dbFactory.newDocumentBuilder();
    Document doc = dBuilder.parse(is);

N/A

IMHO the category header is too big. Currently it is h2 with a size of 2rem:

Suggestion

if we reduce it, it would look much better.

1.2 rem

1.1rem

Hi,

I am running testng (version 1.15) from Jenkins.
I want to be able put newline inside the message.
I try to add "/n" or
but it just show as it and not make new line.
I try with this parameter "Escape exception messages?" checked and unchecked.

I also want in some cases add other html tags.

Can it be done and how ?

Thanks

It would be cool if we could use labels to generate a tag cloud. It would help to highlight the most popular areas/technologies and help users to discover them.

Nice 2 have: each label is a hyperlink

jenkins版本：2.222.1
Publish over SSH版本：1.20.1，
修改了配置信息，项目构建依然使用历史配置信息，
临时解决方案：修改历史SSH Server的Name，历史使用该配置的项目，需要将配置打开，重新保存一下
建议修改：修改Publish over SSH配置后，推送历史项目最新配置文件

Problem with the GitHub page, source file

Link is https://github.com/jenkinsci/github .. which results in a 404
however this seems valid: https://github.com/jenkinsci/github-plugin .. which works and shows 1.3.0 as current version.

Screenshots

TODO: Add screenshots if possible

Possible Solution

Just update to correct link please.

N/A

plugin site:

jenkins.io:

When we use the Tower Plugin in a Freestyle Jenkins Promotion step, the credentials field is not passing the value to Tower job to override the credentials in the Job Template. We did notice that if we put in a bogus value in the Jenkins plugin Tower does report the credentials does not exist. Remember this is just when we use the plugin in a promotion step, this all works perfectly if we use the plugin in a build step.

TODO: Describe the expected and actual behavior here

Screenshots

TODO: Add screenshots if possible

Possible Solution

N/A

Problem with the CVS page, source file

TODO: I try to save the properties of my project, the CVS Root ist set but when saving the project i get this error

Screenshots

I use Jenkins 2.258 with CVS Plugin Version 2.16.

I need help, because i cannot change any of my projects.

Possible Solution

N/A

1. Go to plugins.jenkins.io
2. Enter any search term
3. Press enter and/or click the search button

Nothing happens.

Problem with the Gatling source file

TODO: I'm getting the gatling report pushed to my jenkins job area by using 'gatlingArchive()' function. Simulation result is being pushed okay too. But when I try to open the link, it's triggering a download to my disc, instead of rendering the result in html format in jenkins.

Screenshots

Possible Solution

N/A

E.g. https://plugins.jenkins.io/log-cli/ looks weird. These are h1s, and they have a 4rem margin on top.

Enhancement for the Config File Provider page,

TODO: I would like to allow certain people to have access to this plugin as read-only and other as read-write permissions

If possible to add this plugin to the Project-based Matrix Authorization Strategy and Role-Based Strategy.

Thank you ,the default port the gitee-plugin webhook use is 8888, but that port has been used.So I wonder if I can change the port in webhook ?
Thanks!

Currently the plugin site uses Jenkins Jira. Many plugins use GitHub Issues, and for them we still display Jira. E.g. https://plugins.jenkins.io/configuration-as-code/#issues , CC @timja @jetersen . I am not sure what is missing there, maybe we just need to get the update center metadata over the line

Migrating https://issues.jenkins-ci.org/browse/INFRA-2434:

https://plugins.jenkins.io/external-monitor-job shows the Japanese wiki page content from https://wiki.jenkins.io/display/JA/Monitoring+external+jobs and not the content of https://wiki.jenkins.io/display/JENKINS/Monitoring+external+jobs despite https://github.com/jenkinsci/external-monitor-job-plugin/blob/a401b0ce4220272abd986c85db2aada5de6818fe/pom.xml#L15

main.module.css is using css modules, and a lot of !important rules

Migrate everything to normal postcss style css rules so its using the same system

• There are 7 plugins marked with a label: https://plugins.jenkins.io/ui/search/?labels=adopt-this-plugin
• Navigating to any plugin page does not show the respective label and the adoption warning which should be displayed after #130
• Same for deprecated. https://plugins.jenkins.io/ui/search/?labels=deprecated works, but not all plugin pages actually show it

Looks like the static pages were not regenerated after the merge of jenkins-infra/update-center2#342 (24 hrs ago)

Problem with the Job Import page, source file

When we import jobs that is in folders, we are getting invalid character "" message

Screenshots

Possible Solution

N/A

it would be great to add a new "report a problem" button so that Jenkins users could quickly create GitHub issues. It would be similar to what @timja did in jenkins-infra/jenkins.io#2896 for jenkins.io

Problem with the GitHub Branch Source page, source file

setting the apiRateLimitChecker in the Github API Configuration via config-as-code results in a broken GUI setting in the Jenkins global config (see screenshot below)

gitHubConfiguration:
    apiRateLimitChecker: ThrottleOnOver
    ...

basically you can only set those values with casc:

• ThrottleForNormalize
• ThrottleOnOver
• NoThrottle

as this is exposed as enum value ... so all other values are blocked anyway. So the casc part seems to be correct, but as soon as it is deployed with any of those values, the GUI setting gets broken. You cannot change the value anymore there, as the list only contains the one selected value (untranslated).

Screenshots

screenshots of broken UI after rolling out with config-as-code

Possible Solution

It might be just a display bug ?

Problem with the Active Directory page, source file

TODO:
Actually I can't download the active directory plugin (active-directory.hpi) from the download site
https://updates.jenkins.io/download/plugins/active-directory/
I always get the message "The requested URL /plugins/active-directory/2.16/active-directory.hpi was not found on this server."

Best Regards
Ingo

Problem with the Docker page, source file

TODO: Releases tab doesn't contain any info

Screenshots

TODO: Add screenshots if possible

Possible Solution

N/A

Just a cosmetic/confusing minor problem with the Bitbucket page, source file

In the history, PR-63 and PR-58 seem to be the other way around.

Possible Solution

Swap the changelog entries, PRC-63 is PR-58 and vice-versa.

In some cases trends look and feel can be improved, especially we could chose minimum and maximum Y axis values. See the trend for Ownership plugin, for example

Currently the plugin name is shown only on the documentation tab.
I propose to move it up above the tabs and to display it for all tabs.

Current plugin version can be moved to a separate row within the documentation or kept as is now

I need to run performance tests with varied parameters(for example number of parallel jobs) using Jenkins pipeline. Tests should run in parallel so Kuberntes Job is the best choice for that. When I'm starting a pipeline with the following code:

pipeline {
  agent any
  stages {
    stage('Running Jmeter') {
      agent {
        kubernetes {
            label "jmeter_tests_executor"
            yaml '''
apiVersion: batch/v1
kind: Job
metadata:
    name: jmeter
    namespace: jenkins
spec:
  parallelism: 2
  completions: 2
  backoffLimit: 1
  ttlSecondsAfterFinished: 100
  ...   

Pipeline hangs trying to schedule a task:
All nodes of label ‘jmeter_tests_executor’ are offline...
When I run that manifest directly on kubernetes cluster it works without any problems.
Is it possible to implement this using your plugin? Do you have a plan to make it possible?
Probably you know another options how to do it, but I should be able to run them in parallel,get logs during/after execution.
Will appreciate you help as it's not rather popular issue.

right now it just says
UI TBD / API bd2a5fe

After creating a credential, plugin doesn't list new credential in Jenkins setup page neither in job setup page.

Jenkins version: 2.249.1 (installed with apt-get)
OS: Ubuntu Linux in AWS

see #252

Should be https://github.com/jenkins-infra/plugin-site/tree/master/src/templates/plugin.jsx
but is https://github.com/jenkins-infra/plugin-site/tree/master/srctemplates/plugin.jsx
(note the srctemplates vs src/templates)

There is no reason other than my lack of front-end/design skills that https://updates.jenkins.io/download/plugins/log-cli/ looks like it does.

It's an HTML page, entirely generated by https://github.com/jenkins-infra/update-center2/ and it would be straightforward to pull in e.g. https://www.jenkins.io/template/ and fill it with content, so that it looks like it's properly part of the site.

I'd be happy to do the effort on update-center2, perhaps a plugin site contributor would be interested in designing the page contents? As a first iteration I'd be happy to just take the current content and wrap it in the page template, but something nicer may be worth some additional effort?

When Powershell-plugin 1.4 creates a temp Powershell script file, it inserts a new line of code as the first line of the file. The new line is either,
$ErrorActionPreference="Continue" (When "Stop on Errors" option is unchecked)
or,
$ErrorActionPreference="Stop" (When "Stop on Errors" option is checked)

This insertion breaks original code with param() because it must be the first line. An exception was thrown saying, "The term 'param' is not recognized as the name of a cmdlet, function, script file, or operable program.".

The "ErrorActionPreference" line should be taken off, code developers can certainly manage it by themselves. Or, it should be inserted after the param() block.

Jira ticket: https://issues.jenkins-ci.org/browse/JENKINS-63153

Information in https://github.com/jenkins-infra/plugin-site#running-the-app is needed for users, not contributors. It would be great to move it to https://github.com/jenkins-infra/plugin-site/blob/master/CONTRIBUTING.md so that potential contributors can easily discover it

Copied from https://issues.jenkins-ci.org/browse/INFRA-2425

https://plugins.jenkins.io/websphere-deployer is a plugin that should show a warning exclamation icon next to the plugin name, that opens a popup listing the active security warnings.

(The warnings in the description text are probably just legacy content from the wiki.)

Additionally, warning indicators appear to have been list on the plugins list (search results etc.) as well, although I'm less sure they existed before.

"Previous security warnings" in the sidebar (e.g. https://plugins.jenkins.io/git ) still exist, so it's unlikely to be a data problem.

cc @daniel-beck / @halkeye

Remove the need for search/browse to access plugins.jenkins.io, so in theory the api doesn't need to be exposed to the public

All the data is already in the site anyways.

Good morning,
we're in the process of automating the setup of Jenkins and ran into a problem during the installation of the Nexus Platform plugin (nexus-jenkins-plugin):
The checksum for release 3.9.20200722-164144.e3a1be0 is wrong (as reported by the Update Center).
We've also downloaded the plugin from Sonatype directly and verified that the checksum provided by them is correct.

Seems that something went wrong during the creation of the JSON file for the Update Center.
We also found that this is not an isolated event, e.g. the checksum for release 3.8.20200310-130318.c482b58 is wrong as well.
Regards,

Steffen Elste

Problem with the Release Helper page, source file

Actual: Trying to add values to a custom field of type label. Plugin reports
java.lang.RuntimeException: Field with the name "Build Version" does not exist!

Expected: Field is amended with the given value.

Screenshots

N/A

Possible Solution

N/A

Problem with the Team Concert page, source file

TODO:

Expected: No "slave" mention in document.

Actual: Found the below mention :
(https://plugins.jenkins.io/teamconcert/)
Under RTC topic
"For all the supported build configurations - Build Definition, Repository Workspace, Stream and Snapshot - a valid build toolkit should be present on both the master and slave machines and the Jenkins jobs should be configured to use this toolkit."

Screenshots

Possible Solution

Edit page such that "master" and "slave" used in doc can be removed

Problem with the OWASP Markup Formatter page, source file

I am browsing the new/recently added Releases tab on any of the plugins pages. Clicking on one of the Github Pull Request links goes to a 404 page on plugins.jenkins.io instead of going to the Github Pull Request page.

E.g. https://plugins.jenkins.io/antisamy-markup-formatter/issues/22

Possible Solution

This is similar to #255 and #264 but not identical as those bugs are related to Github Issues and not Pull Requests, however it might be considered a duplicate since the Github issues url redirects to the pull request if given the correct PR number in the url.

E.g. if https://plugins.jenkins.io/antisamy-markup-formatter/issues/22 is converted to jenkinsci/antisamy-markup-formatter-plugin#22 then Github will redirect to the correct PR/pull url at jenkinsci/antisamy-markup-formatter-plugin#22. Should the links be changed to go directly to the PR/pull url or is it ok to rely on github redirecting from the issues url?

Problem with the GitHub page, source file

The graphics are so tiny they are impossible to read (too few pixels) and it's hard to be sure what in Jenkins they are meant to refer to. It's not a matter of browser scaling.

One example: https://github.com/jenkinsci/github-plugin/blob/master/docs/images/ghserver-config.png

(I think that says "GitHub Server Config", which is what the text says - but isn't it called "GitHub plugin"? Or is this somewhere else?)

A worse example: https://github.com/jenkinsci/github-plugin/blob/master/docs/images/manage-token.png

Screenshots

Possible Solution

Replace the screenshots with larger images

For now direct link to jira

when jira/github gets decided on, and exposed, then should goto the right place.