On Mon, Feb 24, 2020 at 4:37 PM Oliver Gondža wrote:
> the baseline candidates
Reference: https://jenkins.io/changelog/
> in advance to speed up the discussion in governance meeting.
Are baselines still selected during governance meetings? I thought
that had switched to the list.
--
You
I am relatively new to the process of selecting a baseline candidate, but i
would like to voice support for the v2.222 weekly. I understand that the
timing is quite close to the LTS selection date, but so far in my testing I
have not encountered any issues. Although a number of the new major
Jesse - cheers for pointing out the previous AWS packaging attempt, I will take
a look.
Re version pinning, if this can’t be done in the POM, are there any Jenkins
tools which can do this, apart from the cloudbees assured update feed? (I’m
thinking of how we could support users on Jenkins
The second RC has performed flawlessly in my testing. I've been running it
for the last 9 days and have detected no issues. My environment runs a
Docker image with 30 agents including Windows, Linux, and FreeBSD. Jobs
that test for specific bugs are run in that cluster and are behaving as
well
The last release of 2.204 LTS line is scheduled for this Wednesday, and
so is the start of new LTS cycle. Let's voice the baseline candidates
and our concerns in advance to speed up the discussion in governance
meeting.
--
oliver
--
You received this message because you are subscribed to the
Mark, how does the second RC perform in your testing?
--
oliver
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Adopt OpenJDK is widely used in the Jenkins project. You're also welcome
to use other OpenJDK implementations. Licensing restrictions on recent
Oracle JDK 8 versions have made it very rarely used in the Jenkins project.
On Mon, Feb 24, 2020 at 11:38 AM Daniel Anechitoaie
wrote:
> Will do. Is
Will do. Is OpenJDK ok? Or i need Oracle JDK?
On Monday, February 24, 2020 at 8:35:39 PM UTC+2, Jesse Glick wrote:
>
> On Mon, Feb 24, 2020 at 12:05 PM Daniel Anechitoaie
> > wrote:
> > I'm compiling on OpenJDK 11.
>
> Best to use JDK 8 for all purposes related to Jenkins.
>
--
You received
On Mon, Feb 24, 2020 at 12:05 PM Daniel Anechitoaie
wrote:
> I'm compiling on OpenJDK 11.
Best to use JDK 8 for all purposes related to Jenkins.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop
Yes, it will. Unfortunately there are some significant delays due to
eventual consistency. Extra fixes may be needed.
FTR https://github.com/jenkins-infra/plugin-site/issues/132
On Mon, Feb 24, 2020, 17:36 Tony Noble wrote:
> So just to clarify - if I remove the 'adpot-this-plugin' topic from
Yes, that was it. I'm compiling on OpenJDK 11.
Using 2.164.1 works now even with parent
POM 3.56
Thank you.
On Monday, February 24, 2020 at 6:30:39 PM UTC+2, Mark Waite wrote:
>
>
>
> On Mon, Feb 24, 2020 at 9:19 AM Daniel Anechitoaie > wrote:
>
>> Hmm, yeah, I had a small brainfart. For some
So just to clarify - if I remove the 'adpot-this-plugin' topic from a
plugin's GitHub project, that will automatically sync to the plugin page?
Tony
On Thu, Feb 20, 2020 at 4:36 PM Oleg Nenashev
wrote:
> *TL;DR*: The process is up and running!
>
>- All foundation pull requests have been
On Mon, Feb 24, 2020 at 9:19 AM Daniel Anechitoaie
wrote:
> Hmm, yeah, I had a small brainfart. For some reason I was thinking in
> decimal and was seeing 3.6 as 3.60 which in my mind was more recent than
> 3.56 (which is the latest 3.x version)/
>
> So now with
>
>
> org.jenkins-ci.plugins
Hmm, yeah, I had a small brainfart. For some reason I was thinking in
decimal and was seeing 3.6 as 3.60 which in my mind was more recent than
3.56 (which is the latest 3.x version)/
So now with
org.jenkins-ci.plugins
plugin
3.56
And
1.8
8
2.121.1
I
On Mon, Feb 24, 2020 at 10:29 AM Daniel Anechitoaie
wrote:
>
> org.jenkins-ci.plugins
> plugin
> 3.6
This is very old. Try using the latest 3.x, and for the newer LTS line
you may need to use a 4.0 beta.
--
You received this message because you are subscribed to
Done, welcome Marky aboard!
On Monday, February 24, 2020 at 4:39:30 AM UTC+1, Marky Jackson wrote:
>
> Thank you Oleg and everyone else for the +1
>
> {
> "regards" : {
> "name" : “marky”,
> "phone" : "+1 (408) 464 2965”,
> "email" : “marky@gmail.com ",
>
Hi,
I just started working on a new plugin and when I run mvn hpi:run I get the
following error:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for org.slf4j:jcl-over-slf4j:1.7.25
paths to dependency are:
Hi John.First of all, thanks a lot for your interest!
The last meaningful update for the plugin was in 2011, so I would not
expect the former plugin maintainers are interested.
Since the timeout is over, I granted the GitHub access to John.
To release a plugin, few steps will be needed:
-
Hi Aytunc,
- Of course, I do not want to throw all the effort in the SPPR, I may use
> some of the codes from there, if it is okay ?
>
As long as you follow the MIT License requirements, sure.
You may also want to consider taking over this plugin or contributing to
its codebase, but it is up to
To follow-up on the original topics, I have approved all SonarCloud GitHub
app requests by plugin maintainers. If it addresses the use-case, no need
to setup the official organization for the moment.
Custom project setups are going to be a mess in the case of plugin
adoption, because we won't
Hello,
Do we have some concrete ETA for the wednesday's upcoming LTS? It will be
great to have some approximate time so we can plan in advance.
Thanks!
--
Raul Arabaolaza Barquin
Staff Software Engineer
CloudBees, Inc.
P: +34-637340429
E: rarabaol...@cloudbees.com
--
You received this
Just an update - my PR has now been merged by the plugin owner (thanks
Suresh), so I no longer need commit access. Please disregard this
conversation.
On Sunday, 23 February 2020 22:15:29 UTC, Ramzi El-Yafi wrote:
>
> Ok - CC’ing as requested.
>
> On 23 Feb 2020, at 20:00, Tim Jacomb wrote:
>
22 matches
Mail list logo
