Hello,
Yes I think this will work long term. (still will let others to comment but,
for now looks good to me)
Thank you.
Peter Mikus
Engineer – Software
Cisco Systems Limited
-Original Message-
From: Vanessa Valderrama via RT
Sent: Monday, August 27, 2018 6:27 PM
To: Peter Mikus -X
Ed developed a script that will allow us to keep/remove artifacts based on the
number of days. So we will remove artifacts older than 30 days. Please let me
know if this meets your requirements.
Thank you,
Vanessa
On Fri Aug 10 09:14:10 2018, jgel...@cisco.com wrote:
>
> Hello,
>
> Could
Hello,
We are creating branches on weekly basis and CSIT being verified in weekly job.
So the question is if there is option to set "date" or "number" when limiting
repo.
Counting the cadence of up to 10 merges per day (artifacts posted on Nexus)
then means that safe value is around 100-120
Hello,
We are creating branches on weekly basis and CSIT being verified in weekly job.
So the question is if there is option to set "date" or "number" when limiting
repo.
Counting the cadence of up to 10 merges per day (artifacts posted on Nexus)
then means that safe value is around 100-120
Peter,
How many artifacts do you need us to retain for your testing?
Thank you,
Vanessa
On Mon Aug 06 04:53:29 2018, pmi...@cisco.com wrote:
> Hello Vanessa,
>
> For CSIT it is not about release or not. We would need to increase
> cadence on our weekly jobs to daily. Currently CSIT jobs are
Hello Vanessa,
For CSIT it is not about release or not. We would need to increase cadence on
our weekly jobs to daily. Currently CSIT jobs are all failing as VPP has more
than 10-15 artifacts in week.
Our defined stable versions of VPP (updated once a week) are not in repo
anymore or are
Hello Vanessa,
For CSIT it is not about release or not. We would need to increase cadence on
our weekly jobs to daily. Currently CSIT jobs are all failing as VPP has more
than 10-15 artifacts in week.
Our defined stable versions of VPP (updated once a week) are not in repo
anymore or are
-...@lists.fd.io; infra-steer...@lists.fd.io; vpp-dev@lists.fd.io
Subject: [vpp-dev] [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP
artifacts
Peter,
We need to make a decision on the number of artifacts to keep. I'd like to
propose the following
previous release repos - 10 packages per
-...@lists.fd.io; infra-steer...@lists.fd.io; vpp-dev@lists.fd.io
Subject: [vpp-dev] [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP
artifacts
Peter,
We need to make a decision on the number of artifacts to keep. I'd like to
propose the following
previous release repos - 10 packages per
Peter,
We need to make a decision on the number of artifacts to keep. I'd like to
propose the following
previous release repos - 10 packages per subproject
master - 10 to 15 packages per subproject
Thank you,
Vanessa
On Tue Jun 05 00:51:02 2018, pmi...@cisco.com wrote:
> Hello Vanessa,
>
>
Hello Vanessa,
Thank you for an explanation. Indeed this will impact certain things that are
planned like "automatic bisecting" (downloading and testing range of
artifacts). Let me analyze current situation with CSIT team and get back to you.
Peter Mikus
Engineer – Software
Cisco Systems
Hello Vanessa,
Thank you for an explanation. Indeed this will impact certain things that are
planned like "automatic bisecting" (downloading and testing range of
artifacts). Let me analyze current situation with CSIT team and get back to you.
Peter Mikus
Engineer – Software
Cisco Systems
Peter,
The fd.io.master.centos7 repo had to be cleaned up significantly to eliminate
Jenkins build timeout errors. This was discussed in the TSC. Going forward
we'll only be keeping an average of 10 of the current release candidate
artifacts in the repository. Please let me know if this
13 matches
Mail list logo
