azure-yaml-build | Sample of Azure DevOps Build Pipeline with YAML | DevOps library

by nikolic-bojan C# Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | azure-yaml-build Summary

azure-yaml-build is a C# library typically used in Devops applications. azure-yaml-build has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Sample of Azure DevOps Build Pipeline with YAML

Support

Quality

Security

License

Reuse

Support

azure-yaml-build has a low active ecosystem.

It has 11 star(s) with 3 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

azure-yaml-build has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of azure-yaml-build is current.

Quality

azure-yaml-build has no bugs reported.

Security

azure-yaml-build has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

azure-yaml-build is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

azure-yaml-build releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of azure-yaml-build

Get all kandi verified functions for this library.

azure-yaml-build Key Features

No Key Features are available at this moment for azure-yaml-build.

azure-yaml-build Examples and Code Snippets

No Code Snippets are available at this moment for azure-yaml-build.

Community Discussions

Trending Discussions on Devops

Windows gitlab runner stop execute job

Podman server API version is too old. Client "4.0.0" server "3.4.4"

Oracle docker container not working properly on Mac M1 BigSur

Gitlab pipeline - instead of 1, 2 are running

Azure Linux App Service : Installing packages after deploy from Devops pipeline

$CI_COMMIT_TAG in "if" statemets of regular job

What are the drawbacks to deploying web applications to Tomcat using the filesystem rather than an EAR file?

cypress command returns error in pipeline

Azure DevOps YAML Pipeline Error: While parsing a block mapping did not find expected key

How to commit and push to a private repo(A), from a different repo(B), in github actions workflow (B) , using personal access token

QUESTION

Windows gitlab runner stop execute job

Asked 2022-Mar-22 at 08:28

ci, and i-ve installed my gitlab-runner on a ec2 machine Ubuntu Server 18.04 LTS t2.micro, and when im pushing my code to start the build i get this

But it keeps stucked like this and after 1 hour it timeouts

I really don't know what to do about this problem knowing that i can clone successfully the project manually in my ec2 machine.

Any help is much appreciated if you ever encountered this problem and thanks in advance.

...

ANSWER

Answered 2022-Mar-22 at 08:28

check your job config or your timeout

Source https://stackoverflow.com/questions/71560799

QUESTION

Podman server API version is too old. Client "4.0.0" server "3.4.4"

Asked 2022-Mar-17 at 16:22

I'm trying to use Podman to build an image of a Spring Boot project in IntelliJ. Jetbrain's guide suggests to "Select TCP socket and specify the Podman API service URL in Engine API URL" within Build,Execution,Deployment > Docker (see https://www.jetbrains.com/help/idea/podman.html).

However, when giving the TCP socket found on Podman's documentation (see https://docs.podman.io/en/latest/markdown/podman-system-service.1.html), IntelliJ says it cannot connect.

Finally, when here is the error that appears in terminal:

...

ANSWER

Answered 2022-Mar-17 at 16:22

Facing the same problem due to podman version upgrade.

Seems like a version downgrade would be required to recover the containers, but haven't tried it yet.
This issue points on deleting the machine and creating it again, but the containers would be lost
https://github.com/containers/podman/issues/13510

Source https://stackoverflow.com/questions/71497349

QUESTION

Oracle docker container not working properly on Mac M1 BigSur

Asked 2022-Mar-05 at 20:46

I was recently trying to create a docker container and connect it with my SQLDeveloper but I started facing some strange issues. I downloaded the docker image using below pull request:

...

ANSWER

Answered 2021-Sep-19 at 21:17

There are two issues here:

Oracle Database is not supported on ARM processors, only Intel. See here: https://github.com/oracle/docker-images/issues/1814
Oracle Database Docker images are only supported with Oracle Linux 7 or Red Hat Enterprise Linux 7 as the host OS. See here: https://github.com/oracle/docker-images/tree/main/OracleDatabase/SingleInstance

Oracle Database ... is supported for Oracle Linux 7 and Red Hat Enterprise Linux (RHEL) 7. For more details please see My Oracle Support note: Oracle Support for Database Running on Docker (Doc ID 2216342.1)

The referenced My Oracle Support Doc ID goes on to say that the database binaries in their Docker image are built specifically for Oracle Linux hosts, and will also work on Red Hat. That's it.

Linux being what it is (flexible), lots of people have gotten the images to run on other flavors like Ubuntu with a bit of creativity, but only on x86 processors and even then the results are not guaranteed by Oracle: you won't be able to get support or practical advice when (and it's always when, not if in IT) things don't work as expected. You might not even be able to tell when things aren't working as they should. This is a case where creativity is not particularly rewarded; if you want it to work and get meaningful help, my advice is to use the supported hardware architecture and operating system version. Anything else is a complete gamble.

Source https://stackoverflow.com/questions/69069927

QUESTION

Gitlab pipeline - instead of 1, 2 are running

Asked 2022-Feb-15 at 12:54

I would like to add to Gitlab pipeline a stage which verifies that the person approving the MR is different from the person doing the creation/merge (for this to work, I checked the setting in Gitlab that says: "Pipelines must succeed").

...

ANSWER

Answered 2022-Feb-12 at 00:24

To avoid duplicate pipelines:

Source https://stackoverflow.com/questions/71083133

QUESTION

Azure Linux App Service : Installing packages after deploy from Devops pipeline

Asked 2022-Jan-26 at 16:26

I'm currently setuping a CI/CD pipeline in Azure Devops to deploy a NodeJS app on a linux hosted app service (not a VM).

My build and deploy both go smoothly, BUT I need to make sure some packages are installed in the environment after the app has been deployed.

The issue is: whatever apt-get script I create after the deploy, I have to run then manually for them to actually take effect. In the Pipeline log they seem to have been executed, though.

Here is the part of my yaml code responsible for the deploy, did I miss something?

...

ANSWER

Answered 2022-Jan-26 at 16:26

For now, went with a "startup.sh" file which I run manually after each deploy. Gonna go through docker later though

Source https://stackoverflow.com/questions/70807360

QUESTION

$CI_COMMIT_TAG in "if" statemets of regular job

Asked 2022-Jan-24 at 19:45

I try to make a pretty basic GitLab CI job.
I want:
When I push to develop, gitlab builds docker image with tag "develop"
When I push to main, gitlab checks that current commit has tag, and builds image with it or job is not triggered.

...

ANSWER

Answered 2022-Jan-24 at 19:45

Gitlab CI/CD has multiple 'pipeline sources', and some of the Predefined Variables only exist for certain sources.

For example, if you simply push a new commit to the remote, the value of CI_PIPELINE_SOURCE will be push. For push pipelines, many of the Predefined Variables will not exist, such as CI_COMMIT_TAG, CI_MERGE_REQUEST_SOURCE_BRANCH_NAME, CI_EXTERNAL_PULL_REQUEST_SOURCE_BRANCH_NAME, etc.

However if you create a Git Tag either in the GitLab UI or from a git push --tags command, it will create a Tag pipeline, and variables like CI_COMMIT_TAG will exist, but CI_COMMIT_BRANCH will not.

One variable that will always be present regardless what triggered the pipeline is CI_COMMIT_REF_NAME. For Push sources where the commit is tied to a branch, this variable will hold the branch name. If the commit isn't tied to a branch (ie, there was once a branch for that commit but now it's been deleted) it will hold the full commit SHA. Or, if the pipeline is for a tag, it will hold the tag name.

For more information, read through the different Pipeline Sources (in the description of the CI_PIPELINE_SOURCE variable) and the other variables in the docs linked above.

What I would do is move this check to the script section so we can make it more complex for our benefit, and either immediately exit 0 so that the job doesn't run and it doesn't fail, or run the rest of the script.

Source https://stackoverflow.com/questions/69199614

QUESTION

What are the drawbacks to deploying web applications to Tomcat using the filesystem rather than an EAR file?

Asked 2022-Jan-04 at 12:28

Since Tomcat just unzips the ~~EAR~~ WAR to the filesystem to serve the app, what is the benefit of using an ~~EAR~~ WAR and what are the drawbacks to just pushing a filesystem to the Tomcat webapps filesystem?

...

ANSWER

Answered 2021-Dec-25 at 11:32

Tomcat supports WAR but not EAR. Anyways , I think your question is about why we normally deploy the application that is packaged as a single WAR rather than the exploded WAR (i.e exploded deployment).

The main advantages for me are :

It is more easy to handle the deployment when you just need to deploy one file versus deploying many files in the exploded WAR deployment.
Because there is only one file get deployed , we can always make sure the application is running in a particular version. If we allow to deploy individual files and someone just update several files to other version , it is difficult to tell what is the exact version that the application is running.

There are already some discussion about such topics before , you can refer this and this for more information.

Source https://stackoverflow.com/questions/70438632

QUESTION

cypress command returns error in pipeline

Asked 2021-Dec-30 at 16:53

I have a CI setup using github Action/workflow to run cypress automated test everytime when a merge is done on the repo. The installation steps works fine however i run into issue when executing cypress command, let me show you the code.

CI pipeline in .github/workflows

...

ANSWER

Answered 2021-Dec-30 at 16:53

After searching for some time turns out i was using cypress 8.7.0 which was causing the issue, i downgraded to cypress 8.5.0 and it started working, hope that helps anyone else having this issue

Source https://stackoverflow.com/questions/70518148

QUESTION

Azure DevOps YAML Pipeline Error: While parsing a block mapping did not find expected key

Asked 2021-Dec-07 at 10:42

I just created a pipeline using the YAML file and I am always getting the error "/_Azure-Pipelines/templates/webpart.yml: (Line: 41, Col: 27, Idx: 1058) - (Line: 41, Col: 60, Idx: 1091): While parsing a block mapping, did not find expected key.". I already verified the indentation of my YAML file and that looks fine.

Below is my YAML file.

...

ANSWER

Answered 2021-Dec-07 at 10:42

It was due to a missing quotation mark in the task PublishBuildArtifacts@1 for the PathtoPublish. I found this error by using a YAML extension provided by RedHat.

Once you enabled that extension and set the formatted for YAML (SHIFT + ALT + F), it should show you the errors in your YAML file.

Source https://stackoverflow.com/questions/70258702

QUESTION

How to commit and push to a private repo(A), from a different repo(B), in github actions workflow (B) , using personal access token

Asked 2021-Dec-05 at 10:05

name: deploy-me
on: [push]
jobs:
  deploys-me:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-node@v2
        with:
          node-version: '14'
      - run: npm install
      - run: npm run dev

     //Next  I want to copy some file from this repo and commit to a different repo and push it

...

ANSWER

Answered 2021-Dec-05 at 09:57

name: deploy-me
'on':
    - push
jobs:
    deploy-me:
        runs-on: ubuntu-latest
        steps:
            - uses: actions/checkout@v2
            - uses: actions/setup-node@v2
              with:
                  node-version: '14'
              env:
                  ACCESS_TOKEN: '${{ secrets.ACCESS_TOKEN }}'
            - run: npm install
            - run: npm run build
            - run: |
                  cd lib
                  git config --global user.email "xxx@gmail.com"
                  git config --global user.name "spark"
                  git config --global credential.helper cache
                  git clone https://${{secrets.ACCESS_TOKEN}}@github.com/sparkdevv/xxxxxx
                  cp index.js clonedFolder/ -f
                  cd clonedFolder
                  git add .
                  git commit -m "$(date)"
                  git push

Source https://stackoverflow.com/questions/70225077

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

Vulnerabilities

No vulnerabilities reported

Install azure-yaml-build

Everything is now in the same repository. Also, all Services are in their new folders. Now we come to the problem - we need to change our build definition, depending on how it was made, of course.
Allowed trigger only on master and only for a folder where Service is. I just wanted to see builds work with the New Repository.
Change all the steps/variables that point to *.sln or *.csproj files to follow new folder structure in order to build just what you want, not the whole darn thing.
Try the build. Build Service, push it on some lower environment and hit it with regression tests. All needs to be in perfect order.
Now you can migrate next Service.
I wasn't very happy with having build triggers only on master. I could have put triggers on all branches, but I wanted more control. What if I wanted to build 2 or 3 Services when code in one changes (remember those Model projects?). I know, that is not clean separation, but after all, the point of having things in one repository is because they are - connected. I wasn't keen on maintaining 20+ builds also. I wanted control in one place.
OK, last piece of the puzzle - Build template. I grabbed it by clicking on View YAML button of my existing build pipeline. Then I had to adjust it a bit. Here is how the first part of it looks (I just kept the Restore task for sample):. Parameters are input parameters for the template. You remember we used name and solutionFolder?. Variables are for the Job and we read some of the input parameters in order to set them up. Important here is myBuildQueue that contains entire list of all Services that should be built. Even more important is the condition that checks if this entire Job should be executed. It checks if solutionFolder is in that semi-colon separated list that was populated in that crazy PowerShell script. If it matches - Tasks in this Job will be ran. If not, it will just skip this entire Job. In the PowerShell script, you can define that Services have dependencies, so you can say that if there is a change in Service 3, you should also build Service 2. That is what I did for Service 3 in this part of the script. That is it! You can setup some interesting rules within the scripts in order to define what should be built on which change.
Remember when I mentioned buildQueueInit and you setup a Variable. Here are the steps to do it in Azure DevOps:. Now, when you manually queue a build, you can add a value in it, e.g. service1;service2; and Service 1 and 2 will be built for you. One scenario where you do want this is maybe for some Release branches, where you do not want stuff to be auto-triggered based on just last commit. You want to decide "those Services will be released after this Sprint".
Go to your Pipeline -> Builds and select your YAML build
Click to Edit build and you will see a button Variables
Click on it and then to + to create new one
Set it's name to buildQueueInit and check Let users override this value when running this pipeline box

Support

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: