I can't speak to if there is an existing plugin that does it, but I don't
see why it can't be implemented as plugin. All the groovy calls are calling
things which are easier to work with inside a plugin.
On Wed., Jul. 31, 2019, 10:38 p.m. 夏润泽, wrote:
> Hi all:
>When I was looking for a
Hi all:
When I was looking for a solution to this problem, many people would
recommend adding a groovy script to the pipeline.
https://stackoverflow.com/questions/40760716/jenkins-abort-running-build-if-new-one-is-started
I have some questions about this, why not have a jenkins step
I vote +1.
On Wednesday, July 31, 2019 at 3:38:17 AM UTC-4, Oleg Nenashev wrote:
>
> Hi all,
>
> Sorry for another boring non-developer topic, I would like to provide an
> update on the GSoC 2019 budget.
> You can find the previous status update for 01.01.2019 here:
>
Hi Devin!
I vote for the solving Dockerfile parsing issures by deprecate and remove
FromFingerprintSte.
Accessing the repository is not my goal: I simply would just like to solve
my problems.
Then I will prepare PRs for:
- Add entrypoint/HEALTH CHECK support (
UPD here: The meeting will happen at usual time, 6PM UTC (in 2 hours)
On Friday, July 26, 2019 at 9:49:31 PM UTC+2, martinda wrote:
>
> Somehow I misread 31 -> 21. I thought the the meeting had already happened.
>
> On Friday, July 26, 2019 at 7:46:17 AM UTC-4, Oleg Nenashev wrote:
>>
>> Hi
GSoC Org admins in 2019:
- Martin d'Anjou
- Jeff Pearce
- Marky Jackson
- Lloyd Chang
- Zhao Xiaojie (Rick)
- me
There will be a paper train in the GSoC org admin mailing list, I am fine
with addin Jenkins board members to it for transparency purposes (warning:
the traffix is
Meanwhile, I have deployed changelogs for 2 latest LTS baselines to
https://github.com/jenkinsci/docker/releases
2.176.3 will be an autogenerated one, more or less
BR, Oleg
On Sunday, July 28, 2019 at 8:41:08 AM UTC+2, Oleg Nenashev wrote:
>
> Ok, will do
>
--
You received this message
(replies inline)
On Wed, 31 Jul 2019, Oleg Nenashev wrote:
> There would be a number of requests to get all the topics covered, and it
> would
> require a lot of overhead in the developer mailing list. Last year we have
> suggested [4]JEP-8Â which basically lets GSoC org admins to manage and
+1 as well.
On Wed, Jul 31, 2019 at 2:55 AM Lloyd Chang wrote:
> +1
>
> --
> 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
--
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 discussion on the web visit
Hi all,
Sorry for another boring non-developer topic, I would like to provide an
update on the GSoC 2019 budget.
You can find the previous status update for 01.01.2019 here:
https://groups.google.com/forum/#!msg/jenkinsci-dev/p_hRMKfQuJw/hDsKzBFMDgAJ
.
- Estimated GSoC balance on
FTR, 1000 USD has been already approved for GSoC 2018 in this thread:
https://groups.google.com/forum/#!msg/jenkinsci-dev/p_hRMKfQuJw/hDsKzBFMDgAJ
We have not used these money, so I'd guess we can consider them as approved
in this request.
On Tuesday, July 23, 2019 at 8:50:09 AM UTC+2, Oleg
Hello Tracy,
I definitely do not mind offering more if we have funds :) Personally I
think that the stipend is secondary. Students get experience from working
with open-source organizations and highly experienced mentors who would not
be available if they joined their local companies.
13 matches
Mail list logo
