-
Notifications
You must be signed in to change notification settings - Fork 19
Add support for username/password authentication #6
Conversation
I have an issue with pipeline setup. I have locally built image and my pipeline returns an error: And resource type:
|
I just pushed us.gcr.io/concourse-resources/gerrit-resource:test-userpass (with this PR) and tested that it still works with cookies. I don't have a gerrit instance with password auth to test against. I have seen |
It is also possible that the missing vendored package in the above commit was breaking it for you. |
I'll test it today and let you know 👍 |
Have you had a chance to test this yet? |
I've changed the approach and performed the test directly inside docker container. I've ran
and the result was:
when I've changed the tag to: test-userpass (built by you) there was no such error. In next step I'll check the image prepared by you using credentials. |
I provided username and password. The result was:
Input arguments:
Image: us.gcr.io/concourse-resources/gerrit-resource:test-userpass |
Could you try this equivalent curl command? Note that the debug output will contain a line
I am particularly interested in the response status code and any response header |
|
Ah, looks like you do need digest auth. It would be nice if the gerrit library could just negotiate that for you. Oh well, easy enough to add the option. |
I pushed a new image, retagging |
OK, now
I've user this result as input for
and executed script:
the execution result was:
|
Found ;) I've prepared wrong input for the |
I prepared a simple pipeline. It seems that the check script always returns one change, even if there are more of them. The same query executed in ui returns proper number of changes. As the result the pipeline isn't triggered. For development purposes local gerrit could be used. For example: |
This is how Concourse works; a new resource will initially return only the newest version. Try creating a new change or patch set in Gerrit after creating the pipeline. Also, the default configuration for |
Thanks for the explanation 👍 |
Replaces #5