Allow me to append myself to the list of developers who would like access
to Java 11 APIs. If we had access to Java 11 APIs, then this
Hi
Hello Victor, would you be able to attend tomorrow's Infra session (or does
> it collide with yours?).
>
I think they don't clash, but I'm not sure though
That would be a great discussion (sounds like webhooks and rebuild can be
> discussed and at least clarified)
>
+1 :)
Thanks a lot!
>
On Thu, Jun 24, 2021 at 5:18 AM Ullrich Hafner
wrote:
> I often have this problem that my working JCasC configuration suddenly
> breaks after an upgrade of JCasC (or another plugin) and Jenkins just not
> starts up. And then you need to dig into log files to see what happens. It
> would be much
On Thu, Jun 24, 2021 at 9:07 AM Tim Jacomb wrote:
>
> There are some flags you can use to tune this behaviour:
>
Hello Victor, would you be able to attend tomorrow's Infra session (or does
it collide with yours?).
That would be a great discussion (sounds like webhooks and rebuild can be
discussed and at least clarified)
Thanks a lot!
Damien
Le jeudi 24 juin 2021 à 17:35:12 UTC+2, ga...@gavinmogan.com a
I've had times when those groovy scripts "silently" fail on startup, and
while isn't a big deal when I'm just restarting an existing instance, it
does suck when I'm spinning up a new instance and suddely I don't have
security setup.
I used to pair my jcasc config with my jenkins docker image, so
There are some flags you can use to tune this behaviour:
https://github.com/jenkinsci/configuration-as-code-plugin/blob/a6983ff60e0cf198ce02d7992bcba927197174db/test-harness/src/test/resources/io/jenkins/plugins/casc/validSelfConfig.yml#L1-L5
The default is to show an error page with what failed.
On Thu, Jun 24, 2021 at 2:18 AM Ullrich Hafner wrote:
> This is a very bad user experience (actually I don’t know of any other
> application that does not start because of a configuration error).
I concur. My initial impression is that JCasC lacks polish, and I was
surprised to see it promoted
I'm sorry i dont understand what your referring to. Do you mean that we do
ci builds for each branch and pr? That seems like the main purpose of ci
What problem are you trying to solve?
On Thu., Jun. 24, 2021, 1:56 a.m. Victor Martinez, <
victormartinezru...@gmail.com> wrote:
> Hi there,
>
>
Hi, any updates on this?
I have not been able to fix this tests yet, it seems Mockito related.
If you can help a bit with that Wei, I am happy to take this over if nobody
responds.
A simply change to the line that has the quote is probably also good, then
the issue is gone too.
On Saturday, May
Cf. https://github.com/jenkinsci/configuration-as-code-plugin/issues/912
On Thu, 24 Jun 2021 at 11:18, Ullrich Hafner
wrote:
>
>
> > Am 24.06.2021 um 00:54 schrieb Basil Crow :
> >
> > After all these years, we finally migrated from Groovy initialization
> > scripts to JCasC on our Jenkins
> Am 24.06.2021 um 00:54 schrieb Basil Crow :
>
> After all these years, we finally migrated from Groovy initialization
> scripts to JCasC on our Jenkins controllers.
>
> While any configuration error is a problem, I noticed that the way
> these errors are reported differs from one mechanism
I've just reported https://issues.jenkins.io/browse/JENKINS-65978
I started to see recently that editing a GitHub PR title triggers a build
in the CI even for the same commit that was built previously. I initially
though it could be some misconfiguration in my company's CI, but then I've
found
Hi there,
I've seen the branch indexing enabled for the plugins in ci.jenkins.io, and
I'm not sure if this is needed or something that should be skipped in terms
of reducing the cost of the infrastructure.
I did a quick search in the jenkins-infra org but I could not find any
references to
Hello dear ci.jenkins.io users,
This email is a notice that today, the agents on ci.jenkins.io that are
virtual machines (ubuntu, ubuntu High-Mem and Windows 2019) will be
upgraded as per https://issues.jenkins.io/browse/INFRA-2976.
The main changes to have in minde are the following (if you
15 matches
Mail list logo