Hello.
Adding my credentials as suggested
here: https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin to speed up
the process..
Github: *guipal*
Jenkins infrastructure account: *palacgui*
Thank you!!
El miércoles, 25 de octubre de 2017, 10:54:09 (UTC+2), guiller.pal escribió:
>
> Hello
Hi,
I would still like to be maintainer of the claim-plugin, but have been very
busy during the last months.
If Arnaud want's to share the ownership in the long run I am fine with that.
Christian
On Fri, Oct 20, 2017 at 7:39 AM, Arnaud wrote:
> Hello Daniel,
>
>
>
>
On Fri, Oct 27, 2017 at 4:22 PM, Daniel Heid wrote:
> I tried to fix the arbritrary code execution vulnerability in the
> PostBuildScript plugin
Why not just use the Groovy Postbuild plugin, which has comparable
functionality (IIUC) but is long since secured, and better
After some discussion within the CERT team, I am happy to propose
https://github.com/jenkinsci/jep/pull/23/files?short_path=b956eee
as a security hardening measure going forward.
(Yes I know the JEP process itself has not been formally adopted yet,
but I figured it could not hurt to start
Actually Hervé Boutemy at Maven was wondering how we (Maven) could use
Jenkins more effectively.
My email description was not doing justice, and I realised that people
needed a new series on plugin development.
Blogs can take a lot of effort to write, plus sometimes it’s better to see
someone
Hi Christian,
However, if you feel like you can invest some time to merge PRs and release
the plugin in a near future, I'm totally ok to have you stay the sole
maintainer.
On the contrary, if you feel like it is a better option to have someone
else to manage this, maybe just for some time
No surprises in my last 3 days of background testing of LTS release
candidate.
Mark Waite
On Thu, Oct 26, 2017 at 9:03 AM Oliver Gondža wrote:
> Hello everyone,
>
> Latest LTS RC was made public and it is ready to be tested. Release is
> scheduled for 2017-11-08.
>
> Report
Stephen awesome vids :)
Is this another attempt at getting me to implement SCM Source for Accurev?
:P
I'll definitely keep a eye out for these videos <3
Once work allows me to focus on Accurev Plugin, sure.
Den mandag den 30. oktober 2017 kl. 19.56.36 UTC+1 skrev Stephen Connolly:
>
> I’ve
FYI
Jesse has proposed the adding an optional JIRA header.
https://github.com/jenkinsci/jep/pull/21
It seems reasonable to me. Unless there is strong opposition I'll merge
this the main proposal on Wednesday.
Thanks,
Liam Newman
On Friday, October 27, 2017 at 4:33:15 PM UTC-7, Kohsuke
Oh and these are all live, unscripted and unedited. Stuff goes wrong and
stuff even goes unexpectedly right (episode 3) but I believe that’s more
interesting as it shows how to solve issues with developing in Jenkins
On Mon 30 Oct 2017 at 18:56, Stephen Connolly <
stephen.alan.conno...@gmail.com>
I’ve been recording a series of (approx 20min) videos focused on getting
better usage of Jenkins at Apache.
The first episode is live.
https://youtu.be/W8BRtJmq_2Y
The second is a “double episode” as I wanted to get to an MVP.
If you are interested in plugin development you might like the
And I volunteer in adopting the plugin to maintain it. I already solved three issues.Am 30.10.2017 7:10 nachm. schrieb Daniel Beck :
> On 30. Oct 2017, at 15:59, Jesse Glick wrote:
>
> Why not just use the Groovy Postbuild plugin, which has comparable
Because there are users that simply want to execute shell scripts.
--
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
> On 30. Oct 2017, at 15:59, Jesse Glick wrote:
>
> Why not just use the Groovy Postbuild plugin, which has comparable
> functionality (IIUC) but is long since secured, and better maintained?
Doesn't replace the regular 'shell' script feature of the plugin though.
--
14 matches
Mail list logo