Rob Jahn Atlassian Partner

What I learned from support is that I was using a "next-gen" JIRA project and smart values are not fully supported yet. I made a NON "next-gen" project and I was able to get the REST request automation to work. But in doing this, I learned the automation web service gives an error if you have an unsigned certificate in the…

@Gonchik Tsymzhitov -- Feel free to reach out to me for any support or questions in your Dynatrace evaluation.

Thank you I submitted a request.

project was just an arbitrary argument name. I just renamed to project1 and re-tried, same issue. The use case was just to enable an easy way for the person working the JIRA ticket to fire off a call to some REST service. My thought was to use the new JIRA automation to call my REST service, but I want the parameters to…

Well I did make a new field (called project in this example)and tried a few ways to reference it in the post body {{project}} {{project.value}} {{customfield_10031}} {{customfield_10031.value}} When I look at the automation audit log, the value for this field is not getting resolved. Perhaps I am not using the right…

I had the same issue running on version atlassian/aws-eks-kubectl-run:1.2.1. By just edited the config map (kubectl edit -n kube-system configmap/aws-auth) and adding the user I configured in my pipeline fixed it. Thank you @martinyung this saved alot time! @Alexander Zhukov if you update the docs, please add to the docs…

What I did was to create some file in the pipe and grab it use that file name as the artifact. Then in a subsequent step, read in that artifact file. I don't add in a folder path. The file just lives in the root folder with the checked out code. See the discussion on this thread, for it was a similar…

I found it also unclear where this file is being created pipe.<span>meta</span>.env In that lambda repo you reference, https://bitbucket.org/atlassian/aws-lambda-deploy/src/master/ , the readme also shows this example of using the build in variable $BITBUCKET_PIPE_SHARED_STORAGE_DIR in the pipe:…

Yes this helps. There some other community questions threads showing the use of BITBUCKET_PIPE_SHARED_STORAGE_DIR which I found did not work outside the pipe. Like you, I was able to just create some file in the pipe and grab it use that file name as the artifact. then in a subsequent step, read in that artifact file.

Hi @Mark Harrison will you share a code snippet from the pipe and the pipeline for how you did this? I have been trying to do the same thing and have no luck getting it to work.

I think I know what to do, but anything specific for the path of the file to write out? My custom pipe is Unix shell script.

Is there an example for this or just a code snippet example for what is needed in the pipe code for this that you can share or point me to? 

@Alexander Zhukov - Hi Alex, just following up on my last post.

Thanks Alex, but I am looking to see the the pipe itself can provide outputs. Use that lambda example, say the lambda returned a Json string. I would want to put that into a variable to then access and manipulate in a secondary pipeline step like a Unix command script step. Not sure if supported in general with pipes. For…

I am also developing custom pipes. Is it possible in general and if yes, is there an example you can point me to?

You can find the video here: https://opsmatters.com/videos/getting-most-out-opsgenieatlassiandynatrace

I have the same issue. Are there any suggested things to try?