-
Hello, I think the deadline has come?
在 2020年1月2日星期四 UTC+8下午7:50:41，Oleg Nenashev写道：
>
> I CCed the maintainer in this thread, so the 2-week timeout starts from
> today. I also would not expect a quick response in this period, so I would
> rather wait for more.
> My
As already mentioned in some previous threads, I extracted the UI components of
the warnings plugin into separate UI plugins. So other plugins can easily use
these components as well (without depending on the warnings plugin). The
following plugins are available as beta now (a source code
How do you opt in to the new notifications thing? I'm only opted in to
some code-owners feature right now.
On Wed, Jan 15, 2020 at 1:58 PM Joseph P wrote:
>
> Here's a crazy thought, use GitHub?
>
> It's a matter of creating appropriate repos and using GitHub issues / pull
> requests.
>
> For
Alright, I have some immediate concerns about the following aspects:
Plugins that contribute to the settings on on the Configure Jenkins page
> should carefully consider if allowing a user with only Jenkins.CONFIGURE
> could result in an unintended privelege escalation.
>
To me, this sounds like
Here's a crazy thought, use GitHub?
It's a matter of creating appropriate repos and using GitHub issues / pull
requests.
For announcement see
https://github.com/dotnet/announcements/issues
if you need some structure create a repo with the desired content structure.
GitHub can get pretty
I'll be reviewing this JEP from a security perspective over the next couple
days.
On Wed, Jan 15, 2020 at 7:02 AM Oleg Nenashev
wrote:
> Just to bump this discussion, the JEP draft was published as
> https://github.com/jenkinsci/jep/tree/master/jep/223
> Any feedback would be appreciated, there
I hoped there would be an easier way, but i'll try if i can figure it out
for the ECS plugin
Am Dienstag, 14. Januar 2020 18:11:27 UTC+1 schrieb Jesse Glick:
>
> On Tue, Jan 14, 2020 at 10:26 AM Andreas Sieferlinger
> > wrote:
> > The problem in this context is that due to the agents being
Hi,
I will try to join if time allows.
Would it make sense to repost this meeting in Advocacy SIG and
make it a recorded SIG meeting?
For those who are interested, below there is some Jenkins-related work by
CommitStrip.
There are also some comics about CI/CD/Jenkins by CommitStrip, but I was
Just to bump this discussion, the JEP draft was published as
https://github.com/jenkinsci/jep/tree/master/jep/223
Any feedback would be appreciated, there were changes since the last post
in this thread
Best regards,
Oleg Nenashev
On Friday, December 27, 2019 at 8:30:30 PM UTC+1, Michael
I'm interested as well
Github: fcojfernandez
JIRA: fcojfernandez
El miércoles, 15 de enero de 2020, 11:14:13 (UTC+1), Evaristo Gutierrez
escribió:
>
> Thanks Oleg and everyone!
>
> Github: varyvol
> JIRA: egutierrez
>
> On Monday, January 13, 2020 at 5:01:28 PM UTC+1, Evaristo Gutierrez wrote:
Thanks Oleg and everyone!
Github: varyvol
JIRA: egutierrez
On Monday, January 13, 2020 at 5:01:28 PM UTC+1, Evaristo Gutierrez wrote:
>
> Hi all,
>
> Nearly a month ago I raised [PR #124|
> https://github.com/jenkinsci/s3-plugin/pull/124] on the S3 plugin. It has
> not been reviewed or merged
+1 from me on doing the cleanup. Meetup groups come and go. Great to see
a documented way to gring them back to life.
On 14/01/2020 14.59, Oleg Nenashev wrote:
Thanks a lot for the notice Alyssa!
If my message is too long, *TL;DR: *the meetups will be restored, but it
is time to clean up the
12 matches
Mail list logo
