-
Notifications
You must be signed in to change notification settings - Fork 20
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
finish gitarro renaming #42
Comments
Yes, and at the same time the way of calling the bot should be configurable (and by default the new name). Right now it's confusing since @gitbot is a mention to a user called However keep in mind that when we change the name we will need to:
|
Some other (boring) names:
And one 'Spanish':
But I also like |
Regarding Jenkins Jobs: I think right now they use a gitbot.rb outside the workspace. I propose making gitarro stable tomorrow, and make a release on monday. Then we will instruct Jenkins Jobs not using Docker to clone gitarro from the repo each time they run, using the release tag. And for the jobs using Docker, I will change the Dockerfile to fetch the latest stable available (right now it downloads the last commit available at master), and will rename the images. Let's discuss it tomorrow. |
Oh, before the release we should consider merging the --change_newer option and the other one to fetch only the commits we need for the tests, instead of the whole repo. Will help a lot with the big repo we have. |
This can now be closed: https://hub.docker.com/r/gitarro/rubocop/tags/ (tested at: https://jenkins.juliogonzalez.es/job/cdtraining-gitbot-test-pr/5/console) |
rename docker images related stuff.
Rename all Jenkins jobs to use gitarro (done partially)
The text was updated successfully, but these errors were encountered: