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

Add configurability and JIRA version creation/release #10

Closed
wants to merge 2 commits into from
Closed

Add configurability and JIRA version creation/release #10

wants to merge 2 commits into from

Conversation

slide
Copy link
Contributor

@slide slide commented Mar 1, 2014

Added a bit of configurability to make it easier to test the bot on a different network or in a different channel. Also added two methods for working with versions on JIRA. createVersion allows a valid user to create a version in JIRA, releaseVersion allows a valid user to mark an existing version as released.

slide and others added 2 commits February 28, 2014 11:57
Added ability to release existing versions on JIRA.

Made the server, channel and nickname configurable via properties
@jenkinsadmin
Copy link

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

this.unknownCommands = unknownCommands;
}

@Override
protected void onMessage(String channel, String sender, String login, String hostname, String message) {
if (!channel.equals("#jenkins")) return; // not in this channel
protected void onMessage(String chan, String sender, String login, String hostname, String message) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there any need to rename channel to chan? It prevents conflicts with class fields, but it causes many changes unrelated to the PR

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It could be swapped so that the class field was chan and the parameter was channel. I can do it if you want me to make that change.

@slide
Copy link
Contributor Author

slide commented Jun 30, 2014

I think it was decided to not go with my proposal for versions, so I am closing this out.

@slide slide closed this Jun 30, 2014
@oleg-nenashev
Copy link
Contributor

I suppose that @kohsuke should make a decisions about the PR.
It could be useful if we decide to host additional projects on Jenkins JIRA (e.g. for shared components like winp, winsw or jira-scraper). These components would require the versioning

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