Hello,
I would like to adopt the gitlab-oauth-pugin, to take care of the
current issues of the plugin.
Gitlab-User-Id: bjkastel
Jenkins-User-Id: bjkastel
I've already tried to contact the current maintainer at the beginning of
September, unfortunately he hasn't answered yet. I've added him
-
> Asciidoc format can be used as well, with the .adoc extension.
- I can add that pretty easily
-
- > Remove the macro references in the top of the document.
-
- Totally done
> If the document includes "Table of contents", remove this section in
Markdown or replace it by :toc: macros in
Okay~~~
https://jenkins-wiki-exporter.g4v.dev/ is now updated to support markdown,
or a zip of markdown + images
Gavin
On Sun, Oct 20, 2019 at 2:11 PM Gavin Mogan wrote:
> Thanks for the PR, I've deployed the change, and started to get prepped
> for straight up markdown, markdown + zip with
> Should I upgrade the plugin to JDK 9+ or it's not mandatory because from
SLA perspective Jenkins should be upgraded?
I believe jenkins core is still minimum requirement of java 8. According to
https://jenkins.io/doc/administration/requirements/java/ 9 and 10 are
explicitly not supported. So
Title: Re: Guideline for upgrading plugin to JDK 9+
I think that's the second option:
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ cucumber-reports ---
[INFO] Restricted to JDK 1.8 yet com.fasterxml.jackson.core:jackson-annotations:jar:2.10.0.pr2:compile contains
You should not change to JDK 9 if not absolutely necessary.
Did your dependency really change the API to JDK 9? Or did they just compile
with JDK 9 and add a module information file which requires the increased class
file level? Those files can be ignored in the pom...
> Am 20.10.2019 um
Hi,
After upgrading some plugin dependencies I found that dependency is
compiled against JDK 9 while my plugin still uses 8 - compilation has
failed.
Is there any recommendation, guideline, best practices that guide about:
1. Should I upgrade the plugin to JDK 9+ or it's not mandatory
Thanks for the PR, I've deployed the change, and started to get prepped for
straight up markdown, markdown + zip with images, and eventually adoc
I'm totally up for forking it to infra or something, I have no idea how to
do that though.
On Sun, Oct 20, 2019 at 1:50 AM Oleg Nenashev
wrote:
>
Hi everyone,
I'm confused by the board election process as currently proposed.
According to https://wiki.jenkins.io/display/JENKINS/Board+Election+Process
* We will never have an even number of board members ("Odd number of people
prevents the tie problem")
* KK holds a permanent position on
Thanks Gavin!
I submitted the pull request for truncating RAW HTML which should improve
the layout. More pull requests to come soon. I would suggest hosting this
service on jenkinsci or jenkins-infra. I think we can get a lot of
contributions. Also, I think we should reserve opportunities to
10 matches
Mail list logo