[Pulp-dev] Moving to travis-ci.com

2020-04-15 Thread David Davis 
A week or two ago, build statuses for repos whose Ci is hosted on
travis-ci.org failed to be reported back to Github. This thread in the
Travis support forum about the issue[0] seems to recommend that we migrate
off travis-ci.org. My one question is whether we'd experience more
congestion if we had all our repos on travis-ci.com I know this has been
an issue in the past.

[0]
https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798/14

David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] pulpcore 3.3.0 GA timeline

2020-04-15 Thread Tatiana Tereshchenko 
The release is unblocked and we'll proceed with it today.
Thanks to everyone for collaboration and quick resolution of the issues.

On Tue, Apr 14, 2020 at 7:29 PM Tatiana Tereshchenko 
wrote:

> The release is currently blocked by:
>
>- the issue with ordering of content https://pulp.plan.io/issues/6347
>- issues with CI
>
> We will update this thread when the release is unblocked (likely tomorrow).
>
> On Thu, Apr 9, 2020 at 5:52 PM Tatiana Tereshchenko 
> wrote:
>
>>
>> We decided to wait a bit more to include the import/export basic
>> functionality into the release.
>> The current plan is to release pulpcore==3.3.0 GA on April 14th.
>> The deadline for merging code is April 13th 23:59:59 EDT. We are planning
>> to start the release process on Tuesday morning.
>>
>> The following items are no longer blocking the release:
>> * The new repository repair API /pulp/api/v3/repair/ -
>> https://pulp.plan.io/issues/5613 - is done and merged.
>> * The setting to increase the accepted header size for pulpcore-content -
>> https://pulp.plan.io/issues/6460 - is moved to 3.4.
>>
>> On Wed, Apr 1, 2020 at 8:58 PM Brian Bouterse 
>> wrote:
>>
>>> We are planning to release pulpcore==3.3.0 GA on April 8th. While we
>>> strive for time-based releases, here are two items that we are hoping to
>>> include based on feedback from Katello who would like to consume 3.3.0 in
>>> their upcoming releases.
>>>
>>> * The new repository repair API /pulp/api/v3/repair/ -
>>> https://pulp.plan.io/issues/5613. This one is a must-have.
>>>
>>> * The import/export parts that belong in pulpcore -
>>> https://pulp.plan.io/issues/6134. This one is a nice-to-have and will
>>> tech-preview if not fully complete.
>>>
>>> ## What plugin writers need to know
>>>
>>> Look at the backwards incompatible changes in the plugin API release
>>> notes to determine if your plugin will require a compatibility release.
>>> Those are the *.removal entries here:
>>>
>>> https://github.com/pulp/pulpcore/tree/master/CHANGES/plugin_api
>>>
>>> Feedback, questions, and discussion are welcome.
>>> ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://www.redhat.com/mailman/listinfo/pulp-dev
>>>
>>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] CI/CD meeting notes

2020-04-15 Thread David Davis 
April 15, 2020


   -

   CI status
   -

  Everything should be green now
  -

   Github actions
   -

  Adjusted PR for NPM: https://github.com/pulp/pulp_npm/pull/13
  -

  Future, waiting on more features from Github Actions
  -

 Need a way to restart jobs inside workflow
 -

 Need a way to reuse jobs in different workflows
 -

  AI: daviddavis to review and merge npm PR
  -

   Out of the box CI on plugin_template
   -

  https://pulp.plan.io/issues/6474
  -

  AI: mdellweg to look into improving docs around
  -

   Single container in CI - https://pulp.plan.io/issues/6477
   -

  Have plugin_template deliver Dockerfile and playbook to each plugin
  -

   Start publishing containers to Docker Hub in addition to quay
   -

   We need to update descriptions on a few repo:
   -

  https://github.com/pulp/pulp_installer
  -

  https://github.com/pulp/pulplift
  -

  https://github.com/pulp/plugin_template
  -

  https://github.com/pulp/pulp-packaging (specify Pulp 2)
  -

  https://github.com/pulp/pulp (specify Pulp 2)
  -

  https://github.com/pulp/pulpcore (specify Pulp 3)
  -

   S3 testing
   -

  Can we use the s3 ansible module to set up the pulp bucket?
  -

 Having trouble using the module, docs are not great
 -

  Can we switch to localstack instead of minio?


David
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev