Hiya,
> As per discussion on IRC, this is now live: KGB notifications for
> commits and CI pipeline stati are now send to #debian-ruby-changes.
I just added the details about #debian-ruby-changes channel to our
Ruby team wiki page :)
Best,
Utkarsh
Hi all,
On 19-08-29 01:01:08, Georg Faerber wrote:
> I'll follow-up to see if consensus can be formed within the Salsa CI
> team to disable the pipeline for tags.
Just for the record: this change was done upstream now [1]: By default,
the pipeline is not run anymore if pushing tags.
Cheers,
Geor
On 19-08-28 08:27:26, Georg Faerber wrote:
> Still, we could at least disable notifications for the pipelines which
> are triggered if tags are pushed. I didn't test this yet, but
> disabling the hook for "Tag push events" should do the trick. This
> way, the pipeline would still run two times, for
Hey,
On 28/08/19 4:18 pm, rajudev wrote:
>
> On 28 August 2019 3:46:27 PM IST, Utkarsh Gupta
> wrote:
>> Hey,
>>
>> On 28/08/19 1:57 pm, Georg Faerber wrote:
>>> Hi,
>>>
>>> This topic is two fold, in my opinion:
>>>
>>> On 19-08-28 08:25:06, Utkarsh Gupta wrote:
It doesn't make much sense
On 28 August 2019 3:46:27 PM IST, Utkarsh Gupta
wrote:
>Hey,
>
>On 28/08/19 1:57 pm, Georg Faerber wrote:
>> Hi,
>>
>> This topic is two fold, in my opinion:
>>
>> On 19-08-28 08:25:06, Utkarsh Gupta wrote:
>>> It doesn't make much sense to run CI on the tags :/
>> Yes, I agree. That's why I c
Hey,
On 28/08/19 1:57 pm, Georg Faerber wrote:
> Hi,
>
> This topic is two fold, in my opinion:
>
> On 19-08-28 08:25:06, Utkarsh Gupta wrote:
>> It doesn't make much sense to run CI on the tags :/
> Yes, I agree. That's why I created [1] some time ago, more recently [2]
> was created, both ticket
Hi,
This topic is two fold, in my opinion:
On 19-08-28 08:25:06, Utkarsh Gupta wrote:
> It doesn't make much sense to run CI on the tags :/
Yes, I agree. That's why I created [1] some time ago, more recently [2]
was created, both tickets asking to disable CI by default for tags.
However, so far,
Hey,
On 27/08/19 2:25 pm, Georg Faerber wrote:
> On 19-08-27 08:44:47, Georg Faerber wrote:
>> Also, Antonio, I think consensus is reached regarding your initial
>> proposal, minus squashing the commits, so I think you're good to go
>> ahead.
> If possible, I would like to not receive build notifi
Hey,
On 27/08/19 7:04 pm, Georg Faerber wrote:
> On 19-08-27 08:44:47, Georg Faerber wrote:
>> Also, Antonio, I think consensus is reached regarding your initial
>> proposal, minus squashing the commits, so I think you're good to go
>> ahead.
> As per discussion on IRC, this is now live: KGB notif
On 19-08-27 08:44:47, Georg Faerber wrote:
> Also, Antonio, I think consensus is reached regarding your initial
> proposal, minus squashing the commits, so I think you're good to go
> ahead.
As per discussion on IRC, this is now live: KGB notifications for
commits and CI pipeline stati are now sen
On 19-08-27 08:44:47, Georg Faerber wrote:
> Also, Antonio, I think consensus is reached regarding your initial
> proposal, minus squashing the commits, so I think you're good to go
> ahead.
If possible, I would like to not receive build notifications for tags,
but just for commits. In the huge ma
Hi all,
On 19-08-17 13:02:44, Antonio Terceiro wrote:
> fair enough. I noticed that the python team has two channels:
> #debian-python for humans, and #debian-python-changes for
> notifications. maybe we could do something similar?
This seems like the way to go given all the mails in response, s
On 19-08-18 22:57:29, Cédric Boutillier wrote:
> Having a dedicated channel for notifications would be a nice solution
> to get all the information we want and keep a sane place for human
> interactions.
+1
Hi!
On Sat, Aug 17, 2019 at 01:02:44PM -0300, Antonio Terceiro wrote:
> fair enough. I noticed that the python team has two channels:
> #debian-python for humans, and #debian-python-changes for notifications.
> maybe we could do something similar?
Having a dedicated channel for notifications wou
Hey,
On 17/08/19 9:32 pm, Antonio Terceiro wrote:
> On Sat, Aug 17, 2019 at 01:05:52PM +0530, Utkarsh Gupta wrote:
>> I'd always say that it is a good idea to see who's doing what under the
>> Ruby team.
>> At least, I'd like to see other's commit; helps me explore the different
>> ways. For insta
Hi
Em 17 de agosto de 2019 13:02:44 BRT, Antonio Terceiro
escreveu:
>On Sat, Aug 17, 2019 at 01:05:52PM +0530, Utkarsh Gupta wrote:
>> Hey,
>>
>> On 16/08/19 7:09 pm, Antonio Terceiro wrote:
>> > Hi,
>> >
>> > To reduce the volume of KGB notifications on IRC, I intend to run
>the
>> > following
On Sat, Aug 17, 2019 at 01:05:52PM +0530, Utkarsh Gupta wrote:
> Hey,
>
> On 16/08/19 7:09 pm, Antonio Terceiro wrote:
> > Hi,
> >
> > To reduce the volume of KGB notifications on IRC, I intend to run the
> > following:
> >
> > $ salsa --group ruby-team update_repo --all --kgb --irc
> > 'debian-r
Hey,
On 16/08/19 7:09 pm, Antonio Terceiro wrote:
> Hi,
>
> To reduce the volume of KGB notifications on IRC, I intend to run the
> following:
>
> $ salsa --group ruby-team update_repo --all --kgb --irc
> 'debian-ruby&pipeline_only_status=failed&squash_threshold=1'
>
> - squash_threshold=1 will m
Hi,
To reduce the volume of KGB notifications on IRC, I intend to run the
following:
$ salsa --group ruby-team update_repo --all --kgb --irc
'debian-ruby&pipeline_only_status=failed&squash_threshold=1'
- squash_threshold=1 will make KGB notify only once each time multiple
commits are pushed
-
19 matches
Mail list logo
