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

The credential with the provided ID () could not be found and no token was specified #678

Closed
3 tasks done
CarlitosDroid opened this issue Mar 10, 2020 · 8 comments
Closed
3 tasks done

Comments

@CarlitosDroid
Copy link

Your checklist for this issue

Description

Steps to reproduce:

  1. In a Freestyle project in Jenkins
  2. Go to Post-build Actions
  3. Add "Add post-build action"
  4. Add "Slack Notification"
  5. Click on "Advanced..."
  6. "Credential" field doesn't recognize credentials, even if the scope is Global or System, always shows "-none-"
  7. Click on "Test Connection"
  8. An error is shown "The credential with the provided ID () could not be found and no token was specified"

Evidence

Screen Shot 2020-03-09 at 9 25 02 PM

@timja
Copy link
Member

timja commented Mar 10, 2020

Can you add a screenshot of how your credential is setup?

@CarlitosDroid
Copy link
Author

This is how I setup my credentials
Screen Shot 2020-03-10 at 9 50 30 AM
Screen Shot 2020-03-10 at 9 50 42 AM

And when I go back to the "Add post-build action" in my job, again I can't be able to detect it, always "none":
Screen Shot 2020-03-10 at 9 51 14 AM

@jetersen
Copy link
Member

You need to use secret text credential type.

@CarlitosDroid
Copy link
Author

@jetersen @timja now it's working fine by using secret text credential type, but I think that it should be also work with the other credential types.
Thank you very much!!!

Screen Shot 2020-03-10 at 7 47 04 PM

Screen Shot 2020-03-10 at 7 51 09 PM

@jetersen
Copy link
Member

No your slack token does not need the username, reason why we only support secret text.

@CarlitosDroid
Copy link
Author

CarlitosDroid commented Mar 11, 2020

You 're right. Thanks a lot @jetersen

@jetersen
Copy link
Member

FYI I would always provide a meaningful ID as you will use the ID in your Jenkins pipeline

@fgm
Copy link

fgm commented Sep 3, 2020

Final item missing was how to find the token in the current Slack UI : in the "incoming-webhooks" integration, its the part of the URL after "services/", xxxx/xxxx/xxx(24chars)xxx.

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

No branches or pull requests

4 participants