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

circleci: push traffic control plugin image to docker hub #1858

Merged
merged 1 commit into from
Sep 13, 2016

Conversation

alepuccetti
Copy link

After this patch, circleci builds the traffic control plugin image and
pushes it on docker hub. Rename traffic control plugin docker image
to "weaveworks/scope-traffic-control-plugin".

After this patch, circleci builds the traffic control plugin image and
pushes it on docker hub. Rename traffic control plugin docker image
to "weaveworks/scope-traffic-control-plugin".
@alepuccetti alepuccetti force-pushed the alessandro/tcd-circleci branch from 3e1735c to 66390c8 Compare September 12, 2016 13:47
@davkal davkal self-assigned this Sep 13, 2016
@davkal
Copy link
Contributor

davkal commented Sep 13, 2016

We've discussed where to put plugins, and decided that the scope repo is not the place for them (apart from the example plugins that are there for the purpose of being examples).

I suggest to host them by the maintainer in their own repo, which also governs their CI (with upload to Docker hub). Once you've set up that repo, could you open a new issue here so we can link to it?

From our side we'll add a bigger plugin section to this repo's readme where 3rd party plugins can be found.

@davkal davkal closed this Sep 13, 2016
@davkal davkal reopened this Sep 13, 2016
@davkal davkal assigned jml and unassigned davkal Sep 13, 2016
@jml
Copy link
Contributor

jml commented Sep 13, 2016

Apparently we decided differently.

LGTM. I'll merge now.

@jml jml merged commit 801c419 into weaveworks:master Sep 13, 2016
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.

3 participants