devops-service | DevOps Service is the core service | Microservice library

 by   open-hand Java Version: 2.0.13 License: No License

kandi X-RAY | devops-service Summary

kandi X-RAY | devops-service Summary

devops-service is a Java library typically used in Manufacturing, Utilities, Automotive, Architecture, Microservice, Spring Boot, Spring, Docker, Prometheus, Grafana applications. devops-service has no bugs, it has no vulnerabilities, it has build file available and it has low support. You can download it from GitHub.

DevOps Service DevOps Service是Choerodon平台实现持续交付的基础. 当前版本为: 0.25.0.

            kandi-support Support

              devops-service has a low active ecosystem.
              It has 59 star(s) with 76 fork(s). There are 10 watchers for this library.
              It had no major release in the last 6 months.
              There are 5 open issues and 6 have been closed. On average issues are closed in 45 days. There are 3 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of devops-service is 2.0.13

            kandi-Quality Quality

              devops-service has 0 bugs and 0 code smells.

            kandi-Security Security

              devops-service has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              devops-service code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              devops-service does not have a standard license declared.
              Check the repository for any license declaration and review the terms closely.
              Without a license, all rights are reserved, and you cannot use the library in your applications.

            kandi-Reuse Reuse

              devops-service releases are not available. You will need to build from source code and install.
              Build file is available. You can build the component from source.
              Installation instructions are not available. Examples and code snippets are available.
              devops-service saves you 108976 person hours of effort in developing the same functionality from scratch.
              It has 116599 lines of code, 15804 functions and 1439 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi has reviewed devops-service and discovered the below as its top functions. This is intended to give you an instant insight into devops-service implemented functionality, and help decide if they suit your requirements.
            • Import a Devops App Service Import
            • Init branch
            • Performs a push
            • Set project hook id for project
            • Deploys an image in a docker cluster
            • Get docker run command
            • Add DevopsHost App DTO
            • Deploy a ji pipeline deployment
            • Calculate the download url
            • Get the detail of a ci pipeline record
            • Update the pipeline schedule
            • Update Devops Environment
            • Rollback host deployment
            • Run for Redis host deploy
            • Initialize the result handler
            • Create a system environment
            • Propagation
            • Starts GitOps synchronously
            • Get app center env detail
            • Gets Sonar table
            • Start a pipeline auto deploy task
            • Create or update a manifest
            • Delete app by id
            • Custom deploy
            • Returns a page of cluster node info
            • Gets a page of branch by options
            Get all kandi verified functions for this library.

            devops-service Key Features

            No Key Features are available at this moment for devops-service.

            devops-service Examples and Code Snippets

            No Code Snippets are available at this moment for devops-service.

            Community Discussions


            How to get the values of pull request Created by and Approved by in Azure DevOps CI pipeline
            Asked 2021-Apr-21 at 06:50

            I have the pull-request build in Azure DevOps in that I have used inline PowerShell script to get the Pull Request ID by following System variables (DevOps Services) documentation.

            But I want to get the values of Pull Request Created by and Approved by using predefined variables.

            So, can anyone suggest how to do it.



            Answered 2021-Apr-21 at 06:50

            There are no predefined variables of Created by or Approved by for a Pull Request. Instead, you could use Pull Requests - Get Pull Request By Id api to get these information, as you have had Pull Request ID:



            Application is not loading when deployed via azure app service
            Asked 2021-Apr-06 at 22:07

            I'm a newbie to Azure

            I created a new Vue project using vue create which runs locally and even serving the dist folder too it run successfully. (serve -s dist)

            And then I deployed the application using GitActions to Azure(Web App Service) which Azure DevOps services indicated that the deployment has been successful: azure-devops-service-github-actions

            So I was expecting to see the default page as: vue-app-default-page-content

            Instead, it still shows as: azure-site-landing-page

            There are no error messages, and I'm not sure how best to debug what has gone wrong with a deployment. Also not sure if later when I use the application with any REST APIs does it include any configurations to get it up and running.

            Secondly, not a blocker, but after removing these lines from the workflow - master.yml file the deployment continued without any issue. Used Node 12 and Node 14. I Googled and have no idea why??



            Answered 2021-Apr-05 at 02:30

            You need to add startup command, you can try it.



            Azure Virtual Machine Scale Set on Azure Devops - predefined variables not recognised
            Asked 2021-Apr-02 at 02:13

            I built a Scale Set(Windows) and I can run simple commands successfully on my Azure Devops Custom Agent Pool, with a custom VM based on Windows 19 Server Core based on this guide.

            However, when I try to access any Azure Devops predefined variables in any of my tasks they are not recognised. For example executing:



            Answered 2021-Apr-02 at 02:13

            I also tested the shell script task on my VMSS Windows-2019 agent, it can correctly print the value of the predefined variables in pipeline. I did not get any error.

            I tried the VMSS created via executing the related Azure CLI on Azure Cloud Shell, and manual created on Azure Portal web UI, both of them can work fine without any error.

            Please check with the following steps:

            1. Try the VMSS in different pipelines, different projects to see if the same issue occurs.
            2. Try creating a new VMSS (you can try manual creation) to see if the issue also occurs on the new VMSS.
            3. Check if there is any syntax or format issue in your pipeline definition (YAML file). Below is a simple pipeline as reference, I tested it on my side and it can work fine.



            Azure Devops Pipeline with Manual Run and User-Set Variables: How to check variables in conditions?
            Asked 2021-Mar-05 at 20:03

            Hoping someone can help me with this as looking back at my git log I've now tried 14 different things to try to get this to work. Here's the scenario:

            • I created a variable in the UI called deploy_custom_env and checked "User can set variable at runtime." I initialized it to "default", but I am expecting users to override it when starting manual runs.

            • I am trying to use this variable in the condition for some of my pipeline stages.

            • I've tried many, many different things. Here are some examples:




            Answered 2021-Mar-05 at 18:37

            If you're doing this in yml file, then $(deploy_custom_env) should work.



            How to get git branch at commit with tag at run Azure pipeline?
            Asked 2020-Dec-07 at 03:32

            In Azure Pipeline is possible use predefined build variables (DevOps Services) Build.SourceBranch and Build.SourceBranchName but their values at case commit with tag are tags.

            In doc. is written

            • When your pipeline is triggered by a tag: refs/tags/your-tag-name
            • The name of the branch in the triggering repo the build was queued for. Git repo branch or pull request: The last path segment in the ref. For example, in refs/heads/master this value is master. In refs/heads/feature/tools this value is tools.
            • this my observation: but in case commit with tag is the last path segment of Build.SourceBranch, so your-tag-name


            Answered 2020-Dec-07 at 03:32

            As it is described in the document. If the pipeline is triggered by a tag. Then variables Build.SourceBranch and Build.SourceBranchName will be the tag name.

            However, you can use git commands(git branch -r --contains $(Build.SourceBranchName) | grep -v $(Build.SourceVersion)) to retrieve the branch name that the tag points to.

            If you want to use the branch name as variable, You can define a variable use the logging commands(echo "##vso[task.setvariable variable=CurrentBranch]$branch"). For below example:



            Difference between basic and Visual Studio professional subscription access levels in Azure DevOps
            Asked 2020-May-09 at 06:21

            Could someone throw some light on the difference between basic and Visual Studio professional subscription access levels in Azure DevOps?

            Microsoft document here provides abstract information regarding the different access levels.

            We have few users who are tagged with basic access level (who also have Visual Studio Professional Subscription) while few other users with Visual Studio professional subscription.

            It is understood from this link that basic access level subscription billed $6 per month, the question that arises now is if azure devops is available for usage without cost if the user has visual studio professional subscription, and do we need to buy basic access level for users who do not have Visual studio professional subscription.



            Answered 2020-May-09 at 06:21

            The difference between basic and Visual Studio professional subscription access levels in Azure DevOps?

            First, assume this professional subscription is available, not expired.

            For active and valid subscription, it has all features of Basic. And also, as a VS Subscriber, you will have a basic license which included in VS subscription. Meanwhile, you can also use a range of features in Azure DevOps that are included with your subscription as a benefit.

            For example, the subscribers have Basic + Test Plans included with their subscription. But for basic user, their Test Plan need be purchased additionally.

            But, if the user don't have valid subscription or expired, at this time, this user will work as Stackholder.

            Do we need to buy basic access level for users who do not have Visual studio professional subscription.

            As I mentioned previously, the Basic feature is included in the Visual Studio Professional Subscription. So, about these users, you don't need worry about their permission, just pay attention for not expired.

            But, for the users who do not have the Visual Studio Professional Subscription, you only have 5 free Basic feature. If these free quotas are used up. You must buy the Basic for them.


            You can see that in the Users tab, and also can get clearly know that who has subscriber level, who just has Basic level and who own Basic + Test Plan:



            Access Azure DevOps analytic data via Power BI using a different PAT
            Asked 2020-Jan-10 at 10:10

            I'm trying to create reporting against work items in Azure DevOps from PowerBI for my entire organization. But I don't have access to all of the projects, so the odata connector returns an error. (per the last statement on

            Can I use a different PAT through Power BI? I don't see a way to do this.

            I tried following the answer from How do you get DimIteration table information from Azure Devops Services into Power BI? with a PAT I was given and a variety of URLS, but did not work.

            And I'm using Power BI (not writing C#, Java, etc.), so I don't see where the Authentication Guide fits into my solution.



            Answered 2020-Jan-10 at 10:10

            Can I use a different PAT through Power BI?

            Do you mean changing authentication credentials? If so you can go through the following steps:

            Click File > Options and Settings > Data Source Settings. Select the correct URL to the OData Feed and click Edit.

            Click the Edit Permissions button under the Credentials setting.

            Edit the credentials as noted above, click Save, then Done, then Close.

            For details ,please refer to this document. If I misunderstood the issue, please indicate.



            How can I call the Wiki REST Api from an Azure DevOps extension?
            Asked 2019-Dec-30 at 03:41

            The Add a dashboard widget tutorial explains how to call the work item REST API using a VSS.require("TFS/WorkItemTracking/RestClient")d rest client.

            I want to do the same, but for the Wiki Rest API. There certainly is a scope for this:

            However, I cannot find the equivalent of "TFS/WorkItemTracking/RestClient" for wiki. Maybe it is as simple as "TFS/Wiki/RestClient", but even if it was, what are the names and parameters of the functions I can use? I don't find that documented anywhere, and I don't want to have to figure that out by trial-and-error, each time publishing a new extension and seeing if it works.

            And looking at REST Clients, there does not even seem to be a Wiki Rest Client.

            So how can I access the Wiki Rest API from an Azure DevOps extension? Is there perhaps an example somewhere, that google has been successful in hiding from me?

            N.B. I do know about the REST API Specs, but the mapping to REST client is not self-evident and apparently.

            I stumbled upon Azure DevOps Web API clients and contracts, however, a brief grep revealed it does not contain the latest and greatest (pre-release) "pagesBatch" feature, and I did not find a relevant branch / tag either.



            Answered 2019-Dec-30 at 03:41

            The wiki rest api documents for azure-devops-extension-api can be found here

            You can also check the restful api for wiki here.

            Check here to discover the client libraries for azure devops service rest api in different coding languages.

            Hope above helps.



            Azure DevOps create build definition via REST API given existing YAML
            Asked 2019-Nov-26 at 21:44

            I have over 100 YAML files within an existing Git repo, each defining their own build pipeline. I am trying to create a PowerShell script to create these build definitions so I don't have to spend hours using the web UI to manually add new build definitions and point to their respective YAML files.

            I've come across similar questions and resources, but haven't been able to get this script to work.

            I know the REST API documentation supports cloning, but does it support creating a build definition that links to a YAML file within the Git repo?



            Answered 2019-Nov-26 at 20:37

            It's failing when you specify process = 0 because process shouldn't be a numeric data type. Process needs to specify a YAML file and a "type" parameter.



            Azure DevOps Server: How to prevent 'Access to path is denied' when initalizing a job?
            Asked 2019-Nov-19 at 19:24

            I am using Azure DevOps Server 2019 (ADOS for short, installed on-premises) to run end to end tests based on Selenium in C#.

            Every now and then a build ends badly without properly stopping the chromedriver.exe process used by my Selenium tests. As a result, the subsequent build fails at the Initialize Job step with an error that looks like this:

            One or more errors occurred. (Access to path 'C:...\chromedriver.exe' is denied.)

            What I understand from this is that because chromedriver.exe is still running ADOS cannot delete its .exe file when it tries to clean the working folder at the start of the build run.

            I've tried disabling the Clean feature of the Get sources step definition but that only shifted the error a bit forward to the Checkout step.

            To resolve the problem I am forced to manually RDP into my agent machine, taskkill /IM chromedriver.exe /F and re-run the failed build.

            My question is - How can I prevent the access denied error? I've thought of these approaches but I'm not sure which is practical:

            1. Get ADOS to run taskkill automatically before the Get sources step. How?

            2. Make the agent have higher privileges so it can delete chromedriver.exe even when its process is still running. Again, how?



            Answered 2019-Nov-14 at 14:06

            If your assumption is correct:

            What I understand from this is that because chromedriver.exe is still running ADOS cannot delete its .exe file when it tries to clean the working folder at the start of the build run.

            Make sure you are using the driver.close() as well as the driver.quit() methods at the end of every test.

            Use teardown to make sure it will always happen.


            As OP commented:

            when I cancel the ADOS build, the test step is terminated abruptly and the teardown step is not executed.

            My recommendation is to an atexit method.

            For C# Use ProcessExit Event (credit to @Fredrik Mörk's answer)

            For Python use atexit


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install devops-service

            You can download it from GitHub.
            You can use devops-service like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the devops-service component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer For Gradle installation, please refer .


            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone open-hand/devops-service

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link