Jenkins link in top left should be customise-able for the destination so that users clicking it stay in the same app.

e.g. for account app it should be https://accounts.jenkins.io, (it should really be relative too so that in local dev you don't accidentally go to production).

also see jenkins-infra/account-app#149

cc @halkeye

Ensure the preservation of the navigation bar layout across all tabs on Jenkins.io. For additional details, kindly refer to the related GitHub issue #6917.

The publishCoverage step

is deprecated in favor of recordCoverage. Take a look at the pipeline docs for more information.

Optimally, the task should be migrated to the new method.

This issue comes from jenkins-infra/jenkins.io#6248

I created a solution for it but just for the main site

and the solution made a bad effect on other websites like the Account app

so we need to do a general solution
@halkeye so it's recommended to make a general fix to the component here, or just fix it for both websites?

Suggested by @MarkEWaite to add "Books" to the end of the "Documentation" drop-down menu of the navbar and remove the "Tutorial" submenus ("Guided Tour" and "More tutorials")
Please refer to this #71 for more details.

Right now whenever a commit to main happens, semantaic version will determine if it needs a release (fix/feat/breaking change) based on the commit message.

Apparently changesets gives a much better experience where you create changelog entries with full markdown, and then determines if a release is necessary.

Gives a much better/richer experience than plain commit messages, and way easier on contributors than to have to rewrite/rebase past commit messages.

Ref: https://www.reddit.com/r/javascript/comments/10chf6k/askjs_publishing_npm_packages_semanticrelease_or/

We require pull request titles to follow the Conventional Commits specification

There should be a CONTRIBUTING.md or pull request template explaining unusual requirements in advance.

Originally posted by @daniel-beck in #104 (comment)

Hello, I'm a potential GSoC student, I'm working on a demo and I'm using those components

the nav has extra space, I can work on it
@halkeye @krisstern

See e.g. jenkins-infra/jenkins.io#6373. No src/ directory.

On plugins.jenkins.io I noticed that jio components complain about the wrong locale code:

The script points to https://cdn.jsdelivr.net/npm/@jenkinsci/[email protected]/src/jio-locale.ts, however, should point to the declaration file located at https://cdn.jsdelivr.net/npm/@jenkinsci/[email protected]/build/jio-locale.d.ts

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://[secure]@github.com/jenkins-infra/jenkins-io-components.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀

What feature do you want to see added?

As of today (November 28) the Jenkins Contributor Spotlight site is now live.

Would it be possible to add this link to the header as its own item titled Contributor Spotlight? It could go between "Success Stories" and "Documentation".
For the footer, could it be added under the Community column?

The contributor spotlight repo has been updated accordingly and should have everything needed for inclusion.

Upstream changes

No response

Hi @halkeye , how are you mate? I have created https://www.npmjs.com/package/sirocco-wc which is a Scaffolding Tool for the fusion of lit with tailwind. which may allow you to mock away your infrastructure and use tailwind for css. I currently use it for cloudbees plugin.

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀