You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I want to start a custom pipeline from another pipeline, but I want it to be activated by the same user who activated the initial pipeline on the same branch and the same repository. It looks reasonable to me that it should be possible without creating additional users and app passwords in that case. A user is running the pipeline already, right? Why does he need extra authentication? :-)
For Pull-Request reports delivery there's a possibility to send requests with curl using proxy server (http://localhost:29418) bypassing the credentials verification. Is it possible to use the same approach to trigger pipelines?
Here's what I tried (without success, but works fine when replacing proxy parameter user credentials):
curl --proxy 'http://localhost:29418'
-X POST -is -H 'Content-Type:application/json'
Hi Mikhail and welcome to the community.
The current proxy only works for pushing back to the repo where Pipelines is running during a Pipelines build, and also with the reports and annotations API endpoints. It is not designed to work with any other endpoints, so I'm afraid that what you're asking is not possible at the moment.
You will need to use authentication in the API call. You can also use the following pipe to trigger another pipeline:
That also requires a username and app password for authentication.
I can create a feature request in our issue tracker about what you're asking, for our product managers and development team to consider. Please feel free to let me know if you'd like me to do that.
Thank you for your reply and feedback
I went ahead and created a feature request in our issue tracker:
I would suggest adding your vote to the feature request (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features.
You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
Implementation of new features is done as per our policy here and any updates will be posted in the feature request.
Please feel free to let me know if you have any questions.