Re: [Pulp-dev] problems with docker tags

On Thu, Mar 8, 2018 at 11:48 AM, Dennis Kliban wrote: > > On Tue, Mar 6, 2018 at 4:03 PM, Austin Macdonald > wrote: > >> Concept: >> ContentUnits are created with a POST request to /v3/content//. >> Adding the Tag to a Repository is a separate call. This

Re: [Pulp-dev] Task groups in the Pulp 3 MVP

+1 but we should also remove this[0] from the code. [0] https://github.com/pulp/pulp/blob/3.0-dev/pulpcore/pulpcore/app/models/task.py#L215 On Thu, Mar 8, 2018 at 5:45 PM, Brian Bouterse wrote: > +1 to removing it from the MVP area. There is already a gap in several > ways

Re: [Pulp-dev] Task groups in the Pulp 3 MVP

+1 to removing it from the MVP area. There is already a gap in several ways with Katello and I think this was one of them. Additional input from other would be good. On Thu, Mar 8, 2018 at 4:59 PM, David Davis wrote: > There’s a section of the MVP doc about task groups: >

[Pulp-dev] Task groups in the Pulp 3 MVP

There’s a section of the MVP doc about task groups: https://pulp.plan.io/projects/pulp/wiki/Pulp_3_Minimum_Viable_Product#Task-Group I haven’t heard any talk about supporting them in the MVP. Should we remove this section? David ___ Pulp-dev mailing

Re: [Pulp-dev] problems with docker tags

I am responding on the list because this seems like a problem that other plugins will also face. It seems like there are 2 possible solutions here. 1) pulp_docker could provide a custom REST api endpoint that will provide 'tagging' functionality. This API would perform all the validation needed

Re: [Pulp-dev] Github Required Checks

+1, that sounds great. It would alleviate a lot of issues with respect to breakages. On Thu, Mar 8, 2018 at 2:03 PM, Dennis Kliban wrote: > I want to introduce an ability to specify in the commit message for > pulpcore a PR for pulp_file and a PR for pulp-smash. Travis

Re: [Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]

#4 is done and here https://pulp.plan.io/projects/pulp/wiki/Sprint_Plans I'm going to revise my suggestion on sprint candidate. I think we can keep Sprint Candidate flag and set sprint = Sprint 34. And that will allow us to flag items for Sprint 35 (next sprint). Jeff - feel free to just make a

Re: [Pulp-dev] Github Required Checks

I set up the pulp_file tests to install pulp 3.0-dev (although we could change this to nightly builds once those are being built): https://github.com/pulp/pulp_file/blob/master/.travis/install.sh#L6 In the situation you mentioned, we’d merge the PR to pulp and then rerun the PR tests against the

Re: [Pulp-dev] Github Required Checks

+1 pulpcore +0 pulp_file -1 Other plugins. I'm thinking about the situation where we need to fix a bug with a PR to pulpcore and to a plugin. How is the version of pulpcore determined for runnning the plugin tests? In the past, we used nightly builds, so plugins would have to wait 24 hours after

[Pulp-dev] Importer Name

Motivation: The name "importer" carries some inaccurate implications. 1) Importers should "import". Tasks like "sync" will do the actual importing. The object only holds the configuration that happens to be used by sync tasks. 2) Sync tasks on mirror mode remove content as well as add it, so

Re: [Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]

I'm porting these today. I'll handle items 1-3. If we really don't like what it looks like we can revert. For item 4, I think we should make a wiki page with the sprint start/end dates per sprint. I'll reply with links to the newly created things so everyone can see it what we've got. On Wed,

Re: [Pulp-dev] possible to upload container image blobs?

i have created an api endpoint in foreman for docker push and from there will be calling pulp. don’t worry about “safe” since there is no manual aspect. if pulp doesn’t support it, i will work around. if it us possible, please tell me how. thanks!! @thomasmckay > On Mar 7, 2018, at 5:25 PM,