Allow core and plugins to specify which Python version to test against

[daviddavis]

The CI uses the pulp_ci_centos image which already has a version of Python installed. Currently, that's Python 3.8. However, we're still releasing older versions of pulpcore and plugins that support Python 3.6 and we need a way to have our CI test against Python 3.6.

[fao89]

I built python36 tag for galaxy
http://docker.io/pulp/pulp-ci-centos:python36

https://github.com/ansible/ansible-hub-ui/pull/675/files

[daviddavis]

Interesting, how was the python36 tag generated?

[fao89]

I reverted python38 commit and manually built and push it

[bmbouter]

@fao89 Do you understand what could be done to have the plugin template get a new variable that could specify which image to use? I'm about to release pulpcore==3.14 and also pulpcore==3.7 and if I reapply the plugin template (which I need to for 3.7 at least) it'll CI against Python 3.8 which I'd like it to have it CI against Python 3.6 instead. Is this something you could possibly help with? @dkliban or do you have any ideas?

[dkliban]

@bmbouter don't update to the latest plugin_template config on the 3.14 branch. is there something specific you need from latest?

[fao89]

Currently it switches between latest and https
https://github.com/pulp/plugin_template/blob/master/templates/github/.github/workflows/scripts/install.sh.j2#L117
we can make this logic smarter

[bmbouter]

Well for the 3.7 branch I need the auto-release stuff. And 3.14 is going to be around a long time so over time we'll have to reapply.

[daviddavis]

We'd need to do more than just switch the ci container image over to use the python36 tag. There are some paths and stuff in the CI files that will need to be updated. But that said, it should be fairly easy.

[bmbouter]

Sounds good. I can do the 3.14.3 release, but I am blocked on the 3.7 release (the one we really need AIUI) until this is done.

[daviddavis]

Can you have the 3.7 release branch run against python 3.8 for now?

Also, how urgently do you need this? If it's urgent, I think I could make some time to work on it tomorrow.

Lastly, just to add: this'll be a bit of a hack and longer term I think we want a way to generate different base CI images with different python versions.

[bmbouter]

Can you have the 3.7 release branch run against python 3.8 for now?

I'm ok with this, but I was ok from the beginning. What I don't want to do is not use our fully automated release machinery. Shall I just run with 3.8 for now?

Also, how urgently do you need this? If it's urgent, I think I could make some time to work on it tomorrow.

After these I don't know of more 3.7 branch releases so maybe not for a few weeks? Really this request originated from @goosemania who was requesting on behalf of katello.

Lastly, just to add: this'll be a bit of a hack and longer term I think we want a way to generate different base CI images with different python versions.

Agreed.

[daviddavis]

I'm ok with this, but I was ok from the beginning. What I don't want to do is not use our fully automated release machinery. Shall I just run with 3.8 for now?

It's worth a try.

[goosemania]

Also, how urgently do you need this? If it's urgent, I think I could make some time to work on it tomorrow.

After these I don't know of more 3.7 branch releases so maybe not for a few weeks? Really this request originated from @goosemania who was requesting on behalf of katello.

The tasking bug blocks some QE testing for pulp-2to3-migration. If we have a patch ready for 3.7, I can share it with QE and they will likely be able to patch their automation.
Definitely no need to push to get the release out this week, next week would be nice butI can figure out a specific deadline based on the build team schedule if you prefer to have a specific date.