Thanks Gavin, great explanation and insight. I'm likely worrying about nothing.
--
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
If its failing because of a system error, Then probably ignorable.
If its failing due to test breaking. It might be worth looking into.
Do daniel's point, If you just feel like ignoring it, ignore it.
In this case however, the error seems to be an issue between master talking
to agent, so not
Also make sure to launch with at least Java 8, preferably the exact version of
Java running Jenkins.
--
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
+1.
We do not have any RFEs in post-2.176 which would desperately need
availability in LTS as soon as possible. Taking the recent Trilead SSH fun,
I would not like to have the LTS scheduled to the conference timeframe if
we can avoid it.
BR, Oleg
> On Thursday, July 18, 2019 at 1:52:25
Hi all,
I would like to provide some heads up about what's going on with the JDK
Tool Plugin. This is a plugin which was detached from Jenkins 2.112, and
this plugin DOES NOT provide a JDK Tool for Jenkins like many users may
think. Actually it only provides an installer for Oracle JDK (Oracle
I like the plan. +1
On Thu, Jul 18, 2019 at 5:44 AM Daniel Beck wrote:
> Hi everyone,
>
> We've previously moved the LTS schedule back by two weeks for the release
> yesterday. Unfortunately, that means that the next LTS release would be
> done during DWJW on August 14.
>
> I don't know yet
Hi everyone,
We've previously moved the LTS schedule back by two weeks for the release
yesterday. Unfortunately, that means that the next LTS release would be done
during DWJW on August 14.
I don't know yet whether there will be security fixes ready to be included in
that release, but if they
Thanks for the clarification and the disclaimer! There is enough time to
cut a release and to address feedback if something goes horribly, so I
think it would be better than keeping the plugin in limbo. If you have some
time to periodically check for new issues, it is also better than the
current
While I can take over for now I have to mention that I will be on parental
leave from August on (6 months) and won't be having much time to maintain
the plugin.
If you still think this is a good idea:
Jira ID: jansohn
GitHub ID: jansohn
On Thursday, 18 July 2019 11:26:30 UTC+2, Oleg Nenashev
Also, please submit a pull request to
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-deploy.yml
in
order to get release permissions.
Doc:
https://github.com/jenkins-infra/repository-permissions-updater#requesting-permissions
On Thu, Jul 18, 2019
Two weeks have passed. What happens next?
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this
> I am requesting permission to use the Jenkins Logo,
Isn’t the logo using the Attribution-ShareAlike 3.0 Unported License? You don’t
need to ask to use it, you just need to reference the Jenkins project...
--
You received this message because you are subscribed to the Google Groups
You're the one doing the release, builds on CI mean nothing. ci.jenkins.io is
actually only CI, it does not publish (unless you count incremental, which you
shouldn't, as they are just a development tool).
> On 17. Jul 2019, at 23:56, Mez Pahlan wrote:
>
> Hi again. I'm probably worrying
> On 18. Jul 2019, at 02:09, martinda wrote:
>
> Jenkins GSoC Org Admin Team
You're representing the project here, so just use it.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving
14 matches
Mail list logo
