great detailed description…
great tutorial ! thanks for your help.
It’s working fine for the pipeline, however i’ve this issue : 2020-01-29T13:47:19.5435953Z ##[error]Unable to deserialize the response. when I would like to release on a community Orchestrator.
Does any one already success to push the package to Orchestrator without any issue ? of fix this one ?
Thanks in advance.
@Stephu Thanks for the nice tutorial!
I got some questions:
- Would you recommend creating a new pipeline for each git repository?
- Any updates on when the autoversioning feature works again?
- What are the alternatives? One pipepline for all packages? How would you handle that in the case you have only a change on one package? The “unit” for package upload is a single package. You cannot upload multiple packages at once.
- No for uipath this azure devops module has no priority. Up to all the ask for these multiple outstanding features🤓 Maybe they work faster for a new release in the case a lot person are asking.
Thanks for the quick reply!
- Currently we use only one pipeline and manually change the git repository and package version for each time we run the pipeline. So we have to start the build manually, but that’s good to have some quality gate at first. When the autoversioning was working that was really nice and easy to use. now with changing the version number everytime it sucks…
I think having for each repo a pipeline just blows up azure devops alot. currently it would be ok with 20-30 repos, but after full scaling it would be a mess to handle 200 pipelines, or?
- Thanks for the information, that’s sad.
- Good point. At the moment I disabled the pipeline because of all this issues. I upload unprofessionally by hand.(at the moment i have 40 packages, and this works quite well) But when everything is running I’m planning to workout one pipeline use this as template to create all others. From my point of view there are also other points which I know from Java or C# programming like writting unit test, static code analyses with shared configurations…
I’m getting the following error, when trying to deploy.
##[error]The operation returned an error: 1000: Invalid credentials, failed to login.
I’ve used both AD, and user and password options. For username and password I tried both email and username. But got the same error. I’m trying to deploy to cloud orchestrator.
Any help would be appreciated.
Does this user has admin rights on orchestrator?
@Stephu Yea, one is the owner, I also tried an admin and a user account
@Stephu , nice article . I have configured the pipeline the same way mentioned . But the package is shipped to default tenant , It is not shipping to the tenant i have mentioned . I have access to multiple tenant orchestra tor. Please suggest . I had set the tenant name in the Orchestrator tenant column .