Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating travis #31

Merged
merged 1 commit into from May 6, 2020
Merged

Updating travis #31

merged 1 commit into from May 6, 2020

Conversation

fao89
Copy link
Member

@fao89 fao89 commented May 4, 2020

[noissue]

[noissue]
@fao89 fao89 requested a review from dkliban May 4, 2020 15:14
popd
fi

pip install -e ./pulpcore[postgres]
sed -i "s/pulp:80/localhost:24817/g" ./pulpcore/.travis/test_bindings.rb
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can see immediately where this comes from (my bad).
But should we not strive for consistency here, and start the same ci-container as used in pulpcore?
Or since we only want to test the bindings-generation, we could use the ready to use container from https://pulp.plan.io/issues/6205.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure, for one side I believe it will make CI slower, for the other side we will have consistency and we rarely touch this repo

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And we'd have more incentive to make that other method faster...
But that's probably not the best reason to do it.
We could defer that question into a new issue and say: This here is fixing the CI today, so take it.

@fao89 fao89 merged commit 1a4e76c into pulp:master May 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants