Skip to content
This repository has been archived by the owner on May 24, 2022. It is now read-only.

Build pipeline broken #53

Open
ghost opened this issue Apr 21, 2021 · 6 comments · May be fixed by #56
Open

Build pipeline broken #53

ghost opened this issue Apr 21, 2021 · 6 comments · May be fixed by #56
Labels

Comments

@ghost
Copy link

ghost commented Apr 21, 2021

Multiple jobs failing in tests due to env not being set up correctly. @splushii something to look at on a rainy day perhaps?

@ghost ghost added the CI label Apr 21, 2021
@cfarvidson
Copy link

Is there a reason why the master branch runs parallel with the v1 branch (which seem to be the one that should be merged into)?

@cfarvidson
Copy link

I think that i should have based my #54 on the v1 branch instead of master

@cfarvidson
Copy link

I think that the issue may be is that master (which seem to be a developer branch) and the v1 branch is not kept in sync.

They have been running parallel since 504185f

@splushii splushii linked a pull request Apr 24, 2021 that will close this issue
@splushii
Copy link

Multiple jobs failing in tests due to env not being set up correctly. @splushii something to look at on a rainy day perhaps?

Yes, let's do it! ☔ 🌈

I've started some efforts in #56

Given python 3.5 is EOL and Ubuntu 16.04 is EOL very soon, I think we should drop them from CI and focus on / add supported versions. The same goes for HAProxy and Varnish (and maybe document it, related to #44), but that may be a lot more intrusive.

@splushii
Copy link

@cfarvidson new features goes into master, and may be backported to the v1 branch (to be released as 1.x.y). master contains breaking changes, that's why there is a v1 branch.

@cfarvidson
Copy link

@cfarvidson new features goes into master, and may be backported to the v1 branch (to be released as 1.x.y). master contains breaking changes, that's why there is a v1 branch.

Ahh, thanks for clearing that up. 😊 👍

@ghost ghost linked a pull request Apr 28, 2021 that will close this issue
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Development

Successfully merging a pull request may close this issue.

2 participants