Hi,
I'd like to adopt scm-filter-aged-refs-plugin. (Mainly to add GitLab
support, but also to modernize it and keep it up-to-date)
- Link to a plugin you want to adopt:
https://github.com/jenkinsci/scm-filter-aged-refs-plugin
- The status of the plugin: abandoned (Last commit over a year ago)
-
Hi again,
On Sat, Sep 25, 2021 at 12:34:04AM +0200, Tobias Gruetzmacher wrote:
> > Created this issue to keep track of this failure. Once jnr/jffi#113
> > fixed, jenkins test failure on s390x will be resolved
>
> Please take a look at https://github.com/jnr/jffi/pull/114 - W
Hi,
On Wed, Oct 06, 2021 at 08:47:36AM -0700, Adam Leon Smith wrote:
> Hi all,
>
> We are trying to release a jenkins plugin. On preparing the maven
> release, maven throws the below:
>
> Unable to tag SCM
> Provider message:
> The git-push command failed.
> Command output:
> fatal: remote
Hi,
I'd like to adopt the Amazon ECR plugin:
- https://plugins.jenkins.io/amazon-ecr/
- https://github.com/jenkinsci/amazon-ecr-plugin
It's a pretty simple (3 classes) but also pretty useful plugin. No
current plans to add new features, only modernizing the plugin, updating
to the modular AWS
Hi,
Am Fri, Sep 24, 2021 at 01:13:18PM +0530 schrieb Nayana Thorat:
> This failure is due to unavailability of libjffi-1.2.so for s390x .
> basically jenkins/core uses posix.jnr which downloads and uses
> jffi-1.3.3-native.jar. jffi-1.3.3-native.jar doesn't have
> s390x/libjffi-1.2.so though
Hi,
Am Tue, Sep 21, 2021 at 03:14:57PM +0100 schrieb Tim Jacomb:
> There was a clear reliable failure change in 2.309 which was caused by
> a minor resource increase required.
>
> But because the resources were so low on the CI (accidentally) it
> manifested as a problem there.
Just as a data
Hi all,
I'm sorry to say that I'm going to orphan the lockable-resources-plugin.
The main reason is that I'm basically not using it anymore, so testing
any changes is pretty hard for me.
I thing the plugin is in a good shape at the moment, but it could use
some love to provide an even better
Hi,
On Sat, Sep 26, 2020 at 06:33:48AM -0700, Léon Hagenaars-Keus wrote:
> The thing this plugin does is provide a global 'build now' url for a
> json post, where the plugin looks at all jobs using the gitlab repo
> contained in the webhook post, and triggers those jobs (depending on
> branch
Hi,
On Tue, Sep 22, 2020 at 02:04:48AM -0700, Léon Hagenaars-Keus wrote:
> Is the development of the gitlab hook
> (https://github.com/jenkinsci/gitlab-hook-plugin,
> https://plugins.jenkins.io/gitlab-hook/) abandoned?
Well, there haven't been any commits in ~3 years, so that's probably a
"yes".
Hi,
On Sun, Sep 13, 2020 at 07:44:14PM +0200, Miguel Campos wrote:
> I saw early today that oracle released their ojdbc jar to maven central.
>
> Does that mean any license change?
Not in a significant way. These artifacts are governed by this license:
On Tue, May 12, 2020 at 01:06:57PM +0200, Oleg Nenashev wrote:
> Proposal. We suggest to explicitly document the theme support policy
> in the Simple Theme Plugin plugin documentation and in Jenkins user
> documentation. We suggest to explicitly document the current state of
> affairs even if it
Hi,
sorry for my slow responses. I'll try to dedicate more time to this
plugin in the coming weeks.
On Sun, Apr 12, 2020 at 12:02:29AM -0700, Tomas Bjerre wrote:
> I have a couple of PR:s open on Lockable Resource Plugin:
>
> * Adding skipIfLocked:
>
Hi,
I'd like to adopt the compact-columns-plugin - I know it's quite old,
but I like it and it's pretty small. It seems there wasn't a "real"
commit or release in over 6 years (which speaks for the API stability in
Jenkins core :D). Last maintainer is added in CC, more recent commits
and release
Hi,
search also looks a little funky in my Neo2 theme: https://imgur.com/9UC4jQZ
Looks like a minor fix IMHO.
On Tue, Feb 25, 2020 at 02:23:28PM +, Tim Jacomb wrote:
> That looks like a fairly minor css tweak to fix that, is it just the
> search input? I wouldn’t exclude it from LTS for
gt; Heiko
>
> -Ursprüngliche Nachricht-
> Von: Tobias Gruetzmacher
> Gesendet: Montag, 13. Mai 2019 10:34
> An: jenkinsci-dev@googlegroups.com
> Betreff: Adopting lockable-resources plugin
>
> Hi,
>
> I'd like to adopt the lockable-resources plugin if no one objects. I'm
>
Hi,
I'd like to adopt the lockable-resources plugin if no one objects. I'm
currently using the plugin in my company's workflow and have one or two
issues with it (I already opened a pull request[1] but nobody with
commit access reacted, even after some prodding...) Apart from that, I'm
open
Hi,
On Mon, Jan 07, 2019 at 05:13:14PM -0800, Ryan wrote:
> FYI, I made a comment - It's worth noting that GitLab CI is not
> available in the Community Edition, which makes Jenkins the best
> available alternative. A strong integration point between Jenkins and
> GitLab Community Edition makes
Hi,
On Wed, Oct 10, 2018 at 07:21:53PM +1030, David van Laatum wrote:
> The next thing I was planning to do was rip a bunch of stuff out and
> put it into a ext-notification plugin that is extendable to allow
> multiple backend drivers ie email and slack. As I see most
> notification style
Hi,
since I'm providing a theme for the simple-theme-plugin
(https://github.com/TobiX/jenkins-neo2-theme) and the plugin is up for
adoption, I'd figure it would be appropriate that I'll maintain it ;)
My GitHub-ID: TobiX
My Jenkins-LDAP-ID: tgr
Regards, Tobias
PS: Should I change the groupID
Hi,
as far as I can see, console-column-plugin[1] is orphaned and
extra-columns[2] contains a column with the same use case. Would it make
sense to deprecate console-column-plugin? How would one notify users to
switch to extra-columns?
Regards, Tobias
[1]
20 matches
Mail list logo
