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

More flexible channel separator syntax #55

Closed
mcandre opened this issue Mar 1, 2015 · 2 comments
Closed

More flexible channel separator syntax #55

mcandre opened this issue Mar 1, 2015 · 2 comments

Comments

@mcandre
Copy link

mcandre commented Mar 1, 2015

The first time I used the Jenkins Slack plugin, I experienced trouble finding the right syntax for configuring a job to notify multiple Slack channels. In the future, could we increase flexibility?

  • Comma separation (the current, undocumented syntax: #chan1,#chan2,...)
  • Space separation (#chan1 #chan2 ...)
  • Comma with space separation (#chan1, #chan2, ...)
@samrocketman
Copy link
Member

Documenting it is a start. It's likely better to account for 1 format and document it for the user rather than account for several syntax variations. I'd say the desired contribution is for someone to submit a pull request documenting the field in the Slack plugin UI of Jenkins configurations.

I don't actively develop the plugin but you're welcome to submit a pull request! I only maintain pull requests and releases.

@mcandre
Copy link
Author

mcandre commented Mar 6, 2015

Perfect! Thank you

alexey-pelykh pushed a commit to brainbeanapps/slack-plugin that referenced this issue Nov 3, 2016
Gave productsign same permissions as codesign to access imported keys without prompt.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants