2016-01-15 17:56 GMT+01:00 Jesse Glick :
> On Fri, Jan 15, 2016 at 9:16 AM, Baptiste Mathus wrote:
> > there are many dependencies in the core classes to those
> (AbstractProject,
> > Computer, ComputerSet. Node...).
>
> The `AbstractProject` usage is pretty trivial, could be deleted IMO.
>
So b
On 15.01.2016, at 20:27, oliver gondža wrote:
> Release is scheduled for 2016-01-20.
Given the very short time until scheduled release, and the fact that this is a
.1 LTS, I suggest we postpone the release by two weeks.
--
You received this message because you are subscribed to the Google Gr
To continue: https://github.com/jenkinsci/jenkins/pull/1982
--
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
Hello everyone,
Latest RC was made public and it is ready to be tested. Release is
scheduled for 2016-01-20.
Report your findings in this thread or on the test plan wiki page.
Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war
Check community maintained LTS test p
On 15.01.2016, at 17:50, pallen wrote:
> How do you hook into the Delete Project event when a Jenkins Job is deleted?
http://javadoc.jenkins-ci.org/hudson/model/listeners/ItemListener.html#onDeleted%28hudson.model.Item%29
--
You received this message because you are subscribed to the Google G
Listener.onDeleted() for items afair
On Friday, January 15, 2016 at 7:50:12 PM UTC+3, pallen wrote:
>
> Hi Guys,
>
> How do you hook into the Delete Project event when a Jenkins Job is
> deleted?
>
> I want to allow the p4 (SCM) plugin to cleanup the workspace (and
> associated Perforce metadata
On Fri, Jan 15, 2016 at 1:07 PM, 'Laurence Bordowitz' via Jenkins
Developers wrote:
> The issue would be how to send the necessary plugins over. There's no
> serialization requirement for BuildWrappers, and some plugins may require
> master-only functionality. This would break current plugins.
We
I think that would be great to do all processing on the slave side! The issue
would be how to send the necessary plugins over. There's no serialization
requirement for BuildWrappers, and some plugins may require master-only
functionality. This would break current plugins. I would not be opposed
On Fri, Jan 15, 2016 at 11:34 AM, 'Laurence Bordowitz' via Jenkins
Developers wrote:
> The plan is to have this as an optional feature flag. Every user who doesn't
> opt-in will experience Jenkins as it is today.
My counterproposal would be to do any requested processing on the
slave side, avoid
On Fri, Jan 15, 2016 at 9:16 AM, Baptiste Mathus wrote:
> there are many dependencies in the core classes to those (AbstractProject,
> Computer, ComputerSet. Node...).
The `AbstractProject` usage is pretty trivial, could be deleted IMO.
Looking at `ComputerSet`, it is mostly about node monitors,
Hi Guys,
How do you hook into the Delete Project event when a Jenkins Job is deleted?
I want to allow the p4 (SCM) plugin to cleanup the workspace (and
associated Perforce metadata). Initially I thought that
'processWorkspaceBeforeDeletion' method from 'SCM' would get called, but
that is only
The plan is to have this as an optional feature flag. Every user who doesn't
opt-in will experience Jenkins as it is today.
I probably shouldn't have used the word "sparkle." These plugins provide
critical functionality for many users' builds (they wouldn't be used
otherwise!). In our use case,
Hi Oleg,
Yeah, I didn't really ignore your question on purpose. Just forgot about
it, sorry about that.
Also my main goal in this thread was mainly to validate the idea of the
extraction, and I thought we would then discuss more precisely those things
as we go.
Anyway, in the meantime, as I've st
Thanks Arnaud!
On Fri, Jan 15, 2016 at 12:36 PM, Arnaud Héritier
wrote:
> Repo and Jira component pipeline-stage-view-plugin created
>
> Cheers
>
> On Fri, Jan 15, 2016 at 12:28 PM, Arnaud Héritier
> wrote:
>
>> Hi
>>
>> Do we have to fork it from somewhere ? Or we just create a new repo ?
>> P
Hi Dennis,
I'll try to review it on this weekend.
BR, Oleg
2016-01-15 15:08 GMT+03:00 Dennis Schulte :
> Hi guys,
>
> after some trouble with the complexity of the plugin I finally managed it
> to create a PR which integrates the Job DSL extension directly into the
> promoted-builds-plugin:
> h
Hi guys,
after some trouble with the complexity of the plugin I finally managed it
to create a PR which integrates the Job DSL extension directly into the
promoted-builds-plugin:
https://github.com/jenkinsci/promoted-builds-plugin/pull/81
It would be great if Oleg could review the PR and merge
Hi Baptiste,
There was a question regarding the decoupling approach.
What are we going too do with monitoring periodic works and NodeMonitor
> APIs?
>
>- We can leave them in the Core
>- We can move them into the plugin as well
>
>
I think it still deserves some discussion
среда, 13 ян
Repo and Jira component pipeline-stage-view-plugin created
Cheers
On Fri, Jan 15, 2016 at 12:28 PM, Arnaud Héritier
wrote:
> Hi
>
> Do we have to fork it from somewhere ? Or we just create a new repo ?
> Please join us on IRC it will be easier/quicker ...
>
> BR
>
> On Fri, Jan 15, 2016 at 12:0
Hi
Do we have to fork it from somewhere ? Or we just create a new repo ?
Please join us on IRC it will be easier/quicker ...
BR
On Fri, Jan 15, 2016 at 12:06 PM, Antonio Muñiz
wrote:
> Hello,
>
> As announced previously, CloudBees is going to open-source the Pipeline
> Stage View plugin, so a
Hello,
As announced previously, CloudBees is going to open-source the Pipeline
Stage View plugin, so a new repository and JIRA component is needed. The
plugin ID will be "pipeline-stage-view".
Could someone create that repo & JIRA component?
Thanks!
--
Antonio Muñiz
Software Engineer
CloudBees
20 matches
Mail list logo
