I'm trying to use the stash build api to connect Jenkins and Stash. I've got it linked up with a simple python script, but when I view the build results in Stash, it only shows the most recent result. I'm posting to <stash-url>/rest/build-status/latest/commits/<sha1> with state, key, name, and url from my jenkins job. Do I need to do something special to store each build result?
What parameters are you passing exactly? According to the documentation:
If a single commit was built by multiple build plans, you can
POSTmultiple results for the same commit. Each result must have a different
Basically if you use the same key, you'll end up with only one result. I suspect that's what might be happening.
Does that help?
PS Have you seen this Jenkins plugin before?
I was looking at the API documentation at https://developer.atlassian.com/static/rest/stash/2.6.0/stash-build-integration-rest.html. It makes sense now that the key should be unique.
That plugin did almost everything I was looking for. There doesn't appear to be a way for it to mark a build as "In Progress".
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot